GIM30206E installing a base product with CA CSM
search cancel

GIM30206E installing a base product with CA CSM

book

Article ID: 129494

calendar_today

Updated On:

Products

Mainframe Software Manager (Chorus Software Manager)

Issue/Introduction



IGetting GIM30206E ** APPLY PROCESSING FAILED FOR SYSMOD nnnnnnn. HOLD REASON IDS WERE NOT RESOLVED. installing a base product with CA CSM 
An actual example:
GIM30206E ** APPLY PROCESSING FAILED FOR SYSMOD CDMFC10. HOLD REASON IDS WERE NOT RESOLVED. 

Environment

Release:
Component: MSM

Resolution

This can happen when a product is being installed in an existing CSI into which maintenance was received for another product.
 The GIM30206E is accompanied by a GIM35901I which identifies the ERROR HOLD data, Base SYSMOD are only put on HOLD for ERROR's.
Example of this message:
GIM35901I ERROR HOLD AC88710 WAS NOT RESOLVED. 
 
If you were installing this product in a new CSI or if maintenance was not previously received the install would not have failed with this message.
What you can do is to reject this HOLDDATA for the SYSMOD, in this example, CDMFC10 then  install the product . After it is install receive and apply all available maintenance. CA CSM will re-receive this HOLDDATA. 

Here is an example of this reject JCL. I recreate it and resolved with this JCL: 
//SMPGO EXEC PGM=GIMSMP,REGION=4096K,PARM='DATE=U' 
//SMPCSI DD DISP=SHR,DSN=hlq.CSI 
//SMPSNAP DD SYSOUT=* 
//SMPHOLD DD DUMMY 
///SMPCNTL DD * 
SET BDY(GLOBAL). 
REJECT S(CDMFC10) HOLDDATA BYPASS(ACCEPTCHECK,APPLYCHECK). 
/* 
 
Replace CDMFC10 with the CSI listed your GIM30206E message.