IBM Integration Bus, Version 9.0.0.8 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Installing service on z/OS

Apply maintenance updates to the broker.

Before you start:

Download the required update package for IBM® Integration Bus, as described in Applying service to the Integration Bus component.
Check that your user ID has the correct authority to complete this task; see Installation and uninstallation authorization for details.

Use this three stage process to install service on z/OS®:

Store the updates on your target system.
Install and test the fix pack. If testing is not satisfactory, you can remove this fix pack at this stage.
After testing, confirm the fix pack as your current base level of installation.

Follow these instructions to complete the process:

Receive the updates. Use SMP/E RECEIVE to transfer the contents of the fix pack from the tape or the downloaded package to your system at the specified location.
Apply the updates. Use SMP/E APPLY to install the fix pack which completes the link edit steps and generates a runtime environment in your chosen location.
The installation process completes updates to USS and to four product data sets (SBIPSAMP, SBIPINST, SBIPPROC, and SBIPAUTH).

If your SMP/E target system is not on the same file system as your production system, copy the data sets (including the data set that represents your USS mount point) to the system where they are to be used, overwriting the current content. When you complete this action, all runtime components use the updated data sets when they next restart.

If you do not want all your brokers to use the updated installation, copy the data sets to a different location and start selected brokers against that copy. Further details are provided in Multiple concurrent installations at different levels.

You can specify the same destination for receiving the fix pack contents (the SMP/E target system) and for installing (the production system). If you specify a different location, you must copy the product data sets to the appropriate location.

When you have installed the fix pack, test it to ensure that it is working correctly in your environment. If you find problems at this stage, you can remove the fix pack by using SMP/E RESTORE. The command restores your installation to the level that you last accepted (SMP/E ACCEPT).
Confirm the update. Use SMP/E ACCEPT to commit the changes and to establish this fix pack as the current level. When you have completed this step, you cannot restore your system to a previous service level. If you want to use an earlier service level, you must reinstall that level.

Multiple concurrent installations at different levels

If you want to install a later fix pack level, and retain your existing installation so that you can use both service levels, install the second level in a different location. You can then set up additional customization so that one or more of your existing brokers can use the second service level. By retaining the product files in the first location, you can switch a broker back to the first level, if required.

The following steps are a summary of the tasks that you must complete to run a broker at one service level concurrently with a broker at another service level. These steps are identical to those you take for setting up an initial installation, except where indicated.

For a full description of installation and customization for brokers, see Creating a broker on z/OS.

To install a second service or fix pack level:
1. Install the second level of the broker by using the instructions provided with that level.
2. Copy all the template data sets and the main files from the HFS file system to a unique location.
To prepare a broker for use with the second installation:
1. Create and customize a new broker component data set. Complete the steps described in Customizing the broker component data set.
2. Copy the template JCL from the second location to the new dataset.
3. Customize the JCL to work with the second location. For more details about this step, see Customizing the broker JCL.
To change a broker to work with the second installation:
1. Submit the BIPGEN job to update the environment file ENVFILE for the broker. This task is described in Creating the environment file.
2. Copy the customized started task from the new data set into the procedures library, for example USER.PROCLIB.
3. Start the broker; the broker is now associated with the second location.
To roll back to the previous version:
1. Open the original broker component data set, that is associated with the first location.
2. Resubmit the BIPGEN job from that data set.
3. Copy the original PROC into the procedures library USER.PROCLIB.
4. Stop and restart the broker.

ah14790_.htm |

Last updated Friday, 21 July 2017