Testing SMS Migration

[Patrick Cribbs]

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).

[Quynh Pham]

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.
[e-mail]
Technical Support Engineer

[Patrick Cribbs]

How do run JCLCheck in batch with the PDS option to scan an entire PDS?  

[Patrick Cribbs]

Also where is the documentation for the run time options for running JCLCheck in batch.   Is there anyway to limited the output to any essential errors?

[Quynh Pham]

JCLCheck technical documentation is found here:
https://techdocs.broadcom.com/us/en/ca-mainframe-software/automation/ca-jclcheck-workload-automation/12-0.html

Runtime options are documented in the Reference guide: 
https://techdocs.broadcom.com/us/en/ca-mainframe-software/automation/ca-jclcheck-workload-automation/12-0/reference/jclcheck-runtime-options/description-of-runtime-options.html

The SEV runtime option limits the output to essential errors.
Example: SEV(8) means that only errors will be written to SYSPRINT.  Informational and Warnings are written to SYSPRINT.

[Quynh Pham]

You may use the sample JCLCheck batch job named AZ1JCHK in the CAZ2JCL library.

Example:
// JOB statement
// JCLLIB ORDER=hlq.jclcheck.CAZ2PROC
//Z1EXJCHK EXEC CAZ1JCHK,
//                   CAILOAD='hlq.jclcheck.CAZ2LOAD',
//                   OPTION='O(OPTS)'
//OPTS DD *  
 PDS  
/*
//SYSIN DD DISP=SHR,DSN=your.pds.jcllib 
/*