RTM VM/ESA Service Instructions

Service Instructions

June 1996

5798-DWD

If you'd like to send me feedback on this program directory you can:

Send e-mail to me at daileybc@us.ibm.com

Or send it to me at: 

Bruce Dailey
Dept G32
IBM Corp.
1701 North St.
Endicott, NY 13760

This program directory, dated June 1996, applies to Realtime Monitor VM/ESA (RTM VM/ESA) Release 5.2, Program Number 5798-DWD for the following:

Service Instructions

  • VMSES/E Service Instructions
  • VMSES/E Service Process Overview
  • Servicing RTM VM/ESA
  • RTM Product Rebuild

    • Service Instructions

    The service procedure for RTM VM/ESA depends on the VM release you have installed the product on. If you are installing the product on VM/ESA Release 2 or later release, then follow the VMSES/E instructions provided in "VMSES/E Service Instructions". For VM/ESA Release 1.1, service the product according to the non-VMSES/E instructions provided in "Non-VMSES/E Service Instructions".

    VMSES/E Service Instructions

    This section of the Program Directory contains the procedure to install CORrective service to RTM VM/ESA. VMSES/E of VM/ESA R2 is used to install service for RTM VM/ESA.

    Note: To become more familiar with service using VMSES/E, you should read the introductory chapters 'VMSES/E Introduction and Reference' manual (SC24-5444) before you begin the procedures in this section. This manual also contains the command syntax for the VMSES/E commands listed in the procedure.

    VMSES/E Service Process Overview

    The overview will give a brief description of the main steps in servicing RTM VM/ESA using VMSES/E.

    • Merging Service

      Use the VMFMRDSK command to clear the alternate apply disk/directory before receiving new service. This allows you to easily remove the new service if a serious problem is found.

    • Receiving Service

      The VMFREC command receives service from the delivery media and places it on the Delta disk/directory.

    • Applying Service

      The VMFAPPLY command updates the version vector table (VVT), which identifies the service level of all the serviced parts. In addition, AUX files are generated from the VVT for parts that require them.

    • Reapplying Local Service (if applicable)

      All local service must be entered into the software inventory to allow VMSES/E to track the changes and build them into the system. See Chapter 7 in the VM/ESA R2 Service Guide for this procedure. (SC24-5527-02).

    • Building New Levels

      The build task generates the serviced level of an object and places the new object on a BUILD disk.

    • Placing the New Service into Production

      Once the service is satisfactorily tested it should be put into production by copying the new service to the production disk or directory, re-saving the NSS (Named Saved System) or DCSS (Discontiguous Saved Segments), etc.

    Servicing RTM VM/ESA

    +---Override Considerations--------------------------------------------------+

    The ppfname used throughout these instructions is 5798DWDC, which assumes you are using the PPF supplied by IBM for RTM VM/ESA. If you have your own PPF override file for RTM VM/ESA, you should use your file's ppfname instead of 5798DWDC. The ppfname you use should be used throughout the rest of this procedure.

    The compname used throughout these instructions is either RTM or RTMSFS, which assumes you are using the component name within the 5798DWDC PPF file. If you specify your own ppfname, you should use the compname from that file instead of RTM or RTMSFS. The compname you use should be used throughout the rest of this procedure. 

    +----------------------------------------------------------------------------+

    +---SFS Considerations-------------------------------------------------------+

    If you are installing to an SFS directory and your A-disk is also an SFS directory but in a different filepool, Coordinated Resource Recovery (CRR) needs to be running on your system. 
    +----------------------------------------------------------------------------+

    1. Log onto 5798DWDC userid and make sure the VMSES code is accessed as filemode B. (By default this disk is MAINT 5E5). 
      
ACCESS 5E5 B
ACCESS 51D D

    2. Setup the the 5798DWDC userid environment to install service. 
      VMFSETUP 5798DWDC RTM
                  RTMSFS

      Note: Use RTM if the product was installed on minidisk, or RTMSFS if the product was installed on SFS.

      The following is an example of the screen displayed after issuing the above VMFSETUP command: 

      vmfsetup 5798dwdc rtm
VMFSET2760I VMFSETUP processing started
VMFUTL2205I Minidisk|Directory Assignments:
            String    Mode  Stat  Vdev  Label/Directory
VMFUTL2205I LOCALSAM  E      R/W  2C2   5792C2
VMFUTL2205I APPLY     F      R/W  2A6   5792A6
VMFUTL2205I           G      R/W  2A2   5792A2
VMFUTL2205I DELTA     H      R/W  2D2   5792D2
VMFUTL2205I BUILD0    I      R/W  400   579400
VMFUTL2205I BUILD1    J      R/W  401   579401
VMFUTL2205I BUILD6    K      R/O  190   MNT190
VMFUTL2205I BUILD6    S      R/O  190   MNT190
VMFUTL2205I BUILD7    L      R/O  193   MNT193
VMFUTL2205I BASE1     M      R/W  2B2   5792B2
VMFUTL2205I --------  A      R/W  191   RTM191
VMFUTL2205I --------  B      R/O  5E5   MNT5E5
VMFUTL2205I --------  D      R/W  51D   MNT51D
VMFUTL2205I --------  Y/S    R/O  19E   MNT19E
VMFSET2760I VMFSETUP processing completed successfully

    3. Issue the VMFMRDSK to clear the alternate APPLY disk for the new service. This command will copy the contents of the 2A6 to the 2A2 (minidisk installs) or copy the contents of the VMSYS:5798DWDC.ALTAPPLY directory to the VMSYS:5798DWDC.PRDAPPLY directory (SFS installs). 
      VMFMRDSK 5798DWDC RTM     APPLY
                  RTMSFS

      Note: Use RTM if the product was installed on minidisk, or RTMSFS if the product was installed on SFS.

      The following is an example of the screen displayed after issuing the above VMFMRDSK command: 

      vmfmrdsk 5798dwdc rtm apply
VMFMRD2760I VMFMRDSK processing started
VMFMRD1937I Merge of APPLY started
VMFMRD1938I Merging APPLY 2A6 to 2A2
VMFMRD2065I APPLY 2A2 is now 3 percent full
VMFMRD1939I Merge of APPLY completed
VMFMRD2760I VMFMRDSK processing completed successfully

    4. Receive the service using the VMFREC command.

      Note: If you are receiving service from Service Link (electronic service) see Appendix B in the VM/ESA R2 Service Guide for information.:enote. All new service is loaded to the 2D2 disk/directory. 

      VMFREC PPF 5798DWDC RTM
                    RTMSFS

      Note: Use RTM if the product was installed on minidisk, or RTMSFS if the product was installed on SFS. 

      The following is an example of the screen displayed after issuing
the above VMFREC command:
vmfrec ppf 5798dwdc
VMFREC2760I VMFREC processing started
VMFREC1852I Volume 1 of 1 of COR nnnn created on 29 September 92
VMFREC1851I (1 of 3) VMFRCAXL processing AXLIST
VMFRCX2159I Loading 0 part(s) to DELTA 2D2 (H)
VMFREC1851I (2 of 3) VMFRCPTF processing PARTLST
VMFRCP2159I Loading 1 part(s) to DELTA 2D2 (H)
VMFREC1851I (3 of 3) VMFRCCOM processing DELTA
VMFRCC2159I Loading 1 part(s) to DELTA 2D2 (H)
VMFREC2189I Updating Requisite table 5798DWDC SRVREQT, Description table
            5798DWDC SRVDESCT and Receive Status table 5798DWDC SRVRECS with 1
            new PTFs from COR nnnn
VMFREC2760I VMFREC processing completed successfully

    5. Apply the new service. 
      VMFAPPLY PPF 5798DWDC RTM
                      RTMSFS

      Note: Use RTM if the product was installed on minidisk, or RTMSFS if the product was installed on SFS. 

      The following is an example of the screen displayed after issuing
the above VMFAPPLY command:
vmfapply ppf 5798dwdc rtm
VMFAPP2760I VMFAPPLY processing started
VMFAPP2106I Apply list RTMESA5 contains 1 PTFs that need to be applied and 0
            PTFs that are already applied
VMFAPP2102I 1 of 1 PTFs processed
VMFAPP2105I VMFAPPLY processing completed successfully.
            The Apply list RTMESA5 contains 1 PTFs.
            0 PTFs were already applied.
            1 PTFs applied successfully.
            0 PTFs were included.
            0 PTFs were excluded or require excluded PTFs.
            0 PTFs failed
VMFAPP2103I The Software Inventory has been updated on the 2A6 (F) disk

    6. Update the Build Status Table with serviced parts. 
      VMFBLD PPF 5798DWDC RTM (STATUS
                    RTMSFS

      Note: Use RTM if the product was installed on minidisk, or RTMSFS if the product was installed on SFS. 

      +---Note---------------------------------------------------------------------+

      The $PPF file, the main RTM control file for VMSES/E, can also be serviced. If the $PPF file has been serviced then you get the following prompt: 

      VMFBLD2185R The following source product parameter files have been
serviced:
VMFBLD2185R 5798DWDC $PPF
VMFBLD2185R When source product parameter files are serviced, all
            product parameter files built from them must be recompiled
            using VMFPPF before VMFBLD can be run.
VMFBLD2185R Enter zero (0) to have the serviced source product
            parameter files built to your A-disk and exit VMFBLD so
            you can recompile your product parameter files with VMFPPF
VMFBLD2185R Enter one (1) to continue only if you have already
            recompiled your product parameter files with VMFPPF

      Enter 0 and complete the following steps before you continue:

      0 

      
VMFPPF 5798DWDC RTM|RTMSFS
COPY 5798DWDC $PPF A = = D (OLDDATE   REPLACE
ERASE 5798DWDC $PPF A

      Note: Use RTM if the product was installed on minidisk, or RTMSFS if the product was installed on SFS.

      After issuing VMFPPF go back to issue the VMFBLD with the STATUS option once more. You may now give a response of '1' to the prompt. 

      +----------------------------------------------------------------------------+

    7. You can view the build requirements identified by SES from the previous command by viewing the message log on the A disk. To view the message log issue the following command: 
      VMFVIEW BUILD

      The following is an example of the screen displayed after issuing the above VMFVIEW command: 

      ST:VMFBLD1851I Reading build lists
ST:VMFBLD2182I Identifying new build requirements
ST:VMFBLD2182I New build req uirements identified
BD:VMFBLD2180I There are 6 build requirements remaining
BD:VMFBLD2180I Build Requirements:
BD:            Bldlist   Object             Status
BD:VMFBLD2180I RTMSRC    =.EXEC             SERVICED
BD:VMFBLD2180I RTMACLIB  RTMCALL            SERVICED
BD:VMFBLD2180I RTMASM    BLDLIST            SERVICED
BD:VMFBLD2180I RTMMOD    RTM.MODULE         SERVICED
BD:VMFBLD2180I           VMC.MODULE         SERVICED
BD:VMFBLD2180I           SNAPP.MODULE       SERVICED
ST:VMFBLD2760I VMFBLD processing completed successfully .

    8. Build RTM VM/ESA serviced parts. Use the VMFBLD command with the options given below: 

      +---If you are installing on VM/ESA Version 2 or later-----------------------+

      If you are installing on VM/ESA Version 2 or later you must have HLASM (5696-234) installed before you can complete the build. 

      +----------------------------------------------------------------------------+

      VMFBLD PPF 5798DWDC RTM    (SERVICED
                    RTMSFS

      Note: Use RTM if the product was installed on minidisk, or RTMSFS if the product was installed on SFS.

      See Appendix B. "Sample output from BUILD command." in this document for an example of the output from from this command.

      Issue the VMFVIEW BUILD command to view any error messages or remaining build requirements.

    9. Place the new service into production after testing.

      1. Copy the RTM VM/ESA code to 5798DWDC's 401 disk (production BUILD disk for minidisk install) or to the VMSYS:RTMESA. directory (production build directory for SFS install).

        • For minidisk install issue the following commands: 
          
ACCESS 400 E/E
ACCESS 401 F
COPYFILE RTM MODULE E = = F (OLDDATE REPLACE

          Note: The RTMESA server machine links to the 401 as 191 and therefore gets access to the new RTM module.:enote.

        • For SFS install issue the following commands: 
          
ACCESS VMSYS:5798DWDC.TBUILD E
ACCESS VMSYS:RTMESA. F (FORCERW
COPYFILE RTM MODULE E = = F (OLDDATE REPLACE

      2. You will also need to put the VMC MODULE into production.

        • For minidisk install issue the following commands: 
          
ACCESS 400 E/E
SENDFILE VMC MODULE E TO MAINT

        • For SFS install issue the following commands: 
          
ACCESS VMSYS:5798DWDC.TBUILD E
SENDFILE VMC MODULE E TO MAINT

        The MAINT owner should copy the VMC MODULE to the 19E disk. MAINT must also re-save CMS to put the 19E (Y-disk) back in shared status.

    RTM Product Rebuild

    If the RTM modules need to be rebuilt between servicing, select one or more of the following commands:

    • VMFSETUP 5798DWDC RTM|RTMSFS

      This will ensure the correct disk access order for building RTM.

    • VMFBLD PPF 5798DWDC RTM|RTMSFS RTMACLIB (ALL

      This will rebuild the RTM maclib.

    • VMFBLD PPF 5798DWDC RTM|RTMSFS RTMASM (ALL

      This will reassemble all the RTM assemble files.

    • VMFBLD PPF 5798DWDC RTM|RTMSFS RTMMOD (ALL

      This will build the RTM module, the VMC module and the SNAPP module.

    Note: Use RTM if the product was installed on minidisk, or RTMSFS if the product was installed on SFS.

    Whenever the above commands are issued, the new modules must be put into production. The instructions are as follows:

    1. Copy the RTM VM/ESA code to 5798DWDC's 401 disk (production BUILD disk for minidisk install) or to the VMSYS:RTMESA. directory (production build directory for SFS install).

      • For minidisk install issue the following commands: 
        
ACCESS 400 E/E
ACCESS 401 F
COPYFILE RTM MODULE E = = F (OLDDATE REPLACE

        Note: The RTMESA server machine links to the 401 as 191 and therefore gets access to the new RTM module.:enote.

      • For SFS install issue the following commands: 
        
ACCESS VMSYS:5798DWDC.TBUILD E
ACCESS VMSYS:RTMESA. F (FORCERW
COPYFILE RTM MODULE E = = F (OLDDATE REPLACE

    2. You will also need to put the VMC MODULE into production.

      • For minidisk install issue the following commands: 
        
ACCESS 400 E/E
SENDFILE VMC MODULE E TO MAINT

      • For SFS install issue the following commands: 
        
ACCESS VMSYS:5798DWDC.TBUILD E
SENDFILE VMC MODULE E TO MAINT

      The MAINT owner should copy the VMC MODULE to the 19E disk. MAINT must also re-save CMS to put the 19E (Y-disk) back in shared status.

    Non-VMSES/E Service Instructions

    This section of the Program Directory contains the procedure to install CORrective service to RTM VM/ESA on VM/ESA Release 1.1.

    The procedure for applying non-VMSES/E service depends on how the service is packaged. Some customers may receive non-VMSES/E envelopes (through IBMLINK for example), while some customers may receive a service tape with the PTFs on it. No matter how you receive your service, you should always make sure that the proper files are located on the appropriate disks. You should follow the instructions provided with the service obtained, but make sure you place the service files on the appropriate minidisks described below.

    Overview

    For non-VMSES/E envelopes, the envelopes should be unpacked and placed on a temporary minidisk. The files are then copied to the appropriate minidisks and the RTMBLD exec is invoked to rebuild the product.

    For cumulative service tapes, the tape is mounted and attached to 5798DWDC. The files on the tape are loaded to a temporary minidisk, and the product rename EXEC (called 5798DWDB) is run to rename the files and the files are then copied to the appropriate minidisk(s) and/or SFS directories. The RTMBLD exec is then invoked to rebuild the product.

    Installing Non-VMSES/E Service

    1. Define and format a temporary work disk to load the service on.

    2. Copy all of the AUXRTM5 files on the auxfile disk (2A6) or directory (VMSYS:5798DWDC.ALTAPPLY) to the backup auxfile disk (2A2) or directory (VMSYS:5798DWDC.PRDAPPLY) in case of any problems with newly applied service.

    3. Erase all of the AUXRTM5 files on the auxfile disk (2A6) or directory (VMSYS:5798DWDC.ALTAPPLY). Note that if you have any problems with the newly applied service, you can just copy all of the AUXRTM5 files from the backup disk/directory to the auxfile disk/directory and rebuild the product with RTMBLD.

    4. Receive the service

      How to receive the service depends on how your service is packaged, instructions are provided here for non-VMSES/E envelopes received electronically (through IBMLINK for example), and cumulative service tapes containing the PTFs. In all cases, refer to the instructions provided with the service on how to receive it.

      • Receiving Service For Non-VMSES Envelopes

        1. Receive product memos from envelope NLSTnnnn SERVLINK.

          Note: Depending on how you receive the service, you may have to unpack the PTF's with the VMUNPAC EXEC. Follow the instructions provided with your service.

          • VMFPLCD RST ENV=NLSTnnnn SERVLINK fm

            fm is the filemode where the envelope exists. The default is A. This command resets the logical position to the beginning of the envelope. The GLOBALV will also be updated with the name of the envelope so that the ENV= parameter will not be required for subsequent VMFPLCD commands.

          • VMFPLCD LOAD * * A (EOD

            This command receives the service documentation for the envelope.

        2. Receive the service for non-VMSES PTF envelopes NPTFnnnn SERVLINK.

          • VMFPLCD RST ENV=NPTFnnnn SERVLINK fm

            This command resets the logical position to the beginning of the envelope. The GLOBALV will also be updated with the name of the envelope so that the ENV= parameter will not have to be specified in subsequent VMFPLCD commands. fm is the file mode of the disk where the envelope exists. The default is the A-disk.

          • VMFPLCD SCAN prodid 010101 (EOD

            Locate the start of service in the envelope for the product to service. prodid is the RTM VM/ESA product id.

          • VMFPLCD LOAD * * fm (DISK

            fm is the filemode of the work disk you are installing service on.

      • Service Tape Format

        1. Issue the following commands to download the service to the temporary work disk. The first command listed here positions the tape and the second command loads the files. Here, fm is the file mode of the temporary work disk.

          • VMFPLC2 SCAN 5798DWDB 010101 (EOT

          • VMFPLC2 LOAD * * fm

        2. Rename the files on the temporary work disk with the following command. Again, fm is the file mode of the temporary work disk.

          • 5798DWDB fm

    5. COPYFILE all the AUXRTM5 files to the auxfile (2A6) disk or directory (VMSYS:5798DWDC.ALTAPPLY).

    6. COPYFILE all the update files to the update (2D2) disk or directory (VMSYS:5798DWDC.DELTA).

    7. COPYFILE any new source files (such as new COPY, MACRO or ASSEMBLE files) to the source (2B2) disk or directory (VMSYS:5798DWDC.SOURCE).

    8. COPYFILE all the full replacement parts (such as new build EXECs) to the test (400) disk or directory (VMSYS:5798DWDC.TBUILD).

      You may want to copy the RTMDISK EXEC and the RTMBLD EXEC to 5798DWDC 191 disk or top directory so that a rebuild of RTM can be done simply by typing RTMBLD without any accessing of disks. (RTMBLD accesses the product disks/directories automatically.).

    9. You may now delete the temporary disk.

    Re-building the product.

    RTMBLD is now run to complete the installation. If the newly applied service makes changes to any RTM MACRO or COPY files, then remember to answer 'YES' when RTMBLD asks if the RTMMESA5 MACLIB should be rebuilt. See "RTMBLD program" for further instructions regarding RTMBLD.

    If service was made to RTMVMC, then you must issue VMCLOAD after RTMBLD completes to rebuild the VMC module.

    RTM Product Rebuild

    If the RTM modules need to be rebuilt between servicing, simply reissue the RTMBLD command.

    Non-VMSES/E RTM Build Files

    The following is the list of files used to build non-VMSES/E RTM.

    • I5798DWD EXEC

      Loads the product from the install tape to the appropriate minidisks or SFS directories. The original version is provided on the GA product tape, and an updated version that provides SFS support is provided with APAR GC05109.

    • RTMDISK EXEC

      This lists the minidisk addresses and/or SFS directory names that contain the various types of RTM parts. This may be modified by the user, but care should be taken to ensure that the addresses in the RTMDISK EXEC match what is installed on the system. RTMBLD uses RTMDISK EXEC. This EXEC is provided with APAR GC05046 and a modified version that provides SFS support is supplied with APAR GC05109.

    • RTMBLD EXEC

      This will rebuild the RTMMESA5 MACLIB and RTM MODULE. This EXEC is provided on the GA product tape, and modified versions are provided with APARs GC05046 and GC05109.

    • RTMMESA5 EXEC

      This lists all RTM MACRO and COPY files to be included in the RTMMESA5 MACLIB. The RTMMESA5 MACLIB can be built with RTMBLD or it can be built by executing VMFMAC RTMMESA5 RTMESA5.

    • RTMLOAD EXEC

      This is the EXEC that takes the RTM TEXT decks and builds a new RTM MODULE. RTMBLD invokes RTMLOAD.

    • VMCLOAD EXEC

      This is the EXEC that takes the RTMVMC TEXT deck and builds a new VMC MODULE. RTMBLD DOES NOT invoke VMCLOAD.

    A single RTM ASSEMBLE file can be assembled by linking and accessing the various RTM disks and issuing VMFHASM RTMxxx RTMESA5.

    Whenever the above commands are issued, the new modules must be put into production. The instructions are as follows:

    1. Copy the RTM VM/ESA code to 5798DWDC's 401 disk (production BUILD disk for minidisk install) or to the VMSYS:RTMESA. directory (production build directory for SFS install).

      • For minidisk install issue the following commands: 
        
ACCESS 400 E/E
ACCESS 401 F
COPYFILE RTM MODULE E = = F (OLDDATE REPLACE

        Note: The RTMESA server machine links to the 401 as 191 and therefore gets access to the new RTM module.:enote.

      • For SFS install issue the following commands: 
        
ACCESS VMSYS:5798DWDC.TBUILD E
ACCESS VMSYS:RTMESA. F (FORCERW
COPYFILE RTM MODULE E = = F (OLDDATE REPLACE

    2. You will also need to put the VMC MODULE into production.

      • For minidisk install issue the following commands: 
        
ACCESS 400 E/E
SENDFILE VMC MODULE E TO MAINT

      • For SFS install issue the following commands: 
        
ACCESS VMSYS:5798DWDC.TBUILD E
SENDFILE VMC MODULE E TO MAINT

      The MAINT owner should copy the VMC MODULE to the 19E disk. MAINT must also re-save CMS to put the 19E (Y-disk) back in shared status.