Installing Service Changes (without Dialogs)

It is recommended to use the dialogs provided by the Interactive Interface for installing service changes to z/VSE. When you are a workstation user, use the VSE Workdesk windows to install service changes to z/VSE. If you cannot use the dialogs for some reason, this section shows selected example jobs for installing the service changes without them.

Note: The product IDs, phase and macro names used in the following examples do not reflect a system environment. They are used for demonstration purposes only.

The z/VSE Interactive Interface dialogs keep their own information, therefore the changes that you make using MSHP might not be reflected in the dialogs.

IBM® distributes service changes for z/VSE either of the following:
  • One or a number of Program Temporary Fixes (PTFs) on tape (or cartridge).
  • An Authorized Program Analysis Report (APAR) fix.
A PTF contains one or more phases, modules, or macros, which replace a corresponding existing phase, module, or macro. An APAR is an update to a phase, a module, or a macro. How to handle PTFs and APARs is summarized below.
  • Handling PTFs

    PTFs are shipped on a distribution tape or can be downloaded from the Internet (Shopz).

    The electronic shipment contains the following:
    1. Readme file
    2. PTF cover letter
    3. PTFs
    The cover letter is in text format. The PTF files are in binary format. Refer to Apply PTFs from the Internet for details.
    The tape (also called service tape) contains the following, in the sequence listed:
    1. A tape history file or a null file
    2. A null file
    3. A null file
    4. An EXCLUDE list or a null file
    5. PTF cover letters or a null file
    6. PTFs
    7. A null file.
    Note: MSHP can install PTFs from a service tape only if the PTFs are stored on the tape as the sixth file with a block size of 10320 bytes.
    When you receive a service tape:
    1. Have MSHP produce a listing of the PTF cover letter file, and read this printout carefully. This helps you in planning and performing the task of installing required PTFs.
    2. Install those PTFs which correct system problems. For preventive service, you can install all PTFs supplied by IBM if this is desirable.

      The service tape as shipped by IBM might not include PTFs whose installation on your system is a prerequisite for one or more of the PTFs you want to install. In this case, MSHP does not install the affected PTF and informs you by a message.

      If you know that prerequisite PTFs exist on another service tape and that these PTFs are not yet installed, have MSHP INCLUDE the additional tape(s) for the prerequisite PTFs in the installation step.

    You might also receive a single PTF from IBM. You get this PTF in the form of an executable job which invokes MSHP.

  • Handling APARs or Local Fixes

    Normally, such fixes are not distributed in machine readable form. You install them using the CORRECT function of MSHP.

  • Revokable or Irrevocable Installation

    The REVOKABLE option of MSHP produces so called backout jobs of PTFs that you install. Use the option only if you install just one or a few PTFs for the purpose of solving a specific problem.

    MSHP writes backout jobs onto the tape mounted on the drive to which SYS004 is assigned. You can use this tape as input to MSHP should you need to back out a PTF. Installing a backout PTF amounts to a re-installation of the library member(s) replaced by installation of the PTF.
    Note: Do not install the backout job for a PTF that is a pre- or corequisite for other PTFs or has comparable APAR/Local Fix dependencies.

    This section gives sample jobs for both the installation of PTFs and the installation of backout jobs.

  • Preparing the System

    Before the installation of service changes, you should produce a backup on tape of the sublibrary (or program) on which you want to install a service change. Perform a Librarian BACKUP run to get a backup of the system library. When you have one program stored in one sublibrary, perform an MSHP BACKUP run to get a backup of an individual program. If several programs are in one sublibrary, you get a backup of the sublibrary.

    There is no need to define the libraries or sublibraries that hold the products which are to be serviced. MSHP establishes required search chains based on the information recorded in the history file. It uses the services of the Librarian to actually delete replaced members and to catalog new, replacement members.