When doing a RESTORE of an APAR, SMP/E may fail with the following messages:
GIM54502E ** ALLOCATION FAILED FOR ddname BECAUSE THERE IS NO DD STATEMENT IN THE JCL AND NO DDDEF ENTRY IN TARGET ZONE CAIT. GIM28307E ** ALLOCATION FAILED FOR ddname, WHICH IS REQUIRED IN ORDER TO PROCESS ELEMENT element IN SYSMOD sysmod. GIM22601I RESTORE PROCESSING FAILED FOR SYSMOD sysmod. GIM20501I RESTORE PROCESSIN
Customers who installed CA PDSMAN using MSM/CSM may have DDDEFs for the distribution libraries missing from the target zone.
NOTE: This problem ONLY affects customers who installed using MSM/CSM.
When doing a RESTORE of an APAR, SMP/E may fail with the following messages:
GIM54502E ** ALLOCATION FAILED FOR ddname BECAUSE THERE IS NO DD STATEMENT IN THE JCL AND NO DDDEF ENTRY IN TARGET ZONE CAIT. GIM28307E ** ALLOCATION FAILED FOR ddname, WHICH IS REQUIRED IN ORDER TO PROCESS ELEMENT element IN SYSMOD sysmod. GIM22601I RESTORE PROCESSING FAILED FOR SYSMOD sysmod. GIM20501I RESTORE PROCESSIN
When doing an APPLY of an APAR that adds a new module, SMP/E may fail with the following messages:
GIM54502I ALLOCATION FAILED FOR ddname BECAUSE THERE IS NO DD STATEMENT IN THE JCL AND NO DDDEF ENTRY IN TARGET ZONE CAIT. GIM65912E ** MODULE module IS NEEDED TO BUILD THE FOLLOWING LOAD MODULES FOR SYSMOD sysmod BUT IS NOT FOUND. THE MODULE'S DISTRIBUTION LIBRARY ddname COULD NOT BE ALLOCATED, AND SYSMOD sysmod WHICH LAST REPLACED THE MODULE IS NOT IN THE SMPPTS. GIM65905I - LOAD MODULE module. GIM22601I APPLY PROCESSING FAILED FOR SYSMOD sysmod.
Solution:
The SMPE ALLOCATION FAILED messages can occur if the DDDEFs for the distribution libraries are only in the distribution zone. They should also be in the target zone. To address these types of errors the following UCLIN can be run.
//UCLIN JOB //************************************************************************* //* * //* Instructions * //* * //* 1) Add an appropriate job card. * //* * //* 2) Tailor the following strings for your environment: * //* * //* String Description * //* -------- --------------------------------------------- * //* YOURHLQ The high-level qualifier of your CA PDSMAN * //* MSM data sets. * //************************************************************************* //UCLIN EXEC PGM=GIMSMP, // REGION=0M, // PARM='CSI=YOURHLQ.CSI,PROCESS=END' //* //SMPRPT DD SYSOUT=* //SMPOUT DD SYSOUT=* //* //SMPCNTL DD * SET BDY(CAIT0). UCLIN. ADD DDDEF(APDSMOD) SHR DA(YOURHLQ.APDSMOD). ADD DDDEF(APDSCLS0) SHR DA(YOURHLQ.APDSCLS0). ADD DDDEF(APDSHELP) SHR DA(YOURHLQ.APDSHELP). ADD DDDEF(APDSMSG0) SHR DA(YOURHLQ.APDSMSG0). ADD DDDEF(APDSPNL0) SHR DA(YOURHLQ.APDSPNL0). ADD DDDEF(APDSSKL0) SHR DA(YOURHLQ.APDSSKL0). ADD DDDEF(APDSTBL0) SHR DA(YOURHLQ.APDSTBL0). ADD DDDEF(APDSTXT) SHR DA(YOURHLQ.APDSTXT). ADD DDDEF(APDSSAMP) SHR DA(YOURHLQ.APDSSAMP). ADD DDDEF(APDSDATA) SHR DA(YOURHLQ.APDSDATA). ADD DDDEF(APDSXML) SHR DA(YOURHLQ.APDSXML). ENDUCL.
The problem is in the PDSMAN MSM/CSM metadata, so it can't be corrected via a PTF (the metadata will be corrected for the next release).