On Sun, 10 Nov 2013 09:02:10 -0600, John McDowell wrote:
>
>>=== really difficult === parallel job steps. JCL runs each STEP in the
>>order it exists in the JCL, perhaps bypassing some steps based on return
>>codes. How about
>>
>>// PARALLEL
>>// ENDPARALLEL
>>
Ouch! DDNAME collisions. Everyone wants to use SYSPRINT. I think
back on my suggestion earlier than this thread for mapping to virtual
DDNAMEs. Ugly; you want separate name spaces for DDNAMEs;
shared for DSNAME ENQueues.
If it could be done, I'd borrow a notion from POSIX shell: any EXEC
statement containing the keyword PARALLEL causes a parallel
ATTACH. The task runs in parallel until a subseqent step WAITs
for it by mentioning its completion status:
//FOO EXEC PGM=WOMBAT,PARALLEL
... runs in parallel until:
//BAR EXEC PGM=FRED,COND=(0,GT,FOO)
(Like "&" in sh). Doesn't JES3 already provide a similar facility?
On restarting: My favorite restartable program is "make". Make
can be interrupted at any point. When I reissue the command,
it takes up where it left off; I don't even need to tell it where to
start, assuming my description file is written correctly (I sometimes
fail at this.) If I have a need to rebuild a particular target, I simply
delete that target and run make again.
-- gil
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
