DSXchange

I have a job sequence that has two 'wait for file' stages. The triggers from the 'wait for file' stages are set to OK.

For some odd reason, the job sequence does not issue the two wait for files immediately. Only one wait for file is issued. When that file arrives, the next wait for file is issued. In this particular case, the one file is already there but not processing is done because the sequence is waiting for non-existant file.

Has anyone come accross this situation before? If so, how did you get around it?
(I would prefer not to write a Unix script or split the job sequence into several sequences).

Describe the design of the Sequence job.

Look at the generated OSH. Unfortunately this IS how it works. Once first wait starts waiting, nothing happens till it returns. You'd have to "roll-your-own" to implement simultaneous waiting. This would not be difficult in a before-job subroutine or in a routine called from a Routine activity. The default is a "sleep wait".

Ah... that would be true, waiting is waiting is a singleton process.

Wasn't aware a Sequence job generated OSH, however.

Look at the generated Job Control code

If you do change the code in the job control and someone else makes a change to the job at a later stage, will the job control be recreated i.e. will my "roll your own" change be overwritten?

(The problem with editing the code is that the next person doing maitenance on the job will not read the documentation about the code being changed. His changes will generate new code and ooops not more "roll your own").

BIuser wrote:If you do change the code in the job control and someone else makes a change to the job at a later stage, will the job control be recreated i.e. will my "roll your own" change be overwritten?

Of course. No-one suggested changing the generated code, merely that it be examined to help explain the issue. That and to perhaps provide a basis for some custom code executed elsewhere, hence the mention of a before-job subroutine.