SMPE error GIM38201E ** THERE IS A MODID ERROR FOR SRC ENTRY xxxxxxxx IN SYSMOD yyyyyyy

Products

• JCLCheck Workload Automation

Issue/Introduction

When applying CA JCLCheck maintenance, why do I get the following SMP/E errors? 

GIM38201E ** THERE IS A MODID ERROR FOR SRC ENTRY xxxxxxxx IN SYSMOD yyyyyyy

GIM31902I SYSMOD yyyyyyyy DOES NOT SPECIFY MZ2nnnn ON THE PRE OR SUP OPERAND. MZ2nnnn IS A UMID FOR SRC xxxxxxxx THAT IS 

 CURRENTLY INSTALLED. 

  (xxxxxxxx represents the JCLCheck module name, yyyyyyy represents the PTF number. and  MZ2nnnn is a usermod number) 

Environment

Release:
Component: CM-Z2

Cause

With SMP/E, whenever you have a custom USERMOD applied, it needs to be SMP/E RESTOREd and REJECTed before applying product maintenance.

Note that usermods should never be ACCEPTed. Look for the informational message similar to the one below to identify the usermod.    

GIM31901I  SYSMOD yyyyyyy DOES NOT SPECIFY MZ2nnnn ON THE PRE OR SUP OPERAND.  MZ2nnnn IS A UMID FOR SRC xxxxxxxx THAT IS CURRENTLY INSTALLED.

(Note: JCLCheck name begins with MZ1 or  MZ2.)

Resolution

 To resolve the SMPE error:

1. ACCEPT all published fixes.  Note: Usermod and test fixes (APAR) must never be acccepted.
2. RESTORE the usermod.   
   Example: SET BDY(CAIT0)
                  RESTORE S(MZ2C023)
3. APPLY the product maintenance.
4. Run an APPLY CHECK for the USERMOD to identify MODID errors, these will need to be added to the PRE of the USERMOD.
5. REJECT the USERMOD 
6. Add the PTFs identified in the APPLY CHECK above to the PRE of the USERMOD
7. RECEIVE the USERMOD.
8. APPLY the USERMOD.

Additional Information

As always, please contact CA Technologies support for CA JCLCheck if you have further questions.