/
z/OS Installation - Stonebranch Solutions 4.x Upgrade, Existing CSI

z/OS Installation - Stonebranch Solutions 4.x Upgrade, Existing CSI

Owned by Stonebranch (Deactivated)
Jan 31, 2024

Stonebranch Solutions 4.x Upgrade, Existing CSI

The Stonebranch Solutions 4.x Upgrade, Existing CSI installation process describes how to upgrade an existing Stonebranch Solutions 4.x package in an existing SMP/E CSI.

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.

Step 1

Edit and submit the JCL in member #SETUP.
 
The #SETUP JCL creates customized installation JCL used by the following installation steps and for product maintenance and customization. All the JCL is created as members in the INSTALL library.
 
To change customizations after the job is executed, edit the #SETUP member with the new customizations and resubmit the job. All INSTALL library members will be replaced.
 
All steps must end with a return code 0.

Step 2

Submit the JCL in member UNVUG4XX. The JCL removes the UAR configuration and component definition members in the non-SMP/E UNVCONF and UNVCOMP libraries, respectively, allocates the UAG model data set, and allocates a PDS used by the Universal Broker keystore feature.
 
All steps must end with return code 0.

Step 3

Submit the JCL in member UNVIN04. 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 4

Submit the JCL in member UNVIN05. The JCL performs an SMP/E APPLY of the 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.

Step 5

Submit the JCL in member UNVIN06. The JCL member performs an SMP/E ACCEPT of 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 6

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

Step 7

Edit and submit the JCL in member UNVIN09. The JCL requires modifications as listed in the MODIFICATIONS section of the comments at the top of the JCL.
 
The JCL copies the Universal Enterprise Controller and Universal Broker started procedure JCL to a system procedure library.
 
All steps must end with a return code 0.

Step 8

Perform required z/OS configuration steps as described in z/OS Installation - Configuration.