Why is there only one member in my BASE SAMPJCL named @README after unloading multiple pax files for CA Common Services for z/OS r14.1 and executing GIMUNZIP?

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

Description:

During the install process of CA Common Services for z/OS r14.1 and after executing both BPXBATCH and GIMUNZIP for themultiple pax files, some customers have found that the BASE SAMPJCL contains only a single member named @README.

The probable cause is that during the download process each pax file was unpackaged into the same product directory and the existing file was overlaid by a subsequent pax file before the initial execution of GIMUNZIP. Assuming the BASE was the first file that was unpackaged, either the OPTIONAL, LEGACY, EVENT MANAGEMENT, or a combination of the three pax file(s), was downloaded to the same directory as the BASE and each, in turn, overlaid the existing file before the first GIMUNZIP was executed.

All members necessary to install the product are copied into the BASE SAMPJCL upon executing GIMUNZIP for the BASE . Each additional pax file contains its own GIMUNZIP and creates a corresponding SAMPJCL (ie. LEGACY,OPTIONAL) consisting of one @README member. Each @README refers you to the BASE SAMPJCL for the necessary JCL to install the components contained within.

Solution:

Download each pax file into its own directory. This is the recommended method as noted in theCA Common Services for z/OS r14.1 Installation Guide on page 107 under the heading of Create a Product Directory from the Pax File. The final sentence of the first paragraph states that you should create a separate directory for each pax file.