🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.lang.asm370
Article #793

MVS JCL

#793
From: SOMITCW
Date: Thu, 16 May 1991 15:04
45 lines
2651 bytes
 On Wed, 15 May 91, hsi!hsi86!siperas@UUNET.UU.NET said;
>a related question to assembler 370. Is there anyway to program a
>mutiple step jcl job to be interactive as it is runs or at the
>beginning of the job determine what steps to run.
>I don't want to have to actually modify the jcl all the time.
>I know that I could bundle the jcl in rexx to do this but was
>looking to see if the jcl could handle the task itself incase
>rexx is not being used.

    I have seen such an animal at one time.  The first step would
 read a control file and set a conditional code of what was in the
 control file, 0 through 40.  The end of the second step would
 write 2 in the control file, the end of the third step would write
 3, the end of the last step would write 0 in the control file.
 An abend in any step would cause the first step to set a condition
 code that would bypass all steps until the correct one to restart.

    Other application systems there used JCL job locks.
 JCL job locks are much easier to code and control, all is done in
 normal JCL, and there is less chance of a bad restart.
 JCL job locks can insure proper restores are done before a restart.

 A simplified Example:
    //JOB1 JOB JOB,JOB,CLASS=P
    //PGM1 EXEC PGM=PGM1
    //LOCK DD  DSN=LOCK.JOB1,DISP=(,CATLG,DELETE),
    //         SPACE=(TRK,0),VOL=REF=CONTROL
    //JOB2 JOB JOB,JOB,CLASS=P
    //PGM2 EXEC PGM=PGM2
    //LOCK DD  DSN=LOCK.JOB1,DISP=(SHR,DELETE,KEEP)
    //LOCK DD  DSN=LOCK.JOB2,DISP=(,CATLG,DELETE),
    //         SPACE=(TRK,0),VOL=REF=CONTROL
    //JOB3 JOB JOB,JOB,CLASS=P
    //PGM3 EXEC PGM=PGM3
    //LOCK DD  DSN=LOCK.JOB2,DISP=(SHR,DELETE,KEEP)
    //LOCK DD  DSN=LOCK.JOB3,
    //         SPACE=(TRK,0),VOL=REF=CONTROL

    Note: Any abend would cause the remaining jobs to JCL error out.
          A resubmit of the job stream would cause all jobs up to
          the abend to JCL error out.
          The job that had abended would be the one to restart.
          If the job ran correctly, then the remain jobs would start.
          Jobs in the stream could switch between CPU's with shared disk.
Technical Details
Message-ID: <9105161443.AA23368@ucbvax.Berkeley.EDU>
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!rpi!crdgw1!uakari.primate.wisc.edu!sdd.hp.com!swrinde!ucsd!ucbvax!VCCSCENT.BITNET!SOMITCW

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!rpi!crdgw1!uakari.primate.wisc.edu!sdd.hp.com!swrinde!ucsd!ucbvax!VCCSCENT.BITNET!SOMITCW
From: SOMITCW@VCCSCENT.BITNET
Newsgroups: comp.lang.asm370
Subject: MVS JCL
Message-ID: <9105161443.AA23368@ucbvax.Berkeley.EDU>
Date: 16 May 91 15:04:34 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: IBM 370 Assembly Programming Discussion List
              <ASM370@OHSTVMA.BITNET>
Distribution: inet
Organization: The Internet
Lines: 45