JES2_UPGRADE_CKPT_LEVEL_JES2
- Description:
- This check determines if the system is ready to upgrade the JES2 checkpoint to z22 mode. If the necessary preconditions are already satisfied on the customer’s system, then a message is given recommending that the system be upgraded to z22 mode. In the case where prerequisite conditions have not been satisfied, an exception message is given indicating that the system is not ready to upgrade to checkpoint level z22.
- Reason for check:
- IBM® suggests that installations
use JES2 z22 mode because it upgrades the JES2 checkpoint and enables
the following functions:
- Job execution controls via the JOBGROUP JCL statement.
- A new method to reconfigure where the JES2 checkpoint data sets reside.
- The ability to resize a JES2 checkpoint data set (within the limits of the device the data set resides on).
- Increased limits for JQEs, JOEs and BERTs. New limits are as follows:
- JQEs = 1,000,000
- JOEs = 2,500,000
- BERTs = 2,500,000
- z/OS® releases the check applies to:
- z/OS V2R2 and later.
- Parameters accepted:
- No
- User override of IBM values:
- The following sample shows the defaults for customizable
values for this check. Use this sample to make permanent check
customizations in an HZSPRMxx parmlib member used at
IBM Health Checker for z/OS startup. If you just want a one-time
only update to the check defaults, omit the first line (ADDREPLACE POLICY)
and use the UPDATE statement on a MODIFY hzsproc command.
Note that using non-POLICY UPDATEs in HZSPRMxx can
lead to unexpected results and is therefore not recommended.ADDREPLACE POLICY[(policyname)] [STATEMENT(name)]
UPDATE
CHECK(IBMJES2,JES2_UPGRADE_CKPT_LEVEL_JES2)
SEVERITY(LOW) INTERVAL(168:00) DATE('date_of_the_change')
REASON('Your reason for making the update.')
- Debug support:
- No.
- Verbose support:
- No.
- Reference:
- For more information, see:
- Messages:
- This check issues the following exception messages:
- HASPH022E
- HASPH028E
- SECLABEL recommended for MLS users:
- SYSLOW