BASE SAMPJCL NOT BEING CREATED

book

Article ID: 49261

calendar_today

Updated On:

Products

CA 1 Tape Management CA 1 Tape Management - Copycat Utility CA 1 Tape Management - Add-On Options CA Compress Data Compression for MVS CA Compress Data Compression for Fujitsu CA Datacom - DB CA Datacom CA Datacom - AD CA Datacom - Server CA CIS CA Common Services for z/OS CA 90s Services CA Database Management Solutions for DB2 for z/OS CA Common Product Services Component CA Common Services CA ecoMeter Server Component FOC CA Easytrieve Report Generator for Common Services CA Infocai Maintenance CA IPC Unicenter CA-JCLCheck Common Component CA Mainframe VM Product Manager CA Chorus Software Manager CA On Demand Portal CA Service Desk Manager - Unified Self Service CA PAM Client for Linux for zSeries CA Mainframe Connector for Linux on System z CA Graphical Management Interface CA Web Administrator for Top Secret CA CA- Xpertware CA Datacom/AD

Issue/Introduction

Description:

The batch JCL executed to extract the product pax file into the product directory may not appear to be working properly. The unpax of the BASE pax file is yielding the following statement in the UNZIPJCL member.

<ARCHDEF archid="CAI.SAMPJCL"
   	newname="yourHLQ.OPTIONAL.SAMPJCL"

Solution:

The CA Common Services r14.1 Installation Guide, states the following on page 93:

Use the sample job attached to the PDF file as Unpackage.txt to extract the product pax file into a product installation directory. Since CA Common Services software components are packaged using four pax files, it may be easier to perform this procedure for all the pax files you require now versus coming back to this procedure later. You should create a separate directory for each pax file.

Failure to create a separate directory for each pax file will result in similar files being overlaid when each pax file is unpaxed into a dynamically created directory.

The following link will direct you to some notes that will be helpful in setting up the USS directories to allow for the processing of the pax files delivered with CA Common Services.

https://support.ca.com/phpdocs/0/5112/5112_Upload_to_Mainframe.pdf

After creating a separate directory, and loading the individual pax files to their respective directories, unpax each pax file and proceed to customizing and running the UNZIPJCL jobs to create the necessary data sets on DASD.

Following is an example of the directory structure:

/cai/ESD/CCS/R141/

_ Dir 777 rwxrwxrwx 8192 BASE
_ Dir 777 rwxrwxrwx 8192 LEGACY
_ Dir 777 rwxrwxrwx 8192 MFNSM
_ Dir 777 rwxrwxrwx 8192 OPTIONAL

Environment

Release: CA90SV00200-14.1-Common Services-for z/OS
Component:

Attachments

1558535059418TEC581911.zip get_app