JES3_DATASET_INTEGRITY

Description:

This check determines if DSI or NODSI has been specified on the JES3 entries in the Program Properties Table (PPT). Specifying DSI enables Data Set Integrity for JES3 data sets allocated via DYNALLOC statements. The check generates an exception message when the current DSI setting does not match the specified setting.

Reason for check:

JES3 uses the DSI PPT specification from the SCHEDxx member of SYS1.PARMLIB. IBM recommends that you use DSI so there is an ENQUEUE outstanding on all its data sets (major name=SYSDSN, minor name=dsname) while JES3 is up and running.

JES3 does not hold any data set ENQUEUE when NODSI is specified which allows other jobs or address spaces to access JES3 data sets. Updating JES3 data sets without using DSI can cause great damage with the ultimate result being a cold start.

z/OS® releases the check applies to:

z/OS V2R2 and later.

Type of check (local, remote, or REXX):

Local

Parameters accepted:

Yes, the following parameters are accepted:

PARM('DSI(YES)'), which is the default, indicates the check should expect JES3 data set integrity to be enabled with DSI in the PPT.
PARM('DSI(NO)'), indicates the check should expect JES3 data set integrity to be disabled with NODSI in the PPT.

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. End of change

ADDREPLACE POLICY[(policyname)] [STATEMENT(name)]
UPDATE
CHECK(IBMJES3,JES3_DATASET_INTEGRITY),
SEVERITY(LOW),
INTERVAL(ONETIME),
PARM('DSI(YES)')
DATE(’date_of_the_change’),
REASON(’your update reason’)

Debug support:

No.

Verbose support:

No.

Reference:

For more information, see:

Messages:

This check issues the following exception messages:

IATH003E

See the IATH messages in z/OS JES3 Messages.

SECLABEL recommended for MLS users:

SYSLOW - see z/OS Planning for Multilevel Security and the Common Criteria for information on using SECLABELs.