Circumstances f$context will not find an existing process

[SDIH1]

The check on all nodes is intentional.

The fear of checking the wrong process is definitely real on a lot of systems, but on this system there are about 3 users that have access to the command prompt, who are usually sitting within arm's length and have to pay
a lot of snacks if they mess up process names.

[SDIH1]

Hi,

I'm closing this thread, to summarize:

The problem was that after a submit a job took 22 seconds to actually start, causing the submitting batch job to fail.

I was pointed out that this shouldn't be so much of a problem if different tools were used, or a different approach altogether and some of the tips were interesting and valuable, thanks.

Although 22 seconds is ridiculous in my view, the underlying problem is that process creation is asynchronous, and any tool that controls and monitors processes and doesn't take this in to account will fail one day.

DCL would have to change beyond recognition to be able to accomplish this easily, and writing DCL that tries to do this is difficult and error prone.