UNZIPJCL job run from the pax.Z file to install an IDMS release gets error GIM48900S.

Document ID : KB000052643
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

As part of the install of any IDMS release, an UNZIPJCL job must be run. This may occasionally result in the error GIM48900S ** THE PACKAGE ATTRIBUTE FILE DOES NOT CONTAIN AN ENTRY FOR REQUIRED ARCHIVE AIDMS.Rnnn.BASEnnnn.GJHnnB.FILEnn. The UNZIPJCL from the subdirectory created by the BPXBATCH job is used to unzip and copy the install files from UNIX to the mainframe.

Solution:

The most common explanation for error GIM48900S during a CA IDMS install is that the UNZIPJCL being executed on the mainframe was not taken from the UNIX directory which is being used for the current install. That is, it most likely is from a directory that was used for a previous install of IDMS.

To put this in context, an install for CA IDMS will first require an FTP download from the CA Support Online site of a file in the format RRxxxxDOA00.pax.Z, where RR is the release being installed; this will place the pax.z file in the USS directory you specify. The next step in the install is to process this file using program BPXBATCH, which will create a subdirectory for this install, with a naming convention of GJrrnB for product base tapes and rrGJnM for maintenance tapes, where rr is the release (such as H0 for 17.0) and n the Service level number. An example of this is GJH00B which is IDMS 17.0 SP00 for base. Within each such subdirectory created for every install, there is a GIMPAF.XML file.  That file contains an ARCHID which is used to cross reference the ARCHID in the UNZIPJCL file within the same subdirectory. The GIM48900S indicates that there is no ARCHID in the GIMPAF.XML file that matches the ARCHID specified in the UNZIPJCL file. The archive file name given in the message such as this generic example CAIDMS.Rnnn.BASEnnnn.GJHnnB.FILEnn will be the name specified in the GIMPAF.XML member within this subdirectory, as referenced by the UNZIPJCL.

Here's an example:

Type  Filename                                          
_ Dir   .                                                
_ Dir   ..                                                 
_ File  AREADME                                           
_ File  GIMPAF.XML                                        
_ File  GIMPAF.XSL                                        
_ Dir   SMPPTFIN                                          
_ Dir   SMPRELF                                           
_ File  S0001.CAIDMS.R170.BASE0904.SAMPJCL.pax.Z
_ File  S0010.CAIDMS.R170.BASE0904.GJH01B.FILE12.pax.Z
_ File  UNZIPJCL

You can see that subdirectory structure contains both files UNZIPJCL and GIMPAF.XML.

Within UNZIPJCL there is a ARCHDEF entry:

< >/ARCHDEF>                           
<ARCHDEF archid="CAIDMS.GJH01B.FILE12"   
         newname="yourHLQ.GJH01B.FILE12" 
         volume="*"                      
         replace="YES"

Within GIMPAF.XML there's a corresponding ARCHDEF entry:

</ARCHDEF>         
<ARCHDEF                    
name="S0010.CAIDMS.R170.BASE0904.GJH01B.FILE12.pax.Z" 
archid="CAIDMS.GJH01B.FILE12"                 
description=                          
"IDMS R170 GJH01B CAIDMS.GJH01B.FILE12"      
originalsize="62160"            
size="32256"                   
hash="25767C277BB3E7692CE2B5A42200AF913AD9CCF8">

When the UNZIPJCL is executed, it goes to the GIMPAF.XML file within the same subdirectory, and uses the description there to try to resolve the file name to the actual file within the subdirectory. The error message indicates that no such file exists within the install subdirectory.

This is caused by running the UNZIPJCL file from the wrong subdirectory; usually one for a previous install. To resolve this error, simply find the UNZIPJCL file from the correct subdirectory (the one for this install) and run that JCL. This will reference the corresponding GIMPAF.XML file, which contains the correct file name for this install; this will resolve the error.

Refer to Knowledge Document TEC482627 for more details on the complete install process.