<[email protected]> wrote in message news:<[email protected]>... > Is there any methods for submitting all the members in a pds in order and do return code checking at the job level so that job b is depends on joba rc=0 etc
--- You'd get better response if you submitted to the mailing list rather than posting to the newsgroup. Fortunately some of us read from the newsgroup which contains both. Here's a challenge to yourself or anyone interested in playing for a few hours. I'm busy this weekend otherwise I'd give it a try. Create a procedure "SUBNEXT" where you pass it a PDS/PDSE library name and the current member. Write it in whatever language you are most comfortable. A CLIST or REXX could be used as the PROC could contain "//substep EXEC PGM=IKJEFT1A,PARM='%SUBNEXT &dsname &member'". The SUBNEXT program would allocate the library, create a member list, find the current member and check if another member follows, if so submit that member. The routine could dynamically allocate the INTRDR and using an ACB/RPL submit via PUT the JCL onto the internal reader and at the END of that input member add ... "//LASTSTEP EXEC SUBNEXT,DSNAME=dsname,MEMBER=mem,COND=(0,NE)". When using an ACB/RPL to write to the internal reader after you issue ENDREQ the RPLRBAR field will contain the 8 character job id, which can be used in any messages if you wish. It would be nice to have another step following the "SUBNEXT" step that issues a write to operator if SUBNEXT was NOT executed. I guess that could be up to the user if they wanted that functionality. SUBNEXT would NOT be a mass submission of the PDS/PDSE but rather sequential submission of the members within that library. By using COND= submission would STOP whenever a job does NOT work as expected (in this example the job does not end with a return code of zero. If nobody attempts this in the next few days, I'll give it a shot. I could find this useful for submitting a TEST job streams. Please post to the LIST if you give it a shot and successfully complete this tool. I would like a copy. Thanks, DanD ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
