How to determine and verify that a JCLCheck usermod has been applied
search cancel

How to determine and verify that a JCLCheck usermod has been applied

book

Article ID: 134800

calendar_today

Updated On:

Products

JCLCheck Workload Automation

Issue/Introduction

JCLCheck provides user-modifiable tables in the CAZ2CJCL library.  Those tables are documented here:

(Optional) Install JCLCheck Tables for Modification

 

This Knowledge Base article describes how to identify that a usermod has been installed, and how to verify that the correct usermod is invoked when JCLCheck runs.

Environment

Release : 12.0

Component : JCLCheck workload Automation

Resolution

Steps taken to determine which JCLCheck usermods have been applied, and whether the usermod is actually being invoked when JCLCheck runs: 

1. Run a SMP/E report against the JCLCheck CSI Target zone using the following sample control statements: 

    SET BDY(CAIT0). 

    LIST  USERMODS FORFMID(CAZ1C00 CAZ2C00) .          

 

2. Look for usermod name in the SMPLIST report.

    Sample display:

  NAME                                       

MZ2C023   TYPE            = USERMOD          

          STATUS                  = REC  APP         

          FMID                       = CAZ2C00          

          REWORK                = 20190621         

          DATE/TIME REC   = 19.172  12:26:55 

                                INS    = 19.172  12:28:10 

          PRE    VER(001)    = SO04619          

          ASSEM                   = JCLMSG           

          SRCUPD                 = JCLMSG           

 

Explanation:  JCLCheck usermod MZ2C023 is applied on June 21st, 2019 at 12:28.10 to module JCLMSG.

 

3.  Execute command "TSO ISRDDN" from any TSO/ISPF command line to display current data set allocations.  

 

4. Execute  command "LOAD CAZ2CJCL" from the command line on the "Current Data Set Allocations" panel to display the module. 

 

5. Confirm that the module is from the correct loadlib, and hit enter to display the module content. 

 

6. Find the module containing the usermod (example: FIND JCLMSG), and do repeat find to locate the module header. 

 

7. Compare the module's assembly date/time stamp to the one found in the SMPLIST report.

Example:  

JCLMSG2  CAZ2C00  ~RMID(SO04619)~ 20190621 12.28