Skip to main contentIBM ZLPN Documentation

Customizing the JES2 parameters

This information is intended to describe an approach to implementing changes in the JES2 initialization parameters. There are other ways to achieve the same results.

  1. Logon to TSO with a user ID which has authority to make changes to VENDOR.PROCLIB and VENDOR.PARMLIB. You also need to be able to issue MVS Operator commands from SDSF or from the VM user ID which controls the guest z/OS system.

  2. Look in VENDOR.PROCLIB. If it contains a member called JES2, then these suggestions may not work. Contact the IBM Innovation Center, Dallas if you need assistance.

  3. Look in VENDOR.PARMLIB. If it contains a member called COMMNDJ2, then these suggestions may not work. Contact the IBM Innovation Center, Dallas if you need assistance.

  4. Copy LVL0.PARMLIB(JES2420A) to VENDOR.PARMLIB using a new name. For example, copy LVL0.PARMLIB(JES2420A) to VENDOR.PARMLIB(JES2V01).

  5. Update VENDOR.PARMLIB(JES2V01) with your changes to the JES2 initialization parameters. Do NOT log off your TSO session.

  6. Test the changes in VENDOR.PARMLIB(JES2V01). Go to SDSF or the z/VM ID which is controlling the guest z/OS system and abend JES2 with the $PJES2, ABEND command. (Do not use the FORCE parameter). In most cases JES2 will ABEND as planned. You may need to respond to a prompt. Watch the SYSLOG messages.

  7. Hot start JES2 with the command:

    S JES2,HASPARM=VENDPARM,VENDMEM=JES2V01

  8. In the event there is a problem with the Hot start, tell JES2 to terminate. Fix the problem from your TSO session in VENDOR.PARMLIB(JES2V01). Try the Hot start again. A successful JES2 restart confirms that JES2 will not fail to initialize at the next IPL.

  9. To make JES2 start using the parameters in VENDOR.PARMLIB(JES2V01) at every IPL, copy LVL0.PARMLIB(COMMNDJ2) to VENDOR.PARMLIB(COMMNDJ2).

  10. Update VENDOR.PARMLIB(COMMNDJ2) so it says: COM='S JES2,HASPARM=VENDPARM,VENDMEM=JES2V01'