Deafult Step exection priority in the JOB

sarathbabum · New User Joined: 15 Mar 2007 Posts: 12 Location: Kerala

in a job i have 3 step s1, s2, s3 respectievely. these 3 steps are simple Cobol pgm for display some msg. i didnt specify any priority for these three. which step will execute first

expat · Posted: Tue Mar 20, 2007 6:11 pm

Why not set up the required JCL and test it many times and see what happens.

guptae · Posted: Tue Mar 20, 2007 6:11 pm

Hi Sharath,

It will execut in the order in which it specify in the jcl
So
s1
s2
s3

sarathbabum · New User Joined: 15 Mar 2007 Posts: 12 Location: Kerala

Mam,

it was not like that.... when i submit my pgm it show as s2, s3, s1

expat · Posted: Tue Mar 20, 2007 6:33 pm

Please post your JCL and job output.

sarathbabum · New User Joined: 15 Mar 2007 Posts: 12 Location: Kerala

sarathbabum · New User Joined: 15 Mar 2007 Posts: 12 Location: Kerala

HI,

i submit step in the order s1, s2, s3 but i got o/p as s3 s1 s2

expat · Posted: Tue Mar 20, 2007 6:54 pm

If you look at JESMSGLG it will show you in which order the steps processed.

kanchan kumar · New User Joined: 03 Feb 2007 Posts: 1 Location: delhi

if u would have used dprty then it would have given u priority acc to dprty parameter otherwise now it will certenly give u o/p in the sequence u have submitted ur job.
kanchan

dick scherrer · Posted: Wed Mar 21, 2007 12:31 am

Hello,

Please notice that the output is in DSID sequence. This has nothing to do with execution order. The steps were executed in the order submitted (s1, s2, s3).

The reason for the "out of sequence" DSIDs is that there is only one "//SYSOUT DD SYSOUT=*" statement - on the last step. JES assigned the DSID to the DD that was coded. When the other steps ran and a SYSOUT was generated dynamically, they were assigned the next DSID. If you use a "//SYSOUT DD SYSOUT=*" for each step, the output queue will be as you want/expect.

sarathbabum · New User Joined: 15 Mar 2007 Posts: 12 Location: Kerala

SIR,

will u please explain the purpose of DSID

dick scherrer · Posted: Wed Mar 21, 2007 7:25 pm

Hello,

DSID is how JES keeps track of all of the JES datasets created by a job. It is internally generated. As JES "sees" SYSOUT datasets, it assigns a DSID starting at 101.

When the SYSOUT is created at program execution time (rather than when JES first sees the JCL), the "next" DSID is assigned which can cause the output datasets to be "out of sequence" by execution order.

The best plan is to include the DD statements for every SYSOUT. It doesn't cost much in terms of overhead and makes looking at queued output much easier if the outputs are in the order they were created rather than the order that JES became aware of them.