JCLCheck performs JCL checking according to SMS rules if SMS is active on the system where JCLCheck runs.
To ensure that JCLCheck uses SMS, run a JCLCheck job and look in the SYSPRINT for the following:
- ENVIRONMENT ARRAY:
SHAT00000000000000000
Explanation: S represents SMS; H is HCD, A is APF-authorization, T is Top-Secret (or A for ACF2 and R for RACF)
- OPTIONS IN EFFECT: make sure that option '
NOSMS' is
not present
To scan the entire PDS, use runtime option PDS.
Thanks.
Kiki.pham@broadcom.comTechnical Support Engineer
Original Message:
Sent: 09-30-2020 05:07 PM
From: Patrick Cribbs
Subject: Testing SMS Migration
Does anyone have any suggestions or recommendations for checking the JCL within a PDS for any JCL problems related to using SMS? I am doing a DASD migration to SMS managed datasets, I would like to use JCLCHECK to scan the members for any potential errors particular to SMS datasets. I would like to scan the entire PDS and search for SMS related errors.
For example, one form of JCL usage is known to not work with SMS owned datasets:
//STEP1 EXEC PGM=........
//INPUT DD DSN=LOGONID.FILE1,DISP=(OLD,DELETE,KEEP)
//OUTPUT DD DSN=LOGONID.FILE1,DISP=(NEW,CATLG,DELETE),
// UNIT=SYSDA,SPACE=(TRK,1)
In this example, the same dsname is being used for input and output (deleting the
original and cataloging a new file).