Start of change

Installing service on z/OS

Apply maintenance updates to product components.

Before applying a maintenance update to WebSphere® Event Broker, download the update as described in Applying service to runtime components.
Use this three stage process to install service on z/OS®:
  1. Store the updates on your target system.
  2. Install and test the fix pack. If testing is not satisfactory, you can remove this fix pack at this stage.
  3. After testing, confirm the fix pack as your current base level of installation.

Follow these instructions to complete the process:

  1. 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.
  2. 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 of your components to use the updated installation, copy the data sets to a different location and start selected components 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, you can test it to ensure that it is working correctly in your environment. If you find any problems at this stage, you can remove the fix pack using SMP/E RESTORE. The command restores your installation to the level that you last accepted (SMP/E ACCEPT).

  3. 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 runtime components can use the second service level. By retaining the product files in the first location, you can switch a component back to the first level, if required.

For example, you might choose to change one broker to use the later service level, but keep your Configuration Manager at the original service level until you have completed some tests on the updated broker.

The following steps are a summary of the tasks that you must complete to run components at one service level concurrently with components 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 each component, see Creating a broker on z/OS, Creating a Configuration Manager on z/OS, and Creating a User Name Server on z/OS.

  1. To install a second service or fix pack level:
    1. Install the second level of the product components 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.
  2. To prepare components for use with the second installation:
    1. Create and customize a new component data set. For example, if you want to create a new broker component, 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, but use the existing queue manager definition that you are using with the first location. If the component is a broker, use the existing database definition too. For more details about this step, see the appropriate task for your component, for example Customizing the broker JCL.
  3. To change a component to work with the second installation:
    1. Submit the BIPGEN job to update the environment file ENVFILE for the component. 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 component; the component is now associated with the second location.
  4. To roll back to the previous version:
    1. Open the original component data set, that is associated with the first location.
    2. Resubmit BIPGEN from that data set.
    3. Copy the original PROC into the procedures library USER.PROCLIB.
    4. Stop and restart the component.
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2009Copyright IBM Corporation 1999, 2009. All Rights Reserved.
Last updated : 2009-01-07 15:40:30

ah14790_

End of change