z/OS USS Installation - New Install, New CSI

Owned by
Former user (Deleted)
Jun 11, 2020
2 min read

New Install, New CSI

The New Install, New CSI installation process describes how to install the Universal Agent for z/OS USS package in a newly allocated SMP/E CSI.

Use this installation process for either of these environments:

  • Installing a Universal Agent for z/OS USS package for the first time.
  • Installing a Universal Agent for z/OS USS package in a different SMP/E CSI than other Universal Agent components.

The installation JCL referenced by the installation steps is created by the #SETUP member in the Universal Agent INSTALL library.

Each step consists of running a batch job. The batch job must end with the appropriate return code before proceeding to the next step.

The user ID used to run the installation jobs must have a valid OMVS segment defined and have READ access to the BPX.FILEATTR.APF profile in the FACILITY class.


Step 1

Submit the JCL in member UNVUN01. The JCL allocates the SMP/E target and distribution data sets, creates the z/OS UNIX directories, and defines the DDDEFs in the SMP/E zones. All steps must end with a return code 0.
 
Step ALLOCUSS creates the z/OS UNIX directories required by the USS components. The path prefix where the directories are created was defined when the #SETUP member of the INSTALL library was modified and run as part of the z/OS installation. IBM recommends the path prefix to be /usr/lpp. Review the path prefix used in the ALLOCUSS step PARM value to be sure it meets local requirements.
 
The z/OS UNIX directory where the Universal Agent directories are created must be mounted in read/write mode. The user ID used to run this job must have write access to the directory.
 
If the z/OS UNIX directories already have been created, the ALLOCUSS step will indicate this in its report and end successfully.

Step 2

Submit the JCL in member UNVUN02. The JCL performs an SMP/E RECEIVE of the product FMIDs and available PTFs from the distribution data sets. All steps must end with a return code 0.

Step 3

Submit the JCL in member UNVUN03. The JCL performs a SMP/E APPLY of the USS product FMIDs and any received PTFs. Step APYFMID must end with a condition code of 0.
 
Step APYPTFS is considered successful under any of the following conditions:

  • Step ends with condition code 0.
  • Step ends with condition code 4, and message GIM42001W is written in ddname SMPOUT.
  • Step ends with condition code 12, and message GIM24801S is written in ddname SMPOUT.
    The user ID used to run the job must have READ access to BPX.FILEATTR.APF profile in the FACILITY class in order to set the APF attribute on the UDM file when it is created in the z/OS UNIX directory by the APPLY command.

Step 4

Submit the JCL in member UNVUN04. The JCL member performs a SMP/E ACCEPT of the USS product FMIDs and any applied PTFs. Step ACCFMID must end with a condition code of 0.
 
Step ACCPTFS is considered successful under any of the following conditions:

  • Step ends with condition code 0 or 4.
  • Step ends with condition code 12, and message GIM24801S is written in ddname SMPOUT.

Step 5

Submit the JCL in member UNVUN05. The JCL copies sample configuration members to the configuration library. All steps must end with a return code 0.