How to fix GIM32501E ** APPLY PROCESSING HAS FAILED FOR SYSMOD ... DOES NOT CONTAIN MODULE ... error messages?
book
Article ID: 94715
calendar_today
Updated On:
Products
Database Analyzer for DB2 for z/OSFast Unload for DB2 for z/OSFast Check for DB2 for z/OSFast Index for DB2 for z/OSRapid Reorg for DB2 for z/OS
Issue/Introduction
During SMP/E APPLY or APPLY CHECK got the following SMP/E error message.
GIM32501E ** APPLY PROCESSING HAS FAILED FOR SYSMOD SOnnnnn. SOnnnnn SUPERSEDES SOmmmmm BUT DOES NOT CONTAIN MODULE module-name.
How to fix GIM32501E error messages?. Which steps do you have to follow?.
Environment
Release: Component: INS
Resolution
Normally this error message means SMP/E cannot find the ++MOD statement for the module-name (CSECT's) during the SMP/E APPLY or APPLY CHECK.
This could be caused by a an incorrect download in CA Chorus Software Manager (CA CSM) over the CA CSM Directories or a wrong SMP/E RECEIVE over the SMPPTS library.
If you work with CA CMS the first check the location of the PTF and with the USS Browse path browse the *.bin file, run a FIND ++MOD command and you have to find the ++MOD statement with the module-name, for example ++MOD(module-name) DISTLIB(ADBAMOD0).
If you do not find the ++MOD statement then the *.BIN file was corrupted, you have to delete PTF SOnnnnn from the CA CSM Directory and Software Catalog and acquire it again.
If you find the *.BIN file is fine in the CA CSM Directory or you do not work with CA CSM then you have to check your SMPPTS library. Browse PTF member SOnnnnn and run a FIND ++MOD command, you have to find the ++MOD statement with the module-name. Sometimes the corruption over members in SMPPTS library are caused by problems during SMP/E RECEIVE, for example any Abend SB37 over the SMP/E data sets. Check the possible problems during RECEIVE and run a REJECT for PTF SOnnnnn, then run again the RECEIVE and be sure SMPPTS library is updated correctly.