IBM Z and LinuxONE IBM Z

IBM Z

The enterprise platform for mission-critical applications brings next-level data privacy, security, and resiliency to your hybrid multicloud.

 View Only

  • 1.  JES2 related questions

    Posted 30 days ago
    1. 1 Is there a global and local  for JES2 similar to JES3 ?
    2. 2.Can we stop/start JES2 while other tasks are running ?

    a.      What will happen to the job numbers, does it keep track of the ones that are already running ?

    b.     What happens when JES2 runs out of job numbers ?



    ------------------------------
    Puru Srinivasan DataPower Support
    Systems Engineer
    ANZ Bank
    ------------------------------


  • 2.  RE: JES2 related questions

    Posted 29 days ago

    In JES2 there is no equivalent to JES3 local/global. 

    You can stop JES2 while the system is running, using a $PJES2,ABEND command.It will not affect active address spaces, but you can't introduce any new JES2 work until you restart JES2. 

    But why would you? 

    If you restart JES2, it will continue using the numbers it was using before you brought it down. 

    As you approach the maximum number of jobs(JNUM parameter) you will get $HASP050 warning messages. When you hit 100%, JES2 will not introduce anymore more work.  



    ------------------------------
    Mike Shorkend
    IBM Z platform specialist
    Shorkend
    Shoham
    ------------------------------

    Original Message


  • 3.  RE: JES2 related questions

    Posted 26 days ago

    Please note, as the JES2 job numbers go from 5 digits to 7 digits, the JES2 message prefix changes from JOBxxxxx to Jxxxxxx.  You will need to update any system automation which keys off the JES2 message numbers.



    ------------------------------
    Jerry Edgington
    ------------------------------

    Original Message


  • 4.  RE: JES2 related questions

    Posted 29 days ago

    1) No. JES3 had a single global controlling multiple locals. JES2 doesn't use that model. Instead, it uses a MAS (Multi-Access Spool) of peer "members" that share SPOOL and a checkpoint; control is distributed and serialized via the checkpoint lock (on DASD or a coupling facility). There's no separate "global."

    2) Yes. Operators routinely quiesce/drain and stop JES2, then restart it. Use $P JES2 to withdraw/stop it cleanly; initiators/printers/etc. stop taking new work and finish what they're doing, then go inactive. After you restart ($S JES2), processing resumes. Already-executing jobs either finish during the quiesce/drain or (if you force/terminate) you'll need normal recovery

    A) JES2 keeps track of job identifiers and queues via the checkpoint; warm/warmish restarts rebuild state so in-flight/queued work is known

    B) JES2 job numbers are internal identifiers; you can reset the base with $T NUM,BASE=nnnnn (range 1–999999). JES2 assigns the next available number and won't reuse a number that's still present on the queues; when numbers cycle, reuse is only after the old job is gone. Separately, you can raise the maximum jobs on the queue with $T JOBDEF,JOBNUM

    I hope this has helped.



    ------------------------------
    Matheus Porsch
    Systems Administration - Kyndryl
    Brazil
    ------------------------------

    Original Message


  • 5.  RE: JES2 related questions

    Posted 24 days ago

    I'd like to add something for clarity.

    The numbers of the JOBID (xxxnnnnn or ynnnnnnn, where nnnnn is a zero-filled number, xxx is one of JOB, STC, TSU, or GRP, y is one of J, S, T, or G) roll over when it hits the maximum (99999 or 9999999). For example, with a seven-digit format JOBID, the job entering the system after J9999999 is J0000001. There is never a job number 0. (JES3 has a job 0, but it's a special use case.)

    The format of the JOBID is based on the JES2PARM JOBDEF statement RANGE second parameter. When the upper value is 100000 or higher, JES2 uses the 7 digit version. 

    The number of jobs in the system is controlled by the JOBDEF JOBNUM parameter.



    ------------------------------
    Ray Mullins
    Sr. Software Developer
    Broadcom Mainframe Software Division
    Roseville
    United States
    +19164123982
    ------------------------------

    Original Message


  • 6.  RE: JES2 related questions

    Posted 22 days ago

    Regarding "Can we stop/start JES2 while other tasks are running?"

    If you want to stop JES2 for testing a new release or testing installation-written exit routines or isolation to prevents potential disruption to the primary JES2 and base control program necessary for normal installation production work. You can run multiple JES2 on the same z/OS occurrence. It is known as running multiple copies of JES2 (poly-JES). Check the doc, for 3.1 https://www.ibm.com/docs/en/zos/3.1.0?topic=configurations-running-multiple-copies-jes2-poly-jes.

    Hope this help,



    ------------------------------
    Gilles Robert
    ------------------------------

    Original Message


  • 7.  RE: JES2 related questions

    Posted 22 days ago

    Regarding "Can we stop/start JES2 while other tasks are running?". If you want to stop/restart JES for testing purposes (exits for examples), it is possible for you to run multiple copies of JES2 on the same z/OS occurrence. This is known as Running multiple copies of JES2 (poly-JES), for 3.1 checks https://www.ibm.com/docs/en/zos/3.1.0?topic=configurations-running-multiple-copies-jes2-poly-jescheck.



    ------------------------------
    Gilles Robert
    Software Consultant
    BMC Software Inc.
    QC
    ------------------------------

    Original Message


  • 8.  RE: JES2 related questions

    Posted 21 days ago
    Thank you for your updates sir

    Yahoo Mail: Search, organise, conquer


    Original Message


Related Content