Installing CA MIM via the ESDPAX Process.
search cancel

Installing CA MIM via the ESDPAX Process.


Article ID: 53152


Updated On:


MICS Resource Management MIM Resource Sharing (MIM) MIM Data Sharing (MII) MIM Tape Sharing (MIA) MIM Message Sharing (MIC)



This document is intended to better enlighten the process behind the ESDPAX process that became an option for product download effective at CA MIM Release 11.6 SP2 as part of the CA Mainframe 2.0 Initiative. This documentation reviews the steps of completing the jobs necessary for unpacking and unzipping the CA MIM product post download from CA Support Online and uploading to the USS directory.


This document is intended to better elaborate on the ESDPAX process, which became available as part of the CA Mainframe 2.0 initiatives with the first release being CA MIM 11.6 SP2. The following reviews the series of tasks required for the product download of CA MIM from CA Support Online and uploading the necessary files to the USS directory for product installation. Additional documentation concerning this topic can be viewed on the CA Support Online website by following these links:



The procedure for unpacking the .PAX files are listed below. Please remember to customize only the JCL instructed to be changed. Any other modifications can lead to "unpredictable results". The following dataset member names will be used throughout the process to indicate the steps for easy reference. This process is divided into three (3) steps:

  1. Download USS PAX FILE TO ESD SITE via FTP. (ESDDLDPX member).

  2. Unpack the CA MIM product (ESDUNPAK member).

  3. Run the JCL to create the product files on DASD (ESDUNZIP member).

NOTE: It is recommended to copy thE FOLLOWING JCL templates to a Partitioned Dataset.

  1. Download USS PAX FILE TO ESD SITE via FTP. A template of this document can be found on pg. 24 of the "Pax Enhanced Electronic Software Delivery (ESD) Guide".
    ****** ***************************** Top of Data ****************************** 000001  // yourHLQA JOB (00000000),'FTP DOWNLOAD PAX', 000002  // MSGCLASS=X,CLASS=C,NOTIFY=&SYSUID 000003 //* 000004 //*--------------------------------------------------------------------- 000005 //* FTP download USS PAX FILE TO ESD SITE 000006 //*--------------------------------------------------------------------- 000007 //* 000008 //FTP1 EXEC PGM=FTP,PARM='(Exit TImeout 720' 000009 //* 000010 //SYSTCPD DD DSN=VTAM.TCPIP.TCPIP.DATA,DISP=SHR 000011 //SYSPRINT DD SYSOUT=* 000012 //INPUT DD * 000013 000014 anonymous [email protected] 000015 cd /orders/105246/3624976/comp/ 000016 Binary 000017 get B60809SQJ02.pax.Z + 000018 /u/users/esd/zfs/yourHLQ/B60809SQJ02.pax.Z 000019 dir 000020 quit 000021 /* ****** **************************** Bottom of Data ****************************
    This job is used for the FTP or FTPPATH product download options only. The changes made, other than the Job card), to this job include:

    • FTP Client Instruction Host

    • Directory position of the FTP Path

    • Filename portion of the FTP Path

      The FTP information used in this job is found on Support Online, after clicking on the "Show Individual Components" tab on the "Product Download" page.

      Here is an example of that information for review:

      <Please see attached file for image>

      Figure 1

      If you used the HTTP option for downloading, you may eliminate this step as the product is located on your pc's hard disk in the location that was specified when downloaded.

  2. Customize and execute the ESDUNPAK member to unzip the CA MIM product to your USS directory.
    ************************************ Top of Data ****************************** 000001 // yourHLQU JOB (000000000),'UNPAX ESD FILE', 000002 // MSGCLASS=X,CLASS=C,NOTIFY=&SYSUID 000003 //* 000004 //********************************************************************** 000005 //* 000006 //* IMPORTANT - We use BPXBATCH to interface with the USS directories 000007 //* IMPORTANT - needed for our new ESD system. There is however a 000008 //* IMPORTANT - limitation on the JCL PARM= length which is 100 bytes; 000009 //* IMPORTANT - so if you get a JCL error with the message shown below: 000010 //* IEF642I EXCESSIVE PARAMETER LENGTH IN THE PARM FIELD 000011 //* IMPORTANT - you may have to split the BPXBATCH steps into two steps 000012 //* IMPORTANT - to fix this issue. 000013 //* 000014 //* IMPORTANT - Please try to use a USS directory length of no more 000015 //* IMPORTANT - than 55 bytes. This is so that the customers can use 000016 //* IMPORTANT - the ISPF EDIT field called "OTHER PARTITIONED.." 000017 //* IMPORTANT - You may use longer directory lenghts but this then 000018 //* IMPORTANT - requires customers to know more about USS or ISPF 000019 //* IMPORTANT - editing in a USS environment. We need to keep it simple 000020 //* IMPORTANT - so that anyone can follow the simple instructions in 000021 //* IMPORTANT - the ISPF Edit Entry Panel. 000022 //* 000023 //* IMPORTANT - If you do want to create a NEW directory 000024 //* IMPORTANT - that exceeds this length you will need to create two 000025 //* IMPORTANT - BPXBATCH steps, one to create the USS directory 000026 //* IMPORTANT - and one to UN-PAX the flat file into the directory. 000027 //* 000028 //* IMPORTANT - BPXBATCH step 1 PARM= example is shown below: 000029 //* Change the PARM= field to contain the following: 000030 //* PARM='sh cd /a/yourHLQ/Packaging/MIMSP2/; mkdir NewDIR; 000031 //* cd NewDIR;' 000032 //* IMPORTANT - BPXBATCH step 2 PARM= is shown below: 000033 //* Change the PARM= field to contain the following: 000034 //* PARM='sh cd /a/yourHLQ/Packaging/MIMSP2/NewDIR/; 000035 //* pax -rvf MIM116SP2.pax.Z' 000036 //* 000037 //* To Un-PAX into a NEW USS directory with a directory length of 55 000038 //* bytes or smaller you simply change the PARM field 000039 //* "cd" change directory to the directory you require and set the 000040 //* NewDIR to the New Name directory for the SYSMOD. 000041 //* Do the following to create a new directory. 000042 //* Change the PARM= field to contain the following: 000043 //* PARM='sh cd /a/yourHLQ/Packaging/MIMSP2/; mkdir NewDIR; 000044 //* cd NewDIR; pax -rvf MIM116SP2.pax.Z' 000045 //* 000046 //* TO Un-PAX into an EXISTING USS SMPE directory for 000047 //* testing as shown below: 000048 //* 000049 //********************************************************************* 000050 //* 000051 //*JOBPARM SYSAFF= SYSA <--- set to the required system 000052 //* 000053 //UNPAXDIR EXEC PGM=BPXBATCH, 000054 // PARM='sh cd /u/users/esd/zfs/yourHLQ; x 000055 // pax -rvf B60809SQJ02.pax.Z' 000056 //STDOUT DD SYSOUT=* 000057 //STDERR DD SYSOUT=* 000058 //* 000059 //********************************************************************* 000060 //* Set directory permissions via attribue change mode command. 000061 //* chmod for the mode is to allow for file owner and group to have 000062 //* read, write, search and execute attributes on the BaseInstall dir. 000063 //********************************************************************* 000064 //* 000065 //*DIRMODE EXEC PGM=BPXBATCH, 000066 //* PARM= 'sh chmod -R 775 /a/yourHLQ/Packaging/MIMSP2/Verify/MIMESD' 000067 //*STDOUT DD SYSOUT=* 000068 //*STDERR DD SYSOUT=* 000069 //* ****** **************************** Bottom of Data ****************************
    Other than modifying the Job card, you will need to specify the system and "PARM" settings. These are the same settings for the BPXBATCH settings used in Step 1 of this installation procedure.

    Once the job completes, the .ZIP files are unpackaged and loaded to your USS directory. The job output should specify a set of files, looking similar to these:


  3. Customize and execute the supplied ESDUNZIP JCL to create the product files on a specified DASD volume.
    ********************************* Top of Data ********************************** //* // yourHLQA JOB (123100000),'UNZIP MIM116SP2',MSGCLASS=X,CLASS=C, // NOTIFY=&SYSUID //* //********************************************************** //* //* THIS ESD PACKAGE IS FOR MIM RELEASE R116 //* PRODUCT-LEVEL IDENTITY IS MIM116SP2 //* //* BEFORE SUBMITTING THIS JOB FOR EXECUTION: //* //* - EDIT THE JOB CARD TO INCLUDE A VALID ACCOUNTING //* INFORMATION, JOB CLASS AND MSGCLASS. //* //* - CHANGE"yourHLQ"to your high level qualifier //* Do not use a HLQ that may affect your SMPE installation files //* //* - Set SMPDIR DD PATH= to the new sub-directory that contains //* un-paxed ESD package. //* //* - Set SMPJHOME DD PATH= to the JAVA Path for your site //* //* volume="*"will use default work packs set by your site. (SMS) //* if you require your files to be loaded to a specific pack //* do a global edit change to'volume="*'to'volume="packname'//* Please remember that you will have to delete these files //* manually if you do not use the system default which normally //* deletes these downloaded temporary files after a few days //* automatically. //* //* RC 12 will occur if you uppercase any of these GIMUNZIP commands //* i.e. the use of VOLUME="PACKNAME"instead of volume="PACKNAME"//* archid, newname, volume, replace must be lowercase. //* //********************************************************** //* //STEP1 EXEC PGM=GIMUNZIP,REGION=0M //* //*EXAMPLE DD PATH='/a/CA/Packaging/VIEW/R115/BaseInstall'<-- PRODUCT //* //SMPDIR DD PATH='/u/users/esd/zfs/yourHLQ/MIM116SP2', //   PATHDISP=KEEP //* //*EXAMPLE DD PATH='/usr/lpp/java/J1.4/'<-- JAVA z/OS //* //SMPJHOME DD PATH='/sys/javatm2/v1r4m2/usr/lpp/java/J1.4/'<-- JAVA //* //SMPOUT DD SYSOUT=* //SYSPRINT DD SYSOUT=* //SYSUT2 DD UNIT=SYSALLDA,SPACE=(CYL,(200,20)) //SYSUT3 DD UNIT=SYSALLDA,SPACE=(CYL,(50,10)) //SYSUT4 DD UNIT=SYSALLDA,SPACE=(CYL,(25,5)) //SYSIN DD * <GIMUNZIP> <ARCHDEF archid="INSTALL.NOTES"  newname="yourHLQ.CAI.CTDB600.INSTALL.NOTES"  volume="MIMESD"  replace="YES"> </ARCHDEF> <ARCHDEF archid="SAMPJCL"  newname="yourHLQ.CAI.CTDB600.MIM.CNTL"  volume="MIMESD"  replace="YES"> </ARCHDEF> <ARCHDEF archid="MIM PRODUCT DOCUMENTATION"  newname="yourHLQ.CAI.CTDB600.MIM.TGZ"  volume="MIMESD"  replace="YES"> </ARCHDEF> <ARCHDEF archid="SMPMCS"  newname="yourHLQ.CAI.CTDB600.MIM.SMPMCS"  volume="MIMESD"  replace="YES"> </ARCHDEF> <ARCHDEF archid="CTDB600.F1"  newname="yourHLQ.CAI.CTDB600.F1"  volume="MIMESD"  replace="YES"> </ARCHDEF> <ARCHDEF archid="CTDB600.F2"  newname="yourHLQ.CAI.CTDB600.F2"  volume="MIMESD"  replace="YES"> </ARCHDEF> </GIMUNZIP> ******************************** Bottom of Data ********************************
    This job is located in the UNZIPJCL file, inside the unzipped CA MIM USS directory. It is recommended that a copy of this job be made for submission and not to alter the actual template located in the member. This job will take your MIM.CNTL files and load them to a DASD file or workpack (See instructions).

    Changes made, (other than the Job card), to this job include:

    • Specifying your USS directory.

    • Change ONLY the "yourHLQ" to your high level qualifiers for the installation files. NOTE: NOT TO MODIFY THE LOW LEVEL QUALIFIERS!

    • Specify the DASD volume (if applicable).

      If job completes successfully with a condition code of zero (0), the output will display files similar to these which will be on the DASD volumes specified in the job:
           yourHLQ.CAI.CTDB600.F1     yourHLQ.CAI.CTDB600.F2     yourHLQ.CAI.CTDB600.INSTALL.NOTES     yourHLQ.CAI.CTDB600.MIM.CNTL     yourHLQ.CAI.CTDB600.MIM.SMPMCS     yourHLQ.CAI.CTDB600.MIM.TGZ
      You may now begin the CA MIM Installation Guide to install the CA MIM product. Due to USS directory space, it may be required to delete the product .PAX directory and their associated files.

Troubleshooting and Common Problems:

Common issues noted by customers and CA Support with this process are:

  • Customer site unzipping the .PAX file prior to USS upload.

  • Customer modifying the UNZIPJCL member in a manner that would not allow it to work as designed.

  • Customer receiving the following messages upon implementing the product files to DASD:


    *This was the result of the customer using "in-house" installation JCL.*

  • Customers naming the .PAX files in lower case format when defining the ESDUNPAK member.

  • Customers attempting to overwrite their SMP/e members with the new SMP/e target and DLIB CSI.

  • Customers attempt to use the "Old ESD Process" (Legacy ESD) when installing the product .PAX files.

If there are any questions concerning this document, the ESDPAX process, or the Mainframe 2.0 Initiative, please do not hesitate to contact CA Support.


Component: MICS


1558720830502000053152_sktwi1f5rjvs16vtw.gif get_app get_app