The probable cause is that during the download process, each pax file was unpackaged into the same product directory before executing GIMUNZIP. which overlaid the previous file. Assuming the BASE was the first file that was unpackaged, any additional pax file downloaded into the same directory as the BASE will overlay it. Thus, when GIMUNZIP was executed, it processed the last file. All members necessary to install the product are copied into the BASE SAMPJCL when GIMUNZIP is executed 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 the specific pax file.
There are two methods that can be used to avoid this from occurring
- Download each pax file into it's own directory
- This is the recommended method as noted in the Common Services r14.1 Installation Guide and Documentation wiki
- If the same directory is to be used, ensure that each pax file is downloaded and the file specific GIMUNZIP is executed before processing the next file