When applying a fix that is in received status the client receives SMP/E error message GIM65902E MODULE IS NOT IN THE SMPPTS.
book
Article ID: 106367
calendar_today
Updated On:
Products
InterTest - CICSInterTest - BatchInterTest VSE - CICS
Issue/Introduction
The client is applying the CA Intertest and Symdump CICS r 11 incremental four fixes. All the fixes have been received and have PREREQ requirements of earlier fixes. But the Apply fails with message
GIM65902E ** MODULE IN71AILC IS NEEDED TO BUILD THE FOLLOWING LOAD MODULES FOR SYSMOD SO01925 BUT CAN NOT BE USED. ITS DISTRIBUTION ZONE RMID CABAB00 IS DIFFERENT FROM THE TARGET ZONE RMID RO97425, AND SYSMOD RO97425 WHICH LAST REPLACED THE MODULE IS NOT IN THE SMPPTS. GIM65905I - LOAD MODULE IN71MU1. GIM65905I - LOAD MODULE IN71RMIO. GIM65905I - LOAD MODULE IN71SER1. GIM22601I APPLY CHECK PROCESSING FAILED FOR SYSMOD SO01925.
Environment
Z/OS
Cause
The client has all the previous CA Intertest and Symdump CICS r 11 Increment one, two and three fixes applied. These fixes are very large and at some point when applying the fixes over the last few months the SMPPTS ran out of space. So the client allocated an SMPPTS1 dataset instead of expanding the current SMPPTS dataset. Now the fixes for the different incremental fixes are in two SMPPTS* datasets(SMPPTS and SMPPTS1). The increment four PTF SO01925 requires modules from the increment one fix RO97425 which is in the SMPPTS1 dataset not in SMPPTS.
Resolution
The client had to add the DDDEF for the SMPPTS1 to the SMP environment so it would be allocated during the apply.
This particular client had a custom SMP/E environment. The default SMP/E environment for CA Intertest and Symdump CICS is shipped with SMPPTS1 as follows.
SET BOUNDARY(GLOBAL). ADD DDDEF(SMPPTS1) SHR DA(SMPPTS1) .
SET BOUNDARY(CAID0). ADD DDDEF(SMPPTS1) SHR DA(SMPPTS1)
SET BOUNDARY(CAID0). ADD DDDEF(SMPPTS1) SHR DA(SMPPTS1)