RTM VM/ESA Program Directory
If you'd like to send feedback on this program directory you can:
Send e-mail to me at daileybc@us.ibm.com
Or send it to:
Bruce Dailey Dept G32 IBM Corp. 1701 North St. Endicott, NY 13760
+---Note!--------------------------------------------------------------------+
Before using this information and the product it supports, be sure
to read the general information under "Notices".
+----------------------------------------------------------------------------+
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:
+=============+=================+============================================+ | COMPIDs | Feature Numbers | | +=============+=================+============================================+ | 5798DWD00 | 5891 | | | | 5892 | | | | 5702 | | +-------------+-----------------+--------------------------------------------+
Table of Contents
Program and Service Level Information
Installation Requirements and Considerations
Appendix A. Applying Local Modifications to RTM VM/ESA.
Appendix B. Sample output from BUILD command.
Appendix C. Sample non-VMSES/E install from 9302 Refresh Tape
Appendix D. Sample Non-VMSES/E Install with CORrective Service Tape.
Notices
References in this document to IBM products, programs, or services do not imply that IBM intends to make these available in all countries in which IBM operates. Any reference to an IBM product, program, or service is not intended to state or imply that only IBM's product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe on any of IBM's intellectual property rights may be used instead of the IBM product, program, or service. Evaluation and verification of operation in conjunction with other products, except those expressly designated by IBM, is the user's responsibility.
IBM may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to the
IBM Director of Commercial RelationsIBM Corporation
Purchase, NY 10577
Trademarks and Service Marks
The following terms, denoted by an asterisk (*), used in this
document, are trademarks or service marks of IBM Corporation in
the United States or other countries:
IBM
VM/ESA
Realtime Monitor VM/ESA
Introduction
This program directory is intended for the system programmer responsible for program installation and maintenance. It contains information concerning the material and procedures associated with the installation of RTM VM/ESA. You should read all of this program directory before installing the program and then keep it for future reference.
The program directory contains the following sections:
- "Program Materials" identifies the basic and optional program materials and documentation for RTM VM/ESA.
- "Program Support" describes the IBM support available for RTM VM/ESA.
- "Program and Service Level Information" lists the APARs (program level) and PTFs (service level) incorporated into RTM VM/ESA.
- "Installation Requirements and Considerations" identifies the resources and considerations for installing and using RTM VM/ESA.
- "Installation Instructions" provides detailed installation instructions for RTM VM/ESA.
- "Service Instructions" provides detailed servicing instructions for RTM VM/ESA.
Before installing RTM VM/ESA, read "Preventive Service Planning". This section tells you how to find any updates to the information and procedures in this program directory.
Program Materials
An IBM program is identified by a program number. The program number for RTM VM/ESA is 5798-DWD.
The program announcement material describes the features supported by RTM VM/ESA. Ask your IBM marketing representative for this information if you have not already received a copy.
The following sections identify the basic and optional program materials available with this program.
Basic Machine-Readable Material
The distribution medium for this program is 9-track magnetic tape (written at 6250 BPI) and 3480 tape cartridge. The tape or cartridge contains all the programs and data needed for installation. See "Installation Instructions" for more information about how to install the program. Table 2. describes the tape or cartridge. Table 3.
Table 2. Basic Material: Program Tape
+==========+=========+===========+====================+======================+ | Feature | Medium | Physical | Tape Content | External Tape Label | | Number | | Volume | | | +==========+=========+===========+====================+======================+ | 5891 | 6250 | 1 | RTM 1.5.2 Base | RTM152 Base 1of1 | | | tape | | Product | | +----------+---------+-----------+--------------------+----------------------+ | 5892 | 3480 | 1 | RTM 1.5.2 Base | RTM152 Base 1of1 | | | cart. | | Product | | +----------+---------+-----------+--------------------+----------------------+ | 5702 | 4MM-DAT | 1 | RTM 1.5.2 Base | RTM152 Base 1of1 | | | Cartrid | | Product | | | | ge | | | | +----------+---------+-----------+--------------------+----------------------+
Table 3. Program Tape: File Content
+=======+==========================================================+=========+ | Tape | Content | Number | | File | | of | | | | files | +=======+==========================================================+=========+ | 1 | tape header | 10 | +-------+----------------------------------------------------------+---------+ | 2 | product header | 3 | +-------+----------------------------------------------------------+---------+ | 3 | service apply lists | 2 | +-------+----------------------------------------------------------+---------+ | 4 | PTFPARTs | 9 | +-------+----------------------------------------------------------+---------+ | 5 | RTM service (VMSES/E) | 78 | +-------+----------------------------------------------------------+---------+ | 6 | RTM service (VMSES/E) | 36 | +-------+----------------------------------------------------------+---------+ | 7 | RTM source code | 73 | +-------+----------------------------------------------------------+---------+ | 8 | RTM Maclib | 15 | +-------+----------------------------------------------------------+---------+ | 9 | VMC Module | 2 | +-------+----------------------------------------------------------+---------+ | 10 | RTM samples | 5 | +-------+----------------------------------------------------------+---------+ | 11 | RTM service (non-VMSES/E) | 56 | +-------+----------------------------------------------------------+---------+ | 12 | RTM service (non-VMSES/E) | 31 | +-------+----------------------------------------------------------+---------+
Program Publications
The following sections identify the basic and optional publications for RTM VM/ESA.
Basic Program Publications
One copy of the following publication is included when you order the basic materials for RTM VM/ESA. For additional copies, contact your IBM representative.
Table 4. Basic Material: Unlicensed Publications
+=============================================================+==============+ | Publication Title | Form Number | +=============================================================+==============+ | Realtime Monitor VM/ESA Program Description/Operations | SH26-7000 | | Manual | | +-------------------------------------------------------------+--------------+
Microfiche Support
There is no microfiche for RTM VM/ESA.
Publications Useful During Installation
If you are installing RTM VM/ESA on VM/ESA Version 2 Release 1, then you may find the following publications listed in Table 5. useful during installation. To order copies, contact your IBM representative.
Table 5. Publications Useful During Installation
+=============================================================+==============+ | Publication Title | Form Number | +=============================================================+==============+ | VMSES/E Introduction And Reference | SC24-5747 | +-------------------------------------------------------------+--------------+ | VM/ESA Service Guide | SC24-5749 | +-------------------------------------------------------------+--------------+
If you are installing RTM VM/ESA on VM/ESA Release 2, then you may find the following publications listed in Table 6. useful during installation. To order copies, contact your IBM representative.
Table 6. Publications Useful During Installation
+=============================================================+==============+ | Publication Title | Form Number | +=============================================================+==============+ | VMSES/E Introduction And Reference | SC24-5444 | +-------------------------------------------------------------+--------------+ | VM/ESA Service Guide | SC24-5527 | +-------------------------------------------------------------+--------------+
Program Support
This section describes the IBM support available for RTM VM/ESA.
Preventive Service Planning
Before installing RTM VM/ESA, check with your IBM Support Center or use either Information/Access or IBMLink (Service Link) to see whether there is additional Preventive Service Planning (PSP) information that you should know. To obtain this information, specify the following UPGRADE and SUBSET values:Table 7. PSP Upgrade and Subset ID
+==============+==============+=============+ | Release Code | Upgrade | Subset | +==============+==============+=============+ | 152 | VMRTMESA152 | RTMESA/152 | +--------------+--------------+-------------+ | F52 | VMRTMESA152 | RTMESA/F52 | +--------------+--------------+-------------+
If you have received RTM VM/ESA only from IBM Software Distribution, before installing RTM VM/ESA, you should also check with your IBM Support Center or use either Information/Access or SoftwareXcel Extended to see if there is additional PSP information that you should know.
Statement of Support Procedures
Report any difficulties you have using this program to your IBM Support Center. In the U.S.A., if an APAR is required, submit the data to the location identified in the Programming System General Information manual (PSGIM), G229-2228, as being responsible for the failing component.
Table 8. identifies the component ID (COMPID), Retain Release and Field Engineering Service Number (FESN) for RTM VM/ESA.
Table 8. Component IDs
+============+=============+==========+==========================+===========+ | Release | Retain | COMPID | Release | Component | | Code | | | | Name | +============+=============+==========+==========================+===========+ | 152 | 5798DWD00 | 152 | RTM VM/ESA 152 | 0991822 | +------------+-------------+----------+--------------------------+-----------+ | F52 | 5798DWD00 | F52 | RTM VM/ESA 152 | 0991822 | | | | | (non-VMSES/E) | | +------------+-------------+----------+--------------------------+-----------+
Program and Service Level Information
This section identifies the program and any relevant service levels of RTM VM/ESA. The program level refers to the APAR fixes incorporated into the program. The service level refers to the PTFs integrated. Information about the cumulative service tape is also provided.
Program Level Information
The following APAR fixes against previous releases of RTM VM/ESA have been incorporated into this release:
GC04908 GC04939 GC04458 GC04872 GC04868 GC04859 GC04794 GC04796 GC04788 GC04780 GC04769 GC04475 GC04731 GC04683 GC04634 GC04618
Service Level Information
The following APAR fixes to RTM VM/ESA 1.5.2 are incorporated into this product tape:
GC05012 GC05016 GC05041 GC05043 GC05045 GC05044 GC05026 GC05046 GC05103 GC05121 GC05109 GC05131 GC05143 GC05162 GC05182 GC05201 GC05219 GC05242 GC05262 GC05288 GC04959 GC04960 GC04949 GC05340 GC05354 GC05115 GC05357 GC05362 GC05363 GC05365 GC05374
Cumulative Service Tape
There is no cumulative service tape for RTM VM/ESA that ships with the product.
Installation Requirements and Considerations
The following sections identify the system requirements for installing and activating RTM VM/ESA.
System Requirements
This section describes the system environment required to install RTM VM/ESA.
Programming Requirements
RTM VM/ESA is assembled on the system on which it will run. It requires HASM or HLASM (5696-234). HASM is shipped with VM/ESA Version 1. There is no assembler shipped with VM/ESA Version 2 so HLASM must be installed before installing RTM VM/ESA on VM/ESA Version 2.
DASD Storage Requirements
RTM VM/ESA can be installed on either minidisks or SFS directories. The following is a listing of the default minidisks/directories required to install RTM VM/ESA. The shipped version of RTM VM/ESA is set up to install without any user modifications on the following minidisks or directories.
Install on Minidisks
The following table lists the userids, minidisks and their space requirements. Skip to the next section if you are installing on SFS.
Table 9. DASD Storage Requirements for Target Minidisks/Directories
+==============+==========+===============+===================+================+ | | | Storage in | | | | Minidisk | | Cylinders | Storage in Blocks | | | owner | Default +=======+=======+========+==========+ | | (userid) | Address | DASD | CYLS | Type | Blocks | Description | +==============+==========+=======+=======+========+==========+================+ | 5798DWDC | 2B2 | 9345 | 20 | FB512 | 24000 | Source disk. | | | | 3390 | 17 | 1K | 12000 | Contains RTM | | | | 3380 | 20 | 2K | 6000 | source files. | | | | 3375 | 20 | 4K | 3000 | | | | | 3350 | 20 | | | | +--------------+----------+-------+-------+--------+--------- +----------------+ | 5798DWDC | 2C2 | 9345 | 2 | FB512 | 2400 | Sample Files. | | | | 3390 | 2 | 1K | 1200 | | | | | 3380 | 2 | 2K | 600 | | | | | 3375 | 2 | 4K | 300 | | | | | 3350 | 2 | | | | +--------------+----------+-------+-------+--------+----------+----------------+ | 5798DWDC | 2D2 | 9345 | 15 | FB512 | 18000 | Update disk. | | | | 3390 | 13 | 1K | 9000 | Contains all | | | | 3380 | 15 | 2K | 4500 | update files | | | | 3375 | 15 | 4K | 2250 | for the | | | | 3350 | 15 | | | product. | +--------------+----------+-------+-------+--------+----------+----------------+ | 5798DWDC | 2A6 | 9345 | 5 | FB512 | 6000 | Auxfile disk. | | | | 3390 | 5 | 1K | 3000 | Contains the | | | | 3380 | 5 | 2K | 1500 | AUX files used | | | | 3375 | 5 | 4K | 750 | during a build | | | | 3350 | 5 | | | of the | +--------------+----------+-------+-------+--------+----------+----------------+ | 5798DWDC | 2A2 | 9345 | 10 | FB512 | 12000 | Staging disk. | | | | 3390 | 9 | 1K | 6000 | Used to save | | | | 3380 | 10 | 2K | 3000 | previous | | | | 3375 | 10 | 4K | 1500 | version of AUX | | | | 3350 | 10 | | | files. | +--------------+----------+-------+-------+--------+----------+----------------+ | 5798DWDC | 191 | 9345 | 10 | FB512 | 12000 | Work disk. | | | | 3390 | 9 | 1K | 6000 | Used to | | | | 3380 | 10 | 2K | 3000 | temporarily | | | | 3375 | 10 | 4K | 1500 | store files | | | | 3350 | 10 | | | created during | +--------------+----------+-------+-------+--------+----------+----------------+ | 5798DWDC | 401 | 9345 | 10 | FB512 | 12000 | Server | | | | 3390 | 9 | 1K | 6000 | machines A | | | | 3380 | 10 | 2K | 3000 | disk. Used to | | | | 3375 | 10 | 4K | 1500 | store the | | | | 3350 | 10 | | | production | +--------------+----------+-------+-------+--------+----------+----------------+ | 5798DWDC | 400 | 9345 | 15 | FB512 | 18000 | Test disk. | | | | 3390 | 13 | 1K | 9000 | Used to store | | | | 3380 | 15 | 2K | 4500 | object files | | | | 3375 | 15 | 4K | 2250 | created during | | | | 3350 | 15 | | | product build. | +--------------+----------+-------+-------+--------+----------+----------------+ | RTMESA | n/a | 9345 | n/a | n/a | n/a | n/a | | | | 3390 | n/a | n/a | n/a | | | | | 3380 | n/a | n/a | n/a | | | | | 3375 | n/a | n/a | n/a | | | | | 3350 | n/a | | | | +--------------+----------+-------+-------+-----------+-------+----------------+
Note: For non-VMSES/E installations, the number of required minidisks may be changed by the installation in order to decrease the amount of total DASD space used. Refer to section "Changing the Default Minidisks" for details on how this is done.
Install on SFS Directories
The following table lists the userids, directories and the total filepool space requirements in 4K blocks. Skip this section if you are installing on minidisk.
Table 10. SFS Directory Requirements
+============+================================+================================+ | Directory | Directory name | Description | | owner | | | | (userid) | | | +============+================================+================================+ | 5798DWDC | VMSYS:5798DWDC.SOURCE | Source directory. Contains RTM | | | | source files. | +------------+--------------------------------+--------------------------------+ | 5798DWDC | VMSYS:5798DWDC.SAMPLE | Sample Files. | +------------+--------------------------------+--------------------------------+ | 5798DWDC | VMSYS:5798DWDC.DELTA | Update directory. Contains all | | | | update files for the product. | +------------+--------------------------------+--------------------------------+ | 5798DWDC | VMSYS:5798DWDC.ALTAPPLY | Auxfile directory. Contains | | | | the AUX files used during a | | | | build of the product. | +------------+--------------------------------+--------------------------------+ | 5798DWDC | VMSYS:5798DWDC.PRDAPPLY | Staging directory. Used to | | | | save previous version of AUX | | | | files. | +------------+--------------------------------+--------------------------------+ | 5798DWDC | VMSYS:5798DWDC. | Work directory. Used to | | | | temporarily store files | | | | created during build of | | | | product. | +------------+--------------------------------+--------------------------------+ | 5798DWDC | VMSYS:5798DWDC.TBUILD | Test disk. Used to store | | | | object files created during | | | | product build. | +------------+--------------------------------+--------------------------------+ | RTMESA | VMSYS:RTMESA. | Server machines A directory. | | | | Used to store the production | | | | version of RTM VM/ESA | +------------+--------------------------------+--------------------------------+
Filepool Space Requirements
The filepool space requirements in filepool VMSYS will be 1500 4K blocks for user RTMESA and 11,500 blocks for user 5798DWDC.
Additional Considerations
User 5798DWDC will need to copy files to the VMSYS:RTMESA. directory, ensure that this user has the proper authority to do so.
Userid Requirements
RTM VM/ESA requires two userids. 5798DWDC is used for installation and service. This userid requires access to CP maclibs: HCPOM1, HCPOM2, HCPPSI and HCPGPI. By default, these are located on the MAINT 190 and 193 disks. If this is not correct for your system, ensure that the disks that do contain these maclibs are accessible to user 5798DWDC. In addition, RTM VM/ESA requires access to the DMSGPI maclib and the H-assembler. By default, these files are located on the MAINT 190 and 19E disks. Again, if this is does not reflect your system, ensure that the disks containing the DMSGPI maclib and the H-assembler are accessible to user 5798DWDC. If you are installing RTM VM/ESA on VM/ESA Release 1.1, then you also need a link to MAINT 5E5 disk for the INSTFPP EXEC. RTMESA is the product server machine. It requires class E privilege because RTM accesses CP control block data areas during execution.
Note: Wherever the locations of your maclibs and H-assembler are, you must ensure that they are on minidisks or directories that are accessed when the product is built. For VMSES/E installations, this is done by simply accessing the minidisks or directories before invoking the build commands. For non-VMSES/E installations, this is done either by accessing the minidisks or directories manually or by specifying the disks or directories before invoking the RTMBLD command.
CP Directory Entries for Minidisk Install
Skip to next section if installing on SFS
Following are sample directory statements for these userids. Note that the actual LINK statements you use will depend on the location of the CP maclibs required for the build of RTM VM/ESA and the address of the disk where the H-assembler is installed. The actual MDISK statements that you use will depend on the type of DASD you install the product on. With CMS12 (VM/ESA Version 2 Release 1) the MACHINE 370 is no longer supported and MACHINE XA must be used. If running CMS11 on VM/ESA Version 2 Release 1 MACHINE 370 must be used.
USER 5798DWDC xxxxx 16M 16M G MACHINE 370 (for VM/ESA Release 2.2 or earlier releases only) MACHINE XA (for VM/ESA Version 2 Release 1 or later releases only) ACCOUNT xxxx IPL CMS CONSOLE 0009 3215 SPOOL 000C 2540 READER * SPOOL 000D 2540 PUNCH A SPOOL 000E 1403 A LINK MAINT 193 193 RR LINK MAINT 51D 51D MR (for VM/ESA Release 2 or later releases only) LINK MAINT 5E5 5E5 RR LINK MAINT 190 190 RR LINK MAINT 19D 19D RR LINK MAINT 19E 19E RR MDISK 191 3380 xxx 010 xxxxxx MR MDISK 2B2 3380 xxx 020 xxxxxx MR MDISK 2C2 3380 xxx 002 xxxxxx MR MDISK 2D2 3380 xxx 015 xxxxxx MR MDISK 2A6 3380 xxx 005 xxxxxx MR MDISK 2A2 3380 xxx 010 xxxxxx MR MDISK 400 3380 xxx 015 xxxxxx MR MDISK 401 3380 xxx 010 xxxxxx MR *
USER RTMESA xxxxx 32M 32M EG *USER RTMESA xxxxx 16M 16M EG (for VM/ESA Version 1.2.2 or earlier) OPTION QUICKDSP MACHINE 370 (for VM/ESA Version 1.2.2 or earlier releases only) MACHINE XA (for VM/ESA Version 2 Release 1 or later releases only) SHARE ABSOLUTE 3% AUTOLOG AUTOLOG1 MAINT OPERATOR ACCOUNT xxxx IPL CMS CONSOLE 0009 3215 SPOOL 000C 2540 READER * SPOOL 000D 2540 PUNCH A SPOOL 000E 1403 A LINK MAINT 190 190 RR LINK MAINT 19D 19D RR LINK MAINT 19E 19E RR LINK 5798DWDC 401 191 MR
CP Directory Entries for SFS Install
Skip this next section if installing on minidisk
Following are sample directory statements for these userids Note that the actual LINK statements you use will depend on the location of the CP maclibs required for the build of RTM VM/ESA and the address of the disk where the H-assembler is installed.
USER 5798DWDC xxxxx 16M 16M G MACHINE 370 (for VM/ESA Release 2.2 or earlier releases only) MACHINE XA (for VM/ESA Version 2 Release 1 or later releases only) ACCOUNT xxxx IPL CMS PARM FILEPOOL VMSYS: CONSOLE 0009 3215 SPOOL 000C 2540 READER * SPOOL 000D 2540 PUNCH A SPOOL 000E 1403 A LINK MAINT 193 193 RR LINK MAINT 51D 51D MR (for VM/ESA Release 2 or later releases only) LINK MAINT 5E5 5E5 RR LINK MAINT 190 190 RR LINK MAINT 19D 19D RR LINK MAINT 19E 19E RR *
USER RTMESA xxxxx 32M 32M EG *USER RTMESA xxxxx 16M 16M EG (for VM/ESA Version 1.2.2 or earlier) OPTION QUICKDSP MACHINE 370 (for VM/ESA Version 1.2.2 or earlier releases only) MACHINE XA (for VM/ESA Version 2 Release 1 or later releases only) SHARE ABSOLUTE 3% AUTOLOG AUTOLOG1 MAINT OPERATOR ACCOUNT xxxx IPL CMS PARM FILEPOOL VMSYS: CONSOLE 0009 3215 SPOOL 000C 2540 READER * SPOOL 000D 2540 PUNCH A SPOOL 000E 1403 A LINK MAINT 190 190 RR LINK MAINT 19D 19D RR LINK MAINT 19E 19E RR
Program Considerations
The following sections list the programming considerations for installing RTM VM/ESA and activating its functions.
Operating System Requirements
The following operating systems support RTM VM/ESA.
- VM/ESA Version 2 Release 1
- VM/ESA Release 2.2
- VM/ESA Release 2.1
The following are notes concerning VM/ESA releases no longer supported:
VM/ESA Release 2 - Requires VMSES/E APAR VM56361 to install RTM VM/ESA from the 9302 refresh product tape.
RTM VM/ESA will run on the following operating system if RTM APAR GC05046 is applied:
- VM/ESA Release 1.1
System Considerations
If RTM VM/ESA is being installed on VM/ESA Release 2 or later releases, then the product should be installed according to the instructions listed in "Installation with VMFINS (VMSES/E)"
With APAR GC05046, RTM VM/ESA will run on VM/ESA Release 1.1 which requires a non-VMSES/E installation. Refer to the installation instructions listed in "Installation with INSTFPP (Non-VMSES/E)".
Note: The VM Release Compatability Information has been moved to the RTM VM/ESA Operations Manual available 6/94.
Installation Instructions
Installing RTM VM/ESA
If RTM VM/ESA is being installed on VM/ESA Release 2 or later releases, then the product should be installed according to the instructions listed in "Installation with VMFINS (VMSES/E)"
With APAR GC05046, RTM VM/ESA will run on VM/ESA Release 1.1 which requires a non-VMSES/E installation. Refer to the installation instructions listed in "Installation with INSTFPP (Non-VMSES/E)". You must order and apply the latest service for RTM VM/ESA before completing the build step on a VM/ESA Release 1.1 system.
Installation with VMFINS (VMSES/E)
Note: VM APAR VM56361 is required to install the product from the 9302 refresh tape. Note: VM56361 is included the base for VM/ESA 1.2.1 and subsequent releases.
Follow these instructions ONLY if installing on VM/ESA Release 2 or later releases.
VMFINS can be used to install RTM VM/ESA. VMFINS is an installation aid supplied as part of VMSES/E with VM/ESA 1.2.0 to make installation of VM products consistent.
For a complete description of all VMFINS installation options refer to the VMSES/E Introduction and Reference (SC24-5444). The "Install Scenarios" chapter illustrates how various VMFINS operands and options are used.
You may plan the install of the product from a general userid that has access to the minidisks named in steps 3 and 4 below. The plan function of the install will generate a 'PLANINFO' file listing all:
- the userid/mdisks requirements
- required products
+---Plan---------------------------------------------------------------------+
To plan the product install use the following steps:
+----------------------------------------------------------------------------+
- Log on to userid 5798DWDC.
Note: The userid used must have access to the 2 minidisks listed in steps 3 and 4 below.:enote.
- Mount the installation tape and attach it as virtual device 181.
- Link and access the minidisks that contain the DMSGPI maclib and H-assembler if they are different than the 190 and 19E disks.
- Link and access the MAINT 5E5 disk as filemode B in read mode.
- Link and access the MAINT 51D disk as filemode D in read/write mode.
- Format all the required minidisks or create all of the SFS directories defined in "DASD Storage Requirements". If you are installing on SFS, be sure to give user 5798DWDC authority to create and replace files in the VMSYS:RTMESA. directory.
- Issue the following VMSES/E command with the INFO option.
This command will load the product memos and product's VMSES/E
control files to MAINT's 51D disk. It will also load a 5798DWDC
PRODLIST to your A-disk or directory
that lists all products included on the
tape.
VMFINS INSTALL INFO (NOMEMO
The NOMEMO option will load the memos but will not issue a prompt to send them to the system printer. Use MEMO if you wish to be prompted for printing the memo.
The following is an example of the screen displayed after issuing the above VMFINS command:
vmfins install info ( nomemo VMFINS2760I VMFINS processing started VMFINS1909I VMFINS PRODLIST created on your A-disk VMFINS2760I VMFINS processing completed successfully
- Use the VMFINS INSTALL command with the PLAN
option to get useful resource planning information. The product
will not be loaded at this time.
Do this by issuing:
VMFINS INSTALL PPF 5798DWDC RTMINS (ADD PLAN NOMEMO RTMINSSFSNote: Use RTMINS if installing the product on minidisk, or RTMINSSFS if installing the product on SFS.
- The ADD option indicates that you want to add a new copy of RTM VM/ESA to your system.
- The PLAN option indicates that you want VMFINS to perform requisite checking, plan system resources, and provide an opportunity to override the defaults in the product parameter file. Your override can change the name of your product parameter file or change the default userids, disk addresses and/or directory names.
The following is an example of the screen displayed after issuing the above VMFINS command:
vmfins install ppf 5798DWDC rtmins (add plan nomemo VMFINS2760I VMFINS processing started VMFREQ2805I Product 5798DWDC component RTM passed requisite checking Do you want to create an override for 5798DWDC RTM (prodid 5798DWDC) Enter 0 (No), 1 (Yes) or 2 (Exit) 0 VMFRMT2760I VMFRMT processing started VMFRMT2760I VMFRMT processing completed successfully VMFPLA1909I 5798DWDC PLANINFO created on your A-disk VMFINS2760I VMFINS processing completed successfully
Use the '1' option if you wish to make changes to the default installation configuration for RTM VM/ESA.
-
Use the planning information in the 5798DWDC PLANINFO file, created in
the PLAN step, to create the required userids and minidisks
with VM/Dirmaint or an equivalent CP directory maintenance
method.
Note: Make sure the minidisks are formatted before beginning the install.
+---Install------------------------------------------------------------------+
You are now ready to install RTM VM/ESA
+----------------------------------------------------------------------------+
-
To install RTM VM/ESA
run the VMFINS INSTALL command.
The next command assumes you are logged onto 5798DWDC userid, the default userid for RTM VM/ESA. If you chose to change the default userid/minidisks, etc. you should now logon to the userid you chose before issuing the following command.
Note: Make sure the MAINT 5E5 is accessed R/O at filemode B, and MAINT 51D is accessed R/W at filemode D before beginning this step.
VMFINS INSTALL PPF 5798DWDC RTMINS (ADD NOMEMO NOLINK RTMINSSFSNote: Use RTMINS if installing the product on minidisk, or RTMINSSFS if installing the product on SFS.
- The ADD option indicates that you want to add a new copy of RTM VM/ESA to your system.
- The NOLINK option indicates that you don't want VMFINS to link to the appropriate minidisks, only access them if not accessed. These are the minidisks defined in the :DCL section of the PPF file.
- The NOMEMO option indicates that you do not want to print the Memo-to-Users if it was already printed in the planning step.
The following is an example of the screen displayed after issuing the above VMFINS command:
VMFINS2760I VMFINS processing started VMFREQ2805I Product 5798DWDC component RTM passed requisite checking Do you want to create an override for 5798DWDC RTM (prodid 5798DWDC)? Enter 0 (No), 1 (Yes) or 2 (Exit) 0 VMFINT2760I VMFINST processing started VMFLDP2706I 5798DWDC RTM (prodid 5798DWDC) will be processed as a PDI product 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 579191 VMFUTL2205I -------- B R/O 5E5 MNT5E5 VMFUTL2205I -------- D R/W 51D MNT51D VMFUTL2205I -------- Y/S R/O 19E MNT19E VMFSET2760I VMFSETUP processing completed successfully VMFREC2760I VMFREC processing started VMFREC1851I (1 of 8) VMFRCAXL processing AXLIST VMFRCX2159I Loading 0 part(s) to DELTA 2D2 (H) VMFREC1851I (2 of 8) VMFRCPTF processing PARTLST VMFRCP2159I Loading 0 part(s) to DELTA 2D2 (H) VMFREC1851I (3 of 8) VMFRCCOM processing DELTA VMFRCC2159I Loading 0 part(s) to DELTA 2D2 (H) VMFREC1851I (4 of 8) VMFRCALL processing APPLY VMFRCA2159I Loading part(s) to APPLY 2A6 (F) VMFRCA2159I Loaded 19 part(s) to APPLY 2A6 (F) VMFREC1851I (5 of 8) VMFRCALL processing SOURCE VMFRCA2159I Loading part(s) to BASE1 2B2 (M) VMFRCA2159I Loaded 73 part(s) to BASE1 2B2 (M) VMFREC1851I (6 of 8) VMFRCALL processing RTMMAC VMFRCA2159I Loading part(s) to BUILD0 400 (I) VMFRCA2159I Loaded 1 part(s) to BUILD0 400 (I) VMFREC1851I (7 of 8) VMFRCALL processing VMCMOD VMFRCA2159I Loading part(s) to BUILD0 400 (I) VMFRCA2159I Loaded 1 part(s) to BUILD0 400 (I) VMFREC1851I (8 of 8) VMFRCALL processing SAMPLE VMFRCA2159I Loading part(s) to LOCALSAM 2C2 (E) VMFRCA2159I Loaded 5 part(s) to LOCALSAM 2C2 (E) VMFREC2760I VMFREC processing completed successfully VMFINT2760I VMFINST processing completed successfully VMFINS2760I VMFINS processing completed successfullyYou may be prompted for additional information during VMFINS INSTALL processing depending on your installation environment. If you are unsure how to respond to a prompt refer to the "Installing Products with VMFINS" and "Install Scenarios" chapters in the VMSES/E Introduction and Reference to decide how to proceed.
When processing is complete, you see the message:
VMFINS2760I VMFINS processing completed successfully
+---If you have service to apply to RTM/ESA----------------------------------+
If you have a service tape to apply to RTM/ESA go to HREF="#Section_8.0">"Service Instructions" to complete the installation
+----------------------------------------------------------------------------+
-
Build the new RTM VM/ESA using the following command:
+---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.
+----------------------------------------------------------------------------+
VMFINS BUILD PPF 5798DWDC RTMINS (ALL NOLINK RTMINSSFSNote: Use RTMINS if installing the product on minidisk, or RTMINSSFS if installing the product on SFS.
The ALL option for VMFINS BUILD will build all RTM VM/ESA 152 objects, regardless of whether they include service.
Note: See Appendix B. "Sample output from BUILD command." for output from the VMFINS BUILD command.:enote.
+---Post install-------------------------------------------------------------+
Put RTM VM/ESA into production when testing is completed.
+----------------------------------------------------------------------------+
- 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
- For minidisk install issue the following commands:
-
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.
- For minidisk install issue the following commands:
Additional information about using VMFINS can be found in the VMSES/E Introduction and Reference.
The RTM VM/ESA product is now installed and built on your system.
Go to "Activating the Program" for instructions on activating the program.
Installation with INSTFPP (Non-VMSES/E)
Follow these instructions ONLY if installing on VM/ESA Release 1.1.
This section provides great detail on the non-VMSES/E install process including how to modify some installation defaults. It is recommended that you read this section before starting an actual install of the product. For an example of a non-VMSES/E install with the GA product tape with a cumulative service tape applied, see appendix D. For an example of a non-VMSES/E install from the 9302 refresh product tape see appendix C. For instructions on how to apply local modifications to the RTM VM/ESA source code, see appendix A.
The non-SES build EXECs (RTMBLD and RTMDISK) are used to build RTM VM/ESA. These EXECs were designed to allow modification of the default installation setup; however, it is recommended, especially for a first time install, that you follow these instructions to avoid any problems.
Note: These EXECs are not on the GA product tape, they are supplied with APAR GC05046; thus, APAR GC05046 must be applied before building the product. In addition, serviced versions that include support for install on SFS directories are provided with APAR GC05109. The build EXECs are on the 9302 refresh product tape, which contains PTFs for APARS GC05046 and GC05109. In addition, the 9302 refresh tape contains a serviced install EXEC (I5798DWD). The instructions provided here are for the 9302 refresh product tape install and the GA level product install AFTER the PTFs for APARs GC05046 and GC05109 have been applied. Differences in the install process between the GA product tape and the 9302 refresh product tape will be noted by GA level installs.
Overview of non-SES installation.
Here is an overview of what will happen during a non-SES install of RTM VM/ESA.
- Minidisks/SFS directories and CP directory entries are defined according to instructions provided in "System Requirements".
- If installing on minidisk, minidisks are formatted.
- Tape is mounted and attached to 5798DWDC as 181.
- User invokes INSTFPP which invokes I5798DWD (or alternatively I5798DWD can be invoked without INSTFPP)
- I5798DWD will ask the user if the install will be to the
default minidisks, the default directories, or if the user would
like to override the deaults.
- If the user wants to override the defaults, they will be prompted for the addresses of the source, test, sample, auxfile, and update disk.
Note: GA Level Installs - You will always be prompted for the disk addresses of the sample, source and test disks. There is no service on the GA level product tape, so the auxfile and update disks are left untouched by I5789DWD EXEC. Please refer to the section "GA Level Installs (I5798DWD)" for details on how to install from the GA product tape. Also see appendix D for an example of an install from the GA product tape.
- I5798DWD will download all the files from the install tape to minidisk or SFS directories.
- If required, install service (see "Non-VMSES/E Service Instructions" for more information.) and/or apply local modifications (see Appendix A. "Applying Local Modifications to RTM VM/ESA." for information on how to change the RTM source code).
- Invoke RTMBLD to build the product.
Overview of RTMBLD:
- RTMBLD accesses all of the minidisks and/or SFS directories required for the build of the product. RTMBLD uses the RTMDISK EXEC to determine the minidisk addresses or SFS directory names are that will contain the RTM source files, update files, etc.. If desired, you may modify RTMDISK EXEC to change the default locations of these files. Note that if you changed the locations where these files go during the install (I5798DWD), then you must change this file to match where you installed the product.
- RTMBLD asks if the RTMMESA5 MACLIB should be rebuilt. If service has been applied then you should answer YES. If YES was specified then the MACLIB gets rebuilt.
- RTMBLD assembles all the RTM source files.
- RTMBLD invokes RTMLOAD to build a new RTM MODULE.
Note: A new VMC MODULE is not created as part of the build since one is supplied with the install tape. If service has been applied to RTMVMC ASSEMBLE file, then after the build completes you should issue VMCLOAD to build a new VMC MODULE.
Pre-installation instructions
The RTMDISK EXEC (APARs GC05046 and GC05109 required) lists all the default minidisk addresses for install of the product. If you installed the product on different minidisks than the defaults, or the CP maclibs on your system do not reside on MAINT 193 and 190 disks, or you are installing on SFS directories, then you MUST edit this file. The default install addresses listed in RTMDISK EXEC are shown below. Notice that the default SFS directories are commented out. If you are installing on SFS directories, then you should uncomment the lines that define the SFS directories, and comment out the lines that specify minidisks.
source_disk='2B2' /* RTM source files, such as ASSEMBLE .. */ test_disk='400' /* RTM executables such as TEXT decks... */ update_disk='2D2' /* RTM update files for RTM service */ auxfile_disk='2A6' /* All AUX files for RTM go here */ work_disk='191' /* Work disk for build - REQUIRED! */ /* source_disk='VMSYS:5798DWDC.SOURCE' */ /* test_disk='VMSYS:5798DWDC.TBUILD' */ /* update_disk='VMSYS:5798DWDC.DELTA' */ /* auxfile_disk='VMSYS:5798DWDC.ALTAPPLY' */ /* work_disk='VMSYS:5798DWDC.' */ CPmac_disk='193'; CPmac_owner='MAINT' /* CP maclib disks. */Even if you are installing RTM VM/ESA on the default minidisks owned by 5798DWDC, please check to make sure that the disks containing the CP maclibs HCPOM1 and HCPOM2 is correctly identified for your system.
Changing the RTMDISK EXEC
The RTMDISK EXEC must conform to REXX coding rules. The RTMDISK EXEC MUST contain valid source_disk, test_disk, work_disk, update_disk and auxfile_disk entries or the RTMBLD exec will halt with an error indication.
If you change the default addresses of the source, test, update, auxfile or work disks, simply specify their new addresses or SFS directory names (SFS support requires APAR GC05109). If APAR GC05109 is applied, then the CPmac_disk/CPmac_owner lines may be repeated. Thus, if your system has the CP maclibs spread across multiple minidisks or SFS directories, simply include a CPmac_disk/CPmac_owner line for each one. Note that the 9302 refresh tape contains the PTF for APAR GC05109.
If APAR GC05109 is NOT applied, then the RTMBLD EXEC will only recognize one CPmac_disk/CPmac_owner line (you can only specify one minidisk). In this case, you will have to link and access any additional minidisks or SFS directories required for the build by hand.
If you are installing some or all of the files in SFS directories, then you must provide the FULL length directory name. For example, if the source files were to be placed in 5798DWDC.SOURCE directory in filepool VMSYS, the RTMDISK EXEC would contain:
:
:
source_disk='VMSYS:5798DWDC.SOURCE'
:
:
If the CP maclibs reside in SFS directories, you do not
need to specify a CPMac_owner entry (since it is redundant).
For example, if the CP maclibs were stored in a directory
called MAINT.MACS in filepool VMSYS, the RTMDISK EXEC
would contain:
:
:
Cpmac_disk='VMSYS:MAINT.MACS'
:
:
RTM assumes the DMSGPI maclib is on the 190 disk and the H-assembler is on the 19E disk. If they are not and APAR GC05109 is applied, then you can include CPmac_disk/CPmac_owner lines in the RTMDISK EXEC so that the proper disks are accessed. If APAR GC05109 is not applied, you must link and access the minidisks or SFS directories before invoking RTMBLD.
Note: You should not specify the 190 or 19E disk in the RTMDISK EXEC, they are assumed to be accessed.
Changing the Default Minidisks
By default, the non-SES installation uses the same minidisks as the VMSES/E installation. Some installations may find it desirable to consolidate the number of minidisks used to hold the product, or install the product in SFS directories to reduce DASD space requirements. This may be accomplished by consolidating the files from the various minidisks onto fewer (larger) minidisks or installing the product in SFS directories, and changing the RTMDISK EXEC. You can use as few as one minidisk or SFS directory when installing the product in the non-VMSES/E manner.
Changing the Defaults Before Installation
If you have not yet installed the product, then you should plan to use at least 40 cylinders of 3380 DASD (or equivalent amount of space for other DASD types) and must decide where the product files should reside. The build EXEC groups the files into 5 categories: source files, AUX files, update files, test files (object code), and work files. There is a minidisk address or SFS directory name defined for each type. You may change any of the defaults in the RTMDISK EXEC. To do so, you must create the SFS directories and/or define the minidisks that you will install the product on. If you install on minidisks, then you must format them before installing the product. When you run the install exec (I5798DWD), specify the minidisk addresses or SFS directory names you have choosen for the various files instead of the defaults.
If you have a service tape, then apply the service. Next, change the RTMDISK EXEC to match the changes you made to your minidisk/directory layout and then invoke the RTMBLD EXEC.
Changing the Defaults After Installation
This case assumes you have already successfully installed the product on the default minidisks. To consolidate the various files onto fewer minidisks, or to install the product on SFS directories, you must define new minidisks or directories to hold the files or increase the sizes of the ones that you will use to hold the consolidated files. Consolidate the files (with the CMS COPYFILE command) and then change the RTMDISK EXEC to match the new minidisk/directory configuration and reinvoke RTMBLD to ensure that you can rebuild the product successfully.
Example RTMDISK EXEC with Changes
Here's an example of an RTMDISK EXEC that is used by an installation that decided to install the product in SFS directories and combined all RTM update files and AUX files onto one directory. This installation has the CP maclibs on two disks - MAINT 193 and MAINT 194. In this example, the filepool is called SERVER.
source_disk='SERVER:5798DWDC.SOURCE' test_disk='SERVER:5798DWDC.TEST' update_disk='SERVER:5798DWDC.SERVICE' auxfile_disk='SERVER:5798DWDC.SERVICE' work_disk='SERVER:5798DWDC.' CPmac_disk='193'; CPmac_owner='MAINT' CPmac_disk='194'; CPmac_owner='MAINT'
Non-VMSES/E Installation Instructions.
- Format required minidisks.
Once the directory entry and minidisks are defined for the product install, log on 5798DWDC and format the minidisks:
FORMAT 191 A (BLK 4K
Format all of the other required minidisks.Note: Skip this step if installing the product in SFS directories.
- Mount product tape in available tape drive and attach tape to 5798DWDC as 181.
- Invoke installation program
- The following steps should be performed only if you are installing
the product with INSTFPP on a VM/ESA system. INSTFPP resides
on MAINT's 5E5 disk by default on VM/ESA systems.
ACCESS 5E5 B INSTFPP 5798DWDC
- The following steps should be performed only if you are installing
the product without INSTFPP. Note that the VMFPLC2 LOAD command is
issued twice to position the tape at the beginning of file 3.
VMFPLC2 LOAD VMFPLC2 LOAD I5798DWD
- The following steps should be performed only if you are installing
the product with INSTFPP on a VM/ESA system. INSTFPP resides
on MAINT's 5E5 disk by default on VM/ESA systems.
Installation program I5798DWD
Note: If you are installing the program from the GA level product tape, then skip to section "GA Level Installs (I5798DWD)" for instruction on how to install the product.
I5798DWD will ask the user if they wish to install the product on the default mindisks, the default SFS directories, or override the defaults and specify their own configuration.
If you want to override the defaults, I5798DWD will prompt you for the minidisk addresses or SFS directory names that will contain the RTM VM/ESA source, sample, test, AUX and update disks. If you are installing the product in SFS directories, make sure you specify the full directory name in the format:
filepool:userid.directory ...
Two examples are shown here, in the first example, the user
chose to install the product on the default minidisks, and the
second example shows a user who decided to override the installation
defaults.
Example 1
I5798DWD ******************************************************** *** Please choose one of the following install options: *** *** 1. Enter '1' to install the product on the default *** minidisks. *** 2. Enter '2' to install the product on the default *** SFS directories. *** 3. Enter '3' to override the installation defaults. *** You will be prompted for the minidisk addresses *** or SFS directory names that the product will *** be installed on. *** *** 1 ************************************************************* *** *** Press ENTER to install RTM VM/ESA on the following disks: *** *** All RTM VM/ESA source files will be loaded on 2B2 disk/dir *** All RTM VM/ESA test files will be loaded on 400 disk/dir *** All RTM VM/ESA sample files will be loaded on 2C2 disk/dir *** All RTM VM/ESA update files will be loaded on 2D2 disk/dir *** All RTM VM/ESA AUX files will be loaded on 2A6 disk/dir *** *** Enter QUIT to exit ***At this point, the product will be installed on the default minidisks.
Example 2
I5798DWD ******************************************************** *** Please choose one of the following install options: *** *** 1. Enter '1' to install the product on the default *** minidisks. *** 2. Enter '2' to install the product on the default *** SFS directories. *** 3. Enter '3' to override the installation defaults. *** You will be prompted for the minidisk addresses *** or SFS directory names that the product will *** be installed on. *** *** 3 ******************************************************** *** Enter the minidisk address or full SFS directory *** name that will contain the RTM source files. Press *** ENTER to install the files on the default 2B2 disk.******************************************************** *** Enter the minidisk address or full SFS directory *** name that will contain the RTM test files. Press *** ENTER to install the files on the default 400 disk. 191 ******************************************************** *** Enter the minidisk address or full SFS directory *** name that will contain the RTM sample files. Press *** ENTER to install the files on the default 2C2 disk. 191 ******************************************************** *** Enter the minidisk address or full SFS directory *** name that will contain the RTM update files. Press *** ENTER to install the files on the default 2D2 disk. 192 ******************************************************** *** Enter the minidisk address or full SFS directory *** name that will contain the RTM AUX files. Press *** ENTER to install the files on the default 2A6 disk. 192
************************************************************* *** *** Press ENTER to install RTM VM/ESA on the following disks: *** *** All RTM VM/ESA source files will be loaded on 2B2 disk/dir *** All RTM VM/ESA test files will be loaded on 191 disk/dir *** All RTM VM/ESA sample files will be loaded on 191 disk/dir *** All RTM VM/ESA update files will be loaded on 192 disk/dir *** All RTM VM/ESA AUX files will be loaded on 192 disk/dir *** *** Enter QUIT to exit ***At this point, all the source files get loaded to the 2B2 disk, the test (executable) files and sample files get loaded to the 191 disk, and the service files get loaded on the 192 disk.
After the files are loaded to the mindisks or directories, the product must be built with the RTMBLD program. Skip to section "RTMBLD program" to continue with the install.
GA Level Installs (I5798DWD)
Read this section ONLY if you are installing the product from the GA level tape. If you are installing the product from the 9302 refresh level tape, or any subsequent refresh tape, then you should follow the instruction provided in "Installation program I5798DWD".
The GA level installation program (I5798DWD) does not work quite the same way as the version provided in APAR GC05109, it does not have support to install on SFS directories.
Note: After you install the GA product files, make sure you apply the service for APARs GC05046 and GC05109 since they have the most current and up to date versions of the build EXECs.
With the GA level installation program, you can only install the product on minidisks. The installation program will prompt you for the minidisk addresses of the source, test and sample disk, will install the files on the disks you specify and asks if a service tape needs to be applied, answer Y. Note that you must answer yes here, since you require APARs GC05046 and GC05109 to build the product.
Example of a GA level install
******************************************************** *** Enter the minidisk address to install the RTM VM/ESA *** source files, if different than the default 2B2 diskAt this point, the product files are loaded, and you must install the latest service (including APARS GC05046 and GC05109). Follow the instructions in "Non-VMSES/E Service Instructions". Continue with the next step "RTMBLD program" after installing service.******************************************************** *** Enter the minidisk address to install the RTM VM/ESA *** test files, if different than the default 400 disk ******************************************************** *** Enter the minidisk address to install the RTM VM/ESA *** sample files, if different than the default 2C2 disk ************************************************************* *** *** Press ENTER to install RTM VM/ESA on the following disks: *** *** All RTM VM/ESA source files will be loaded on 2B2 disk *** All RTM VM/ESA test files will be loaded on 400 disk *** All RTM VM/ESA sample files will be loaded on 2C2 disk *** Enter QUIT to exit *** ************************************************************ *** All the files have been loaded. *** Do you have a service tape to be applied (Y/N)? Y ************************************************************ *** To apply RTM VM/ESA service, follow the instructions *** for applying service in the memo to users provided *** with the service tape. When you have completed the *** service installation, you must run the RTMBLD exec to *** create the RTM module. *** You will now exit the installation exec. ************************************************************ Ready; T=0.22/1.46 19:01:26 *** Follow service install instructions, then invoke RTMBLD
RTMBLD program
RTMBLD is used to build the product. The main input to the RTMBLD program is the RTMDISK EXEC.
RTMDISK EXEC
RTMBLD reads the RTMDISK EXEC to obtain the disk addresses and/or SFS directory names where the various parts to the RTM VM/ESA product reside. Be sure that the entries in the RTMDISK EXEC match exactly where the product was installed. If you installed the product on the default minidisks, then you will not have to change this EXEC unless the CP maclibs required by RTM VM/ESA reside somewhere other than the default (MAINT 193) listed in the RTMDISK EXEC.
The original RTMBLD is placed on the source (2B2) disk by default. The RTMDISK EXEC is available with APAR GC05046. By default, serviced build EXECs would reside on the test (400) disk. It is recommended that the most recent serviced version of both the RTMBLD and RTMDISK EXECs are placed on 5798DWDC 191 disk or top level directory so that it can be invoked without having to access the source and/or test disks/directories.
Execution
RTMBLD first accesses the required disks/directories and presents the search order for the build to the user. Below is an example of what RTMBLD will show. Just hit ENTER at this point to continue the build.
****************************************************************** *** *** Below is the search order for this build of RTM. *** *** Mode Vdev/Directory Description *** ---- -------------- ----------- *** A 191 RTM build work disk *** F 400 RTM test disk (executables) *** H 2A6 RTM AUX files *** I 2D2 RTM update files (service) *** J 2B2 RTM base files *** K 193 (MAINT) VM CP MACLIBS *** *** Press ENTER to continue, or type QUIT to exit. *** ******************************************************************
RTMBLD then asks if the RTMMESA5 MACLIB should be rebuilt.
Note: Any service to RTM COPY files or MACRO files REQUIRES that the maclib be rebuilt.
****************************************************************** *** *** The RTM VM/ESA build process requires a re-generation of the *** RTM VM/ESA maclib (called RTMMESA5) if any service has *** been applied to RTM since the last build of RTM. *** *** Enter '1' if you would like the RTMMESA5 maclib rebuilt. *** *** Enter '0' to continue without rebuilding the maclib. *** *** NOTE: If this is a first time installation without any RTM *** service applied, then you do not need to rebuild the *** maclib. *** *** Enter QUIT to halt. *** ****************************************************************** 0
If 1 was specified above, RTMBLD rebuilds the maclib. In either case, RTMBLD then shows the maclibs used for the build of RTM. Just hit ENTER at the next prompt to continue the build.
****************************************************************** *** *** The following is the list of maclibs used in this build of RTM: *** *** *** RTMMESA5 MACLIB X1 *** DMSGPI MACLIB S2 *** HCPOM1 MACLIB L2 *** HCPOM2 MACLIB L2 *** HCPGPI MACLIB S2 *** HCPPSI MACLIB S2 *** *** If the MACLIBs listed above are correct, press ENTER to *** continue. Otherwise enter QUIT to halt. *** ******************************************************************
At this point RTMBLD performs the required RTM assemblies and builds the RTM MODULE. See Appendices C and D for sample console output from a non-SES RTM install.
VMCLOAD
If service was made to the VMC module, then the user should now issue VMCLOAD to rebuild the VMC module.
-
VMCLOAD Ready; T=0.22/1.46 19:01:26
RTM is now fully installed and built, you can now put it into production.
+---Post install-------------------------------------------------------------+
Put RTM VM/ESA into production when testing is completed.
+----------------------------------------------------------------------------+
- 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
- For minidisk install issue the following commands:
-
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.
- For minidisk install issue the following commands:
Post Installation Consideration
Activating the Program
Execute the following procedure to insure that RTM VM/ESA was installed properly:
- Logon to RTMESA.
- Enter RTM.
This will begin execution of RTM VM/ESA.
- When RTM VM/ESA is invoked, an RTM logo will initially appear. This will verify that RTM VM/ESA was installed correctly.
The first automatic display will occur approximately five seconds after the program is started (after the logo is presented). To terminate RTM VM/ESA, enter the QUIT command. You have now completed RTM VM/ESA installation verification.
Access to RTM VM/ESA via the VMC command
The VMC command to access to RTM VM/ESA must be issued from a separate virtual machine. The VMC module should be placed on a common disk such that it can be accessed by all concerned. RTM VM/ESA commands may then be executed through VMCF by entering:
VMC userid commandThe userid is the user ID of the virtual machine running RTM VM/ESA (in this document, referred to as RTMESA) and command is any valid RTM VM/ESA command.
The VMC module is supported in toleration mode for XA or ESA mode virtual machines. As previously discussed in this chapter, the RTM module must be run in a 370 mode virtual machine. The following error message will occur if the RTM module is invoked from an XA or ESA mode virtual machine:
RTM VM/ESA startup failed because the virtual machine is not in 370 mode
Modifying RTM VM/ESA Tables
RTM VM/ESA table sizes may be customized if they are inappropriate for your system. Care should be taken when changing these values, they should never be set to zero. The following table summarizes where to find the equates that relate to RTM VM/ESA tables:
+---------------------------Summary of RTM equates---------------------------+
Table 11. RTM VM/ESA field equates table
+==================+==============+=============+===============================================+ | RTM VM/ESA Table | RTM Module | Field Name | Use | +------------------+--------------+-------------+-----------------------------------------------+ | SYSDASD | RTMDAT | NUMSDA (1) | Number of System DASD entries | | USER | RTMDAT | NUMUSR (2) | Number of Userids | | MPUSER | RTMDAT | NUMMPUSR | Number of MP Users | | VECTOR | RTMDAT | NUMVEC | Number of Vector entries | | SRC & VMX | RTMDAT | NMSRCVMX | Number of SRC/VMX entries | | DEVICE | RTMDAT | NUMDEV | Number of device entries | | SDA | RTMDAT | NUMSDA | Number of system owned device entries | | ALOG | RTMOUT | ALOGNUM | Number of analysis log entries | | SCLOG | RTMOUT | SCLOGNUM | Number of scheduler log entries | | SLOG | RTMOUT | SLOGNUM | Number of system log entries | | TRLOG | RTMOUT | TRLOGNUM | Number of transaction log entries | | ULOG | RTMOUT | ULOGNUM | Number of user log entries | | VMCFLOG | RTMOUT | VMCFNUM | Number of vmcf log entries | | XSLOG | RTMOUT | XSLOGNUM | Number of extended system log entries | | XTLOG | RTMOUT | XTLOGNUM | Number of XSTORE log entries | | ULIST | RTMOUT | ULISTNUM | Number of userids not monitored for IDLE | | DATVMCBF | RTMDAT | NUMVMCF | Number of buffer entries for VMCF for LOGMSGs | +==================+==============+=============+===============================================+
Footnotes:
(1) This also includes the number of minidisks belonging to a storage group for an SFS server.
(2) This equate is also used in deriving the size of the VECTOR and SRC/VMX tables.
+-----------------------End of Summary of RTM equates------------------------+
Once the fields have been modified, reassemble ALL RTM VM/ESA modules, and generate a new RTM VM/ESA module. See RTM Product Rebuild.
Customizing the System
Two sample EXECs and one Assemble file are provided to enhance the usability and serviceability of RTM VM/ESA:
- RTMINIT EXEC
- A procedure used to initialize RTM VM/ESA from a separate virtual
machine through the VMCF interface.
This is an EXEC that is comparable to the SMINIT EXEC provided for
VM/RTM.
It is suggested that RTMESA be autologged first by AUTOLOG1 and that
this EXEC be the last command issued by AUTOLOG1.
After installation and servicing, a base copy of the
exec may be found on the 2C2 disk. A serviced copy
of the exec (RTMINIT EXCnnnnn, where nnnnn is the
PTF number) can be found on the 2D2 disk.
The latest (or a user modified) copy of this exec can
be sent to AUTOLOG1 with the name RTMINIT EXEC.
RTMINIT EXEC notes:
- The EXEC should be modified to tailor RTM VM/ESA to your installation.
This EXEC can be used to set RTM VM/ESA parameters like:
- SET ULIST
- SET LP
- SET PRINT
- SET LOG
- SET VMCF
- SET MSG
- SET INTERVAL
- SET TMR
- SET MODE
- SET LOGMSG
- It may be necessary to increase the time that the RTMINIT exec waits for the RTMESA virtual machine to initialize. This is done by changing the CP SLEEP statement in the RTMINIT exec.
- The following link should be in AUTOLOG1's directory entry:
LINK MAINT 19E 19E RR
This will allow AUTOLOG1 to access the VMC module. If RACF has been installed, make sure AUTOLOG1 has the authority to link to MAINT's 19E disk.
- Although we do not recommend that you spool the RTM machines console, adding a CP SLEEP 60 SEC and SET MODE DISPLAY will prevent all of the RTM displays from going to the console.
- The EXEC should be modified to tailor RTM VM/ESA to your installation.
This EXEC can be used to set RTM VM/ESA parameters like:
- PROFILE EXEC
- Sets up PF keys for RTM VM/ESA commands and invokes RTM VM/ESA.
The default PROFILE exec will also set MSG and WNG off for the virtual machine.
MSG and WNG are set off, so as to avoid receiving system messages, operator warnings, and the "midnight message" from VM/ESA Release 2. All of these can cause the terminal to go into a HOLDING state and stop RTM VM/ESA from processing data until the screen is cleared.
After installation, this exec is found on the 2C2. It should be copied to the 400 disk for testing with the RTM module before being moved to the 401 disk when you are ready to put RTM into production. (Ref #1.)
- SNAPP
- Is a sample program which uses the SNAP interface. The SNAP interface allows a virtual machine to extract RTM VM/ESA data for its own manipulation. It can be found, after installation, on the 2C2 disk. This program can be used as a model for other application programs. The assemble file is RTMSNAPP. The module is called SNAPP.
Service to CP control blocks
Note: Any service applied to the following HCP control blocks/modules may affect the RTM module and require that the RTM module be rebuilt.
Once the fields have been modified, reassemble ALL RTM VM/ESA modules, and generate a new RTM VM/ESA module. See RTM Product Rebuild.
+------------------CP Control blocks used by RTM VM/ESA 152------------------+
+-------------------------+-------------------------+-------------------------+ | HCPASCBK (VM/ESA only) | HCPDDITB (VM/XA only) | HCPSIEBK | | HCPCLASS | HCPMEXBK (VM/ESA Only) | HCPSRMBK | | HCPCPCOL | HCPMTBEK | HCPSYSCM | | HCPDVTYP | HCPPFXPG | HCPTCMBK | | HCPEQUAT | HCPPLSBK | HCPVDEV | | HCPEXPBK | HCPRDEV | HCPVMDBK | | HCPFSATE | HCPRSM | HCPXSTMG | | HCPMDC | HCPSCMBK | VMCBLOKS | +-------------------------+-------------------------+-------------------------+
+--------------End of CP Control blocks used by RTM VM/ESA 152---------------+
Building RTM VM/ESA For Multiple VM Systems.
RTM 1.5.2 runs on all currently supported VM/ESA releases (except the 370 Feature). Some installations may want to build RTM modules that run on a number of VM releases. This can easily be done.
You should install the product according to the VMSES/E or non-VMSES/E instructions (BUT NOT A MIXTURE OF BOTH!) on one of your systems.
If you have a VM/ESA Release 2 or later release at your installation, then you should install RTM VM/ESA on that system according to the VMSES/E installation instructions. If you wish to create an RTM VM/ESA MODULE that will run on another VM release at your installation, then all you need to do is make sure you have a minidisk that contains the CP maclibs for that VM release in your search order and build the product with the instructions provided in "RTM Product Rebuild"
If you do not have a VM/ESA Release 2 or later release system at your installation, then you must install RTM VM/ESA on one of your VM systems according to the non-VMSES/E installation instructions. If you wish to create an RTM VM/ESA MODULE that will run on another VM release at your installation, then all you need to do is modify the RTMDISK EXEC to reflect the location of the CP MACLIBs that were used to build the VM system that you wish to create the RTM module for. Then reissue the RTMBLD EXEC.
In summary, if you have multiple VM systems, you only need to install RTM VM/ESA on one of the systems. As you build RTM modules to run on each of your systems, make sure that you build each RTM module with the corresponding CP maclibs that were used to build the system that the RTM module is intended to run on. Thus, you want to make the CP maclibs used to build your various systems accessible to user 5798DWDC.
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.
+----------------------------------------------------------------------------+
-
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
- Setup the the 5798DWDC userid environment to install service.
VMFSETUP 5798DWDC RTM RTMSFSNote: 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 - 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 RTMSFSNote: 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
- 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 RTMSFSNote: 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
- Apply the new service.
VMFAPPLY PPF 5798DWDC RTM RTMSFSNote: 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
- Update the Build Status Table with serviced parts.
VMFBLD PPF 5798DWDC RTM (STATUS RTMSFSNote: 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 VMFPPFEnter 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.
+----------------------------------------------------------------------------+
- 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 .
- 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 RTMSFSNote: 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.
- Place the new service into production after testing.
- 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
- For minidisk install issue the following commands:
-
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.
- For minidisk install issue the following commands:
- 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).
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:
- 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
- For minidisk install issue the following commands:
-
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.
- For minidisk install issue the following commands:
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
- Define and format a temporary work disk to load the service on.
- 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.
- 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.
- 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
- 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.
- VMFPLCD RST ENV=NLSTnnnn SERVLINK fm
- 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.
- VMFPLCD RST ENV=NPTFnnnn SERVLINK fm
- Receive product memos from envelope NLSTnnnn SERVLINK.
- Service Tape Format
- 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
- 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
- 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.
- Receiving Service For Non-VMSES Envelopes
- COPYFILE all the AUXRTM5 files to the auxfile (2A6) disk or directory (VMSYS:5798DWDC.ALTAPPLY).
- COPYFILE all the update files to the update (2D2) disk or directory (VMSYS:5798DWDC.DELTA).
- COPYFILE any new source files (such as new COPY, MACRO or ASSEMBLE files) to the source (2B2) disk or directory (VMSYS:5798DWDC.SOURCE).
- 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.).
- 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:
- 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
- For minidisk install issue the following commands:
-
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.
- For minidisk install issue the following commands:
Appendix A. Applying Local Modifications to RTM VM/ESA.
VMSES/E Local Modifications Procedure
Copy Files (MACROS)
If you wish to apply local modifications to any of the RTM copy or macro files you must follow this procedure:
RTM ships updates to it's copy files but does NOT send the replacement COPY file. Therefore, instead of updating the local VVT (version vector table) with the new COPY name, the local VVT should be updated to reflect a change has been made to the COPY file... Our examples below uses RTMINTDA as the modified file.
- Access VMSES/E disks
VMFSETUP 5798DWDC RTM | RTMSFS
- Update RTM's VVT
VMFSIM LOGMOD 5798DWDC VVTRTML fm TDATA :MOD LCL0001.updftype :PART fn ft
where:
fm is the filemode of the local/sample disk (2C2) or directory (VMSYS:5798DWDC.SAMPLE).
updftype is the filetype of the local update file.
fn is the filename of the assemble part being modified.
ft is the filetype of the assemble part being modified.
For example, a modification to RTMDAT would look like this:
VMFSIM LOGMOD 5798DWDC VVTRTML E TDATA :MOD LCL0001.GCMYMOD :PART RTMINTDA COPY
- Edit the local AUX file on the local/sample disk or directory.
XEDIT fn AUXRTML fm (NOPROF INPUT updftype LCL LCL0001 FILEwhere:
fn is the filename of the assemble part being modified.
fm is the filemode of the local/sample disk (2C2) or directory (VMSYS:5798DWDC.SAMPLE).
updftype is the filetype of the local update file.
For example, a modification to RTMDAT would look like this:
XEDIT RTMINTDA AUXRTML E (NOPROF INPUT GCMYMOD LCL LCL0001 FILE - Edit the RTMESA5 CNTRL to appear as below:
TEXT MACS ... : TEXT AUXRTML * RTM AUX File and VVTRTML Level for Local Mods TEXT AUXRTM5 * RTM AUX FILE and VVTRTM5 Level for PTF service
- Edit the file to be modified and put the update file on the
sample/local disk.
XEDIT fn ASSEMBLE fm (CTL RTMESA5 make your changes FM updfmode FILE
where:
fn is the filename of the assemble part being modified.
fm is the filemode of the assemble part being modified.
updfmode is the filemode of the local/sample disk (2C2) or directory (VMSYS:5798DWDC.SAMPLE).
For example, a modification to RTMDAT would look like this:
XEDIT RTMINTDA COPY M (CTL RTMESA5 make your changes FM E FILE
- Rebuild the RTM MACLIB. Follow the directions for RTM Product Rebuild.
- Use the VMFHASM or VMFHLASM command with the CTL option to
verify a clean compile.
Even the assembled file of the local mod will be forced to
a filetype of 'TEXT'.
VMFHLASM fn RTMESA5 (CTL
where:
fn is the filename of the assemble part being modified.
For example, a modification to RTMDAT would look like this:
VMFHLASM RTMDAT RTMESA5 (CTL
- RTM requires that all ASSEMBLE parts be assembled using the same level of CP and RTM macro libraries. Once you have a clean compile for each modified part then you must recompile all of the parts. Follow the directions for RTM Product Rebuild.
Assemble Files
If you wish to apply local modifications to any of the RTM assemble files you must follow this procedure:
RTM ships updates to it's assemble files but does NOT send the replacement TEXT file. Therefore, instead of updating the local VVT (version vector table) with the new TEXT name, the local VVT should be updated to reflect a change has been made to the ASSEMBLE file... Our examples below uses RTMDAT as the modified file.
- Access VMSES/E disks
VMFSETUP 5798DWDC RTM | RTMSFS
- Update RTM's VVT
VMFSIM LOGMOD 5798DWDC VVTRTML fm TDATA :MOD LCL0001.updftype :PART fn ft
where:
fm is the filemode of the local/sample disk (2C2) or directory (VMSYS:5798DWDC.SAMPLE).
updftype is the filetype of the local update file.
fn is the filename of the assemble part being modified.
ft is the filetype of the assemble part being modified.
For example, a modification to RTMDAT would look like this:
VMFSIM LOGMOD 5798DWDC VVTRTML E TDATA :MOD LCL0001.GCMYMOD :PART RTMDAT ASSEMBLE
- Edit the local AUX file on the local/sample disk or directory.
XEDIT fn AUXRTML fm (NOPROF INPUT updftype LCL LCL0001 FILEwhere:
fn is the filename of the assemble part being modified.
fm is the filemode of the local/sample disk (2C2) or directory (VMSYS:5798DWDC.SAMPLE).
updftype is the filetype of the local update file.
For example, a modification to RTMDAT would look like this:
XEDIT RTMDAT AUXRTML E (NOPROF INPUT GCMYMOD LCL LCL0001 FILE - Edit the RTMESA5 CNTRL to appear as below:
TEXT MACS ... : TEXT AUXRTML * RTM AUX File and VVTRTML Level for Local Mods TEXT AUXRTM5 * RTM AUX FILE and VVTRTM5 Level for PTF service
- Edit the file to be modified and put the update file on the
sample/local disk.
XEDIT fn ASSEMBLE fm (CTL RTMESA5 make your changes FM updfmode FILE
where:
fn is the filename of the assemble part being modified.
fm is the filemode of the assemble part being modified.
updfmode is the filemode of the local/sample disk (2C2) or directory (VMSYS:5798DWDC.SAMPLE).
For example, a modification to RTMDAT would look like this:
XEDIT RTMDAT ASSEMBLE M (CTL RTMESA5 make your changes possibly update NUMUSR EQU FM E FILE
- Use the VMFHASM or VMFHLASM command with the CTL option to
verify a clean compile.
Even the assembled file of the local mod will be forced to
a filetype of 'TEXT'.
VMFHLASM fn RTMESA5 (CTL
where:
fn is the filename of the assemble part being modified.
For example, a modification to RTMDAT would look like this:
VMFHLASM RTMDAT RTMESA5 (CTL
- RTM requires that all ASSEMBLE parts be assembled using the same level of CP and RTM macro libraries. Once you have a clean compile for each modified part then you must recompile all of the parts. Follow the directions for RTM Product Rebuild.
Full Part Replacement Files
If you wish to apply local modifications to any of the RTM full part replacement files you must follow the same convention of applying local mods as used by VM/ESA components with the following exception:
- Edit the RTMESA5 CNTRL to appear as below:
TEXT MACS ... : TEXT AUXRTML * RTM AUX File and VVTRTML Level for Local Mods TEXT AUXRTM5 * RTM AUX FILE and VVTRTM5 Level for PTF service
- All references to VVTLCL should use VVTRTML for the local version vector table (vvtft).
Non-VMSES/E Local Modifications Procedure
Explicit instructions were provided in "Pre-installation instructions" that show how to change the default minidisk requirements. That section explained how to install the product in SFS directories and/or change the default minidisks to install the product on.
Applying code modifications to RTM VM/ESA to change its function (i.e. changing the source code) must be done manually. The instructions are provided here.
- Link and access the minidisks that contain the source files, AUX files, update files and object files. (If you did not change the default minidisk configuration, these would be addresses 2B2, 2A6, 2D2 and 400 respectively, or if you installed on SFS directories, these would be the .SOURCE, .ALTAPPLY, .DELTA and .TBUILD directories respectively).
- Edit the RTMESA5 CNTRL to appear as below:
TEXT MACS ... : TEXT AUXRTML * RTM AUX File for Local Mods TEXT AUXRTM5 * RTM AUX FILE for PTF service
- For any parts you wish to modify, you must update its AUXRTML
file (or create a new one if it doesn't exist) to point to the
the update that you are creating. For example, assuming you
were going to change RTMDAT and call your update LCLMOD, then you
would do the following:
- XEDIT RTMDAT AUXRTML
- I LCLMOD (This puts the update at the top of the file)
- FILE = = A (Puts it on your work disk)
- XEDIT the files you wish to change. For example, to change RTMDAT:
- XEDIT RTMDAT ASSEMBLE (CTL RTMESA5
- File your changes. When done creating all your updates
rebuild the product with RTMBLD.
- RTMBLD
Note: If you change MACRO or COPY files, then you must rebuild the RTMMESA5 MACLIB. Its recommended that you keep your local modifications separate (on a different minidisk for example) from the IBM supplied modifications.
Appendix B. Sample output from BUILD command.
This is the output from the build command obtained from an install of the 9302 refresh product tape.
VMFINS BUILD PPF 5798DWDC RTMINS (ALL NOLINK
VMFINS2760I VMFINS processing started
VMFREQ2805I Product 5798DWDC component RTMINS passed requisite checking
VMFSET2760I VMFSETUP processing started
VMFUTL2205I Minidisk|Directory Assignments:
String Mode Stat Vdev Label/Directory
VMFUTL2205I LOCALSAM E R/W 2C2 RTM2C2
VMFUTL2205I APPLY F R/W 2A6 RTM2A6
VMFUTL2205I G R/W 2A2 RTM2A2
VMFUTL2205I DELTA H R/W 2D2 RTM2D2
VMFUTL2205I BUILD0 I R/W 400 RTM400
VMFUTL2205I BUILD1 J R/W 401 RTM401
VMFUTL2205I BUILD6 K R/O 190 CMS21
VMFUTL2205I BUILD6 S R/O 190 CMS21
VMFUTL2205I BUILD7 L R/O 193 MNT193
VMFUTL2205I BASE1 M R/W 2B2 RTM2B2
VMFUTL2205I -------- A R/W 191 RTM191
VMFUTL2205I -------- B R/O DIR EPLLIB:EDLLIB4.DRV120.VMF
VMFUTL2205I -------- C R/O 120 SQVAUX
VMFUTL2205I -------- D R/W 51D RTM51D
VMFUTL2205I -------- Y/S R/O 19E YDISK
VMFSET2760I VMFSETUP processing completed successfully
VMFBLD2760I VMFBLD processing started
VMFBLD1851I Reading build lists
VMFBLD2182I Identifying new build requirements
VMFBLD2182I New build requirements identified
VMFBLD1851I (1 of 4) VMFBDCOM processing RTMSRC EXEC
VMFBDC2179I There are no build requirements matching your request at this time.
No objects will be built
VMFBDC2179I There are no build requirements matching your request at this time.
No objects will be built
VMFBDC2179I There are no build requirements matching your request at this time.
No objects will be built
VMFBDC2179I There are no build requirements matching your request at this time.
No objects will be built
VMFBDC2179I There are no build requirements matching your request at this time.
No objects will be built
VMFBLD1851I (1 of 4) VMFBDCOM completed with return code 0
VMFBLD1851I (2 of 4) VMFBDMLB processing RTMACLIB EXC02301
VMFMLB2217I RTMMESA5 MACLIB will be rebuilt because all members must be rebuilt
VMFMLB2219I Processing object RTMMEXBK
VMFMLB2219I Processing object RTMDDITB
VMFMLB2219I Processing object RTMASCBK
VMFMLB2219I Processing object RTMSYDAT
VMFMLB2219I Processing object RTMINTDA
VMFMLB2219I Processing object RTMIOPAS
VMFMLB2219I Processing object RTMVMBAD VMFMLB2219I Processing object RTMASBLK VMFMLB2219I Processing object RTMACTNS VMFMLB2219I Processing object RTMDEVAD VMFMLB2219I Processing object RTMFTADR VMFMLB2219I Processing object RTMFTDAT VMFMLB2219I Processing object RTMDVSTB VMFMLB2219I Processing object RTMHDRDA VMFMLB2219I Processing object RTMLGMSG VMFMLB2219I Processing object RTMLOGTB VMFMLB2219I Processing object RTMOPTNS VMFMLB2219I Processing object RTMPLBDA VMFMLB2219I Processing object RTMPFAAD VMFMLB2219I Processing object RTMPFTDA VMFMLB2219I Processing object RTMSCNTB VMFMLB2219I Processing object RTMSRCTB VMFMLB2219I Processing object RTMSYTDA VMFMLB2219I Processing object RTMSDAAD VMFMLB2219I Processing object RTMSDATB VMFMLB2219I Processing object RTMTEADR VMFMLB2219I Processing object RTMTEDAT VMFMLB2219I Processing object RTMTMRTB VMFMLB2219I Processing object RTMUSRTB VMFMLB2219I Processing object RTMVECTB VMFMLB2219I Processing object RTMEXIT VMFMLB2219I Processing object RTMNEWTM VMFMLB2219I Processing object RTMRSLIH VMFMLB2219I Processing object RTMSSLIH VMFMLB2219I Processing object RTMUSING VMFMLB2219I Processing object RTMWRAP VMFMLB2219I Processing object RTMCALL VMFMLB2219I Processing object RTMDROP VMFMLB2219I Processing object RTMENTER VMFMLB2219I Processing object RTMMULDL VMFMLB2219I Processing object RTMPROLG VMFMLB2219I Processing object RTMSWAPT VMFMLB2219I Processing object RTMBLANK VMFMLB2219I Processing object RTMCC VMFMLB2219I Processing object RTMTRACE VMFMLB2220I Updating service history member for RTMMESA5 MACLIB VMFBLD1851I (2 of 4) VMFBDMLB completed with return code 0 VMFBLD1851I (3 of 4) RTMBDUTL processing RTMASM EXEC VMFASM2760I VMFHASM processing started DMSUPD181E No update files were found
VMFASM1907I Assembling RTMSNAPP
VMFASM2507I RTMSNAPP TEXT created on your A-disk for use in a non-VMSES/E
environment
VMFASM2760I VMFHASM processing completed successfully
PRT FILE 0539 SENT FROM 5798DWDC PRT WAS 0539 RECS 0888 CPY 001 A NOHOLD NOKEEP
VMFASM2760I VMFHASM processing started
DMSUPD178I Updating RTMCMD ASSEMBLE M1
DMSUPD178I Applying RTMCMD G05041RM H1
DMSUPD178I Applying RTMCMD G05044RM H1
DMSUPD178I Applying RTMCMD G05046RM H1
VMFASM1907I Assembling RTMCMD
VMFASM2507I RTMCMD TEXT created on your A-disk for use in a non-VMSES/E
environment
VMFASM2760I VMFHASM processing completed successfully
PRT FILE 0540 SENT FROM 5798DWDC PRT WAS 0540 RECS 010K CPY 001 A NOHOLD NOKEEP
VMFASM2760I VMFHASM processing started
DMSUPD178I Updating RTMCMP ASSEMBLE M1
DMSUPD178I Applying RTMCMP G05044RM H1
DMSUPD178I Applying RTMCMP G05046RM H1
VMFASM1907I Assembling RTMCMP
VMFASM2507I RTMCMP TEXT created on your A-disk for use in a non-VMSES/E
environment
VMFASM2760I VMFHASM processing completed successfully
PRT FILE 0541 SENT FROM 5798DWDC PRT WAS 0541 RECS 011K CPY 001 A NOHOLD NOKEEP
VMFASM2760I VMFHASM processing started
DMSUPD178I Updating RTMDAT ASSEMBLE M1
DMSUPD178I Applying RTMDAT G05044RM H1
DMSUPD178I Applying RTMDAT G05046RM H1
VMFASM1907I Assembling RTMDAT
VMFASM2507I RTMDAT TEXT created on your A-disk for use in a non-VMSES/E
environment
VMFASM2760I VMFHASM processing completed successfully
PRT FILE 0542 SENT FROM 5798DWDC PRT WAS 0542 RECS 8525 CPY 001 A NOHOLD NOKEEP
VMFASM2760I VMFHASM processing started
DMSUPD178I Updating RTMDRV ASSEMBLE M1
DMSUPD178I Applying RTMDRV G05044RM H1
DMSUPD178I Applying RTMDRV G05046RM H1
VMFASM1907I Assembling RTMDRV
VMFASM2507I RTMDRV TEXT created on your A-disk for use in a non-VMSES/E
environment
VMFASM2760I VMFHASM processing completed successfully
PRT FILE 0543 SENT FROM 5798DWDC PRT WAS 0543 RECS 012K CPY 001 A NOHOLD NOKEEP
VMFASM2760I VMFHASM processing started
DMSUPD178I Updating RTMDSL ASSEMBLE M1
DMSUPD178I Applying RTMDSL G05044RM H1
DMSUPD178I Applying RTMDSL G05046RM H1
VMFASM1907I Assembling RTMDSL
VMFASM2507I RTMDSL TEXT created on your A-disk for use in a non-VMSES/E
environment
VMFASM2760I VMFHASM processing completed successfully
PRT FILE 0544 SENT FROM 5798DWDC PRT WAS 0544 RECS 6259 CPY 001 A NOHOLD NOKEEP
VMFASM2760I VMFHASM processing started
DMSUPD178I Updating RTMDSP ASSEMBLE M1
DMSUPD178I Applying RTMDSP G05044RM H1
DMSUPD178I Applying RTMDSP G05046RM H1
VMFASM1907I Assembling RTMDSP
VMFASM2507I RTMDSP TEXT created on your A-disk for use in a non-VMSES/E
environment
VMFASM2760I VMFHASM processing completed successfully
PRT FILE 0545 SENT FROM 5798DWDC PRT WAS 0545 RECS 012K CPY 001 A NOHOLD NOKEEP
VMFASM2760I VMFHASM processing started
DMSUPD178I Updating RTMDSU ASSEMBLE M1
DMSUPD178I Applying RTMDSU G05044RM H1
DMSUPD178I Applying RTMDSU G05026RM H1
DMSUPD178I Applying RTMDSU G05046RM H1
VMFASM1907I Assembling RTMDSU
VMFASM2507I RTMDSU TEXT created on your A-disk for use in a non-VMSES/E
environment
VMFASM2760I VMFHASM processing completed successfully
PRT FILE 0546 SENT FROM 5798DWDC PRT WAS 0546 RECS 010K CPY 001 A NOHOLD NOKEEP
VMFASM2760I VMFHASM processing started
DMSUPD178I Updating RTMDSV ASSEMBLE M1
DMSUPD178I Applying RTMDSV G05044RM H1
DMSUPD178I Applying RTMDSV G05046RM H1
VMFASM1907I Assembling RTMDSV
VMFASM2507I RTMDSV TEXT created on your A-disk for use in a non-VMSES/E
environment
VMFASM2760I VMFHASM processing completed successfully
PRT FILE 0547 SENT FROM 5798DWDC PRT WAS 0547 RECS 8971 CPY 001 A NOHOLD NOKEEP
VMFASM2760I VMFHASM processing started
DMSUPD178I Updating RTMDSW ASSEMBLE M1
DMSUPD178I Applying RTMDSW G05016RM H1
DMSUPD178I Applying RTMDSW G05044RM H1
DMSUPD178I Applying RTMDSW G05046RM H1
VMFASM1907I Assembling RTMDSW
VMFASM2507I RTMDSW TEXT created on your A-disk for use in a non-VMSES/E
environment
VMFASM2760I VMFHASM processing completed successfully
PRT FILE 0548 SENT FROM 5798DWDC PRT WAS 0548 RECS 7705 CPY 001 A NOHOLD NOKEEP
VMFASM2760I VMFHASM processing started
DMSUPD178I Updating RTMDSX ASSEMBLE M1
DMSUPD178I Applying RTMDSX G05043RM H1
DMSUPD178I Applying RTMDSX G05044RM H1
DMSUPD178I Applying RTMDSX G05046RM H1
DMSUPD178I Applying RTMDSX G05103RM H1
VMFASM1907I Assembling RTMDSX
VMFASM2507I RTMDSX TEXT created on your A-disk for use in a non-VMSES/E
environment
VMFASM2760I VMFHASM processing completed successfully
PRT FILE 0549 SENT FROM 5798DWDC PRT WAS 0549 RECS 6212 CPY 001 A NOHOLD NOKEEP
VMFASM2760I VMFHASM processing started
DMSUPD178I Updating RTMERM ASSEMBLE M1
DMSUPD178I Applying RTMERM G05046RM H1
VMFASM1907I Assembling RTMERM
VMFASM2507I RTMERM TEXT created on your A-disk for use in a non-VMSES/E
environment
VMFASM2760I VMFHASM processing completed successfully
PRT FILE 0550 SENT FROM 5798DWDC PRT WAS 0550 RECS 4606 CPY 001 A NOHOLD NOKEEP
VMFASM2760I VMFHASM processing started
DMSUPD178I Updating RTMIOP ASSEMBLE M1
DMSUPD178I Applying RTMIOP G05045RM H1
DMSUPD178I Applying RTMIOP G05044RM H1
DMSUPD178I Applying RTMIOP G05046RM H1
DMSUPD178I Applying RTMIOP G05121RM H1
VMFASM1907I Assembling RTMIOP
VMFASM2507I RTMIOP TEXT created on your A-disk for use in a non-VMSES/E
environment
VMFASM2760I VMFHASM processing completed successfully
PRT FILE 0551 SENT FROM 5798DWDC PRT WAS 0551 RECS 011K CPY 001 A NOHOLD NOKEEP
VMFASM2760I VMFHASM processing started
DMSUPD178I Updating RTMOUT ASSEMBLE M1
DMSUPD178I Applying RTMOUT G05046RM H1
DMSUPD178I Applying RTMOUT G05121RM H1
DMSUPD178I Applying RTMOUT G05109RM H1
VMFASM1907I Assembling RTMOUT
VMFASM2507I RTMOUT TEXT created on your A-disk for use in a non-VMSES/E
environment
VMFASM2760I VMFHASM processing completed successfully
PRT FILE 0552 SENT FROM 5798DWDC PRT WAS 0552 RECS 2896 CPY 001 A NOHOLD NOKEEP
VMFASM2760I VMFHASM processing started
DMSUPD178I Updating RTMSDA ASSEMBLE M1
DMSUPD178I Applying RTMSDA G05045RM H1
DMSUPD178I Applying RTMSDA G05044RM H1
DMSUPD178I Applying RTMSDA G05046RM H1
VMFASM1907I Assembling RTMSDA
VMFASM2507I RTMSDA TEXT created on your A-disk for use in a non-VMSES/E
environment
VMFASM2760I VMFHASM processing completed successfully
PRT FILE 0553 SENT FROM 5798DWDC PRT WAS 0553 RECS 9776 CPY 001 A NOHOLD NOKEEP
VMFASM2760I VMFHASM processing started
DMSUPD178I Updating RTMSRV ASSEMBLE M1
DMSUPD178I Applying RTMSRV G05046RM H1
VMFASM1907I Assembling RTMSRV
VMFASM2507I RTMSRV TEXT created on your A-disk for use in a non-VMSES/E
environment
VMFASM2760I VMFHASM processing completed successfully
PRT FILE 0554 SENT FROM 5798DWDC PRT WAS 0554 RECS 011K CPY 001 A NOHOLD NOKEEP
VMFASM2760I VMFHASM processing started
DMSUPD178I Updating RTMSYS ASSEMBLE M1
DMSUPD178I Applying RTMSYS G05044RM H1
DMSUPD178I Applying RTMSYS G05046RM H1
VMFASM1907I Assembling RTMSYS
VMFASM2507I RTMSYS TEXT created on your A-disk for use in a non-VMSES/E
environment
VMFASM2760I VMFHASM processing completed successfully
PRT FILE 0555 SENT FROM 5798DWDC PRT WAS 0555 RECS 8350 CPY 001 A NOHOLD NOKEEP
VMFASM2760I VMFHASM processing started
DMSUPD178I Updating RTMSYT ASSEMBLE M1
DMSUPD178I Applying RTMSYT G05044RM H1
DMSUPD178I Applying RTMSYT G05046RM H1
VMFASM1907I Assembling RTMSYT
VMFASM2507I RTMSYT TEXT created on your A-disk for use in a non-VMSES/E
environment
VMFASM2760I VMFHASM processing completed successfully
PRT FILE 0556 SENT FROM 5798DWDC PRT WAS 0556 RECS 8716 CPY 001 A NOHOLD NOKEEP
VMFASM2760I VMFHASM processing started
DMSUPD178I Updating RTMUSR ASSEMBLE M1
DMSUPD178I Applying RTMUSR G05044RM H1
DMSUPD178I Applying RTMUSR G05046RM H1
VMFASM1907I Assembling RTMUSR
VMFASM2507I RTMUSR TEXT created on your A-disk for use in a non-VMSES/E
environment
VMFASM2760I VMFHASM processing completed successfully
PRT FILE 0557 SENT FROM 5798DWDC PRT WAS 0557 RECS 013K CPY 001 A NOHOLD NOKEEP
VMFASM2760I VMFHASM processing started
DMSUPD181E No update files were found
VMFASM1907I Assembling RTMVMC
VMFASM2507I RTMVMC TEXT created on your A-disk for use in a non-VMSES/E
environment
VMFASM2760I VMFHASM processing completed successfully
PRT FILE 0558 SENT FROM 5798DWDC PRT WAS 0558 RECS 3398 CPY 001 A NOHOLD NOKEEP
VMFBLD1851I (3 of 4) RTMBDUTL completed with return code 0
VMFBLD1851I (4 of 4) VMFBDMOD processing RTMMOD EXC02080
VMFBDM2219I Processing object RTM.MODULE
VMFBDM2219I Processing object VMC.MODULE
VMFBDM2219I Processing object SNAPP.MODULE
VMFBLD1851I (4 of 4) VMFBDMOD completed with return code 0
VMFBLD2180I There are 0 build requirements remaining
VMFBLD2760I VMFBLD processing completed successfully
VMFINB2173I No verification exec found for this product
VMFINB2822I Product 5798DWDC RTMINS built successfully
VMFINS2760I VMFINS processing completed successfully
Appendix C. Sample non-VMSES/E install from 9302 Refresh Tape
In this example, the install of the product on the default minidisks is shown.
REW 181 Rewind complete Ready; T=0.01/0.01 14:21:17 VMFPLC2 LOAD Loading ... INS 9302 A1 I5798DWD EXEC A1 I5798DWD 015212 A1 5798DWDC 0152121 A1 5798DWDC PRODPART A1 5798DWDC $PPF A1 5798DWDC PPF A1 5798DWDC MEMO A1 5798DWDC $INS0000 A1 RTM SRVAPPS A1 End-of-file or end-of-tape Ready; T=0.01/0.04 14:21:26 VMFPLC2 LOAD Loading ... 5798DWDC 0152121 A1 5798DWDC MEMO A1 I5798DWD MEMO A1 End-of-file or end-of-tape Ready; T=0.01/0.01 14:21:30 I5798DWD ******************************************************** *** Please choose one of the following install options: *** *** 1. Enter '1' to install the product on the default *** minidisks. *** 2. Enter '2' to install the product on the default *** SFS directories. *** 3. Enter '3' to override the installation defaults. *** You will be prompted for the minidisk addresses *** or SFS directory names that the product will *** be installed on. *** *** 1
************************************************************* *** *** Press ENTER to install RTM VM/ESA on the following disks: *** *** All RTM source files will be loaded on 2B2 disk/dir *** All RTM test files will be loaded on 400 disk/dir *** All RTM sample files will be loaded on 2C2 disk/dir *** All RTM update files will be loaded on 2D2 disk/dir *** All RTM AUX files will be loaded on 2A6 disk/dir *** *** Enter QUIT to exit *** ************************************************************ *** *** Loading the RTM VM/ESA source files *** on the 2B2 disk/directory *** ************************************************************ ************************************************************ *** *** Loading the RTM VM/ESA test files *** on the 400 disk/directory *** ************************************************************ ************************************************************ *** *** Loading the RTM VM/ESA sample files *** on the 2C2 disk/directory *** ************************************************************ ************************************************************ *** *** Loading the RTM VM/ESA update files *** on the 2D2 disk/directory *** ************************************************************ ************************************************************ *** *** Loading the RTM VM/ESA AUX files *** on the 2A6 disk/directory *** ************************************************************
************************************************************ *** All the RTM VM/ESA product files have been loaded. *** *** You should now do the following to complete the install: *** *** 1. Edit the RTMDISK EXEC to match where you installed *** the product and where the CP maclibs are stored *** *** 2. Invoke RTMBLD to create the RTMMESA5 MACLIB, *** assemble the product, and build the RTM MODULE *** ************************************************************ PRT FILE 0496 SENT FROM 5798DWDC PRT WAS 0496 RECS 0194 CPY 001 A NOHOLD NOKEEP Ready; T=0.38/1.22 14:23:00 XEDIT RTMDISK EXEC Ready; T=0.01/0.02 14:23:23 RTMBLD RTMBLD001I ACCESSING TEST DISK 400 AS MODE D RTMBLD001I ACCESSING AUXFILE DISK 2A6 AS MODE E RTMBLD001I ACCESSING UPDATE DISK 2D2 AS MODE F RTMBLD001I ACCESSING SOURCE DISK 2B2 AS MODE G RTMBLD001I ACCESSING CP MACLIBS ON DISK $MAINT 193 AS MODE H DMSACP723I H (101) R/O ****************************************************************** *** *** Below is the search order for this build of RTM. *** *** Mode Vdev/Directory Description *** ---- -------------- ----------- *** A 191 RTM build work disk *** D 400 RTM test disk (executables) *** E 2A6 RTM AUX files *** F 2D2 RTM update files (service) *** G 2B2 RTM base files *** H 193 ($MAINT) VM CP MACLIBS *** *** Press ENTER to continue, or type QUIT to exit. *** ******************************************************************
****************************************************************** *** *** The RTM VM/ESA build process requires a re-generation of the *** RTM VM/ESA maclib (called RTMMESA5) if any service has *** been applied to RTM since the last build of RTM. *** *** Enter '1' if you would like the RTMMESA5 maclib rebuilt. *** *** Enter '0' to continue without rebuilding the maclib. *** *** NOTE: If this is a first time installation without any RTM *** service applied, then you do not need to rebuild the *** maclib. *** *** Enter QUIT to halt. *** ****************************************************************** 1 DMSUPD181E No update files were found RTMCC MACRO ADDED. DMSUPD181E No update files were found RTMWRAP MACRO ADDED. DMSUPD181E No update files were found RTMUSING MACRO ADDED. DMSUPD181E No update files were found RTMSWAPT MACRO ADDED. DMSUPD181E No update files were found RTMSSLIH MACRO ADDED. DMSUPD181E No update files were found RTMRSLIH MACRO ADDED. DMSUPD181E No update files were found RTMPROLG MACRO ADDED. DMSUPD181E No update files were found RTMNEWTM MACRO ADDED. DMSUPD181E No update files were found RTMEXIT MACRO ADDED. DMSUPD181E No update files were found RTMENTER MACRO ADDED. DMSUPD181E No update files were found RTMDROP MACRO ADDED. DMSUPD181E No update files were found RTMCALL MACRO ADDED. DMSUPD181E No update files were found RTMBLANK MACRO ADDED. DMSUPD181E No update files were found RTMMULDL MACRO ADDED.
DMSUPD178I Updating RTMTRACE MACRO D2 DMSUPD178I Applying RTMTRACE F05044RM F1 RTMTRACE MACRO ADDED. DMSUPD178I Updating RTMVMBAD COPY G1 DMSUPD178I Applying RTMVMBAD F05046RM F1 RTMVMBAD COPY ADDED. DMSUPD181E No update files were found RTMVECTB COPY ADDED. DMSUPD181E No update files were found RTMUSRTB COPY ADDED. DMSUPD181E No update files were found RTMTMRTB COPY ADDED. DMSUPD181E No update files were found RTMTEDAT COPY ADDED. DMSUPD181E No update files were found RTMTEADR COPY ADDED. DMSUPD181E No update files were found RTMSYTDA COPY ADDED. DMSUPD178I Updating RTMSYDAT COPY G1 DMSUPD178I Applying RTMSYDAT F05046RM F1 RTMSYDAT COPY ADDED. DMSUPD181E No update files were found RTMSRCTB COPY ADDED. DMSUPD181E No update files were found RTMSCNTB COPY ADDED. DMSUPD178I Updating RTMPLBDA COPY G1 DMSUPD178I Applying RTMPLBDA F05046RM F1 RTMPLBDA COPY ADDED. DMSUPD181E No update files were found RTMPFTDA COPY ADDED. DMSUPD181E No update files were found RTMPFAAD COPY ADDED. DMSUPD178I Updating RTMOPTNS COPY G1 DMSUPD178I Applying RTMOPTNS F05046RM F1 RTMOPTNS COPY ADDED. DMSUPD181E No update files were found RTMLOGTB COPY ADDED. DMSUPD181E No update files were found RTMLGMSG COPY ADDED. DMSUPD181E No update files were found RTMINTDA COPY ADDED. DMSUPD181E No update files were found RTMHDRDA COPY ADDED. DMSUPD181E No update files were found RTMFTDAT COPY ADDED. DMSUPD181E No update files were found
RTMFTADR COPY ADDED. DMSUPD178I Updating RTMDVSTB COPY G1 DMSUPD178I Applying RTMDVSTB F05121RM F1 RTMDVSTB COPY ADDED. DMSUPD178I Updating RTMDEVAD COPY G1 DMSUPD178I Applying RTMDEVAD F05046RM F1 RTMDEVAD COPY ADDED. DMSUPD181E No update files were found RTMACTNS COPY ADDED. DMSUPD178I Updating RTMASBLK COPY G1 DMSUPD178I Applying RTMASBLK F05046RM F1 RTMASBLK COPY ADDED. DMSUPD181E No update files were found RTMIOPAS COPY ADDED. DMSUPD178I Updating RTMSDATB COPY G1 DMSUPD178I Applying RTMSDATB F05045RM F1 RTMSDATB COPY ADDED. DMSUPD178I Updating RTMSDAAD COPY G1 DMSUPD178I Applying RTMSDAAD F05046RM F1 RTMSDAAD COPY ADDED. DMSUPD178I Updating RTMMEXBK COPY D2 DMSUPD178I Applying RTMMEXBK F05046RM F1 RTMMEXBK COPY ADDED. DMSUPD178I Updating RTMASCBK COPY D2 DMSUPD178I Applying RTMASCBK F05046RM F1 RTMASCBK COPY ADDED. DMSUPD178I Updating RTMDDITB COPY D2 DMSUPD178I Applying RTMDDITB F05046RM F1 RTMDDITB COPY ADDED. RTMMESA5 COPY ADDED. PRT FILE 0497 SENT FROM 5798DWDC PRT WAS 0497 RECS 8108 CPY 001 A NOHOLD NOKEEP
****************************************************************** *** *** The following is the list of maclibs used in this build of RTM: *** *** *** DMSGPI MACLIB S2 *** HCPOM1 MACLIB H2 *** HCPOM2 MACLIB H2 *** HCPGPI MACLIB S2 *** HCPPSI MACLIB S2 *** RTMMESA5 MACLIB A1 *** *** If the MACLIBs listed above are correct, press ENTER to *** continue. Otherwise enter QUIT to halt. *** ******************************************************************VMFASM2760I VMFHASM processing started DMSUPD178I Updating RTMCMD ASSEMBLE G1 DMSUPD178I Applying RTMCMD F05041RM F1 DMSUPD178I Applying RTMCMD F05044RM F1 DMSUPD178I Applying RTMCMD F05046RM F1 VMFASM1907I Assembling RTMCMD VMFASM2507I RTMCMD TEXT created on your A-disk for use in a non-VMSES/E environment VMFASM2760I VMFHASM processing completed successfully PRT FILE 0498 SENT FROM 5798DWDC PRT WAS 0498 RECS 010K CPY 001 A NOHOLD NOKEEP VMFASM2760I VMFHASM processing started DMSUPD178I Updating RTMCMP ASSEMBLE G1 DMSUPD178I Applying RTMCMP F05044RM F1 DMSUPD178I Applying RTMCMP F05046RM F1 VMFASM1907I Assembling RTMCMP VMFASM2507I RTMCMP TEXT created on your A-disk for use in a non-VMSES/E environment VMFASM2760I VMFHASM processing completed successfully PRT FILE 0499 SENT FROM 5798DWDC PRT WAS 0499 RECS 011K CPY 001 A NOHOLD NOKEEP VMFASM2760I VMFHASM processing started DMSUPD178I Updating RTMDAT ASSEMBLE G1 DMSUPD178I Applying RTMDAT F05044RM F1 DMSUPD178I Applying RTMDAT F05046RM F1 VMFASM1907I Assembling RTMDAT VMFASM2507I RTMDAT TEXT created on your A-disk for use in a non-VMSES/E environment VMFASM2760I VMFHASM processing completed successfully PRT FILE 0500 SENT FROM 5798DWDC PRT WAS 0500 RECS 8523 CPY 001 A NOHOLD NOKEEP VMFASM2760I VMFHASM processing started
DMSUPD178I Updating RTMDRV ASSEMBLE G1
DMSUPD178I Applying RTMDRV F05044RM F1
DMSUPD178I Applying RTMDRV F05046RM F1
VMFASM1907I Assembling RTMDRV
VMFASM2507I RTMDRV TEXT created on your A-disk for use in a non-VMSES/E
environment
VMFASM2760I VMFHASM processing completed successfully
PRT FILE 0501 SENT FROM 5798DWDC PRT WAS 0501 RECS 012K CPY 001 A NOHOLD NOKEEP
VMFASM2760I VMFHASM processing started
DMSUPD178I Updating RTMDSL ASSEMBLE G1
DMSUPD178I Applying RTMDSL F05044RM F1
DMSUPD178I Applying RTMDSL F05046RM F1
VMFASM1907I Assembling RTMDSL
VMFASM2507I RTMDSL TEXT created on your A-disk for use in a non-VMSES/E
environment
VMFASM2760I VMFHASM processing completed successfully
PRT FILE 0502 SENT FROM 5798DWDC PRT WAS 0502 RECS 6257 CPY 001 A NOHOLD NOKEEP
VMFASM2760I VMFHASM processing started
DMSUPD178I Updating RTMDSP ASSEMBLE G1
DMSUPD178I Applying RTMDSP F05044RM F1
DMSUPD178I Applying RTMDSP F05046RM F1
VMFASM1907I Assembling RTMDSP
VMFASM2507I RTMDSP TEXT created on your A-disk for use in a non-VMSES/E
environment
VMFASM2760I VMFHASM processing completed successfully
PRT FILE 0503 SENT FROM 5798DWDC PRT WAS 0503 RECS 012K CPY 001 A NOHOLD NOKEEP
VMFASM2760I VMFHASM processing started
DMSUPD178I Updating RTMDSU ASSEMBLE G1
DMSUPD178I Applying RTMDSU F05044RM F1
DMSUPD178I Applying RTMDSU F05026RM F1
DMSUPD178I Applying RTMDSU F05046RM F1
VMFASM1907I Assembling RTMDSU
VMFASM2507I RTMDSU TEXT created on your A-disk for use in a non-VMSES/E
environment
VMFASM2760I VMFHASM processing completed successfully
PRT FILE 0504 SENT FROM 5798DWDC PRT WAS 0504 RECS 010K CPY 001 A NOHOLD NOKEEP
VMFASM2760I VMFHASM processing started
DMSUPD178I Updating RTMDSV ASSEMBLE G1
DMSUPD178I Applying RTMDSV F05044RM F1
DMSUPD178I Applying RTMDSV F05046RM F1
VMFASM1907I Assembling RTMDSV
VMFASM2507I RTMDSV TEXT created on your A-disk for use in a non-VMSES/E
environment
VMFASM2760I VMFHASM processing completed successfully
PRT FILE 0505 SENT FROM 5798DWDC PRT WAS 0505 RECS 8969 CPY 001 A NOHOLD NOKEEP
VMFASM2760I VMFHASM processing started
DMSUPD178I Updating RTMDSW ASSEMBLE G1
DMSUPD178I Applying RTMDSW F05016RM F1
DMSUPD178I Applying RTMDSW F05044RM F1
DMSUPD178I Applying RTMDSW F05046RM F1
VMFASM1907I Assembling RTMDSW
VMFASM2507I RTMDSW TEXT created on your A-disk for use in a non-VMSES/E
environment
VMFASM2760I VMFHASM processing completed successfully
PRT FILE 0506 SENT FROM 5798DWDC PRT WAS 0506 RECS 7702 CPY 001 A NOHOLD NOKEEP
VMFASM2760I VMFHASM processing started
DMSUPD178I Updating RTMDSX ASSEMBLE G1
DMSUPD178I Applying RTMDSX F05043RM F1
DMSUPD178I Applying RTMDSX F05044RM F1
DMSUPD178I Applying RTMDSX F05046RM F1
DMSUPD178I Applying RTMDSX F05103RM F1
VMFASM1907I Assembling RTMDSX
VMFASM2507I RTMDSX TEXT created on your A-disk for use in a non-VMSES/E
environment
VMFASM2760I VMFHASM processing completed successfully
PRT FILE 0507 SENT FROM 5798DWDC PRT WAS 0507 RECS 6209 CPY 001 A NOHOLD NOKEEP
VMFASM2760I VMFHASM processing started
DMSUPD178I Updating RTMERM ASSEMBLE G1
DMSUPD178I Applying RTMERM F05046RM F1
VMFASM1907I Assembling RTMERM
VMFASM2507I RTMERM TEXT created on your A-disk for use in a non-VMSES/E
environment
VMFASM2760I VMFHASM processing completed successfully
PRT FILE 0508 SENT FROM 5798DWDC PRT WAS 0508 RECS 4605 CPY 001 A NOHOLD NOKEEP
VMFASM2760I VMFHASM processing started
DMSUPD178I Updating RTMIOP ASSEMBLE G1
DMSUPD178I Applying RTMIOP F05045RM F1
DMSUPD178I Applying RTMIOP F05044RM F1
DMSUPD178I Applying RTMIOP F05046RM F1
DMSUPD178I Applying RTMIOP F05121RM F1
VMFASM1907I Assembling RTMIOP
VMFASM2507I RTMIOP TEXT created on your A-disk for use in a non-VMSES/E
environment
VMFASM2760I VMFHASM processing completed successfully
PRT FILE 0509 SENT FROM 5798DWDC PRT WAS 0509 RECS 011K CPY 001 A NOHOLD NOKEEP
VMFASM2760I VMFHASM processing started
DMSUPD178I Updating RTMOUT ASSEMBLE G1
DMSUPD178I Applying RTMOUT F05046RM F1
DMSUPD178I Applying RTMOUT F05121RM F1
DMSUPD178I Applying RTMOUT F05109RM F1
VMFASM1907I Assembling RTMOUT
VMFASM2507I RTMOUT TEXT created on your A-disk for use in a non-VMSES/E
environment
VMFASM2760I VMFHASM processing completed successfully
PRT FILE 0510 SENT FROM 5798DWDC PRT WAS 0510 RECS 2895 CPY 001 A NOHOLD NOKEEP
VMFASM2760I VMFHASM processing started
DMSUPD178I Updating RTMSDA ASSEMBLE G1
DMSUPD178I Applying RTMSDA F05045RM F1
DMSUPD178I Applying RTMSDA F05044RM F1
DMSUPD178I Applying RTMSDA F05046RM F1
VMFASM1907I Assembling RTMSDA
VMFASM2507I RTMSDA TEXT created on your A-disk for use in a non-VMSES/E
environment
VMFASM2760I VMFHASM processing completed successfully
PRT FILE 0511 SENT FROM 5798DWDC PRT WAS 0511 RECS 9773 CPY 001 A NOHOLD NOKEEP
VMFASM2760I VMFHASM processing started
DMSUPD178I Updating RTMSRV ASSEMBLE G1
DMSUPD178I Applying RTMSRV F05046RM F1
VMFASM1907I Assembling RTMSRV
VMFASM2507I RTMSRV TEXT created on your A-disk for use in a non-VMSES/E
environment
VMFASM2760I VMFHASM processing completed successfully
PRT FILE 0512 SENT FROM 5798DWDC PRT WAS 0512 RECS 011K CPY 001 A NOHOLD NOKEEP
VMFASM2760I VMFHASM processing started
DMSUPD178I Updating RTMSYS ASSEMBLE G1
DMSUPD178I Applying RTMSYS F05044RM F1
DMSUPD178I Applying RTMSYS F05046RM F1
VMFASM1907I Assembling RTMSYS
VMFASM2507I RTMSYS TEXT created on your A-disk for use in a non-VMSES/E
environment
VMFASM2760I VMFHASM processing completed successfully
PRT FILE 0513 SENT FROM 5798DWDC PRT WAS 0513 RECS 8348 CPY 001 A NOHOLD NOKEEP
VMFASM2760I VMFHASM processing started
DMSUPD178I Updating RTMSYT ASSEMBLE G1
DMSUPD178I Applying RTMSYT F05044RM F1
DMSUPD178I Applying RTMSYT F05046RM F1
VMFASM1907I Assembling RTMSYT
VMFASM2507I RTMSYT TEXT created on your A-disk for use in a non-VMSES/E
environment
VMFASM2760I VMFHASM processing completed successfully
PRT FILE 0514 SENT FROM 5798DWDC PRT WAS 0514 RECS 8714 CPY 001 A NOHOLD NOKEEP
VMFASM2760I VMFHASM processing started
DMSUPD178I Updating RTMUSR ASSEMBLE G1
DMSUPD178I Applying RTMUSR F05044RM F1
DMSUPD178I Applying RTMUSR F05046RM F1
VMFASM1907I Assembling RTMUSR
VMFASM2507I RTMUSR TEXT created on your A-disk for use in a non-VMSES/E
environment
VMFASM2760I VMFHASM processing completed successfully
PRT FILE 0515 SENT FROM 5798DWDC PRT WAS 0515 RECS 013K CPY 001 A NOHOLD NOKEEP
VMFASM2760I VMFHASM processing started
DMSUPD181E No update files were found
VMFASM1907I Assembling RTMVMC
VMFASM2507I RTMVMC TEXT created on your A-disk for use in a non-VMSES/E
environment
VMFASM2760I VMFHASM processing completed successfully
PRT FILE 0516 SENT FROM 5798DWDC PRT WAS 0516 RECS 3397 CPY 001 A NOHOLD NOKEEP
******************************************************************
***
*** RTM build completed successfully.
***
*** Copying all TEXT files, MACLIB, and/or MODULE to the test disk.
***
******************************************************************
DASD 0101 DETACHED
******************************************************************
***
*** Exiting RTMBLD EXEC.
***
*** You should now copy the RTM MODULE to the RTM VM/ESA service
*** machine's 191 disk or top level directory
***
******************************************************************
Ready; T=23.45/38.78 14:35:13
Appendix D. Sample Non-VMSES/E Install with CORrective Service Tape.
In this example, the installation has the GA product tape (which contains the base product with no service) and a cumulative service tape that contains the PTFs for RTM APARs: GC05012, GC05016, GC05041, GC05043, GC05045, GC05044, GC05026 and GC05046. GC05046 contains the RTMBLD EXEC and RTMDISK EXEC required for the build of the product. Thus, the GA product tape and the service tape must be installed before the product can be built. The product is installed on the default minidisks.
Three basic steps are required to install and build RTM VM/ESA from the GA product tape and the cumulative service tape. The first step is to install the GA product tape files with the I5798DWD EXEC, the second step is to install the service tape files, and the last step is to build the product with RTMBLD EXEC.
Install of GA Product Tape with I5798DWD EXEC
Ready; T=0.01/0.01 18:50:42 rew 181 Rewind complete Ready; T=0.01/0.01 18:50:50 vmfplc2 load Loading ... INS 9200 A1 I5798DWD EXEC A1 I5798DWD 015210 A1 5798DWDC 0152101 A1 5798DWDC PRODPART A1 5798DWDC $PPF A1 5798DWDC PPF A1 5798DWDC MEMO A1 5798DWDC $INS0000 A1 End-of-file or end-of-tape Ready; T=0.03/0.07 18:50:58 vmfplc2 load Loading ... 5798DWDC 0152101 A1 5798DWDC MEMO A1 I5798DWD MEMO A1 End-of-file or end-of-tape Ready; T=0.01/0.02 18:51:18 i5798dwd ******************************************************** *** Enter the minidisk address to install the RTM VM/ESA *** source files, if different than the default 2B2 disk******************************************************** *** Enter the minidisk address to install the RTM VM/ESA *** test files, if different than the default 400 disk ******************************************************** *** Enter the minidisk address to install the RTM VM/ESA *** sample files, if different than the default 2C2 disk
************************************************************* *** *** Press ENTER to install RTM VM/ESA on the following disks: *** *** All RTM VM/ESA source files will be loaded on 2B2 disk *** All RTM VM/ESA test files will be loaded on 400 disk *** All RTM VM/ESA sample files will be loaded on 2C2 disk *** Enter QUIT to exit *************************************************************** *** *** Loading the RTM VM/ESA ASSEMBLE, MACRO, COPY files, *** and RTMMESA5 maclib on 2B2 disk *** ************************************************************ ************************************************************ *** *** Loading the RTM VM/ESA test files on 400 disk *** ************************************************************ ************************************************************ *** *** Loading the RTM VM/ESA sample files on 2C2 disk *** ************************************************************ ************************************************************ *** All the files have been loaded. *** Do you have a service tape to be applied (Y/N)? Y ************************************************************ *** To apply RTM VM/ESA service, follow the instructions *** for applying service in the memo to users provided *** with the service tape. When you have completed the *** service installation, you must run the RTMBLD exec to *** create the RTM module. *** You will now exit the installation exec. ************************************************************ Ready; T=0.27/0.93 18:51:27
Install of Cumulative Service Tape
At this point, the base product has been installed with I5798DWD and the service tape must be installed. Note that this example also applies to the case where RTM VM/ESA has been fully installed but corrective service needs to be applied.
Ready; T=0.01/0.01 13:36:57 rew 181 Rewind complete Ready; T=0.01/0.01 13:37:02 def t3380 99 10 DASD 0099 DEFINED Ready; T=0.01/0.01 13:37:08 format 99 b DMSFOR603R FORMAT will erase all files on disk B(099). Do you wish to continue? Enter 1 (YES) or 0 (NO). 1 DMSFOR605R Enter disk label: TEMP DMSFOR733I Formatting disk B DMSFOR732I 10 cylinders formatted on B(099) Ready; T=0.01/0.02 13:37:31 vmfplc2 scan 5798dwdb 010101 (EOT Scanning ... End-of-file or end-of-tape 5798DWDB 010101 U1 Ready; T=0.01/0.01 13:37:43 vmfplc2 load * * B Loading ... 5798DWDB 010101 B1 RTMACLIB EXC02300 B1 RTMACLIB EXC02188 B1 RTMASBLK AUM02300 B1 RTMASBLK F05046RM B1 RTMASCBK AUM02300 B1 RTMASCBK CPY02300 B1 RTMASCBK F05046RM B1 RTMBLD EXC02300 B1 RTMCMD AUM02300 B1 RTMCMD AUM02188 B1 RTMCMD AUM02158 B1 RTMCMD F05041RM B1 RTMCMD F05044RM B1 RTMCMD F05046RM B1 RTMCMP AUM02300 B1 RTMCMP AUM02188 B1 RTMCMP F05044RM B1 RTMCMP F05046RM B1 RTMDAT AUM02300 B1 RTMDAT AUM02188 B1 RTMDAT F05044RM B1 RTMDAT F05046RM B1 RTMDDITB AUM02300 B1 RTMDDITB CPY02300 B1 RTMDDITB F05046RM B1 RTMDEVAD AUM02300 B1 RTMDEVAD F05046RM B1
RTMDISK EXC02300 B1 RTMDRV AUM02300 B1 RTMDRV AUM02188 B1 RTMDRV F05044RM B1 RTMDRV F05046RM B1 RTMDSL AUM02300 B1 RTMDSL AUM02188 B1 RTMDSL F05044RM B1 RTMDSL F05046RM B1 RTMDSP AUM02300 B1 RTMDSP AUM02188 B1 RTMDSP F05044RM B1 RTMDSP F05046RM B1 RTMDSU AUM02300 B1 RTMDSU AUM02192 B1 RTMDSU AUM02188 B1 RTMDSU F05026RM B1 RTMDSU F05044RM B1 RTMDSU F05046RM B1 RTMDSV AUM02300 B1 RTMDSV AUM02188 B1 RTMDSV F05044RM B1 RTMDSV F05046RM B1 RTMDSW AUM02300 B1 RTMDSW AUM02188 B1 RTMDSW AUM02081 B1 RTMDSW F05016RM B1 RTMDSW F05044RM B1 RTMDSW F05046RM B1 RTMDSX AUM02300 B1 RTMDSX AUM02188 B1 RTMDSX AUM02158 B1 RTMDSX F05043RM B1 RTMDSX F05044RM B1 RTMDSX F05046RM B1 RTMERM AUM02300 B1 RTMERM F05046RM B1 RTMESA5 CTL02300 B1 RTMIOP AUM02300 B1
RTMIOP AUM02188 B1 RTMIOP AUM02158 B1 RTMIOP F05044RM B1 RTMIOP F05045RM B1 RTMIOP F05046RM B1 RTMMESA5 EXC02300 B1 RTMMESA5 EXC02188 B1 RTMMEXBK AUM02300 B1 RTMMEXBK CPY02300 B1 RTMMEXBK F05046RM B1 RTMMOD EXC02079 B2 RTMOPTNS AUM02300 B1 RTMOPTNS F05046RM B1 RTMOUT AUM02300 B1 RTMOUT F05046RM B1 RTMPLBDA AUM02300 B1 RTMPLBDA F05046RM B1 RTMSDA AUM02300 B1 RTMSDA AUM02188 B1 RTMSDA AUM02158 B1 RTMSDA F05044RM B1 RTMSDA F05045RM B1 RTMSDA F05046RM B1 RTMSDAAD AUM02300 B1 RTMSDAAD F05046RM B1 RTMSDATB AUM02158 B1 RTMSDATB F05045RM B1 RTMSRV AUM02300 B1 RTMSRV F05046RM B1 RTMSYDAT AUM02300 B1 RTMSYDAT F05046RM B1 RTMSYS AUM02300 B1 RTMSYS AUM02188 B1 RTMSYS F05044RM B1 RTMSYS F05046RM B1 RTMSYT AUM02300 B1 RTMSYT AUM02188 B1 RTMSYT F05044RM B1 RTMSYT F05046RM B1 RTMTRACE AUM02188 B1 RTMTRACE F05044RM B1
RTMTRACE MAC02188 B1 RTMUSR AUM02300 B1 RTMUSR AUM02188 B1 RTMUSR F05044RM B1 RTMUSR F05046RM B1 RTMVMBAD AUM02300 B1 RTMVMBAD F05046RM B1 VMCLOAD EXC02300 B1 5798DWDC MEM02300 B1 5798DWDC MEM02192 B1 5798DWDC MEM02188 B1 5798DWDC MEM02158 B1 5798DWDC MEM02081 B1 5798DWDC MEM02079 B1 5798DWDB EXEC B1 End-of-file or end-of-tape Ready; T=0.13/0.33 13:38:09 5798dwdb b RENAME RTMACLIB EXC02300 B = EXEC = ERASE RTMACLIB EXC02188 B RENAME RTMASBLK AUM02300 B = AUXRTM5 = RENAME RTMASCBK AUM02300 B = AUXRTM5 = RENAME RTMASCBK CPY02300 B = COPY = RENAME RTMBLD EXC02300 B = EXEC = RENAME RTMCMD AUM02300 B = AUXRTM5 = ERASE RTMCMD AUM02188 B ERASE RTMCMD AUM02158 B RENAME RTMCMP AUM02300 B = AUXRTM5 = ERASE RTMCMP AUM02188 B RENAME RTMDAT AUM02300 B = AUXRTM5 = ERASE RTMDAT AUM02188 B RENAME RTMDDITB AUM02300 B = AUXRTM5 = RENAME RTMDDITB CPY02300 B = COPY = RENAME RTMDEVAD AUM02300 B = AUXRTM5 = RENAME RTMDISK EXC02300 B = EXEC = RENAME RTMDRV AUM02300 B = AUXRTM5 = ERASE RTMDRV AUM02188 B RENAME RTMDSL AUM02300 B = AUXRTM5 = ERASE RTMDSL AUM02188 B RENAME RTMDSP AUM02300 B = AUXRTM5 = ERASE RTMDSP AUM02188 B
RENAME RTMDSU AUM02300 B = AUXRTM5 = ERASE RTMDSU AUM02192 B ERASE RTMDSU AUM02188 B RENAME RTMDSV AUM02300 B = AUXRTM5 = ERASE RTMDSV AUM02188 B RENAME RTMDSW AUM02300 B = AUXRTM5 = ERASE RTMDSW AUM02188 B ERASE RTMDSW AUM02081 B RENAME RTMDSX AUM02300 B = AUXRTM5 = ERASE RTMDSX AUM02188 B ERASE RTMDSX AUM02158 B RENAME RTMERM AUM02300 B = AUXRTM5 = RENAME RTMESA5 CTL02300 B = CNTRL = RENAME RTMIOP AUM02300 B = AUXRTM5 = ERASE RTMIOP AUM02188 B ERASE RTMIOP AUM02158 B RENAME RTMMESA5 EXC02300 B = EXEC = ERASE RTMMESA5 EXC02188 B RENAME RTMMEXBK AUM02300 B = AUXRTM5 = RENAME RTMMEXBK CPY02300 B = COPY = RENAME RTMMOD EXC02079 B = EXEC = RENAME RTMOPTNS AUM02300 B = AUXRTM5 = RENAME RTMOUT AUM02300 B = AUXRTM5 = RENAME RTMPLBDA AUM02300 B = AUXRTM5 = RENAME RTMSDA AUM02300 B = AUXRTM5 = ERASE RTMSDA AUM02188 B ERASE RTMSDA AUM02158 B RENAME RTMSDAAD AUM02300 B = AUXRTM5 = RENAME RTMSDATB AUM02158 B = AUXRTM5 = RENAME RTMSRV AUM02300 B = AUXRTM5 = RENAME RTMSYDAT AUM02300 B = AUXRTM5 = RENAME RTMSYS AUM02300 B = AUXRTM5 = ERASE RTMSYS AUM02188 B RENAME RTMSYT AUM02300 B = AUXRTM5 = ERASE RTMSYT AUM02188 B RENAME RTMTRACE AUM02188 B = AUXRTM5 = RENAME RTMTRACE MAC02188 B = MACRO = RENAME RTMUSR AUM02300 B = AUXRTM5 = ERASE RTMUSR AUM02188 B RENAME RTMVMBAD AUM02300 B = AUXRTM5 = RENAME VMCLOAD EXC02300 B = EXEC = RENAME 5798DWDC MEM02300 B = MEMO =
ERASE 5798DWDC MEM02192 B ERASE 5798DWDC MEM02188 B ERASE 5798DWDC MEM02158 B ERASE 5798DWDC MEM02081 B ERASE 5798DWDC MEM02079 B Ready; T=0.03/0.07 13:38:25
Note: At this point you would copy the AUXRTM5 files to the delta (2A6) disk, copy the update files to the APPLY (2D2) disk, copy any new source files to the source (2B2) disk and place the full replacement parts, such as the build EXECs on the test (400) disk. In this example, the MACRO, COPY and ASSEMBLE files are copied to the 2B2 disk. (There are no new ASSEMBLE files so the COPYFILE fails). The AUXRTM5 files are copied to the 2A6 disk. The build EXECs and new CNTRL file are copied to the 2D2 disk. All non-VMSES/E RTM update files have a filetype that begins with F0, and the user would copy all these files to the 2D2 disk. In addition, as recommended the latest RTMBLD and RTMDISK EXECs are copied to the 191 disk.
acc 2b2 z Ready; T=0.01/0.01 13:38:41 copyf * macro b = = z (oldd Ready; T=0.01/0.01 13:38:59 copyf * copy b = = z (oldd Ready; T=0.01/0.01 13:39:09 copyf * assemble b = = z (oldd DMSCPY002E INPUT file * ASSEMBLE B not found Ready(00028); T=0.01/0.01 13:39:17 acc 2a6 z DMSACC724I 2A6 replaces Z (2B2) Ready; T=0.01/0.01 13:39:27 copyf * auxrtm5 b = = z (rep oldd Ready; T=0.02/0.05 13:39:44 acc 400 z DMSACC724I 400 replaces Z (2A6) Ready; T=0.01/0.01 13:39:51 copyf * exec b = = z (rep oldd Ready; T=0.01/0.01 13:40:27 copyf * cntrl b = = z (rep oldd Ready; T=0.01/0.01 13:40:36 copyf rtmdisk exec z = = a (rep oldd Ready; T=0.01/0.01 13:42:47 copyf rtmbld exec z = = a (rep oldd Ready; T=0.01/0.01 13:42:58 acc 2d2 z DMSACC724I 2D2 replaces Z (400) Ready; T=0.01/0.01 13:40:54 filel * f0*RM b Ready; T=0.39/0.44 13:42:04
Note: User would copy all these files to the delta (2D2) disk.
rel b Ready; T=0.01/0.01 13:42:11 x rtmdisk exec Ready; T=0.02/0.02 13:43:24
Note: In this example, the user modifies the RTMDISK EXEC. Their installation has the CP MACLIBS on the $MAINT 193 disk. The default listed in the RTMDISK EXEC is MAINT 193 disk; hence, it must be changed. The CPmac_owner='MAINT' is changed to CPmac_owner='$MAINT' in the RTMDISK EXEC.
Build of RTM VM/ESA
At this point the product has been fully installed, including the latest service. The product needs to now be built. Note that the user chose to rebuild the RTMMESA5 MACLIB since there was service to some of the RTM COPY and MACRO files.
rtmbld RTMBLD001I ACCESSING TEST DISK 400 AS MODE B RTMBLD001I ACCESSING AUXFILE DISK 2A6 AS MODE E RTMBLD001I ACCESSING UPDATE DISK 2D2 AS MODE F RTMBLD001I ACCESSING SOURCE DISK 2B2 AS MODE H RTMBLD001I ACCESSING CP MACLIBS ON DISK $MAINT 193 AS MODE I DMSACP723I I (101) R/O ****************************************************************** *** *** Below is the search order for this build of RTM. *** *** Mode Vdev Description *** ---- ---- ----------- *** A 191 RTM build work disk *** B 400 RTM test disk (executables) *** E 2A6 RTM AUX files *** F 2D2 RTM update files (service) *** H 2B2 RTM base files *** I 193 ($MAINT) VM CP MACLIBS *** *** Press ENTER to continue, or type QUIT to exit. *** ************************************************************************************************************************************ *** *** The RTM VM/ESA build process requires a re-generation of the *** RTM VM/ESA maclib (called RTMMESA5) if any service has *** been applied to RTM since the last build of RTM. *** *** Enter '1' if you would like the RTMMESA5 maclib rebuilt. *** *** Enter '0' to continue without rebuilding the maclib. *** *** NOTE: If this is a first time installation without any RTM *** service applied, then you do not need to rebuild the *** maclib. *** *** Enter QUIT to halt. *** ****************************************************************** 1
DMSUPD181E No update files were found RTMCC MACRO ADDED. DMSUPD181E No update files were found RTMWRAP MACRO ADDED. DMSUPD181E No update files were found RTMUSING MACRO ADDED. DMSUPD181E No update files were found RTMSWAPT MACRO ADDED. DMSUPD181E No update files were found RTMSSLIH MACRO ADDED. DMSUPD181E No update files were found RTMRSLIH MACRO ADDED. DMSUPD181E No update files were found RTMPROLG MACRO ADDED. DMSUPD181E No update files were found RTMNEWTM MACRO ADDED. DMSUPD181E No update files were found RTMEXIT MACRO ADDED. DMSUPD181E No update files were found RTMENTER MACRO ADDED. DMSUPD181E No update files were found RTMDROP MACRO ADDED. DMSUPD181E No update files were found RTMCALL MACRO ADDED. DMSUPD181E No update files were found RTMBLANK MACRO ADDED. DMSUPD181E No update files were found RTMMULDL MACRO ADDED. DMSUPD178I Updating RTMTRACE MACRO H1 DMSUPD178I Applying RTMTRACE F05044RM F1 RTMTRACE MACRO ADDED. DMSUPD178I Updating RTMVMBAD COPY H1 DMSUPD178I Applying RTMVMBAD F05046RM F1 RTMVMBAD COPY ADDED. DMSUPD181E No update files were found RTMVECTB COPY ADDED.
DMSUPD181E No update files were found RTMUSRTB COPY ADDED. DMSUPD181E No update files were found RTMTMRTB COPY ADDED. DMSUPD181E No update files were found RTMTEDAT COPY ADDED. DMSUPD181E No update files were found RTMTEADR COPY ADDED. DMSUPD181E No update files were found RTMSYTDA COPY ADDED. DMSUPD178I Updating RTMSYDAT COPY H1 DMSUPD178I Applying RTMSYDAT F05046RM F1 RTMSYDAT COPY ADDED. DMSUPD181E No update files were found RTMSRCTB COPY ADDED. DMSUPD181E No update files were found RTMSCNTB COPY ADDED. DMSUPD178I Updating RTMPLBDA COPY H1 DMSUPD178I Applying RTMPLBDA F05046RM F1 RTMPLBDA COPY ADDED. DMSUPD181E No update files were found RTMPFTDA COPY ADDED. DMSUPD181E No update files were found RTMPFAAD COPY ADDED. DMSUPD178I Updating RTMOPTNS COPY H1 DMSUPD178I Applying RTMOPTNS F05046RM F1 RTMOPTNS COPY ADDED. DMSUPD181E No update files were found RTMLOGTB COPY ADDED. DMSUPD181E No update files were found RTMLGMSG COPY ADDED. DMSUPD181E No update files were found RTMINTDA COPY ADDED. DMSUPD181E No update files were found RTMHDRDA COPY ADDED. DMSUPD181E No update files were found RTMFTDAT COPY ADDED. DMSUPD181E No update files were found RTMFTADR COPY ADDED.
DMSUPD181E No update files were found RTMDVSTB COPY ADDED. DMSUPD178I Updating RTMDEVAD COPY H1 DMSUPD178I Applying RTMDEVAD F05046RM F1 RTMDEVAD COPY ADDED. DMSUPD181E No update files were found RTMACTNS COPY ADDED. DMSUPD178I Updating RTMASBLK COPY H1 DMSUPD178I Applying RTMASBLK F05046RM F1 RTMASBLK COPY ADDED. DMSUPD181E No update files were found RTMIOPAS COPY ADDED. DMSUPD178I Updating RTMSDATB COPY H1 DMSUPD178I Applying RTMSDATB F05045RM F1 RTMSDATB COPY ADDED. DMSUPD178I Updating RTMSDAAD COPY H1 DMSUPD178I Applying RTMSDAAD F05046RM F1 RTMSDAAD COPY ADDED. DMSUPD178I Updating RTMMEXBK COPY H1 DMSUPD178I Applying RTMMEXBK F05046RM F1 RTMMEXBK COPY ADDED. DMSUPD178I Updating RTMASCBK COPY H1 DMSUPD178I Applying RTMASCBK F05046RM F1 RTMASCBK COPY ADDED. DMSUPD178I Updating RTMDDITB COPY H1 DMSUPD178I Applying RTMDDITB F05046RM F1 RTMDDITB COPY ADDED. RTMMESA5 COPY ADDED. PRT FILE 0030 SENT FROM 5798DWDC PRT WAS 0030 RECS 8096 CPY 001 A NOHOLD NOKEEP
****************************************************************** *** *** The following is the list of maclibs used in this build of RTM: *** *** *** DMSGPI MACLIB S2 *** HCPOM1 MACLIB I2 *** HCPOM2 MACLIB I2 *** HCPPSI MACLIB S2 *** HCPGPI MACLIB S2 *** RTMMESA5 MACLIB A1 *** *** If the MACLIBs listed above are correct, press ENTER to *** continue. Otherwise enter QUIT to halt. *** ******************************************************************VMFASM2760I VMFHASM processing started DMSUPD178I Updating RTMCMD ASSEMBLE H1 DMSUPD178I Applying RTMCMD F05041RM F1 DMSUPD178I Applying RTMCMD F05044RM F1 DMSUPD178I Applying RTMCMD F05046RM F1 VMFASM1907I Assembling RTMCMD VMFASM2507I RTMCMD TEXT created on your A-disk for use in a non-VMSES/E environment VMFASM2760I VMFHASM processing completed successfully PRT FILE 0031 SENT FROM 5798DWDC PRT WAS 0031 RECS 010K CPY 001 A NOHOLD NOKEEP VMFASM2760I VMFHASM processing started DMSUPD178I Updating RTMCMP ASSEMBLE H1 DMSUPD178I Applying RTMCMP F05044RM F1 DMSUPD178I Applying RTMCMP F05046RM F1 VMFASM1907I Assembling RTMCMP VMFASM2507I RTMCMP TEXT created on your A-disk for use in a non-VMSES/E environment VMFASM2760I VMFHASM processing completed successfully PRT FILE 0032 SENT FROM 5798DWDC PRT WAS 0032 RECS 011K CPY 001 A NOHOLD NOKEEP VMFASM2760I VMFHASM processing started DMSUPD178I Updating RTMDAT ASSEMBLE H1 DMSUPD178I Applying RTMDAT F05044RM F1 DMSUPD178I Applying RTMDAT F05046RM F1 VMFASM1907I Assembling RTMDAT
VMFASM2507I RTMDAT TEXT created on your A-disk for use in a non-VMSES/E
environment
VMFASM2760I VMFHASM processing completed successfully
PRT FILE 0033 SENT FROM 5798DWDC PRT WAS 0033 RECS 8519 CPY 001 A NOHOLD NOKEEP
VMFASM2760I VMFHASM processing started
DMSUPD178I Updating RTMDRV ASSEMBLE H1
DMSUPD178I Applying RTMDRV F05044RM F1
DMSUPD178I Applying RTMDRV F05046RM F1
VMFASM1907I Assembling RTMDRV
VMFASM2507I RTMDRV TEXT created on your A-disk for use in a non-VMSES/E
environment
VMFASM2760I VMFHASM processing completed successfully
PRT FILE 0034 SENT FROM 5798DWDC PRT WAS 0034 RECS 012K CPY 001 A NOHOLD NOKEEP
VMFASM2760I VMFHASM processing started
DMSUPD178I Updating RTMDSL ASSEMBLE H1
DMSUPD178I Applying RTMDSL F05044RM F1
DMSUPD178I Applying RTMDSL F05046RM F1
VMFASM1907I Assembling RTMDSL
VMFASM2507I RTMDSL TEXT created on your A-disk for use in a non-VMSES/E
environment
VMFASM2760I VMFHASM processing completed successfully
PRT FILE 0035 SENT FROM 5798DWDC PRT WAS 0035 RECS 6257 CPY 001 A NOHOLD NOKEEP
VMFASM2760I VMFHASM processing started
DMSUPD178I Updating RTMDSP ASSEMBLE H1
DMSUPD178I Applying RTMDSP F05044RM F1
DMSUPD178I Applying RTMDSP F05046RM F1
VMFASM1907I Assembling RTMDSP
VMFASM2507I RTMDSP TEXT created on your A-disk for use in a non-VMSES/E
environment
VMFASM2760I VMFHASM processing completed successfully
PRT FILE 0036 SENT FROM 5798DWDC PRT WAS 0036 RECS 012K CPY 001 A NOHOLD NOKEEP
VMFASM2760I VMFHASM processing started
DMSUPD178I Updating RTMDSU ASSEMBLE H1
DMSUPD178I Applying RTMDSU F05044RM F1
DMSUPD178I Applying RTMDSU F05026RM F1
DMSUPD178I Applying RTMDSU F05046RM F1
VMFASM1907I Assembling RTMDSU
VMFASM2507I RTMDSU TEXT created on your A-disk for use in a non-VMSES/E
environment
VMFASM2760I VMFHASM processing completed successfully
PRT FILE 0037 SENT FROM 5798DWDC PRT WAS 0037 RECS 010K CPY 001 A NOHOLD NOKEEP
VMFASM2760I VMFHASM processing started
DMSUPD178I Updating RTMDSV ASSEMBLE H1
DMSUPD178I Applying RTMDSV F05044RM F1
DMSUPD178I Applying RTMDSV F05046RM F1
VMFASM1907I Assembling RTMDSV
VMFASM2507I RTMDSV TEXT created on your A-disk for use in a non-VMSES/E
environment
VMFASM2760I VMFHASM processing completed successfully
PRT FILE 0038 SENT FROM 5798DWDC PRT WAS 0038 RECS 8966 CPY 001 A NOHOLD NOKEEP
VMFASM2760I VMFHASM processing started
DMSUPD178I Updating RTMDSW ASSEMBLE H1
DMSUPD178I Applying RTMDSW F05016RM F1
DMSUPD178I Applying RTMDSW F05044RM F1
DMSUPD178I Applying RTMDSW F05046RM F1
VMFASM1907I Assembling RTMDSW
VMFASM2507I RTMDSW TEXT created on your A-disk for use in a non-VMSES/E
environment
VMFASM2760I VMFHASM processing completed successfully
PRT FILE 0039 SENT FROM 5798DWDC PRT WAS 0039 RECS 7701 CPY 001 A NOHOLD NOKEEP
VMFASM2760I VMFHASM processing started
DMSUPD178I Updating RTMDSX ASSEMBLE H1
DMSUPD178I Applying RTMDSX F05043RM F1
DMSUPD178I Applying RTMDSX F05044RM F1
DMSUPD178I Applying RTMDSX F05046RM F1
VMFASM1907I Assembling RTMDSX
VMFASM2507I RTMDSX TEXT created on your A-disk for use in a non-VMSES/E
environment
VMFASM2760I VMFHASM processing completed successfully
PRT FILE 0040 SENT FROM 5798DWDC PRT WAS 0040 RECS 6183 CPY 001 A NOHOLD NOKEEP
VMFASM2760I VMFHASM processing started
DMSUPD178I Updating RTMERM ASSEMBLE H1
DMSUPD178I Applying RTMERM F05046RM F1
VMFASM1907I Assembling RTMERM
VMFASM2507I RTMERM TEXT created on your A-disk for use in a non-VMSES/E
environment
VMFASM2760I VMFHASM processing completed successfully
PRT FILE 0041 SENT FROM 5798DWDC PRT WAS 0041 RECS 4604 CPY 001 A NOHOLD NOKEEP
VMFASM2760I VMFHASM processing started
DMSUPD178I Updating RTMIOP ASSEMBLE H1
DMSUPD178I Applying RTMIOP F05045RM F1
DMSUPD178I Applying RTMIOP F05044RM F1
DMSUPD178I Applying RTMIOP F05046RM F1
VMFASM1907I Assembling RTMIOP
VMFASM2507I RTMIOP TEXT created on your A-disk for use in a non-VMSES/E
environment
VMFASM2760I VMFHASM processing completed successfully
PRT FILE 0042 SENT FROM 5798DWDC PRT WAS 0042 RECS 011K CPY 001 A NOHOLD NOKEEP
VMFASM2760I VMFHASM processing started
DMSUPD178I Updating RTMOUT ASSEMBLE H1
DMSUPD178I Applying RTMOUT F05046RM F1
VMFASM1907I Assembling RTMOUT
VMFASM2507I RTMOUT TEXT created on your A-disk for use in a non-VMSES/E
environment
VMFASM2760I VMFHASM processing completed successfully
PRT FILE 0043 SENT FROM 5798DWDC PRT WAS 0043 RECS 2873 CPY 001 A NOHOLD NOKEEP
VMFASM2760I VMFHASM processing started
DMSUPD178I Updating RTMSDA ASSEMBLE H1
DMSUPD178I Applying RTMSDA F05045RM F1
DMSUPD178I Applying RTMSDA F05044RM F1
DMSUPD178I Applying RTMSDA F05046RM F1
VMFASM1907I Assembling RTMSDA
VMFASM2507I RTMSDA TEXT created on your A-disk for use in a non-VMSES/E
environment
VMFASM2760I VMFHASM processing completed successfully
PRT FILE 0044 SENT FROM 5798DWDC PRT WAS 0044 RECS 9769 CPY 001 A NOHOLD NOKEEP
VMFASM2760I VMFHASM processing started
DMSUPD178I Updating RTMSRV ASSEMBLE H1
DMSUPD178I Applying RTMSRV F05046RM F1
VMFASM1907I Assembling RTMSRV
VMFASM2507I RTMSRV TEXT created on your A-disk for use in a non-VMSES/E
environment
VMFASM2760I VMFHASM processing completed successfully
PRT FILE 0045 SENT FROM 5798DWDC PRT WAS 0045 RECS 011K CPY 001 A NOHOLD NOKEEP
VMFASM2760I VMFHASM processing started
DMSUPD178I Updating RTMSYS ASSEMBLE H1
DMSUPD178I Applying RTMSYS F05044RM F1
DMSUPD178I Applying RTMSYS F05046RM F1
VMFASM1907I Assembling RTMSYS
VMFASM2507I RTMSYS TEXT created on your A-disk for use in a non-VMSES/E
environment
VMFASM2760I VMFHASM processing completed successfully
PRT FILE 0046 SENT FROM 5798DWDC PRT WAS 0046 RECS 8347 CPY 001 A NOHOLD NOKEEP
VMFASM2760I VMFHASM processing started
DMSUPD178I Updating RTMSYT ASSEMBLE H1
DMSUPD178I Applying RTMSYT F05044RM F1
DMSUPD178I Applying RTMSYT F05046RM F1
VMFASM1907I Assembling RTMSYT
VMFASM2507I RTMSYT TEXT created on your A-disk for use in a non-VMSES/E
environment
VMFASM2760I VMFHASM processing completed successfully
PRT FILE 0047 SENT FROM 5798DWDC PRT WAS 0047 RECS 8713 CPY 001 A NOHOLD NOKEEP
VMFASM2760I VMFHASM processing started
DMSUPD178I Updating RTMUSR ASSEMBLE H1
DMSUPD178I Applying RTMUSR F05044RM F1
DMSUPD178I Applying RTMUSR F05046RM F1
VMFASM1907I Assembling RTMUSR
VMFASM2507I RTMUSR TEXT created on your A-disk for use in a non-VMSES/E
environment
VMFASM2760I VMFHASM processing completed successfully
PRT FILE 0048 SENT FROM 5798DWDC PRT WAS 0048 RECS 013K CPY 001 A NOHOLD NOKEEP
VMFASM2760I VMFHASM processing started
DMSUPD181E No update files were found
VMFASM1907I Assembling RTMVMC
VMFASM2507I RTMVMC TEXT created on your A-disk for use in a non-VMSES/E
environment
VMFASM2760I VMFHASM processing completed successfully
PRT FILE 0049 SENT FROM 5798DWDC PRT WAS 0049 RECS 3396 CPY 001 A NOHOLD NOKEEP
******************************************************************
***
*** RTM build completed successfully.
***
*** Copying all TEXT files, MACLIB, and/or MODULE to the test disk.
***
******************************************************************
DASD 0101 DETACHED
****************************************************************** *** *** Exiting RTMBLD EXEC. *** *** You should now copy the RTM MODULE to the RTM VM/ESA service *** machine's 191 disk. *** ****************************************************************** Ready; T=25.78/39.68 13:47:57 vmcload Ready; T=0.01/0.02 13:48:28
Note: In this example, the user issues VMCLOAD to create a new VMC MODULE since RTMBLD does not create it. The user would now copy the the new RTM and VMC MODULEs to the appropriate disks. (By default, these are the RTM VM/ESA service machines' 191 and MAINT 19E disk respectively).