ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

When installing CA Datacom/DB Version 15.0 from installation PAX file, getting several IKJ56228I messages in the SMP/e RECEIVE job DCM4RECV (or DCM4RECD). Example: IKJ56228I DATA SET yourHlq.CAI.CABDF00.F1 NOT IN CATALOG..."

book

Article ID: 36104

calendar_today

Updated On:

Products

Datacom DATACOM - AD CIS COMMON SERVICES FOR Z/OS 90S SERVICES DATABASE MANAGEMENT SOLUTIONS FOR DB2 FOR Z/OS COMMON PRODUCT SERVICES COMPONENT Common Services Datacom/AD CA ecoMeter Server Component FOC EASYTRIEVE REPORT GENERATOR FOR COMMON SERVICES INFOCAI MAINTENANCE IPC UNICENTER JCLCHECK COMMON COMPONENT Mainframe VM Product Manager CHORUS SOFTWARE MANAGER CA On Demand Portal CA Service Desk Manager - Unified Self Service PAM CLIENT FOR LINUX ON MAINFRAME MAINFRAME CONNECTOR FOR LINUX ON MAINFRAME GRAPHICAL MANAGEMENT INTERFACE WEB ADMINISTRATOR FOR TOP SECRET Xpertware

Issue/Introduction

Issue:

When installing CA Datacom/DB Version 15.0 from installation PAX file, getting several IKJ56228I messages in the SMP/e RECEIVE job DCM4RECV (or DCM4RECD).

Example:

      IKJ56228I DATA SET yourHlq.CAI.CABDF00.F1 NOT IN CATALOG..." 

Environment:

z/OS 

Cause:

The ".CAI." node was removed when editing the UNZIPJCL job that is used to un-pax and create the installation data sets. 

Resolution:

Refer to the unedited UNZIPJCL JCL.

Notice this UNZIPJCL comment:

//*    - CHANGE “yourHLQ” to your high level qualifier
//*      Do not use a HLQ that may affect your SMPE installation files  
//*      The length of yourHLQ must not be greater than 26 characters.  
 
Now, notice the ".CAI." node that is not part of the change for "yourHLQ":
 
//SYSIN    DD  *                                   
<GIMUNZIP>                                         
<ARCHDEF archid="SAMPJCL"                          
         newname="yourHLQ.CAI.SAMPJCL"             
         volume="*"                                
         replace="YES"                             
> </ARCHDEF>                                       
<ARCHDEF archid="CAI.ABDE0G0.SMPMCS"               
         newname="yourHLQ.CAI.ABDE0G0.SMPMCS"      
         volume="*"                                
         replace="YES"                             
> </ARCHDEF>                                       
<ARCHDEF archid="CAI.CBAPE00.F1"                   
         newname="yourHLQ.CAI.CBAPE00.F1"          
         volume="*"                                
         replace="YES"                             
> </ARCHDEF>                                       
<ARCHDEF archid="CAI.CABDE00.F1"                   
         newname="yourHLQ.CAI.CABDE00.F1"          
         volume="*"                                
         replace="YES"                             
> </ARCHDEF>                                       
... etc ... more files... 
 
 
To resolve this situation:
 - Delete the created data sets by the UNZIPJCL.
 - Correct your UNZIPJCL to put back the ".CAI." qualifier.
 - Run the corrected UNZIPJCL.
 - Run the SMP/e RECEIVE job and continue with the installation.
 
 
Additional Information:

The UNZIPJCL job is standard for all CA product PAX file installation.

So, the same situation defined here would be true for other CA product and other product versions.

Environment

Release:
Component: DB