SMP/E Apply check for Intertest CICS CARS package fails with GIM65902E MODULE IS NOT IN THE SMPPTS.

Products

• InterTest - CICS

Issue/Introduction

SMP/E Apply check of the latest Intertest CICS CARS maintenance package fails with error message

GIM65902E ** MODULE CAMRUADD IS NEEDED TO BUILD THE FOLLOWING LOAD MODULES FOR SYSMOD LU06403 BUT CAN NOT BE USED. ITS       
                       DISTRIBUTION ZONE RMID CAMRB00 IS DIFFERENT FROM THE TARGET ZONE RMID LU02903, AND SYSMOD LU02903 WHICH         
                       LAST REPLACED THE MODULE IS NOT IN THE SMPPTS.   

Environment

Z/OS 

Cause

The Intertest CICS and Symdump SMP CSI and SMPPTS datasets were are out of SYNC.

Resolution

The Intertest CICS and Symdump SMP CSI and SMPPTS datasets are out of SYNC. This site has a customized SMP/E environment and needs to find the SMPPTS datasets that correspond to the CSI. Intertest CICS ships with two SMPPTS datasets  called SMPPTS and SMPPTS1. This particular site has at least six SMPPTS datasets associated with SMP environment. 

The SMP/E Apply check output allocations report lists the SMPPTS datasets used in the apply check. Below is a sample of the SMPPTS datasets listed in the Allocation Report.

SMP APPLY    CHECK FILE ALLOCATION REPORT 

SMPPTS                     PERM    TEST.SMPPTS                                VOLUM1             SHR       
SMPPTS1                    PERM    TEST.SMPPTS1                              VOLUM2            SHR       
SMPPTS2                    PERM    TEST.SMPPTS2                              VOLUM3            SHR       
SMPPTS3                    PERM    TEST.SMPPTS3                              VOLUM4            SHR       
SMPPTS4                    PERM    TEST.SMPPTS4                              VOLUM5            SHR       
SMPPTS5                    PERM    TEST.SMPPTS5                              VOLUM6            SHR       
 

Below are additional details for message GIM65902E.

GIM65902E

MODULE modname IS NEEDED TO BUILD THE FOLLOWING LOAD MODULES      
FOR SYSMOD sysmod1 BUT CAN NOT BE USED.  ITS DISTRIBUTION         
ZONE umidtype dzumid IS DIFFERENT FROM THE TARGET ZONE            
umidtype tzumid, AND SYSMOD sysmod2 WHICH LAST REPLACED THE       
MODULE IS NOT IN THE SMPPTS.                                      
                                                                               
Explanation:                                                      
                                                                               
modname   module name                                             
sysmod1    SYSMOD ID                                               
umidtype   FMID, RMID, or UMID                                     
dzumid      distribution zone FMID or RMID. This field is blank     
                 if umidtype is UMID.                                    
tzumid      target zone FMID or RMID. This field is blank if        
                umidtype is UMID.                                       
                sysmod2   module's target zone RMID                               
                                                                               
SMP/E required the specified module to build load modules. It     
Found the module in the distribution zone, but the module was 
at the wrong service level. A module may have different       
service levels in the target zone and the distribution zone   
if any service is applied to the target zone and not accepted 
in the distribution zone.                                     
                                                              
SMP/E also could not find in the SMPPTS data set SYSMOD       
sysmod2 that last replaced the module in the target system.   
This SYSMOD is the module's target zone RMID. If the SYSMOD   
was found in the SMPPTS, the copy of the module within the    
SYSMOD would be included during link edit operations.         
                                                              
Message GIM65905 follows this message and identifies the load 
modules that could not be built.                              
                                                              
System Action:  SYSMOD processing stops.                      
                                                              
Programmer Response:  Do one of the following and rerun the   
job:                                                          
                                                              

 1.  RECEIVE into the Global zone and SMPPTS data set SYSMOD                                       
     sysmod2 that last replaced the module in the target                                           
     system. SMP/E will then find and use the module in the                                        
     SMPPTS data set when you rerun the job.                                                       
                                                                                                   
 2.  List the module in the target and distribution zones and                                      
     compare the FMID, RMID, and UMIDs. (If the message                                            
     indicated an FMID or RMID mismatch, the UMIDs may also                                        
     mismatch.) You may then be able to use the ACCEPT or                                          
     RESTORE commands to synchronize the target zone and                                           
     distribution zone either restoring or accepting the                                           
     module's target zone FMID, RMID, or UMID (whichever was                                       
     indicated as causing the mismatch). This will allow SMP/E                                     
     to find a usable copy of the module in the distribution                                       
     zone when you rerun the job.