IBM i Installation - Propagating New Release to Additional Systems

Owned by
Former user (Deleted)
Last updated: Nov 29, 2022 by
IT Stonebranch
Version comment
2 min read

Currently, IBM i runs Workload Automation 5.1.1.   These pages provide information for that version.

Propagating New Release to Additional Systems

You may want to install Workload Automation on a pre-production system, implement needed changes such as customizing configuration files, and then propagate these changes to other systems.

One method to propagate the customized product is via the SAVLICPGM and RSTLICPGM commands (see SAVLICPGM and RSTLICPGM Method, below).

Warning

A number of Stonebranch objects are created during the installation process. These include, but are not limited to:

  • Commands in QSYS
  • UBROKER job queue and class
  • Job definitions in the product library
  • Universal Broker Subsystem
  • Print files in the product library.


The default command reference library, UNVCMDREF, is created during installation unless a library of that name exists on the system. This process only recreates the objects previously identified. It will not propagate changes made to those objects.

V5R4 systems

Before installing Workload Automation for IBM i, either download and apply PTF SI27629 or verify that it is applied to the system.

SAVLICPGM and RSTLICPGM Method

 The following steps are recommended:

Step 1

Install Workload Automation (see New Installation (Default) and New Installation (Custom)).

Step 2

Download the latest product maintenance from the Stonebranch Customer Portal and temporarily apply the PTFs.
 
Allow the system to automatically handle any permanent PTF application via the APYPTF command. See Upgrade Installation for Maintenance Release for detailed instructions on applying a maintenance release.

Step 3

Customize the Workload Automation installation as described in Customization.

Step 4

Verify that the 5.1.1 Universal Broker Subsystem, UNVUBR511, is not active.

Step 5

To create a save file in which to save the customized product, invoke:
 

Step 6

Invoke:
 

Step 7

If needed, restart the Universal Broker Subsystem:
 

Step 8

Via what ever mechanism you prefer, move the save file to each system on which you want to restore the product.

Step 9

Invoke:
 

Note

Although this procedure describes use of a save file, any other available save and restore device can be used.