Program Directory for Realtime Monitor VM/ESA - z/VM - IBM

IBMProgram Directory forRealtime Monitor VM/ESARelease 5.2Program Number 5798-DWDfor Use withVM/ESA Release 2.1VM/ESA Release 2.2VM/ESA Version 2 Release 1Document Date: October 1997xxxx-yyyy-zz

Note!Before using this information and the product it supports, be sure to read the general information under “Notices” on page vi.This program directory, dated October 1997, applies to Realtime Monitor VM/ESA (RTM VM/ESA) Release 5.2, Program Number5798-DWD for the following:COMPIDsFeature Numbers5798DWD00 589158925702A form for reader's comments appears at the back of this publication. When you send information to IBM, you grant IBM anonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you.© Copyright International Business Machines Corporation 1985, 1992. All rights reserved.Note to U.S. Government Users — Documentation related to restricted rights — Use, duplication or disclosure is subject torestrictions set forth in GSA ADP Schedule Contract with IBM Corp.

ContentsNotices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viTrademarks and Service Marks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi1.0 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.0 Program Materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.1 Basic Machine-Readable Material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.2 Program Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32.2.1 Basic Program Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32.3 Microfiche Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32.4 Publications Useful During Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33.0 Program Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53.1 Preventive Service Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53.2 Statement of Support Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54.0 Program and Service Level Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64.1 Program Level Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64.2 Service Level Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64.3 Cumulative Service Tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65.0 Installation Requirements and Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75.1 System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75.1.1 Programming Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75.1.2 DASD Storage Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75.1.2.1 Install on Minidisks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75.1.2.2 Install on SFS Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95.1.2.2.1 Filepool Space Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95.1.2.2.2 Additional Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95.1.3 Userid Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95.1.3.1.1 CP Directory Entries for Minidisk Install . . . . . . . . . . . . . . . . . . . . . . . . . . 105.1.3.1.2 CP Directory Entries for SFS Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115.2 Program Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125.2.1 Operating System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125.3 System Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136.0 Installation Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146.1 Installing RTM VM/ESA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146.1.1 Installation with VMFINS (VMSES/E) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146.1.2 Installation with INSTFPP (Non-VMSES/E) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196.1.2.1 Overview of non-SES installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206.1.2.1.1 Overview of RTMBLD: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20© Copyright IBM Corp. 1985, 1992 iii

6.1.2.2 Pre-installation instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216.1.2.2.1 Changing the RTMDISK EXEC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216.1.2.2.2 Changing the Default Minidisks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226.1.2.2.3 Changing the Defaults Before Installation . . . . . . . . . . . . . . . . . . . . . . . . . 226.1.2.2.4 Changing the Defaults After Installation . . . . . . . . . . . . . . . . . . . . . . . . . . 226.1.2.2.5 Example RTMDISK EXEC with Changes . . . . . . . . . . . . . . . . . . . . . . . . . . 236.1.2.3 Non-VMSES/E Installation Instructions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236.1.2.4 Installation program I5798DWD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246.1.2.4.1 Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246.1.2.4.2 Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256.1.2.5 GA Level Installs (I5798DWD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266.1.2.5.1 Example of a GA level install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266.1.2.6 RTMBLD program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286.1.2.6.1 RTMDISK EXEC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286.1.2.6.2 Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286.1.2.6.3 VMCLOAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296.2 Post Installation Consideration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306.2.1 Activating the Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306.2.2 Access to RTM VM/ESA via the VMC command . . . . . . . . . . . . . . . . . . . . . . . . . . 316.2.3 Modifying RTM VM/ESA Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326.2.4 Customizing the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336.2.5 Service to CP control blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346.3 Building RTM VM/ESA For Multiple VM Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357.0 Service Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367.1 VMSES/E Service Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367.1.1 VMSES/E Service Process Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367.1.2 Servicing RTM VM/ESA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377.1.3 RTM Product Rebuild . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427.2 Non-VMSES/E Service Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437.2.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437.2.2 Installing Non-VMSES/E Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437.2.3 Re-building the product. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457.2.4 RTM Product Rebuild . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457.3 Non-VMSES/E RTM Build Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Appendix A. Applying Local Modifications to RTM VM/ESA. . . . . . . . . . . . . . . . . . . . . . . 47A.1 VMSES/E Local Modifications Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47A.1.1 Assemble Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47A.1.2 Full Part Replacement Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47A.2 Non-VMSES/E Local Modifications Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Appendix B. Sample output from BUILD command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Appendix C. Sample non-VMSES/E install from 9302 Refresh Tape . . . . . . . . . . . . . . . . . . 57ivRTM VM/ESA Program Directory

Appendix D. Sample Non-VMSES/E Install with CORrective Service Tape. . . . . . . . . . . . . . . 68D.1 Install of GA Product Tape with I5798DWD EXEC . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68D.2 Install of Cumulative Service Tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70D.3 Build of RTM VM/ESA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Reader's Comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87Figures1. Basic Material: Program Tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22. Program Tape: File Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23. Basic Material: Unlicensed Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34. Publications Useful During Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35. Publications Useful During Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46. PSP Upgrade and Subset ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57. Component IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58. DASD Storage Requirements for Target Minidisks/Directories . . . . . . . . . . . . . . . . . . . . 79. SFS Directory Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 910. RTM VM/ESA field equates table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Contentsv

NoticesReferences in this document to IBM products, programs, or services do not imply that IBM intends tomake 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. Anyfunctionally equivalent product, program, or service that does not infringe on any of IBM's intellectualproperty rights may be used instead of the IBM product, program, or service. Evaluation and verificationof operation in conjunction with other products, except those expressly designated by IBM, is the user'sresponsibility.IBM may have patents or pending patent applications covering subject matter in this document. Thefurnishing of this document does not give you any license to these patents. You can send licenseinquiries, in writing, to theIBM Director of Commercial RelationsIBM CorporationPurchase, NY 10577Trademarks and Service MarksThe following terms, denoted by an asterisk (*), used in this document, are trademarks or service marks ofIBM Corporation in the United States or other countries:IBMVM/ESARealtime Monitor VM/ESAvi © Copyright IBM Corp. 1985, 1992

1.0 IntroductionThis program directory is intended for the system programmer responsible for program installation andmaintenance. It contains information concerning the material and procedures associated with theinstallation of RTM VM/ESA. You should read all of this program directory before installing theprogram and then keep it for future reference.The program directory contains the following sections: 2.0, “Program Materials” on page 2 identifies the basic and optional program materials anddocumentation for RTM VM/ESA. 3.0, “Program Support” on page 5 describes the IBM support available for RTM VM/ESA. 4.0, “Program and Service Level Information” on page 6 lists the APARs (program level) and PTFs(service level) incorporated into RTM VM/ESA. 5.0, “Installation Requirements and Considerations” on page 7 identifies the resources andconsiderations for installing and using RTM VM/ESA. 6.0, “Installation Instructions” on page 14 provides detailed installation instructions for RTM VM/ESA. 7.0, “Service Instructions” on page 36 provides detailed servicing instructions for RTM VM/ESA.Before installing RTM VM/ESA, read 3.1, “Preventive Service Planning” on page 5. This section tells youhow to find any updates to the information and procedures in this program directory.© Copyright IBM Corp. 1985, 1992 1

2.0 Program MaterialsAn IBM program is identified by a program number. The program number for RTM VM/ESA is5798-DWD.The program announcement material describes the features supported by RTM VM/ESA. Ask your IBMmarketing 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.2.1 Basic Machine-Readable MaterialThe distribution medium for this program is 9-track magnetic tape (written at 6250 BPI) and 3480 tapecartridge. The tape or cartridge contains all the programs and data needed for installation. See 6.0,“Installation Instructions” on page 14 for more information about how to install the program. Figure 1describes the tape or cartridge. Figure 2 describes the file content of the program tape or cartridge.Figure 1. Basic Material: Program TapeFeatureNumberMedium5891 6250tape5892 3480cart.5702 4MM-DATCartridgePhysicalVolume Tape Content External Tape Label1 RTM 1.5.2 Base Product RTM152 Base 1of11 RTM 1.5.2 Base Product RTM152 Base 1of11 RTM 1.5.2 Base Product RTM152 Base 1of1Figure 2 (Page 1 of 2). Program Tape: File ContentTapeFileContent1 tape header 102 product header 33 service apply lists 24 PTFPARTs 95 RTM service (VMSES/E) 786 RTM service (VMSES/E) 367 RTM source code 738 RTM Maclib 159 VMC Module 2Number offiles2 © Copyright IBM Corp. 1985, 1992

Figure 2 (Page 2 of 2). Program Tape: File ContentTapeFileContent10 RTM samples 511 RTM service (non-VMSES/E) 5612 RTM service (non-VMSES/E) 31Number offiles2.2 Program PublicationsThe following sections identify the basic and optional publications for RTM VM/ESA.2.2.1 Basic Program PublicationsOne copy of the following publication is included when you order the basic materials for RTM VM/ESA.For additional copies, contact your IBM representative.Figure 3. Basic Material: Unlicensed PublicationsPublication TitleRealtime Monitor VM/ESA Program Description/Operations ManualForm NumberSH26-70002.3 Microfiche SupportThere is no microfiche for RTM VM/ESA.2.4 Publications Useful During InstallationIf you are installing RTM VM/ESA on VM/ESA Version 2 Release 1, then you may find the followingpublications listed in Figure 4 useful during installation. To order copies, contact your IBM representative.Figure 4. Publications Useful During InstallationPublication TitleVMSES/E Introduction And ReferenceVM/ESA Service GuideForm NumberSC24-5747SC24-5749If you are installing RTM VM/ESA on VM/ESA Release 2, then you may find the following publicationslisted in Figure 5 useful during installation. To order copies, contact your IBM representative.Program Materials 3

3.0 Program SupportThis section describes the IBM support available for RTM VM/ESA.3.1 Preventive Service PlanningBefore installing RTM VM/ESA, check with your IBM Support Center or use either Information/Access orIBMLink (Service Link) to see whether there is additional Preventive Service Planning (PSP) informationthat you should know. To obtain this information, specify the following UPGRADE and SUBSET values:Figure 6. PSP Upgrade and Subset IDRelease Code Upgrade Subset152 VMRTMESA152 RTMESA/152F52 VMRTMESA152 RTMESA/F52If 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 SoftwareXcelExtended to see if there is additional PSP information that you should know.3.2 Statement of Support ProceduresReport any difficulties you have using this program to your IBM Support Center. In the U.S.A., if an APARis required, submit the data to the location identified in the Programming System General Informationmanual (PSGIM), G229-2228, as being responsible for the failing component.Figure 7 identifies the component ID (COMPID), Retain Release and Field Engineering Service Number(FESN) for RTM VM/ESA.Figure 7. Component IDsRelease CodeCOMPIDRetainReleaseComponent NameFESN152 5798DWD00 152 RTM VM/ESA 152 0991822F52 5798DWD00 F52 RTM VM/ESA 152 (non-VMSES/E) 0991822© Copyright IBM Corp. 1985, 1992 5

4.0 Program and Service Level InformationThis section identifies the program and any relevant service levels of RTM VM/ESA. The program levelrefers 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.4.1 Program Level InformationThe following APAR fixes against previous releases of RTM VM/ESA have been incorporated into thisrelease:GC04908GC04939GC04458GC04872GC04868GC04859GC04794GC04796GC04788GC04780GC04769GC04475GC04731GC04683GC04634GC046184.2 Service Level InformationThe following APAR fixes to RTM VM/ESA 1.5.2 are incorporated into this product tape:GC05012GC05016GC05041GC05043GC05045GC05044GC05026GC05046GC05103GC05121GC05109GC05131GC05143GC05162GC05182GC05201GC05219GC05242GC05262GC05288GC04959GC04960GC04949GC05340GC05354GC05115GC05357GC05362GC05363GC05365GC053744.3 Cumulative Service TapeThere is no cumulative service tape for RTM VM/ESA that ships with the product.6 © Copyright IBM Corp. 1985, 1992

5.0 Installation Requirements and ConsiderationsThe following sections identify the system requirements for installing and activating RTM VM/ESA.5.1 System RequirementsThis section describes the system environment required to install RTM VM/ESA.5.1.1 Programming RequirementsRTM 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 soHLASM must be installed before installing RTM VM/ESA on VM/ESA Version 2.5.1.2 DASD Storage RequirementsRTM VM/ESA can be installed on either minidisks or SFS directories. The following is a listing of thedefault minidisks/directories required to install RTM VM/ESA. The shipped version of RTM VM/ESA is setup to install without any user modifications on the following minidisks or directories.5.1.2.1 Install on Minidisks: The following table lists the userids, minidisks and their spacerequirements. Skip to the next section if you are installing on SFS.Figure 8 (Page 1 of 2). DASD Storage Requirements for Target Minidisks/DirectoriesMinidiskowner(userid)DefaultAddress5798DWDC 2B2 934533903380337533505798DWDC 2C2 934533903380337533505798DWDC 2D2 93453390338033753350Storage inCylindersStorage in BlocksDASD CYLS Type Blocks2017202020222221513151515FB5121K2K4KFB5121K2K4KFB5121K2K4K2400012000600030002400120060030018000900045002250DescriptionSource disk.Contains RTMsource files.Sample Files.Update disk.Contains allupdate files forthe product.© Copyright IBM Corp. 1985, 1992 7

Figure 8 (Page 2 of 2). DASD Storage Requirements for Target Minidisks/DirectoriesMinidiskowner(userid)DefaultAddress5798DWDC 2A6 934533903380337533505798DWDC 2A2 934533903380337533505798DWDC 191 934533903380337533505798DWDC 401 934533903380337533505798DWDC 400 93453390338033753350RTMESA n/a 93453390338033753350Storage inCylindersStorage in BlocksDASD CYLS Type Blocks555551091010101091010101091010101513151515n/an/an/an/an/aFB5121K2K4KFB5121K2K4KFB5121K2K4KFB5121K2K4KFB5121K2K4Kn/an/an/an/a60003000150075012000600030001500120006000300015001200060003000150018000900045002250n/an/an/an/aDescriptionAuxfile disk.Contains the AUXfiles used duringa build of theproduct.Staging disk.Used to saveprevious versionof AUX files.Work disk. Usedto temporarilystore files createdduring build ofproduct.Server machinesA disk. Used tostore theproduction versionof RTM VM/ESATest disk. Usedto store objectfiles createdduring productbuild.n/aNote: For non-VMSES/E installations, the number of required minidisks may be changed by theinstallation in order to decrease the amount of total DASD space used. Refer to section 6.1.2.2.2,“Changing the Default Minidisks” on page 22 for details on how this is done.8 RTM VM/ESA Program Directory

5.1.2.2 Install on SFS Directories: The following table lists the userids, directories and the totalfilepool space requirements in 4K blocks. Skip this section if you are installing on minidisk.Figure 9. SFS Directory RequirementsDirectoryowner(userid) Directory name Description5798DWDC 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 forthe product.5798DWDC VMSYS:5798DWDC.ALTAPPLY Auxfile directory. Contains the AUX files used duringa build of the product.5798DWDC VMSYS:5798DWDC.PRDAPPLY Staging directory. Used to save previous versionof AUX files.5798DWDC VMSYS:5798DWDC. Work directory. Used to temporarily storefiles created during build of product.5798DWDC VMSYS:5798DWDC.TBUILD Test disk. Used to store object filescreated during product build.RTMESA VMSYS:RTMESA. Server machines A directory. Used tostore the production version of RTM VM/ESA5.1.2.2.1 Filepool Space Requirements: The filepool space requirements in filepool VMSYS will be1500 4K blocks for user RTMESA and 11,500 blocks for user 5798DWDC.5.1.2.2.2 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.5.1.3 Userid RequirementsRTM VM/ESA requires two userids. 5798DWDC is used for installation and service. This userid requiresaccess to CP maclibs: HCPOM1, HCPOM2, HCPPSI and HCPGPI. By default, these are located on theMAINT 190 and 193 disks. If this is not correct for your system, ensure that the disks that do containthese maclibs are accessible to user 5798DWDC. In addition, RTM VM/ESA requires access to theDMSGPI maclib and the H-assembler. By default, these files are located on the MAINT 190 and 19Edisks. Again, if this is does not reflect your system, ensure that the disks containing the DMSGPI macliband the H-assembler are accessible to user 5798DWDC. If you are installing RTM VM/ESA on VM/ESARelease 1.1, then you also need a link to MAINT 5E5 disk for the INSTFPP EXEC. RTMESA is theproduct server machine. It requires class E privilege because RTM accesses CP control block data areasduring execution.Note: Wherever the locations of your maclibs and H-assembler are, you must ensure that they are onminidisks or directories that are accessed when the product is built. For VMSES/E installations, this isInstallation Requirements and Considerations 9

USER RTMESA xxxxx 32M 32M EGUSER RTMESA xxxxx 16M 16M EG (for VM/ESA Release 2.2 or earlier releases)OPTION QUICKDSPMACHINE 37(for VM/ESA Release 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 OPERATORACCOUNT xxxxIPL CMSCONSOLE 9 3215SPOOL C 254 READER SPOOL D 254 PUNCH ASPOOL E 143 ALINK MAINT 19 19 RRLINK MAINT 19D 19D RRLINK MAINT 19E 19E RRLINK 5798DWDC 41 191 MR5.1.3.1.2 CP Directory Entries for SFS Install: Skip this next section if installing on minidiskFollowing are sample directory statements for these userids Note that the actual LINK statements you usewill depend on the location of the CP maclibs required for the build of RTM VM/ESA and the address ofthe disk where the H-assembler is installed.USER 5798DWDC xxxxx 16M 16M GMACHINE 37(for VM/ESA Release 2.2 or earlier releases only)MACHINE XA(for VM/ESA Version 2 Release 1 or later releases only)ACCOUNT xxxxIPL CMS PARM FILEPOOL VMSYS:CONSOLE 9 3215SPOOL C 254 READER SPOOL D 254 PUNCH ASPOOL E 143 ALINK MAINT 193 193 RRLINK MAINT 51D 51D MR (for VM/ESA Release 2 or later releases only)LINK MAINT 5E5 5E5 RRLINK MAINT 19 19 RRLINK MAINT 19D 19D RRLINK MAINT 19E 19E RRInstallation Requirements and Considerations 11

USER RTMESA xxxxx 32M 32M EGUSER RTMESA xxxxx 16M 16M EG (for VM/ESA Release 2.2 or earlier releases)OPTION QUICKDSPMACHINE 37(for VM/ESA Release 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 OPERATORACCOUNT xxxxIPL CMS PARM FILEPOOL VMSYS:CONSOLE 9 3215SPOOL C 254 READER SPOOL D 254 PUNCH ASPOOL E 143 ALINK MAINT 19 19 RRLINK MAINT 19D 19D RRLINK MAINT 19E 19E RR5.2 Program ConsiderationsThe following sections list the programming considerations for installing RTM VM/ESA and activating itsfunctions.5.2.1 Operating System RequirementsThe following operating systems support RTM VM/ESA. VM/ESA Version 2 Release 1 VM/ESA Release 2.2 VM/ESA Release 2.1The 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 refreshproduct tape.RTM VM/ESA will run on the following operating system if RTM APAR GC05046 is applied: VM/ESA Release 1.112 RTM VM/ESA Program Directory

5.3 System ConsiderationsIf RTM VM/ESA is being installed on VM/ESA Release 2 or later releases, then the product should beinstalled according to the instructions listed in 6.1.1, “Installation with VMFINS (VMSES/E)” on page 14With APAR GC05046, RTM VM/ESA will run on VM/ESA Release 1.1 which requires a non-VMSES/Einstallation. Refer to the installation instructions listed in 6.1.2, “Installation with INSTFPP(Non-VMSES/E)” on page 19.Note: The VM Release Compatability Information has been moved to the RTM VM/ESA OperationsManual available 6/94.Installation Requirements and Considerations 13

6.0 Installation Instructions6.1 Installing RTM VM/ESAIf RTM VM/ESA is being installed on VM/ESA Release 2 or later releases, then the product should beinstalled according to the instructions listed in 6.1.1, “Installation with VMFINS (VMSES/E)” on page 14With APAR GC05046, RTM VM/ESA will run on VM/ESA Release 1.1 which requires a non-VMSES/Einstallation. Refer to the installation instructions listed in 6.1.2, “Installation with INSTFPP(Non-VMSES/E)” on page 19. You must order and apply the latest service for RTM VM/ESA beforecompleting the build step on a VM/ESA Release 1.1 system.6.1.1 Installation with VMFINS (VMSES/E)Note: VM APAR VM56361 is required to install the product from the 9302 refresh tape. Note: VM56361is 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/Ewith 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 andReference (SC24-5444). The "Install Scenarios" chapter illustrates how various VMFINS operands andoptions are used.You may plan the install of the product from a general userid that has access to the minidisks named insteps 3 and 4 below. The plan function of the install will generate a 'PLANINFO' file listing all: the userid/mdisks requirements required productsfor installing RTM VM/ESA. The plan function is shown below (steps 1 - 7). Once your userid has beenadded and all product requirements have been met you can log on to the new userid and proceed withstep 8 to install the product.PlanTo plan the product install use the following steps:1. Log on to userid 5798DWDC.Note: The userid used must have access to the 2 minidisks listed in steps 3 and 4 below.2. Mount the installation tape and attach it as virtual device 181.14 © Copyright IBM Corp. 1985, 1992

3. Link and access the minidisks that contain the DMSGPI maclib and H-assembler if they are differentthan the 190 and 19E disks.4. Link and access the MAINT 5E5 disk as filemode B in read mode.5. Link and access the MAINT 51D disk as filemode D in read/write mode.6. Format all the required minidisks or create all of the SFS directories defined in 5.1.2, “DASD StorageRequirements” on page 7. If you are installing on SFS, be sure to give user 5798DWDC authority tocreate and replace files in the VMSYS:RTMESA. directory.7. Issue the following VMSES/E command with the INFO option. This command will load the productmemos and product's VMSES/E control files to MAINT's 51D disk. It will also load a 5798DWDCPRODLIST to your A-disk or directory that lists all products included on the tape.VMFINS INSTALL INFO (NOMEMOThe NOMEMO option will load the memos but will not issue a prompt to send them to the systemprinter. 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 ( nomemoVMFINS276I VMFINS processing startedVMFINS199I VMFINS PRODLIST created on your A-diskVMFINS276I VMFINS processing completed successfully8. Use the VMFINS INSTALL command with the PLAN option to get useful resource planninginformation. The product will not be loaded at this time.Do this by issuing:VMFINS INSTALL PPF 5798DWDC RTMINS (ADD PLAN NOMEMORTMINSSFSNote: Use RTMINS if installing the product on minidisk, or RTMINSSFS if installing the product onSFS. 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 systemresources, and provide an opportunity to override the defaults in the product parameter file. Youroverride can change the name of your product parameter file or change the default userids, diskaddresses and/or directory names.The following is an example of the screen displayed after issuing the above VMFINS command:Installation Instructions 15

vmfins install ppf 5798DWDC rtmins (add plan nomemoVMFINS276I VMFINS processing startedVMFREQ285I Product 5798DWDC component RTM passed requisite checkingDo you want to create an override for 5798DWDC RTM (prodid 5798DWDC)Enter (No), 1 (Yes) or 2 (Exit)VMFRMT276I VMFRMT processing startedVMFRMT276I VMFRMT processing completed successfullyVMFPLA199I 5798DWDC PLANINFO created on your A-diskVMFINS276I VMFINS processing completed successfullyUse the '1' option if you wish to make changes to the default installation configuration for RTMVM/ESA.9. Use the planning information in the 5798DWDC PLANINFO file, created in the PLAN step, to createthe required userids and minidisks with VM/Dirmaint or an equivalent CP directory maintenancemethod.Note: Make sure the minidisks are formatted before beginning the install.InstallYou are now ready to install RTM VM/ESA10. To install RTM VM/ESA run the VMFINS INSTALL command.The next command assumes you are logged onto 5798DWDC userid, the default userid for RTMVM/ESA. If you chose to change the default userid/minidisks, etc. you should now logon to the useridyou 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/Wat filemode D before beginning this step.VMFINS INSTALL PPF 5798DWDC RTMINS (ADD NOMEMO NOLINKRTMINSSFSNote: Use RTMINS if installing the product on minidisk, or RTMINSSFS if installing the product onSFS. 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, onlyaccess 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 alreadyprinted in the planning step.The following is an example of the screen displayed after issuing the above VMFINS command:16 RTM VM/ESA Program Directory

VMFINS276I VMFINS processing startedVMFREQ285I Product 5798DWDC component RTM passed requisite checkingDo you want to create an override for 5798DWDC RTM (prodid 5798DWDC)?Enter (No), 1 (Yes) or 2 (Exit)VMFINT276I VMFINST processing startedVMFLDP276I 5798DWDC RTM (prodid 5798DWDC) will be processed as a PDI productVMFSET276I VMFSETUP processing startedVMFUTL225I Minidisk|Directory Assignments:String Mode Stat Vdev Label/DirectoryVMFUTL225I LOCALSAM E R/W 2C2 5792C2VMFUTL225I APPLY F R/W 2A6 5792A6VMFUTL225I G R/W 2A2 5792A2VMFUTL225I DELTA H R/W 2D2 5792D2VMFUTL225I BUILD I R/W 4 5794VMFUTL225I BUILD1 J R/W 41 57941VMFUTL225I BUILD6 K R/O 19 MNT19VMFUTL225I BUILD6 S R/O 19 MNT19VMFUTL225I BUILD7 L R/O 193 MNT193VMFUTL225I BASE1 M R/W 2B2 5792B2VMFUTL225I -------- A R/W 191 579191VMFUTL225I -------- B R/O 5E5 MNT5E5VMFUTL225I -------- D R/W 51D MNT51DVMFUTL225I -------- Y/S R/O 19E MNT19EVMFSET276I VMFSETUP processing completed successfullyVMFREC276I VMFREC processing startedVMFREC1851I (1 of 8) VMFRCAXL processing AXLISTVMFRCX2159I Loading part(s) to DELTA 2D2 (H)VMFREC1851I (2 of 8) VMFRCPTF processing PARTLSTVMFRCP2159I Loading part(s) to DELTA 2D2 (H)VMFREC1851I (3 of 8) VMFRCCOM processing DELTAVMFRCC2159I Loading part(s) to DELTA 2D2 (H)VMFREC1851I (4 of 8) VMFRCALL processing APPLYVMFRCA2159I Loading part(s) to APPLY 2A6 (F)VMFRCA2159I Loaded 19 part(s) to APPLY 2A6 (F)VMFREC1851I (5 of 8) VMFRCALL processing SOURCEVMFRCA2159I Loading part(s) to BASE1 2B2 (M)VMFRCA2159I Loaded 73 part(s) to BASE1 2B2 (M)VMFREC1851I (6 of 8) VMFRCALL processing RTMMACVMFRCA2159I Loading part(s) to BUILD 4 (I)VMFRCA2159I Loaded 1 part(s) to BUILD 4 (I)VMFREC1851I (7 of 8) VMFRCALL processing VMCMODVMFRCA2159I Loading part(s) to BUILD 4 (I)VMFRCA2159I Loaded 1 part(s) to BUILD 4 (I)VMFREC1851I (8 of 8) VMFRCALL processing SAMPLEVMFRCA2159I Loading part(s) to LOCALSAM 2C2 (E)VMFRCA2159I Loaded 5 part(s) to LOCALSAM 2C2 (E)VMFREC276I VMFREC processing completed successfullyVMFINT276I VMFINST processing completed successfullyInstallation Instructions 17

VMFINS276I VMFINS processing completed successfullyYou may be prompted for additional information during VMFINS INSTALL processing depending onyour installation environment. If you are unsure how to respond to a prompt refer to the “InstallingProducts with VMFINS” and “Install Scenarios” chapters in the VMSES/E Introduction and Referenceto decide how to proceed.When processing is complete, you see the message:VMFINS276I VMFINS processing completed successfullyIf you have service to apply to RTM/ESAIf you have a service tape to apply to RTM/ESA go to 7.0, “Service Instructions” on page 36 tocomplete the installation11. Build the new RTM VM/ESA using the following command:If you are installing on VM/ESA Version 2 or laterIf you are installing on VM/ESA Version 2 or later you must have HLASM (5696-234) installedbefore you can complete the build.VMFINS BUILD PPF 5798DWDC RTMINS (ALL NOLINKRTMINSSFSNote: Use RTMINS if installing the product on minidisk, or RTMINSSFS if installing the product onSFS.The ALL option for VMFINS BUILD will build all RTM VM/ESA 152 objects, regardless of whether theyinclude service.Note: See Appendix B, “Sample output from BUILD command.” on page 49 for output from theVMFINS BUILD command.Post installPut RTM VM/ESA into production when testing is completed.12. Copy the RTM VM/ESA code to 5798DWDC's 401 disk (production BUILD disk for minidisk install) orto the VMSYS:RTMESA. directory (production build directory for SFS install). For minidisk install issue the following commands:ACCESS 4 E/EACCESS 41 FCOPYFILE RTM MODULE E = = F (OLDDATE REPLACENote: The RTMESA server machine links to the 401 as 191 and therefore gets access to thenew RTM module. For SFS install issue the following commands:18 RTM VM/ESA Program Directory

ACCESS VMSYS:5798DWDC.TBUILD EACCESS VMSYS:RTMESA. F (FORCERWCOPYFILE RTM MODULE E = = F (OLDDATE REPLACE13. You will also need to put the VMC MODULE into production. For minidisk install issue the following commands:ACCESS 4 E/ESENDFILE VMC MODULE E TO MAINT For SFS install issue the following commands:ACCESS VMSYS:5798DWDC.TBUILD ESENDFILE VMC MODULE E TO MAINTThe MAINT owner should copy the VMC MODULE to the 19E disk. MAINT must also re-save CMS toput the 19E (Y-disk) back in shared status.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 6.2.1, “Activating the Program” on page 30 for instructions on activating the program.6.1.2 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 someinstallation defaults. It is recommended that you read this section before starting an actual install of theproduct. For an example of a non-VMSES/E install with the GA product tape with a cumulative servicetape applied, see appendix D. For an example of a non-VMSES/E install from the 9302 refresh producttape see appendix C. For instructions on how to apply local modifications to the RTM VM/ESA sourcecode, see appendix A.The non-SES build EXECs (RTMBLD and RTMDISK) are used to build RTM VM/ESA. These EXECswere 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 includesupport for install on SFS directories are provided with APAR GC05109. The build EXECs are on the9302 refresh product tape, which contains PTFs for APARS GC05046 and GC05109. In addition, the9302 refresh tape contains a serviced install EXEC (I5798DWD). The instructions provided here are forthe 9302 refresh product tape install and the GA level product install AFTER the PTFs for APARsGC05046 and GC05109 have been applied. Differences in the install process between the GA producttape and the 9302 refresh product tape will be noted by GA level installs.Installation Instructions 19

6.1.2.1 Overview of non-SES installation.: Here is an overview of what will happen during anon-SES install of RTM VM/ESA.1. Minidisks/SFS directories and CP directory entries are defined according to instructions provided in5.1, “System Requirements” on page 7.2. If installing on minidisk, minidisks are formatted.3. Tape is mounted and attached to 5798DWDC as 181.4. User invokes INSTFPP which invokes I5798DWD (or alternatively I5798DWD can be invoked withoutINSTFPP)5. I5798DWD will ask the user if the install will be to the default minidisks, the default directories, or if theuser 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, sourceand test disks. There is no service on the GA level product tape, so the auxfile and update disks areleft untouched by I5789DWD EXEC. Please refer to the section 6.1.2.5, “GA Level Installs(I5798DWD)” on page 26 for details on how to install from the GA product tape. Also see appendix Dfor an example of an install from the GA product tape.6. I5798DWD will download all the files from the install tape to minidisk or SFS directories.7. If required, install service (see 7.2, “Non-VMSES/E Service Instructions” on page 43 for moreinformation.) and/or apply local modifications (see Appendix A, “Applying Local Modifications to RTMVM/ESA.” on page 47 for information on how to change the RTM source code).8. Invoke RTMBLD to build the product.6.1.2.1.1 Overview of RTMBLD:1. 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 arethat will contain the RTM source files, update files, etc.. If desired, you may modify RTMDISK EXECto change the default locations of these files. Note that if you changed the locations where these filesgo during the install (I5798DWD), then you must change this file to match where you installed theproduct.2. RTMBLD asks if the RTMMESA5 MACLIB should be rebuilt. If service has been applied then youshould answer YES. If YES was specified then the MACLIB gets rebuilt.3. RTMBLD assembles all the RTM source files.4. 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 issueVMCLOAD to build a new VMC MODULE.20 RTM VM/ESA Program Directory

6.1.2.2 Pre-installation instructions: The RTMDISK EXEC (APARs GC05046 and GC05109required) lists all the default minidisk addresses for install of the product. If you installed the product ondifferent minidisks than the defaults, or the CP maclibs on your system do not reside on MAINT 193 and190 disks, or you are installing on SFS directories, then you MUST edit this file. The default installaddresses listed in RTMDISK EXEC are shown below. Notice that the default SFS directories arecommented out. If you are installing on SFS directories, then you should uncomment the lines that definethe SFS directories, and comment out the lines that specify minidisks.source_disk='2B2' / RTM source files, such as ASSEMBLE .. /test_disk='4' / 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 tomake sure that the disks containing the CP maclibs HCPOM1 and HCPOM2 is correctly identified for yoursystem.6.1.2.2.1 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_diskentries 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 theirnew addresses or SFS directory names (SFS support requires APAR GC05109). If APAR GC05109 isapplied, then the CPmac_disk/CPmac_owner lines may be repeated. Thus, if your system has the CPmaclibs spread across multiple minidisks or SFS directories, simply include a CPmac_disk/CPmac_ownerline 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 oneCPmac_disk/CPmac_owner line (you can only specify one minidisk). In this case, you will have to linkand 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 lengthdirectory name. For example, if the source files were to be placed in 5798DWDC.SOURCE directory infilepool VMSYS, the RTMDISK EXEC would contain:::source_disk='VMSYS:5798DWDC.SOURCE'::Installation Instructions 21

If the CP maclibs reside in SFS directories, you do not need to specify a CPMac_owner entry (since it isredundant). For example, if the CP maclibs were stored in a directory called MAINT.MACS in filepoolVMSYS, 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 arenot and APAR GC05109 is applied, then you can include CPmac_disk/CPmac_owner lines in theRTMDISK EXEC so that the proper disks are accessed. If APAR GC05109 is not applied, you must linkand 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 beaccessed.6.1.2.2.2 Changing the Default Minidisks: By default, the non-SES installation uses the sameminidisks as the VMSES/E installation. Some installations may find it desirable to consolidate the numberof minidisks used to hold the product, or install the product in SFS directories to reduce DASD spacerequirements. 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 canuse as few as one minidisk or SFS directory when installing the product in the non-VMSES/E manner.6.1.2.2.3 Changing the Defaults Before Installation: If you have not yet installed the product, then youshould plan to use at least 40 cylinders of 3380 DASD (or equivalent amount of space for other DASDtypes) and must decide where the product files should reside. The build EXEC groups the files into 5categories: source files, AUX files, update files, test files (object code), and work files. There is a minidiskaddress or SFS directory name defined for each type. You may change any of the defaults in theRTMDISK EXEC. To do so, you must create the SFS directories and/or define the minidisks that you willinstall 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 youhave 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 thechanges you made to your minidisk/directory layout and then invoke the RTMBLD EXEC.6.1.2.2.4 Changing the Defaults After Installation: This case assumes you have already successfullyinstalled the product on the default minidisks. To consolidate the various files onto fewer minidisks, or toinstall the product on SFS directories, you must define new minidisks or directories to hold the files orincrease the sizes of the ones that you will use to hold the consolidated files. Consolidate the files (withthe CMS COPYFILE command) and then change the RTMDISK EXEC to match the new minidisk/directoryconfiguration and reinvoke RTMBLD to ensure that you can rebuild the product successfully.22 RTM VM/ESA Program Directory

6.1.2.2.5 Example RTMDISK EXEC with Changes: Here's an example of an RTMDISK EXEC that isused by an installation that decided to install the product in SFS directories and combined all RTM updatefiles and AUX files onto one directory. This installation has the CP maclibs on two disks - MAINT 193 andMAINT 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'6.1.2.3 Non-VMSES/E Installation Instructions.1. Format required minidisks.Once the directory entry and minidisks are defined for the product install, log on 5798DWDC andformat the minidisks:FORMAT 191 A (BLK 4KFormat all of the other required minidisks.Note: Skip this step if installing the product in SFS directories.2. Mount product tape in available tape drive and attach tape to 5798DWDC as 181.3. Invoke installation program The following steps should be performed only if you are installing the product with INSTFPP on aVM/ESA system. INSTFPP resides on MAINT's 5E5 disk by default on VM/ESA systems.ACCESS 5E5 BINSTFPP 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 offile 3.VMFPLC2 LOADVMFPLC2 LOADI5798DWDInstallation Instructions 23

6.1.2.4 Installation program I5798DWDNote: If you are installing the program from the GA level product tape, then skip to section 6.1.2.5, “GALevel Installs (I5798DWD)” on page 26 for instruction on how to install the product.: I5798DWD will askthe user if they wish to install the product on the default mindisks, the default SFS directories, or overridethe defaults and specify their own configuration.If you want to override the defaults, I5798DWD will prompt you for the minidisk addresses or SFSdirectory names that will contain the RTM VM/ESA source, sample, test, AUX and update disks. If youare 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 defaultminidisks, and the second example shows a user who decided to override the installation defaults. means hit the enter key.6.1.2.4.1 Example 1I5798DWD 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 4 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 exitAt this point, the product will be installed on the default minidisks.24 RTM VM/ESA Program Directory

6.1.2.4.2 Example 2I5798DWD 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 4 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.192Installation Instructions 25

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 exitAt this point, all the source files get loaded to the 2B2 disk, the test (executable) files and sample files getloaded 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 RTMBLDprogram. Skip to section 6.1.2.6, “RTMBLD program” on page 28 to continue with the install.6.1.2.5 GA Level Installs (I5798DWD): Read this section ONLY if you are installing the productfrom the GA level tape. If you are installing the product from the 9302 refresh level tape, or anysubsequent refresh tape, then you should follow the instruction provided in 6.1.2.4, “Installation programI5798DWD” on page 24.The GA level installation program (I5798DWD) does not work quite the same way as the version providedin 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 andGC05109 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 installationprogram will prompt you for the minidisk addresses of the source, test and sample disk, will install the fileson the disks you specify and asks if a service tape needs to be applied, answer Y. Note that you mustanswer yes here, since you require APARs GC05046 and GC05109 to build the product.6.1.2.5.1 Example of a GA level install26 RTM VM/ESA Program Directory

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 4 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 4 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=.22/1.46 19:1:26 Follow service install instructions, then invoke RTMBLDAt this point, the product files are loaded, and you must install the latest service (including APARSGC05046 and GC05109). Follow the instructions in 7.2, “Non-VMSES/E Service Instructions” on page 43.Continue with the next step 6.1.2.6, “RTMBLD program” after installing service.Installation Instructions 27

6.1.2.6 RTMBLD program: RTMBLD is used to build the product. The main input to the RTMBLDprogram is the RTMDISK EXEC.6.1.2.6.1 RTMDISK EXEC: RTMBLD reads the RTMDISK EXEC to obtain the disk addresses and/orSFS directory names where the various parts to the RTM VM/ESA product reside. Be sure that theentries in the RTMDISK EXEC match exactly where the product was installed. If you installed the producton the default minidisks, then you will not have to change this EXEC unless the CP maclibs required byRTM 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 availablewith APAR GC05046. By default, serviced build EXECs would reside on the test (400) disk. It isrecommended that the most recent serviced version of both the RTMBLD and RTMDISK EXECs areplaced on 5798DWDC 191 disk or top level directory so that it can be invoked without having to accessthe source and/or test disks/directories.6.1.2.6.2 Execution: RTMBLD first accesses the required disks/directories and presents the searchorder for the build to the user. Below is an example of what RTMBLD will show. Just hit ENTER at thispoint to continue the build. Below is the search order for this build of RTM. Mode Vdev/DirectoryDescription ---- -------------- ----------- A 191 RTM build work disk F 4 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.28 RTM VM/ESA Program Directory

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 '' 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.If 1 was specified above, RTMBLD rebuilds the maclib. In either case, RTMBLD then shows the maclibsused 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. SeeAppendices C and D for sample console output from a non-SES RTM install.6.1.2.6.3 VMCLOAD: If service was made to the VMC module, then the user should now issueVMCLOAD to rebuild the VMC module.VMCLOADReady; T=.22/1.46 19:1:26Installation Instructions 29

RTM is now fully installed and built, you can now put it into production.Post installPut RTM VM/ESA into production when testing is completed.1. Copy the RTM VM/ESA code to 5798DWDC's 401 disk (production BUILD disk for minidisk install) orto the VMSYS:RTMESA. directory (production build directory for SFS install). For minidisk install issue the following commands:ACCESS 4 E/EACCESS 41 FCOPYFILE RTM MODULE E = = F (OLDDATE REPLACENote: The RTMESA server machine links to the 401 as 191 and therefore gets access to thenew RTM module. For SFS install issue the following commands:ACCESS VMSYS:5798DWDC.TBUILD EACCESS VMSYS:RTMESA. F (FORCERWCOPYFILE RTM MODULE E = = F (OLDDATE REPLACE2. You will also need to put the VMC MODULE into production. For minidisk install issue the following commands:ACCESS 4 E/ESENDFILE VMC MODULE E TO MAINT For SFS install issue the following commands:ACCESS VMSYS:5798DWDC.TBUILD ESENDFILE VMC MODULE E TO MAINTThe MAINT owner should copy the VMC MODULE to the 19E disk. MAINT must also re-save CMS toput the 19E (Y-disk) back in shared status.6.2 Post Installation Consideration6.2.1 Activating the ProgramExecute the following procedure to insure that RTM VM/ESA was installed properly:1. Logon to RTMESA.2. Enter RTM.This will begin execution of RTM VM/ESA.3. When RTM VM/ESA is invoked, an RTM logo will initially appear. This will verify that RTM VM/ESAwas installed correctly.30 RTM VM/ESA Program Directory

The first automatic display will occur approximately five seconds after the program is started (after the logois presented). To terminate RTM VM/ESA, enter the QUIT command. You have now completed RTMVM/ESA installation verification.6.2.2 Access to RTM VM/ESA via the VMC commandThe VMC command to access to RTM VM/ESA must be issued from a separate virtual machine. TheVMC module should be placed on a common disk such that it can be accessed by all concerned. RTMVM/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 asRTMESA) 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 previouslydiscussed in this chapter, the RTM module must be run in a 370 mode virtual machine. The followingerror 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 37 modeInstallation Instructions 31

6.2.3 Modifying RTM VM/ESA TablesRTM VM/ESA table sizes may be customized if they are inappropriate for your system. The followingtable summarizes where to find the equates that relate to RTM VM/ESA tables:Summary of RTM equatesRTM VM/ESA Table RTM Module Field Name UseSYSDASD RTMDAT NUMSDA 1 Number of System DASD entriesUSER RTMDAT NUMUSR 2 Number of UseridsMPUSER RTMDAT NUMMPUSR Number of MP UsersVECTOR RTMDAT NUMVEC Number of Vector entriesSRC & VMX RTMDAT NMSRCVMX Number of SRC/VMX entriesDEVICE RTMDAT NUMDEV Number of device entriesSDA RTMDAT NUMSDA Number of system owned device entriesALOG RTMOUT ALOGNUM Number of analysis log entriesSCLOG RTMOUT SCLOGNUM Number of scheduler log entriesSLOG RTMOUT SLOGNUM Number of system log entriesTRLOG RTMOUT TRLOGNUM Number of transaction log entriesULOG RTMOUT ULOGNUM Number of user log entriesVMCFLOG RTMOUT VMCFNUM Number of vmcf log entriesXSLOG RTMOUT XSLOGNUM Number of extended system log entriesXTLOG RTMOUT XTLOGNUM Number of XSTORE log entriesULIST RTMOUT ULISTNUM Number of userids not monitored for IDLEDATVMCBF RTMDAT NUMVMCF Number of buffer entries for VMCF forLOGMSGsFigure 10. RTM VM/ESA field equates tableEnd of Summary of RTM equatesOnce the fields have been modified, reassemble ALL RTM VM/ESA modules, and generate a new RTMVM/ESA module. See 7.1.3, “RTM Product Rebuild” on page 42 RTM Product Rebuild.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.32 RTM VM/ESA Program Directory

6.2.4 Customizing the SystemTwo sample EXECs and one Assemble file are provided to enhance the usability and serviceability ofRTM VM/ESA:RTMINIT EXECA procedure used to initialize RTM VM/ESA from a separate virtual machinethrough the VMCF interface. This is an EXEC that is comparable to the SMINITEXEC provided for VM/RTM. It is suggested that RTMESA be autologged first byAUTOLOG1 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 2C2disk. A serviced copy of the exec (RTMINIT EXCnnnnn, where nnnnn is the PTFnumber) can be found on the 2D2 disk. The latest (or a user modified) copy ofthis exec can be sent to AUTOLOG1 with the name RTMINIT EXEC.RTMINIT EXEC notes:1. The EXEC should be modified to tailor RTM VM/ESA to your installation. ThisEXEC 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 LOGMSG2. It may be necessary to increase the time that the RTMINIT exec waits for theRTMESA virtual machine to initialize. This is done by changing the CPSLEEP statement in the RTMINIT exec.3. The following link should be in AUTOLOG1's directory entry:LINK MAINT 19E 19E RRThis will allow AUTOLOG1 to access the VMC module. If RACF has beeninstalled, make sure AUTOLOG1 has the authority to link to MAINT's 19Edisk.4. 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 theRTM displays from going to the console.Installation Instructions 33

PROFILE EXECSNAPPSets 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, operatorwarnings, and the “midnight message” from VM/ESA Release 2. All of these cancause the terminal to go into a HOLDING state and stop RTM VM/ESA fromprocessing data until the screen is cleared.After installation, this exec is found on the 2C2. It should be copied to the 400disk for testing with the RTM module before being moved to the 401 disk whenyou are ready to put RTM into production.Is a sample program which uses the SNAP interface. The SNAP interface allowsa virtual machine to extract RTM VM/ESA data for its own manipulation. It can befound, after installation, on the 2C2 disk. This program can be used as a modelfor other application programs. The assemble file is RTMSNAPP. The module iscalled SNAPP.6.2.5 Service to CP control blocksNote: Any service applied to the following HCP control blocks/modules may affect the RTM module andrequire that the RTM module be rebuilt.Once the fields have been modified, reassemble ALL RTM VM/ESA modules, and generate a new RTMVM/ESA module. See 7.1.3, “RTM Product Rebuild” on page 42 RTM Product Rebuild.CP Control blocks used by RTM VM/ESA 152HCPASCBK (VM/ESA only)HCPCLASSHCPCPVOLHCPDVTYPHCPEQUATHCPEXPBKHCPFSATEHCPMDCHCPDDITB (VM/XA only)HCPMEXBK (VM/ESA Only)HCPMTEBKHCPPFXPGHCPPLSBKHCPRDEVHCPRSMHCPSCMBKHCPSIEBKHCPSRMBKHCPSYSCMHCPTCMBKHCPVDEVHCPVMDBKHCPXSTMGVMCBLOKSEnd of CP Control blocks used by RTM VM/ESA 15234 RTM VM/ESA Program Directory

6.3 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 installationsmay 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 AMIXTURE 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/ESAon that system according to the VMSES/E installation instructions. If you wish to create an RTM VM/ESAMODULE that will run on another VM release at your installation, then all you need to do is make sure youhave a minidisk that contains the CP maclibs for that VM release in your search order and build theproduct with the instructions provided in 7.1.3, “RTM Product Rebuild” on page 42.If you do not have a VM/ESA Release 2 or later release system at your installation, then you must installRTM VM/ESA on one of your VM systems according to the non-VMSES/E installation instructions. If youwish to create an RTM VM/ESA MODULE that will run on another VM release at your installation, then allyou need to do is modify the RTMDISK EXEC to reflect the location of the CP MACLIBs that were used tobuild 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 thesystems. As you build RTM modules to run on each of your systems, make sure that you build each RTMmodule with the corresponding CP maclibs that were used to build the system that the RTM module isintended to run on. Thus, you want to make the CP maclibs used to build your various systemsaccessible to user 5798DWDC.Installation Instructions 35

7.0 Service InstructionsThe service procedure for RTM VM/ESA depends on the VM release you have installed the product on. Ifyou are installing the product on VM/ESA Release 2 or later release, then follow the VMSES/E instructionsprovided in 7.1, “VMSES/E Service Instructions” on page 36. For VM/ESA Release 1.1, service theproduct according to the non-VMSES/E instructions provided in 7.2, “Non-VMSES/E Service Instructions”on page 43.7.1 VMSES/E Service InstructionsThis section of the Program Directory contains the procedure to install CORrective service to RTMVM/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 thissection. This manual also contains the command syntax for the VMSES/E commands listed in theprocedure.7.1.1 VMSES/E Service Process OverviewThe overview will give a brief description of the main steps in servicing RTM VM/ESA using VMSES/E. Merging ServiceUse the VMFMRDSK command to clear the alternate apply disk/directory before receiving newservice. This allows you to easily remove the new service if a serious problem is found. Receiving ServiceThe VMFREC command receives service from the delivery media and places it on the Deltadisk/directory. Applying ServiceThe VMFAPPLY command updates the version vector table (VVT), which identifies the service level ofall 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 changesand build them into the system. See Chapter 7 in the VM/ESA R2 Service Guide for this procedure.(SC24-5527-02). Building New LevelsThe build task generates the serviced level of an object and places the new object on a BUILD disk. Placing the New Service into Production36 © Copyright IBM Corp. 1985, 1992

Once the service is satisfactorily tested it should be put into production by copying the new service tothe production disk or directory, re-saving the NSS (Named Saved System) or DCSS (DiscontiguousSaved Segments), etc.7.1.2 Servicing RTM VM/ESAOverride ConsiderationsThe ppfname used throughout these instructions is 5798DWDC, which assumes you are using thePPF supplied by IBM for RTM VM/ESA. If you have your own PPF override file for RTM VM/ESA, youshould use your file's ppfname instead of 5798DWDC. The ppfname you use should be usedthroughout the rest of this procedure.The compname used throughout these instructions is either RTM or RTMSFS, which assumes you areusing the component name within the 5798DWDC PPF file. If you specify your own ppfname, youshould use the compname from that file instead of RTM or RTMSFS. The compname you use shouldbe used throughout the rest of this procedure.SFS ConsiderationsIf you are installing to an SFS directory and your A-disk is also an SFS directory but in a differentfilepool, Coordinated Resource Recovery (CRR) needs to be running on your system.1. Log onto 5798DWDC userid and make sure the VMSES code is accessed as filemode B. (By defaultthis disk is MAINT 5E5).ACCESS 5E5 BACCESS 51D D2. Setup the the 5798DWDC userid environment to install service.VMFSETUP 5798DWDC RTMRTMSFSNote: Use RTM if the product was installed on minidisk, or RTMSFS if the product was installed onSFS.The following is an example of the screen displayed after issuing the above VMFSETUP command:Service Instructions 37

vmfsetup 5798dwdc rtmVMFSET276I VMFSETUP processing startedVMFUTL225I Minidisk|Directory Assignments:String Mode Stat Vdev Label/DirectoryVMFUTL225I LOCALSAM E R/W 2C2 5792C2VMFUTL225I APPLY F R/W 2A6 5792A6VMFUTL225I G R/W 2A2 5792A2VMFUTL225I DELTA H R/W 2D2 5792D2VMFUTL225I BUILD I R/W 4 5794VMFUTL225I BUILD1 J R/W 41 57941VMFUTL225I BUILD6 K R/O 19 MNT19VMFUTL225I BUILD6 S R/O 19 MNT19VMFUTL225I BUILD7 L R/O 193 MNT193VMFUTL225I BASE1 M R/W 2B2 5792B2VMFUTL225I -------- A R/W 191 RTM191VMFUTL225I -------- B R/O 5E5 MNT5E5VMFUTL225I -------- D R/W 51D MNT51DVMFUTL225I -------- Y/S R/O 19E MNT19EVMFSET276I VMFSETUP processing completed successfully3. Issue the VMFMRDSK to clear the alternate APPLY disk for the new service. This command will copythe contents of the 2A6 to the 2A2 (minidisk installs) or copy the contents of theVMSYS:5798DWDC.ALTAPPLY directory to the VMSYS:5798DWDC.PRDAPPLY directory (SFSinstalls).VMFMRDSK 5798DWDC RTM APPLYRTMSFSNote: Use RTM if the product was installed on minidisk, or RTMSFS if the product was installed onSFS.The following is an example of the screen displayed after issuing the above VMFMRDSK command:vmfmrdsk 5798dwdc rtm applyVMFMRD276I VMFMRDSK processing startedVMFMRD1937I Merge of APPLY startedVMFMRD1938I Merging APPLY 2A6 to 2A2VMFMRD265I APPLY 2A2 is now 3 percent fullVMFMRD1939I Merge of APPLY completedVMFMRD276I VMFMRDSK processing completed successfully4. Receive the service using the VMFREC command.Note: If you are receiving service from Service Link (electronic service) see Appendix B in theVM/ESA R2 Service Guide for information. All new service is loaded to the 2D2 disk/directory.VMFREC PPF 5798DWDC RTMRTMSFSNote: Use RTM if the product was installed on minidisk, or RTMSFS if the product was installed onSFS.38 RTM VM/ESA Program Directory

The following is an example of the screen displayed after issuingthe above VMFREC command:vmfrec ppf 5798dwdcVMFREC276I VMFREC processing startedVMFREC1852I Volume 1 of 1 of COR nnnn created on 29 September 92VMFREC1851I (1 of 3) VMFRCAXL processing AXLISTVMFRCX2159I Loading part(s) to DELTA 2D2 (H)VMFREC1851I (2 of 3) VMFRCPTF processing PARTLSTVMFRCP2159I Loading 1 part(s) to DELTA 2D2 (H)VMFREC1851I (3 of 3) VMFRCCOM processing DELTAVMFRCC2159I Loading 1 part(s) to DELTA 2D2 (H)VMFREC2189I Updating Requisite table 5798DWDC SRVREQT, Description table5798DWDC SRVDESCT and Receive Status table 5798DWDC SRVRECS with 1new PTFs from COR nnnnVMFREC276I VMFREC processing completed successfully5. Apply the new service.VMFAPPLY PPF 5798DWDC RTMRTMSFSNote: Use RTM if the product was installed on minidisk, or RTMSFS if the product was installed onSFS.The following is an example of the screen displayed after issuingthe above VMFAPPLY command:vmfapply ppf 5798dwdc rtmVMFAPP276I VMFAPPLY processing startedVMFAPP216I Apply list RTMESA5 contains 1 PTFs that need to be applied and PTFs that are already appliedVMFAPP212I 1 of 1 PTFs processedVMFAPP215I VMFAPPLY processing completed successfully.The Apply list RTMESA5 contains 1 PTFs. PTFs were already applied.1 PTFs applied successfully. PTFs were included. PTFs were excluded or require excluded PTFs. PTFs failedVMFAPP213I The Software Inventory has been updated on the 2A6 (F) diskService Instructions 39

6. Update the Build Status Table with serviced parts.VMFBLD PPF 5798DWDC RTM (STATUSRTMSFSNote: Use RTM if the product was installed on minidisk, or RTMSFS if the product was installed onSFS.NoteThe $PPF file, the main RTM control file for VMSES/E, can also be serviced. If the $PPF file hasbeen serviced then you get the following prompt:VMFBLD2185R The following source product parameter files have beenserviced:VMFBLD2185R 5798DWDC $PPFVMFBLD2185R When source product parameter files are serviced, allproduct parameter files built from them must be recompiledusing VMFPPF before VMFBLD can be run.VMFBLD2185R Enter zero () to have the serviced source productparameter files built to your A-disk and exit VMFBLD soyou can recompile your product parameter files with VMFPPFVMFBLD2185R Enter one (1) to continue only if you have alreadyrecompiled your product parameter files with VMFPPFEnter 0 and complete the following steps before you continue:0VMFPPF 5798DWDC RTM|RTMSFSCOPY 5798DWDC $PPF A = = D (OLDDATEERASE 5798DWDC $PPF AREPLACENote: Use RTM if the product was installed on minidisk, or RTMSFS if the product was installedon SFS.After issuing VMFPPF go back to issue the VMFBLD with the STATUS option once more. Youmay now give a response of '1' to the prompt.7. You can view the build requirements identified by SES from the previous command by viewing themessage log on the A disk. To view the message log issue the following command:VMFVIEW BUILDThe following is an example of the screen displayed after issuing the above VMFVIEW command:40 RTM VM/ESA Program Directory

ST:VMFBLD1851I Reading build listsST:VMFBLD2182I Identifying new build requirementsST:VMFBLD2182I New build requirements identifiedBD:VMFBLD218I There are 6 build requirements remainingBD:VMFBLD218I Build Requirements:BD: Bldlist Object StatusBD:VMFBLD218I RTMSRC =.EXEC SERVICEDBD:VMFBLD218I RTMACLIB RTMCALL SERVICEDBD:VMFBLD218I RTMASM BLDLIST SERVICEDBD:VMFBLD218I RTMMOD RTM.MODULE SERVICEDBD:VMFBLD218I VMC.MODULE SERVICEDBD:VMFBLD218I SNAPP.MODULE SERVICEDST:VMFBLD276I VMFBLD processing completed successfully8. 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 laterIf you are installing on VM/ESA Version 2 or later you must have HLASM (5696-234) installedbefore you can complete the build.VMFBLD PPF 5798DWDC RTM (SERVICEDRTMSFSNote: Use RTM if the product was installed on minidisk, or RTMSFS if the product was installed onSFS.See Appendix B, “Sample output from BUILD command.” on page 49 in this document for anexample of the output from from this command.Issue the VMFVIEW BUILD command to view any error messages or remaining build requirements.9. Place the new service into production after testing.a. Copy the RTM VM/ESA code to 5798DWDC's 401 disk (production BUILD disk for minidiskinstall) or to the VMSYS:RTMESA. directory (production build directory for SFS install). For minidisk install issue the following commands:ACCESS 4 E/EACCESS 41 FCOPYFILE RTM MODULE E = = F (OLDDATE REPLACENote: The RTMESA server machine links to the 401 as 191 and therefore gets access tothe new RTM module. For SFS install issue the following commands:ACCESS VMSYS:5798DWDC.TBUILD EACCESS VMSYS:RTMESA. F (FORCERWCOPYFILE RTM MODULE E = = F (OLDDATE REPLACEb. You will also need to put the VMC MODULE into production. For minidisk install issue the following commands:Service Instructions 41

ACCESS 4 E/ESENDFILE VMC MODULE E TO MAINT For SFS install issue the following commands:ACCESS VMSYS:5798DWDC.TBUILD ESENDFILE VMC MODULE E TO MAINTThe MAINT owner should copy the VMC MODULE to the 19E disk. MAINT must also re-saveCMS to put the 19E (Y-disk) back in shared status.7.1.3 RTM Product RebuildIf the RTM modules need to be rebuilt between servicing, select one or more of the following commands: VMFSETUP 5798DWDC RTM|RTMSFSThis will ensure the correct disk access order for building RTM. VMFBLD PPF 5798DWDC RTM|RTMSFS RTMACLIB (ALLThis will rebuild the RTM maclib. VMFBLD PPF 5798DWDC RTM|RTMSFS RTMASM (ALLThis will reassemble all the RTM assemble files. VMFBLD PPF 5798DWDC RTM|RTMSFS RTMMOD (ALLThis 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. Theinstructions are as follows:1. Copy the RTM VM/ESA code to 5798DWDC's 401 disk (production BUILD disk for minidisk install) orto the VMSYS:RTMESA. directory (production build directory for SFS install). For minidisk install issue the following commands:ACCESS 4 E/EACCESS 41 FCOPYFILE RTM MODULE E = = F (OLDDATE REPLACENote: The RTMESA server machine links to the 401 as 191 and therefore gets access to thenew RTM module. For SFS install issue the following commands:ACCESS VMSYS:5798DWDC.TBUILD EACCESS VMSYS:RTMESA. F (FORCERWCOPYFILE RTM MODULE E = = F (OLDDATE REPLACE2. You will also need to put the VMC MODULE into production. For minidisk install issue the following commands:42 RTM VM/ESA Program Directory

ACCESS 4 E/ESENDFILE VMC MODULE E TO MAINT For SFS install issue the following commands:ACCESS VMSYS:5798DWDC.TBUILD ESENDFILE VMC MODULE E TO MAINTThe MAINT owner should copy the VMC MODULE to the 19E disk. MAINT must also re-save CMS toput the 19E (Y-disk) back in shared status.7.2 Non-VMSES/E Service InstructionsThis section of the Program Directory contains the procedure to install CORrective service to RTMVM/ESA on VM/ESA Release 1.1.The procedure for applying non-VMSES/E service depends on how the service is packaged. Somecustomers may receive non-VMSES/E envelopes (through IBMLINK for example), while some customersmay receive a service tape with the PTFs on it. No matter how you receive your service, you shouldalways make sure that the proper files are located on the appropriate disks. You should follow theinstructions provided with the service obtained, but make sure you place the service files on theappropriate minidisks described below.7.2.1 OverviewFor 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 theproduct.For cumulative service tapes, the tape is mounted and attached to 5798DWDC. The files on the tape areloaded to a temporary minidisk, and the product rename EXEC (called 5798DWDB) is run to rename thefiles and the files are then copied to the appropriate minidisk(s) and/or SFS directories. The RTMBLDexec is then invoked to rebuild the product.7.2.2 Installing Non-VMSES/E Service1. Define and format a temporary work disk to load the service on.2. Copy all of the AUXRTM5 files on the auxfile disk (2A6) or directory (VMSYS:5798DWDC.ALTAPPLY)to the backup auxfile disk (2A2) or directory (VMSYS:5798DWDC.PRDAPPLY) in case of anyproblems with newly applied service.3. Erase all of the AUXRTM5 files on the auxfile disk (2A6) or directory(VMSYS:5798DWDC.ALTAPPLY). Note that if you have any problems with the newly applied service,you can just copy all of the AUXRTM5 files from the backup disk/directory to the auxfile disk/directoryand rebuild the product with RTMBLD.4. Receive the serviceService Instructions 43

How to receive the service depends on how your service is packaged, instructions are provided herefor non-VMSES/E envelopes received electronically (through IBMLINK for example), and cumulativeservice tapes containing the PTFs. In all cases, refer to the instructions provided with the service onhow to receive it. Receiving Service For Non-VMSES Envelopesa. Receive product memos from envelope NLSTnnnn SERVLINK.Note: Depending on how you receive the service, you may have to unpack the PTF's withthe VMUNPAC EXEC. Follow the instructions provided with your service.– VMFPLCD RST ENV=NLSTnnnn SERVLINK fmfm is the filemode where the envelope exists. The default is A. This command resets thelogical position to the beginning of the envelope. The GLOBALV will also be updated withthe name of the envelope so that the ENV= parameter will not be required for subsequentVMFPLCD commands.– VMFPLCD LOAD * * A (EODThis command receives the service documentation for the envelope.b. Receive the service for non-VMSES PTF envelopes NPTFnnnn SERVLINK.– VMFPLCD RST ENV=NPTFnnnn SERVLINK fmThis command resets the logical position to the beginning of the envelope. TheGLOBALV 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 thefile mode of the disk where the envelope exists. The default is the A-disk.– VMFPLCD SCAN prodid 010101 (EODLocate the start of service in the envelope for the product to service. prodid is the RTMVM/ESA product id.– VMFPLCD LOAD * * fm (DISKfm is the filemode of the work disk you are installing service on. Service Tape Formata. Issue the following commands to download the service to the temporary work disk. The firstcommand listed here positions the tape and the second command loads the files. Here, fm isthe file mode of the temporary work disk.– VMFPLC2 SCAN 5798DWDB 010101 (EOT– VMFPLC2 LOAD * * fmb. Rename the files on the temporary work disk with the following command. Again, fm is thefile mode of the temporary work disk.– 5798DWDB fm44 RTM VM/ESA Program Directory

5. COPYFILE all the AUXRTM5 files to the auxfile (2A6) disk or directory(VMSYS:5798DWDC.ALTAPPLY).6. COPYFILE all the update files to the update (2D2) disk or directory (VMSYS:5798DWDC.DELTA).7. COPYFILE any new source files (such as new COPY, MACRO or ASSEMBLE files) to the source(2B2) disk or directory (VMSYS:5798DWDC.SOURCE).8. COPYFILE all the full replacement parts (such as new build EXECs) to the test (400) disk or directory(VMSYS:5798DWDC.TBUILD).You may want to copy the RTMDISK EXEC and the RTMBLD EXEC to 5798DWDC 191 disk or topdirectory so that a rebuild of RTM can be done simply by typing RTMBLD without any accessing ofdisks. (RTMBLD accesses the product disks/directories automatically.).9. You may now delete the temporary disk.7.2.3 Re-building the product.RTMBLD is now run to complete the installation. If the newly applied service makes changes to any RTMMACRO or COPY files, then remember to answer 'YES' when RTMBLD asks if the RTMMESA5 MACLIBshould be rebuilt. See 6.1.2.6, “RTMBLD program” on page 28 for further instructions regardingRTMBLD.If service was made to RTMVMC, then you must issue VMCLOAD after RTMBLD completes to rebuild theVMC module.7.2.4 RTM Product RebuildIf the RTM modules need to be rebuilt between servicing, simply reissue the RTMBLD command.7.3 Non-VMSES/E RTM Build FilesThe following is the list of files used to build non-VMSES/E RTM. I5798DWD EXECLoads the product from the install tape to the appropriate minidisks or SFS directories. The originalversion is provided on the GA product tape, and an updated version that provides SFS support isprovided with APAR GC05109. RTMDISK EXECThis lists the minidisk addresses and/or SFS directory names that contain the various types of RTMparts. This may be modified by the user, but care should be taken to ensure that the addresses in theRTMDISK EXEC match what is installed on the system. RTMBLD uses RTMDISK EXEC. This EXECis provided with APAR GC05046 and a modified version that provides SFS support is supplied withAPAR GC05109. RTMBLD EXECService Instructions 45

This will rebuild the RTMMESA5 MACLIB and RTM MODULE. This EXEC is provided on the GAproduct tape, and modified versions are provided with APARs GC05046 and GC05109. RTMMESA5 EXECThis lists all RTM MACRO and COPY files to be included in the RTMMESA5 MACLIB. TheRTMMESA5 MACLIB can be built with RTMBLD or it can be built by executing VMFMAC RTMMESA5RTMESA5. RTMLOAD EXECThis is the EXEC that takes the RTM TEXT decks and builds a new RTM MODULE. RTMBLDinvokes RTMLOAD. VMCLOAD EXECThis is the EXEC that takes the RTMVMC TEXT deck and builds a new VMC MODULE. RTMBLDDOES NOT invoke VMCLOAD.A single RTM ASSEMBLE file can be assembled by linking and accessing the various RTM disks andissuing VMFHASM RTMxxx RTMESA5.Whenever the above commands are issued, the new modules must be put into production. Theinstructions are as follows:1. Copy the RTM VM/ESA code to 5798DWDC's 401 disk (production BUILD disk for minidisk install) orto the VMSYS:RTMESA. directory (production build directory for SFS install). For minidisk install issue the following commands:ACCESS 4 E/EACCESS 41 FCOPYFILE RTM MODULE E = = F (OLDDATE REPLACENote: The RTMESA server machine links to the 401 as 191 and therefore gets access to thenew RTM module. For SFS install issue the following commands:ACCESS VMSYS:5798DWDC.TBUILD EACCESS VMSYS:RTMESA. F (FORCERWCOPYFILE RTM MODULE E = = F (OLDDATE REPLACE2. You will also need to put the VMC MODULE into production. For minidisk install issue the following commands:ACCESS 4 E/ESENDFILE VMC MODULE E TO MAINT For SFS install issue the following commands:ACCESS VMSYS:5798DWDC.TBUILD ESENDFILE VMC MODULE E TO MAINTThe MAINT owner should copy the VMC MODULE to the 19E disk. MAINT must also re-save CMS toput the 19E (Y-disk) back in shared status.46 RTM VM/ESA Program Directory

Appendix A. Applying Local Modifications to RTM VM/ESA.A.1 VMSES/E Local Modifications ProcedureA.1.1 Assemble FilesIf 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 beupdated to reflect a change has been made to the ASSEMBLE file... Our examples below uses RTMDATas the modified file.1. Update RTM's VVTVMFSIM LOGMOD 5798DWDC VVTRTML fm TDATA :MOD LCL1.updftype :PARTRTMDAT ASSEMBLEwhere fm is the filemode of the local/sample disk (2C2) or directory (VMSYS:5798DWDC.SAMPLE).updftype is the filetype of the local update file.2. Your local AUX (RTMESA5 AUXRTML) should look like this: (also filed on the local/sample disk ordirectory)updftype LCL LCL13. Edit the RTMESA5 CNTRL to appear as below:TEXT MACS ...:TEXT AUXRTML RTM AUX File and VVTRTML Level for Local ModsTEXT AUXRTM5 RTM AUX FILE and VVTRTM5 Level for PTF service4. Use the VMFHASM or VMFHLASM command with the CTL option to verify a clean compile. Even theassembled file of the local mod will be forced to a filetype of 'TEXT'.VMFHLASM fn RTMESA5 (CTL5. Follow the directions for RTM/ESA Product Rebuild in 7.1.3, “RTM Product Rebuild” on page 42 ofthe program directory.A.1.2 Full Part Replacement FilesIf you wish to apply local modifications to any of the RTM full part replacement files you must follow thesame convention of applying local mods as used by VM/ESA components with the following exception:1. Edit the RTMESA5 CNTRL to appear as below:© Copyright IBM Corp. 1985, 1992 47

TEXT MACS ...:TEXT AUXRTML RTM AUX File and VVTRTML Level for Local ModsTEXT AUXRTM5 RTM AUX FILE and VVTRTM5 Level for PTF service2. All references to VVTLCL should use VVTRTML for the local version vector table (vvtft).A.2 Non-VMSES/E Local Modifications ProcedureExplicit instructions were provided in 6.1.2.2, “Pre-installation instructions” on page 21 that show how tochange the default minidisk requirements. That section explained how to install the product in SFSdirectories 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) mustbe done manually. The instructions are provided here.1. Link and access the minidisks that contain the source files, AUX files, update files and object files. (Ifyou did not change the default minidisk configuration, these would be addresses 2B2, 2A6, 2D2 and400 respectively, or if you installed on SFS directories, these would be the .SOURCE, .ALTAPPLY,.DELTA and .TBUILD directories respectively).2. Edit the RTMESA5 CNTRL to appear as below:TEXT MACS ...:TEXT AUXRTML RTM AUX File for Local ModsTEXT AUXRTM5 RTM AUX FILE for PTF service3. For any parts you wish to modify, you must update its AUXRTML file (or create a new one if it doesn'texist) to point to the the update that you are creating. For example, assuming you were going tochange 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)4. XEDIT the files you wish to change. For example, to change RTMDAT: XEDIT RTMDAT ASSEMBLE (CTL RTMESA55. File your changes. When done creating all your updates rebuild the product with RTMBLD. RTMBLDNote: If you change MACRO or COPY files, then you must rebuild the RTMMESA5 MACLIB. Itsrecommended that you keep your local modifications seperate (on a different minidisk for example) fromthe IBM supplied modifications.48 RTM VM/ESA Program Directory

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.© Copyright IBM Corp. 1985, 1992 49

VMFINS BUILD PPF 5798DWDC RTMINS (ALL NOLINKVMFINS276I VMFINS processing startedVMFREQ285I Product 5798DWDC component RTMINS passed requisite checkingVMFSET276I VMFSETUP processing startedVMFUTL225I Minidisk|Directory Assignments:String Mode Stat Vdev Label/DirectoryVMFUTL225I LOCALSAM E R/W 2C2 RTM2C2VMFUTL225I APPLY F R/W 2A6 RTM2A6VMFUTL225I G R/W 2A2 RTM2A2VMFUTL225I DELTA H R/W 2D2 RTM2D2VMFUTL225I BUILD I R/W 4 RTM4VMFUTL225I BUILD1 J R/W 41 RTM41VMFUTL225I BUILD6 K R/O 19 CMS21VMFUTL225I BUILD6 S R/O 19 CMS21VMFUTL225I BUILD7 L R/O 193 MNT193VMFUTL225I BASE1 M R/W 2B2 RTM2B2VMFUTL225I -------- A R/W 191 RTM191VMFUTL225I -------- B R/O DIR EPLLIB:EDLLIB4.DRV12.VMFVMFUTL225I -------- C R/O 12 SQVAUXVMFUTL225I -------- D R/W 51D RTM51DVMFUTL225I -------- Y/S R/O 19E YDISKVMFSET276I VMFSETUP processing completed successfullyVMFBLD276I VMFBLD processing startedVMFBLD1851I Reading build listsVMFBLD2182I Identifying new build requirementsVMFBLD2182I New build requirements identifiedVMFBLD1851I (1 of 4) VMFBDCOM processing RTMSRC EXECVMFBDC2179I There are no build requirements matching your request at this time.No objects will be builtVMFBDC2179I There are no build requirements matching your request at this time.No objects will be builtVMFBDC2179I There are no build requirements matching your request at this time.No objects will be builtVMFBDC2179I There are no build requirements matching your request at this time.No objects will be builtVMFBDC2179I There are no build requirements matching your request at this time.No objects will be builtVMFBLD1851I (1 of 4) VMFBDCOM completed with return code VMFBLD1851I (2 of 4) VMFBDMLB processing RTMACLIB EXC231VMFMLB2217I RTMMESA5 MACLIB will be rebuilt because all members must be rebuiltVMFMLB2219I Processing object RTMMEXBKVMFMLB2219I Processing object RTMDDITBVMFMLB2219I Processing object RTMASCBKVMFMLB2219I Processing object RTMSYDATVMFMLB2219I Processing object RTMINTDAVMFMLB2219I Processing object RTMIOPAS50 RTM VM/ESA Program Directory

VMFMLB2219I Processing object RTMVMBADVMFMLB2219I Processing object RTMASBLKVMFMLB2219I Processing object RTMACTNSVMFMLB2219I Processing object RTMDEVADVMFMLB2219I Processing object RTMFTADRVMFMLB2219I Processing object RTMFTDATVMFMLB2219I Processing object RTMDVSTBVMFMLB2219I Processing object RTMHDRDAVMFMLB2219I Processing object RTMLGMSGVMFMLB2219I Processing object RTMLOGTBVMFMLB2219I Processing object RTMOPTNSVMFMLB2219I Processing object RTMPLBDAVMFMLB2219I Processing object RTMPFAADVMFMLB2219I Processing object RTMPFTDAVMFMLB2219I Processing object RTMSCNTBVMFMLB2219I Processing object RTMSRCTBVMFMLB2219I Processing object RTMSYTDAVMFMLB2219I Processing object RTMSDAADVMFMLB2219I Processing object RTMSDATBVMFMLB2219I Processing object RTMTEADRVMFMLB2219I Processing object RTMTEDATVMFMLB2219I Processing object RTMTMRTBVMFMLB2219I Processing object RTMUSRTBVMFMLB2219I Processing object RTMVECTBVMFMLB2219I Processing object RTMEXITVMFMLB2219I Processing object RTMNEWTMVMFMLB2219I Processing object RTMRSLIHVMFMLB2219I Processing object RTMSSLIHVMFMLB2219I Processing object RTMUSINGVMFMLB2219I Processing object RTMWRAPVMFMLB2219I Processing object RTMCALLVMFMLB2219I Processing object RTMDROPVMFMLB2219I Processing object RTMENTERVMFMLB2219I Processing object RTMMULDLVMFMLB2219I Processing object RTMPROLGVMFMLB2219I Processing object RTMSWAPTVMFMLB2219I Processing object RTMBLANKVMFMLB2219I Processing object RTMCCVMFMLB2219I Processing object RTMTRACEVMFMLB222I Updating service history member for RTMMESA5 MACLIBVMFBLD1851I (2 of 4) VMFBDMLB completed with return code VMFBLD1851I (3 of 4) RTMBDUTL processing RTMASM EXECVMFASM276I VMFHASM processing startedDMSUPD181E No update files were foundAppendix B. Sample output from BUILD command. 51

VMFASM197I Assembling RTMSNAPPVMFASM257I RTMSNAPP TEXT created on your A-disk for use in a non-VMSES/EenvironmentVMFASM276I VMFHASM processing completed successfullyPRT FILE 539 SENT FROM 5798DWDC PRT WAS 539 RECS 888 CPY 1 A NOHOLD NOKEEPVMFASM276I VMFHASM processing startedDMSUPD178I Updating RTMCMD ASSEMBLE M1DMSUPD178I Applying RTMCMD G541RM H1DMSUPD178I Applying RTMCMD G544RM H1DMSUPD178I Applying RTMCMD G546RM H1VMFASM197I Assembling RTMCMDVMFASM257I RTMCMD TEXT created on your A-disk for use in a non-VMSES/EenvironmentVMFASM276I VMFHASM processing completed successfullyPRT FILE 54 SENT FROM 5798DWDC PRT WAS 54 RECS 1K CPY 1 A NOHOLD NOKEEPVMFASM276I VMFHASM processing startedDMSUPD178I Updating RTMCMP ASSEMBLE M1DMSUPD178I Applying RTMCMP G544RM H1DMSUPD178I Applying RTMCMP G546RM H1VMFASM197I Assembling RTMCMPVMFASM257I RTMCMP TEXT created on your A-disk for use in a non-VMSES/EenvironmentVMFASM276I VMFHASM processing completed successfullyPRT FILE 541 SENT FROM 5798DWDC PRT WAS 541 RECS 11K CPY 1 A NOHOLD NOKEEPVMFASM276I VMFHASM processing startedDMSUPD178I Updating RTMDAT ASSEMBLE M1DMSUPD178I Applying RTMDAT G544RM H1DMSUPD178I Applying RTMDAT G546RM H1VMFASM197I Assembling RTMDATVMFASM257I RTMDAT TEXT created on your A-disk for use in a non-VMSES/EenvironmentVMFASM276I VMFHASM processing completed successfullyPRT FILE 542 SENT FROM 5798DWDC PRT WAS 542 RECS 8525 CPY 1 A NOHOLD NOKEEPVMFASM276I VMFHASM processing startedDMSUPD178I Updating RTMDRV ASSEMBLE M1DMSUPD178I Applying RTMDRV G544RM H1DMSUPD178I Applying RTMDRV G546RM H1VMFASM197I Assembling RTMDRVVMFASM257I RTMDRV TEXT created on your A-disk for use in a non-VMSES/EenvironmentVMFASM276I VMFHASM processing completed successfullyPRT FILE 543 SENT FROM 5798DWDC PRT WAS 543 RECS 12K CPY 1 A NOHOLD NOKEEPVMFASM276I VMFHASM processing startedDMSUPD178I Updating RTMDSL ASSEMBLE M1DMSUPD178I Applying RTMDSL G544RM H1DMSUPD178I Applying RTMDSL G546RM H152 RTM VM/ESA Program Directory

VMFASM197I Assembling RTMDSLVMFASM257I RTMDSL TEXT created on your A-disk for use in a non-VMSES/EenvironmentVMFASM276I VMFHASM processing completed successfullyPRT FILE 544 SENT FROM 5798DWDC PRT WAS 544 RECS 6259 CPY 1 A NOHOLD NOKEEPVMFASM276I VMFHASM processing startedDMSUPD178I Updating RTMDSP ASSEMBLE M1DMSUPD178I Applying RTMDSP G544RM H1DMSUPD178I Applying RTMDSP G546RM H1VMFASM197I Assembling RTMDSPVMFASM257I RTMDSP TEXT created on your A-disk for use in a non-VMSES/EenvironmentVMFASM276I VMFHASM processing completed successfullyPRT FILE 545 SENT FROM 5798DWDC PRT WAS 545 RECS 12K CPY 1 A NOHOLD NOKEEPVMFASM276I VMFHASM processing startedDMSUPD178I Updating RTMDSU ASSEMBLE M1DMSUPD178I Applying RTMDSU G544RM H1DMSUPD178I Applying RTMDSU G526RM H1DMSUPD178I Applying RTMDSU G546RM H1VMFASM197I Assembling RTMDSUVMFASM257I RTMDSU TEXT created on your A-disk for use in a non-VMSES/EenvironmentVMFASM276I VMFHASM processing completed successfullyPRT FILE 546 SENT FROM 5798DWDC PRT WAS 546 RECS 1K CPY 1 A NOHOLD NOKEEPVMFASM276I VMFHASM processing startedDMSUPD178I Updating RTMDSV ASSEMBLE M1DMSUPD178I Applying RTMDSV G544RM H1DMSUPD178I Applying RTMDSV G546RM H1VMFASM197I Assembling RTMDSVVMFASM257I RTMDSV TEXT created on your A-disk for use in a non-VMSES/EenvironmentVMFASM276I VMFHASM processing completed successfullyPRT FILE 547 SENT FROM 5798DWDC PRT WAS 547 RECS 8971 CPY 1 A NOHOLD NOKEEPVMFASM276I VMFHASM processing startedDMSUPD178I Updating RTMDSW ASSEMBLE M1DMSUPD178I Applying RTMDSW G516RM H1DMSUPD178I Applying RTMDSW G544RM H1DMSUPD178I Applying RTMDSW G546RM H1VMFASM197I Assembling RTMDSWVMFASM257I RTMDSW TEXT created on your A-disk for use in a non-VMSES/EenvironmentVMFASM276I VMFHASM processing completed successfullyPRT FILE 548 SENT FROM 5798DWDC PRT WAS 548 RECS 775 CPY 1 A NOHOLD NOKEEPVMFASM276I VMFHASM processing startedAppendix B. Sample output from BUILD command. 53

DMSUPD178I Updating RTMDSX ASSEMBLE M1DMSUPD178I Applying RTMDSX G543RM H1DMSUPD178I Applying RTMDSX G544RM H1DMSUPD178I Applying RTMDSX G546RM H1DMSUPD178I Applying RTMDSX G513RM H1VMFASM197I Assembling RTMDSXVMFASM257I RTMDSX TEXT created on your A-disk for use in a non-VMSES/EenvironmentVMFASM276I VMFHASM processing completed successfullyPRT FILE 549 SENT FROM 5798DWDC PRT WAS 549 RECS 6212 CPY 1 A NOHOLD NOKEEPVMFASM276I VMFHASM processing startedDMSUPD178I Updating RTMERM ASSEMBLE M1DMSUPD178I Applying RTMERM G546RM H1VMFASM197I Assembling RTMERMVMFASM257I RTMERM TEXT created on your A-disk for use in a non-VMSES/EenvironmentVMFASM276I VMFHASM processing completed successfullyPRT FILE 55 SENT FROM 5798DWDC PRT WAS 55 RECS 466 CPY 1 A NOHOLD NOKEEPVMFASM276I VMFHASM processing startedDMSUPD178I Updating RTMIOP ASSEMBLE M1DMSUPD178I Applying RTMIOP G545RM H1DMSUPD178I Applying RTMIOP G544RM H1DMSUPD178I Applying RTMIOP G546RM H1DMSUPD178I Applying RTMIOP G5121RM H1VMFASM197I Assembling RTMIOPVMFASM257I RTMIOP TEXT created on your A-disk for use in a non-VMSES/EenvironmentVMFASM276I VMFHASM processing completed successfullyPRT FILE 551 SENT FROM 5798DWDC PRT WAS 551 RECS 11K CPY 1 A NOHOLD NOKEEPVMFASM276I VMFHASM processing startedDMSUPD178I Updating RTMOUT ASSEMBLE M1DMSUPD178I Applying RTMOUT G546RM H1DMSUPD178I Applying RTMOUT G5121RM H1DMSUPD178I Applying RTMOUT G519RM H1VMFASM197I Assembling RTMOUTVMFASM257I RTMOUT TEXT created on your A-disk for use in a non-VMSES/EenvironmentVMFASM276I VMFHASM processing completed successfullyPRT FILE 552 SENT FROM 5798DWDC PRT WAS 552 RECS 2896 CPY 1 A NOHOLD NOKEEPVMFASM276I VMFHASM processing startedDMSUPD178I Updating RTMSDA ASSEMBLE M1DMSUPD178I Applying RTMSDA G545RM H1DMSUPD178I Applying RTMSDA G544RM H1DMSUPD178I Applying RTMSDA G546RM H154 RTM VM/ESA Program Directory

VMFASM197I Assembling RTMSDAVMFASM257I RTMSDA TEXT created on your A-disk for use in a non-VMSES/EenvironmentVMFASM276I VMFHASM processing completed successfullyPRT FILE 553 SENT FROM 5798DWDC PRT WAS 553 RECS 9776 CPY 1 A NOHOLD NOKEEPVMFASM276I VMFHASM processing startedDMSUPD178I Updating RTMSRV ASSEMBLE M1DMSUPD178I Applying RTMSRV G546RM H1VMFASM197I Assembling RTMSRVVMFASM257I RTMSRV TEXT created on your A-disk for use in a non-VMSES/EenvironmentVMFASM276I VMFHASM processing completed successfullyPRT FILE 554 SENT FROM 5798DWDC PRT WAS 554 RECS 11K CPY 1 A NOHOLD NOKEEPVMFASM276I VMFHASM processing startedDMSUPD178I Updating RTMSYS ASSEMBLE M1DMSUPD178I Applying RTMSYS G544RM H1DMSUPD178I Applying RTMSYS G546RM H1VMFASM197I Assembling RTMSYSVMFASM257I RTMSYS TEXT created on your A-disk for use in a non-VMSES/EenvironmentVMFASM276I VMFHASM processing completed successfullyPRT FILE 555 SENT FROM 5798DWDC PRT WAS 555 RECS 835 CPY 1 A NOHOLD NOKEEPVMFASM276I VMFHASM processing startedDMSUPD178I Updating RTMSYT ASSEMBLE M1DMSUPD178I Applying RTMSYT G544RM H1DMSUPD178I Applying RTMSYT G546RM H1VMFASM197I Assembling RTMSYTVMFASM257I RTMSYT TEXT created on your A-disk for use in a non-VMSES/EenvironmentVMFASM276I VMFHASM processing completed successfullyPRT FILE 556 SENT FROM 5798DWDC PRT WAS 556 RECS 8716 CPY 1 A NOHOLD NOKEEPVMFASM276I VMFHASM processing startedDMSUPD178I Updating RTMUSR ASSEMBLE M1DMSUPD178I Applying RTMUSR G544RM H1DMSUPD178I Applying RTMUSR G546RM H1VMFASM197I Assembling RTMUSRVMFASM257I RTMUSR TEXT created on your A-disk for use in a non-VMSES/EenvironmentVMFASM276I VMFHASM processing completed successfullyPRT FILE 557 SENT FROM 5798DWDC PRT WAS 557 RECS 13K CPY 1 A NOHOLD NOKEEPVMFASM276I VMFHASM processing startedDMSUPD181E No update files were foundVMFASM197I Assembling RTMVMCVMFASM257I RTMVMC TEXT created on your A-disk for use in a non-VMSES/EAppendix B. Sample output from BUILD command. 55

environmentVMFASM276I VMFHASM processing completed successfullyPRT FILE 558 SENT FROM 5798DWDC PRT WAS 558 RECS 3398 CPYVMFBLD1851I (3 of 4) RTMBDUTL completed with return code VMFBLD1851I (4 of 4) VMFBDMOD processing RTMMOD EXC28VMFBDM2219I Processing object RTM.MODULEVMFBDM2219I Processing object VMC.MODULEVMFBDM2219I Processing object SNAPP.MODULEVMFBLD1851I (4 of 4) VMFBDMOD completed with return code VMFBLD218I There are build requirements remainingVMFBLD276I VMFBLD processing completed successfullyVMFINB2173I No verification exec found for this productVMFINB2822I Product 5798DWDC RTMINS built successfullyVMFINS276I VMFINS processing completed successfully1 A NOHOLD NOKEEP56 RTM VM/ESA Program Directory

Appendix C. Sample non-VMSES/E install from 9302 RefreshTapeIn this example, the install of the product on the default minidisks is shown.REW 181Rewind completeReady; T=.1/.1 14:21:17VMFPLC2 LOADLoading ...INS 932 A1I5798DWD EXEC A1I5798DWD 15212 A15798DWDC 152121 A15798DWDC PRODPART A15798DWDC $PPF A15798DWDC PPF A15798DWDC MEMO A15798DWDC $INS A1RTM SRVAPPS A1End-of-file or end-of-tapeReady; T=.1/.4 14:21:26VMFPLC2 LOADLoading ...5798DWDC 152121 A15798DWDC MEMO A1I5798DWD MEMO A1End-of-file or end-of-tapeReady; T=.1/.1 14:21:3I5798DWD 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© Copyright IBM Corp. 1985, 1992 57

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 4 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 4 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/directory58 RTM VM/ESA Program 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 MODULEPRT FILE 496 SENT FROM 5798DWDC PRT WAS 496 RECS 194 CPY 1 A NOHOLD NOKEEPReady; T=.38/1.22 14:23:XEDIT RTMDISK EXECReady; T=.1/.2 14:23:23RTMBLDRTMBLD1I ACCESSING TEST DISK 4 AS MODE DRTMBLD1I ACCESSING AUXFILE DISK 2A6 AS MODE ERTMBLD1I ACCESSING UPDATE DISK 2D2 AS MODE FRTMBLD1I ACCESSING SOURCE DISK 2B2 AS MODE GRTMBLD1I ACCESSING CP MACLIBS ON DISK $MAINT 193 AS MODE HDMSACP723I H (11) R/O Below is the search order for this build of RTM. Mode Vdev/DirectoryDescription ---- -------------- ----------- A 191 RTM build work disk D 4 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.Appendix C. Sample non-VMSES/E install from 9302 Refresh Tape 59

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 '' 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.1DMSUPD181E No update files were foundRTMCC MACRO ADDED.DMSUPD181E No update files were foundRTMWRAP MACRO ADDED.DMSUPD181E No update files were foundRTMUSING MACRO ADDED.DMSUPD181E No update files were foundRTMSWAPT MACRO ADDED.DMSUPD181E No update files were foundRTMSSLIH MACRO ADDED.DMSUPD181E No update files were foundRTMRSLIH MACRO ADDED.DMSUPD181E No update files were foundRTMPROLG MACRO ADDED.DMSUPD181E No update files were foundRTMNEWTM MACRO ADDED.DMSUPD181E No update files were foundRTMEXIT MACRO ADDED.DMSUPD181E No update files were foundRTMENTER MACRO ADDED.DMSUPD181E No update files were foundRTMDROP MACRO ADDED.DMSUPD181E No update files were foundRTMCALL MACRO ADDED.DMSUPD181E No update files were foundRTMBLANK MACRO ADDED.DMSUPD181E No update files were foundRTMMULDL MACRO ADDED.60 RTM VM/ESA Program Directory

DMSUPD178I Updating RTMTRACE MACRO D2DMSUPD178I Applying RTMTRACE F544RM F1RTMTRACE MACRO ADDED.DMSUPD178I Updating RTMVMBAD COPY G1DMSUPD178I Applying RTMVMBAD F546RM F1RTMVMBAD COPY ADDED.DMSUPD181E No update files were foundRTMVECTB COPY ADDED.DMSUPD181E No update files were foundRTMUSRTB COPY ADDED.DMSUPD181E No update files were foundRTMTMRTB COPY ADDED.DMSUPD181E No update files were foundRTMTEDAT COPY ADDED.DMSUPD181E No update files were foundRTMTEADR COPY ADDED.DMSUPD181E No update files were foundRTMSYTDA COPY ADDED.DMSUPD178I Updating RTMSYDAT COPY G1DMSUPD178I Applying RTMSYDAT F546RM F1RTMSYDAT COPY ADDED.DMSUPD181E No update files were foundRTMSRCTB COPY ADDED.DMSUPD181E No update files were foundRTMSCNTB COPY ADDED.DMSUPD178I Updating RTMPLBDA COPY G1DMSUPD178I Applying RTMPLBDA F546RM F1RTMPLBDA COPY ADDED.DMSUPD181E No update files were foundRTMPFTDA COPY ADDED.DMSUPD181E No update files were foundRTMPFAAD COPY ADDED.DMSUPD178I Updating RTMOPTNS COPY G1DMSUPD178I Applying RTMOPTNS F546RM F1RTMOPTNS COPY ADDED.DMSUPD181E No update files were foundRTMLOGTB COPY ADDED.DMSUPD181E No update files were foundRTMLGMSG COPY ADDED.DMSUPD181E No update files were foundRTMINTDA COPY ADDED.DMSUPD181E No update files were foundRTMHDRDA COPY ADDED.DMSUPD181E No update files were foundRTMFTDAT COPY ADDED.DMSUPD181E No update files were foundAppendix C. Sample non-VMSES/E install from 9302 Refresh Tape 61

RTMFTADR COPY ADDED.DMSUPD178I Updating RTMDVSTB COPY G1DMSUPD178I Applying RTMDVSTB F5121RM F1RTMDVSTB COPY ADDED.DMSUPD178I Updating RTMDEVAD COPY G1DMSUPD178I Applying RTMDEVAD F546RM F1RTMDEVAD COPY ADDED.DMSUPD181E No update files were foundRTMACTNS COPY ADDED.DMSUPD178I Updating RTMASBLK COPY G1DMSUPD178I Applying RTMASBLK F546RM F1RTMASBLK COPY ADDED.DMSUPD181E No update files were foundRTMIOPAS COPY ADDED.DMSUPD178I Updating RTMSDATB COPY G1DMSUPD178I Applying RTMSDATB F545RM F1RTMSDATB COPY ADDED.DMSUPD178I Updating RTMSDAAD COPY G1DMSUPD178I Applying RTMSDAAD F546RM F1RTMSDAAD COPY ADDED.DMSUPD178I Updating RTMMEXBK COPY D2DMSUPD178I Applying RTMMEXBK F546RM F1RTMMEXBK COPY ADDED.DMSUPD178I Updating RTMASCBK COPY D2DMSUPD178I Applying RTMASCBK F546RM F1RTMASCBK COPY ADDED.DMSUPD178I Updating RTMDDITB COPY D2DMSUPD178I Applying RTMDDITB F546RM F1RTMDDITB COPY ADDED.RTMMESA5 COPY ADDED.PRT FILE 497 SENT FROM 5798DWDC PRT WAS 497 RECS 818 CPY1 A NOHOLD NOKEEP62 RTM VM/ESA Program Directory

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.VMFASM276I VMFHASM processing startedDMSUPD178I Updating RTMCMD ASSEMBLE G1DMSUPD178I Applying RTMCMD F541RM F1DMSUPD178I Applying RTMCMD F544RM F1DMSUPD178I Applying RTMCMD F546RM F1VMFASM197I Assembling RTMCMDVMFASM257I RTMCMD TEXT created on your A-disk for use in a non-VMSES/EenvironmentVMFASM276I VMFHASM processing completed successfullyPRT FILE 498 SENT FROM 5798DWDC PRT WAS 498 RECS 1K CPY 1 A NOHOLD NOKEEPVMFASM276I VMFHASM processing startedDMSUPD178I Updating RTMCMP ASSEMBLE G1DMSUPD178I Applying RTMCMP F544RM F1DMSUPD178I Applying RTMCMP F546RM F1VMFASM197I Assembling RTMCMPVMFASM257I RTMCMP TEXT created on your A-disk for use in a non-VMSES/EenvironmentVMFASM276I VMFHASM processing completed successfullyPRT FILE 499 SENT FROM 5798DWDC PRT WAS 499 RECS 11K CPY 1 A NOHOLD NOKEEPVMFASM276I VMFHASM processing startedDMSUPD178I Updating RTMDAT ASSEMBLE G1DMSUPD178I Applying RTMDAT F544RM F1DMSUPD178I Applying RTMDAT F546RM F1VMFASM197I Assembling RTMDATVMFASM257I RTMDAT TEXT created on your A-disk for use in a non-VMSES/EenvironmentVMFASM276I VMFHASM processing completed successfullyPRT FILE 5 SENT FROM 5798DWDC PRT WAS 5 RECS 8523 CPY 1 A NOHOLD NOKEEPVMFASM276I VMFHASM processing startedAppendix C. Sample non-VMSES/E install from 9302 Refresh Tape 63

DMSUPD178I Updating RTMDRV ASSEMBLE G1DMSUPD178I Applying RTMDRV F544RM F1DMSUPD178I Applying RTMDRV F546RM F1VMFASM197I Assembling RTMDRVVMFASM257I RTMDRV TEXT created on your A-disk for use in a non-VMSES/EenvironmentVMFASM276I VMFHASM processing completed successfullyPRT FILE 51 SENT FROM 5798DWDC PRT WAS 51 RECS 12K CPY 1 A NOHOLD NOKEEPVMFASM276I VMFHASM processing startedDMSUPD178I Updating RTMDSL ASSEMBLE G1DMSUPD178I Applying RTMDSL F544RM F1DMSUPD178I Applying RTMDSL F546RM F1VMFASM197I Assembling RTMDSLVMFASM257I RTMDSL TEXT created on your A-disk for use in a non-VMSES/EenvironmentVMFASM276I VMFHASM processing completed successfullyPRT FILE 52 SENT FROM 5798DWDC PRT WAS 52 RECS 6257 CPY 1 A NOHOLD NOKEEPVMFASM276I VMFHASM processing startedDMSUPD178I Updating RTMDSP ASSEMBLE G1DMSUPD178I Applying RTMDSP F544RM F1DMSUPD178I Applying RTMDSP F546RM F1VMFASM197I Assembling RTMDSPVMFASM257I RTMDSP TEXT created on your A-disk for use in a non-VMSES/EenvironmentVMFASM276I VMFHASM processing completed successfullyPRT FILE 53 SENT FROM 5798DWDC PRT WAS 53 RECS 12K CPY 1 A NOHOLD NOKEEPVMFASM276I VMFHASM processing startedDMSUPD178I Updating RTMDSU ASSEMBLE G1DMSUPD178I Applying RTMDSU F544RM F1DMSUPD178I Applying RTMDSU F526RM F1DMSUPD178I Applying RTMDSU F546RM F1VMFASM197I Assembling RTMDSUVMFASM257I RTMDSU TEXT created on your A-disk for use in a non-VMSES/EenvironmentVMFASM276I VMFHASM processing completed successfullyPRT FILE 54 SENT FROM 5798DWDC PRT WAS 54 RECS 1K CPY 1 A NOHOLD NOKEEPVMFASM276I VMFHASM processing startedDMSUPD178I Updating RTMDSV ASSEMBLE G1DMSUPD178I Applying RTMDSV F544RM F1DMSUPD178I Applying RTMDSV F546RM F1VMFASM197I Assembling RTMDSVVMFASM257I RTMDSV TEXT created on your A-disk for use in a non-VMSES/EenvironmentVMFASM276I VMFHASM processing completed successfullyPRT FILE 55 SENT FROM 5798DWDC PRT WAS 55 RECS 8969 CPY 1 A NOHOLD NOKEEPVMFASM276I VMFHASM processing startedDMSUPD178I Updating RTMDSW ASSEMBLE G164 RTM VM/ESA Program Directory

DMSUPD178I Applying RTMDSW F516RM F1DMSUPD178I Applying RTMDSW F544RM F1DMSUPD178I Applying RTMDSW F546RM F1VMFASM197I Assembling RTMDSWVMFASM257I RTMDSW TEXT created on your A-disk for use in a non-VMSES/EenvironmentVMFASM276I VMFHASM processing completed successfullyPRT FILE 56 SENT FROM 5798DWDC PRT WAS 56 RECS 772 CPY 1 A NOHOLD NOKEEPVMFASM276I VMFHASM processing startedDMSUPD178I Updating RTMDSX ASSEMBLE G1DMSUPD178I Applying RTMDSX F543RM F1DMSUPD178I Applying RTMDSX F544RM F1DMSUPD178I Applying RTMDSX F546RM F1DMSUPD178I Applying RTMDSX F513RM F1VMFASM197I Assembling RTMDSXVMFASM257I RTMDSX TEXT created on your A-disk for use in a non-VMSES/EenvironmentVMFASM276I VMFHASM processing completed successfullyPRT FILE 57 SENT FROM 5798DWDC PRT WAS 57 RECS 629 CPY 1 A NOHOLD NOKEEPVMFASM276I VMFHASM processing startedDMSUPD178I Updating RTMERM ASSEMBLE G1DMSUPD178I Applying RTMERM F546RM F1VMFASM197I Assembling RTMERMVMFASM257I RTMERM TEXT created on your A-disk for use in a non-VMSES/EenvironmentVMFASM276I VMFHASM processing completed successfullyPRT FILE 58 SENT FROM 5798DWDC PRT WAS 58 RECS 465 CPY 1 A NOHOLD NOKEEPVMFASM276I VMFHASM processing startedDMSUPD178I Updating RTMIOP ASSEMBLE G1DMSUPD178I Applying RTMIOP F545RM F1DMSUPD178I Applying RTMIOP F544RM F1DMSUPD178I Applying RTMIOP F546RM F1DMSUPD178I Applying RTMIOP F5121RM F1VMFASM197I Assembling RTMIOPVMFASM257I RTMIOP TEXT created on your A-disk for use in a non-VMSES/EenvironmentVMFASM276I VMFHASM processing completed successfullyPRT FILE 59 SENT FROM 5798DWDC PRT WAS 59 RECS 11K CPY 1 A NOHOLD NOKEEPVMFASM276I VMFHASM processing startedDMSUPD178I Updating RTMOUT ASSEMBLE G1DMSUPD178I Applying RTMOUT F546RM F1DMSUPD178I Applying RTMOUT F5121RM F1DMSUPD178I Applying RTMOUT F519RM F1VMFASM197I Assembling RTMOUTVMFASM257I RTMOUT TEXT created on your A-disk for use in a non-VMSES/EenvironmentAppendix C. Sample non-VMSES/E install from 9302 Refresh Tape 65

VMFASM276I VMFHASM processing completed successfullyPRT FILE 51 SENT FROM 5798DWDC PRT WAS 51 RECS 2895 CPY 1 A NOHOLD NOKEEPVMFASM276I VMFHASM processing startedDMSUPD178I Updating RTMSDA ASSEMBLE G1DMSUPD178I Applying RTMSDA F545RM F1DMSUPD178I Applying RTMSDA F544RM F1DMSUPD178I Applying RTMSDA F546RM F1VMFASM197I Assembling RTMSDAVMFASM257I RTMSDA TEXT created on your A-disk for use in a non-VMSES/EenvironmentVMFASM276I VMFHASM processing completed successfullyPRT FILE 511 SENT FROM 5798DWDC PRT WAS 511 RECS 9773 CPY 1 A NOHOLD NOKEEPVMFASM276I VMFHASM processing startedDMSUPD178I Updating RTMSRV ASSEMBLE G1DMSUPD178I Applying RTMSRV F546RM F1VMFASM197I Assembling RTMSRVVMFASM257I RTMSRV TEXT created on your A-disk for use in a non-VMSES/EenvironmentVMFASM276I VMFHASM processing completed successfullyPRT FILE 512 SENT FROM 5798DWDC PRT WAS 512 RECS 11K CPY 1 A NOHOLD NOKEEPVMFASM276I VMFHASM processing startedDMSUPD178I Updating RTMSYS ASSEMBLE G1DMSUPD178I Applying RTMSYS F544RM F1DMSUPD178I Applying RTMSYS F546RM F1VMFASM197I Assembling RTMSYSVMFASM257I RTMSYS TEXT created on your A-disk for use in a non-VMSES/EenvironmentVMFASM276I VMFHASM processing completed successfullyPRT FILE 513 SENT FROM 5798DWDC PRT WAS 513 RECS 8348 CPY 1 A NOHOLD NOKEEPVMFASM276I VMFHASM processing startedDMSUPD178I Updating RTMSYT ASSEMBLE G1DMSUPD178I Applying RTMSYT F544RM F1DMSUPD178I Applying RTMSYT F546RM F1VMFASM197I Assembling RTMSYTVMFASM257I RTMSYT TEXT created on your A-disk for use in a non-VMSES/EenvironmentVMFASM276I VMFHASM processing completed successfullyPRT FILE 514 SENT FROM 5798DWDC PRT WAS 514 RECS 8714 CPY 1 A NOHOLD NOKEEPVMFASM276I VMFHASM processing startedDMSUPD178I Updating RTMUSR ASSEMBLE G1DMSUPD178I Applying RTMUSR F544RM F1DMSUPD178I Applying RTMUSR F546RM F1VMFASM197I Assembling RTMUSR66 RTM VM/ESA Program Directory

VMFASM257I RTMUSR TEXT created on your A-disk for use in a non-VMSES/EenvironmentVMFASM276I VMFHASM processing completed successfullyPRT FILE 515 SENT FROM 5798DWDC PRT WAS 515 RECS 13K CPY 1 A NOHOLD NOKEEPVMFASM276I VMFHASM processing startedDMSUPD181E No update files were foundVMFASM197I Assembling RTMVMCVMFASM257I RTMVMC TEXT created on your A-disk for use in a non-VMSES/EenvironmentVMFASM276I VMFHASM processing completed successfullyPRT FILE 516 SENT FROM 5798DWDC PRT WAS 516 RECS 3397 CPY 1 A NOHOLD NOKEEP RTM build completed successfully. Copying all TEXT files, MACLIB, and/or MODULE to the test disk.DASD 11 DETACHED Exiting RTMBLD EXEC. You should now copy the RTM MODULE to the RTM VM/ESA service machine's 191 disk or top level directoryReady; T=23.45/38.78 14:35:13Appendix C. Sample non-VMSES/E install from 9302 Refresh Tape 67

Appendix D. Sample Non-VMSES/E Install with CORrectiveService 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 andRTMDISK EXEC required for the build of the product. Thus, the GA product tape and the service tapemust 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 thecumulative 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 RTMBLDEXEC.D.1 Install of GA Product Tape with I5798DWD EXEC68 © Copyright IBM Corp. 1985, 1992

Ready; T=.1/.1 18:5:42rew 181Rewind completeReady; T=.1/.1 18:5:5vmfplc2 loadLoading ...INS 92 A1I5798DWD EXEC A1I5798DWD 1521 A15798DWDC 15211 A15798DWDC PRODPART A15798DWDC $PPF A15798DWDC PPF A15798DWDC MEMO A15798DWDC $INS A1End-of-file or end-of-tapeReady; T=.3/.7 18:5:58vmfplc2 loadLoading ...5798DWDC 15211 A15798DWDC MEMO A1I5798DWD MEMO A1End-of-file or end-of-tapeReady; T=.1/.2 18:51:18i5798dwd 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 4 disk Enter the minidisk address to install the RTM VM/ESA sample files, if different than the default 2C2 diskAppendix D. Sample Non-VMSES/E Install with CORrective Service Tape. 69

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 4 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 4 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=.27/.93 18:51:27D.2 Install of Cumulative Service TapeAt 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 correctiveservice needs to be applied.70 RTM VM/ESA Program Directory

Ready; T=.1/.1 13:36:57rew 181Rewind completeReady; T=.1/.1 13:37:2def t338 99 1DASD 99 DEFINEDReady; T=.1/.1 13:37:8format 99 bDMSFOR63R FORMAT will erase all files on disk B(99). Do you wish to continue? Enter 1 (YES) or (NO).1DMSFOR65R Enter disk label:TEMPDMSFOR733I Formatting disk BDMSFOR732I 1 cylinders formatted on B(99)Ready; T=.1/.2 13:37:31vmfplc2 scan 5798dwdb 111 (EOTScanning ...End-of-file or end-of-tape5798DWDB 111 U1Ready; T=.1/.1 13:37:43vmfplc2 load BLoading ...5798DWDB 111 B1RTMACLIB EXC23 B1RTMACLIB EXC2188 B1RTMASBLK AUM23 B1RTMASBLK F546RM B1RTMASCBK AUM23 B1RTMASCBK CPY23 B1RTMASCBK F546RM B1RTMBLD EXC23 B1RTMCMD AUM23 B1RTMCMD AUM2188 B1RTMCMD AUM2158 B1RTMCMD F541RM B1RTMCMD F544RM B1RTMCMD F546RM B1RTMCMP AUM23 B1RTMCMP AUM2188 B1RTMCMP F544RM B1RTMCMP F546RM B1RTMDAT AUM23 B1RTMDAT AUM2188 B1RTMDAT F544RM B1RTMDAT F546RM B1RTMDDITB AUM23 B1RTMDDITB CPY23 B1RTMDDITB F546RM B1RTMDEVAD AUM23 B1Appendix D. Sample Non-VMSES/E Install with CORrective Service Tape. 71

RTMDEVAD F546RM B1RTMDISK EXC23 B1RTMDRV AUM23 B1RTMDRV AUM2188 B1RTMDRV F544RM B1RTMDRV F546RM B1RTMDSL AUM23 B1RTMDSL AUM2188 B1RTMDSL F544RM B1RTMDSL F546RM B1RTMDSP AUM23 B1RTMDSP AUM2188 B1RTMDSP F544RM B1RTMDSP F546RM B1RTMDSU AUM23 B1RTMDSU AUM2192 B1RTMDSU AUM2188 B1RTMDSU F526RM B1RTMDSU F544RM B1RTMDSU F546RM B1RTMDSV AUM23 B1RTMDSV AUM2188 B1RTMDSV F544RM B1RTMDSV F546RM B1RTMDSW AUM23 B1RTMDSW AUM2188 B1RTMDSW AUM281 B1RTMDSW F516RM B1RTMDSW F544RM B1RTMDSW F546RM B1RTMDSX AUM23 B1RTMDSX AUM2188 B1RTMDSX AUM2158 B1RTMDSX F543RM B1RTMDSX F544RM B1RTMDSX F546RM B1RTMERM AUM23 B1RTMERM F546RM B1RTMESA5 CTL23 B1RTMIOP AUM23 B172 RTM VM/ESA Program Directory

RTMIOP AUM2188 B1RTMIOP AUM2158 B1RTMIOP F544RM B1RTMIOP F545RM B1RTMIOP F546RM B1RTMMESA5 EXC23 B1RTMMESA5 EXC2188 B1RTMMEXBK AUM23 B1RTMMEXBK CPY23 B1RTMMEXBK F546RM B1RTMMOD EXC279 B2RTMOPTNS AUM23 B1RTMOPTNS F546RM B1RTMOUT AUM23 B1RTMOUT F546RM B1RTMPLBDA AUM23 B1RTMPLBDA F546RM B1RTMSDA AUM23 B1RTMSDA AUM2188 B1RTMSDA AUM2158 B1RTMSDA F544RM B1RTMSDA F545RM B1RTMSDA F546RM B1RTMSDAAD AUM23 B1RTMSDAAD F546RM B1RTMSDATB AUM2158 B1RTMSDATB F545RM B1RTMSRV AUM23 B1RTMSRV F546RM B1RTMSYDAT AUM23 B1RTMSYDAT F546RM B1RTMSYS AUM23 B1RTMSYS AUM2188 B1RTMSYS F544RM B1RTMSYS F546RM B1RTMSYT AUM23 B1RTMSYT AUM2188 B1RTMSYT F544RM B1RTMSYT F546RM B1RTMTRACE AUM2188 B1RTMTRACE F544RM B1Appendix D. Sample Non-VMSES/E Install with CORrective Service Tape. 73

RTMTRACE MAC2188 B1RTMUSR AUM23 B1RTMUSR AUM2188 B1RTMUSR F544RM B1RTMUSR F546RM B1RTMVMBAD AUM23 B1RTMVMBAD F546RM B1VMCLOAD EXC23 B15798DWDC MEM23 B15798DWDC MEM2192 B15798DWDC MEM2188 B15798DWDC MEM2158 B15798DWDC MEM281 B15798DWDC MEM279 B15798DWDB EXEC B1End-of-file or end-of-tapeReady; T=.13/.33 13:38:95798dwdb bRENAME RTMACLIB EXC23 B = EXEC =ERASE RTMACLIB EXC2188 BRENAME RTMASBLK AUM23 B = AUXRTM5 =RENAME RTMASCBK AUM23 B = AUXRTM5 =RENAME RTMASCBK CPY23 B = COPY =RENAME RTMBLD EXC23 B = EXEC =RENAME RTMCMD AUM23 B = AUXRTM5 =ERASE RTMCMD AUM2188 BERASE RTMCMD AUM2158 BRENAME RTMCMP AUM23 B = AUXRTM5 =ERASE RTMCMP AUM2188 BRENAME RTMDAT AUM23 B = AUXRTM5 =ERASE RTMDAT AUM2188 BRENAME RTMDDITB AUM23 B = AUXRTM5 =RENAME RTMDDITB CPY23 B = COPY =RENAME RTMDEVAD AUM23 B = AUXRTM5 =RENAME RTMDISK EXC23 B = EXEC =RENAME RTMDRV AUM23 B = AUXRTM5 =ERASE RTMDRV AUM2188 BRENAME RTMDSL AUM23 B = AUXRTM5 =ERASE RTMDSL AUM2188 BRENAME RTMDSP AUM23 B = AUXRTM5 =ERASE RTMDSP AUM2188 B74 RTM VM/ESA Program Directory

RENAME RTMDSU AUM23 B = AUXRTM5 =ERASE RTMDSU AUM2192 BERASE RTMDSU AUM2188 BRENAME RTMDSV AUM23 B = AUXRTM5 =ERASE RTMDSV AUM2188 BRENAME RTMDSW AUM23 B = AUXRTM5 =ERASE RTMDSW AUM2188 BERASE RTMDSW AUM281 BRENAME RTMDSX AUM23 B = AUXRTM5 =ERASE RTMDSX AUM2188 BERASE RTMDSX AUM2158 BRENAME RTMERM AUM23 B = AUXRTM5 =RENAME RTMESA5 CTL23 B = CNTRL =RENAME RTMIOP AUM23 B = AUXRTM5 =ERASE RTMIOP AUM2188 BERASE RTMIOP AUM2158 BRENAME RTMMESA5 EXC23 B = EXEC =ERASE RTMMESA5 EXC2188 BRENAME RTMMEXBK AUM23 B = AUXRTM5 =RENAME RTMMEXBK CPY23 B = COPY =RENAME RTMMOD EXC279 B = EXEC =RENAME RTMOPTNS AUM23 B = AUXRTM5 =RENAME RTMOUT AUM23 B = AUXRTM5 =RENAME RTMPLBDA AUM23 B = AUXRTM5 =RENAME RTMSDA AUM23 B = AUXRTM5 =ERASE RTMSDA AUM2188 BERASE RTMSDA AUM2158 BRENAME RTMSDAAD AUM23 B = AUXRTM5 =RENAME RTMSDATB AUM2158 B = AUXRTM5 =RENAME RTMSRV AUM23 B = AUXRTM5 =RENAME RTMSYDAT AUM23 B = AUXRTM5 =RENAME RTMSYS AUM23 B = AUXRTM5 =ERASE RTMSYS AUM2188 BRENAME RTMSYT AUM23 B = AUXRTM5 =ERASE RTMSYT AUM2188 BRENAME RTMTRACE AUM2188 B = AUXRTM5 =RENAME RTMTRACE MAC2188 B = MACRO =RENAME RTMUSR AUM23 B = AUXRTM5 =ERASE RTMUSR AUM2188 BRENAME RTMVMBAD AUM23 B = AUXRTM5 =RENAME VMCLOAD EXC23 B = EXEC =RENAME 5798DWDC MEM23 B = MEMO =ERASE 5798DWDC MEM2192 BERASE 5798DWDC MEM2188 BERASE 5798DWDC MEM2158 BERASE 5798DWDC MEM281 BERASE 5798DWDC MEM279 BReady; T=.3/.7 13:38:25Appendix D. Sample Non-VMSES/E Install with CORrective Service Tape. 75

Note: At this point you would copy the AUXRTM5 files to the delta (2A6) disk, copy the update files tothe APPLY (2D2) disk, copy any new source files to the source (2B2) disk and place the full replacementparts, such as the build EXECs on the test (400) disk. In this example, the MACRO, COPY andASSEMBLE 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 the2D2 disk. All non-VMSES/E RTM update files have a filetype that begins with F0, and the user wouldcopy all these files to the 2D2 disk. In addition, as recommended the latest RTMBLD and RTMDISKEXECs are copied to the 191 disk.acc 2b2 zReady; T=.1/.1 13:38:41copyf macro b = = z (olddReady; T=.1/.1 13:38:59copyf copy b = = z (olddReady; T=.1/.1 13:39:9copyf assemble b = = z (olddDMSCPY2E INPUT file ASSEMBLE B not foundReady(28); T=.1/.1 13:39:17acc 2a6 zDMSACC724I 2A6 replaces Z (2B2)Ready; T=.1/.1 13:39:27copyf auxrtm5 b = = z (rep olddReady; T=.2/.5 13:39:44acc 4 zDMSACC724I 4 replaces Z (2A6)Ready; T=.1/.1 13:39:51copyf exec b = = z (rep olddReady; T=.1/.1 13:4:27copyf cntrl b = = z (rep olddReady; T=.1/.1 13:4:36copyf rtmdisk exec z = = a (rep olddReady; T=.1/.1 13:42:47copyf rtmbld exec z = = a (rep olddReady; T=.1/.1 13:42:58acc 2d2 zDMSACC724I 2D2 replaces Z (4)Ready; T=.1/.1 13:4:54filel fRM bReady; T=.39/.44 13:42:4Note: User would copy all these files to the delta (2D2) disk.rel bReady; T=.1/.1 13:42:11x rtmdisk execReady; T=.2/.2 13:43:24Note: In this example, the user modifies the RTMDISK EXEC. Their installation has the CP MACLIBSon the $MAINT 193 disk. The default listed in the RTMDISK EXEC is MAINT 193 disk; hence, it must bechanged. The CPmac_owner='MAINT' is changed to CPmac_owner='$MAINT' in the RTMDISK EXEC.76 RTM VM/ESA Program Directory

D.3 Build of RTM VM/ESAAt this point the product has been fully installed, including the latest service. The product needs to nowbe built. Note that the user chose to rebuild the RTMMESA5 MACLIB since there was service to some ofthe RTM COPY and MACRO files.rtmbldRTMBLD1I ACCESSING TEST DISK 4 AS MODE BRTMBLD1I ACCESSING AUXFILE DISK 2A6 AS MODE ERTMBLD1I ACCESSING UPDATE DISK 2D2 AS MODE FRTMBLD1I ACCESSING SOURCE DISK 2B2 AS MODE HRTMBLD1I ACCESSING CP MACLIBS ON DISK $MAINT 193 AS MODE IDMSACP723I I (11) R/O Below is the search order for this build of RTM. Mode Vdev Description ---- ---- ----------- A 191 RTM build work disk B 4 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 '' 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.1Appendix D. Sample Non-VMSES/E Install with CORrective Service Tape. 77

DMSUPD181E No update files were foundRTMCC MACRO ADDED.DMSUPD181E No update files were foundRTMWRAP MACRO ADDED.DMSUPD181E No update files were foundRTMUSING MACRO ADDED.DMSUPD181E No update files were foundRTMSWAPT MACRO ADDED.DMSUPD181E No update files were foundRTMSSLIH MACRO ADDED.DMSUPD181E No update files were foundRTMRSLIH MACRO ADDED.DMSUPD181E No update files were foundRTMPROLG MACRO ADDED.DMSUPD181E No update files were foundRTMNEWTM MACRO ADDED.DMSUPD181E No update files were foundRTMEXIT MACRO ADDED.DMSUPD181E No update files were foundRTMENTER MACRO ADDED.DMSUPD181E No update files were foundRTMDROP MACRO ADDED.DMSUPD181E No update files were foundRTMCALL MACRO ADDED.DMSUPD181E No update files were foundRTMBLANK MACRO ADDED.DMSUPD181E No update files were foundRTMMULDL MACRO ADDED.DMSUPD178I Updating RTMTRACE MACRO H1DMSUPD178I Applying RTMTRACE F544RM F1RTMTRACE MACRO ADDED.DMSUPD178I Updating RTMVMBAD COPY H1DMSUPD178I Applying RTMVMBAD F546RM F1RTMVMBAD COPY ADDED.DMSUPD181E No update files were foundRTMVECTB COPY ADDED.78 RTM VM/ESA Program Directory

DMSUPD181E No update files were foundRTMUSRTB COPY ADDED.DMSUPD181E No update files were foundRTMTMRTB COPY ADDED.DMSUPD181E No update files were foundRTMTEDAT COPY ADDED.DMSUPD181E No update files were foundRTMTEADR COPY ADDED.DMSUPD181E No update files were foundRTMSYTDA COPY ADDED.DMSUPD178I Updating RTMSYDAT COPY H1DMSUPD178I Applying RTMSYDAT F546RM F1RTMSYDAT COPY ADDED.DMSUPD181E No update files were foundRTMSRCTB COPY ADDED.DMSUPD181E No update files were foundRTMSCNTB COPY ADDED.DMSUPD178I Updating RTMPLBDA COPY H1DMSUPD178I Applying RTMPLBDA F546RM F1RTMPLBDA COPY ADDED.DMSUPD181E No update files were foundRTMPFTDA COPY ADDED.DMSUPD181E No update files were foundRTMPFAAD COPY ADDED.DMSUPD178I Updating RTMOPTNS COPY H1DMSUPD178I Applying RTMOPTNS F546RM F1RTMOPTNS COPY ADDED.DMSUPD181E No update files were foundRTMLOGTB COPY ADDED.DMSUPD181E No update files were foundRTMLGMSG COPY ADDED.DMSUPD181E No update files were foundRTMINTDA COPY ADDED.DMSUPD181E No update files were foundRTMHDRDA COPY ADDED.DMSUPD181E No update files were foundRTMFTDAT COPY ADDED.DMSUPD181E No update files were foundRTMFTADR COPY ADDED.Appendix D. Sample Non-VMSES/E Install with CORrective Service Tape. 79

DMSUPD181E No update files were foundRTMDVSTB COPY ADDED.DMSUPD178I Updating RTMDEVAD COPY H1DMSUPD178I Applying RTMDEVAD F546RM F1RTMDEVAD COPY ADDED.DMSUPD181E No update files were foundRTMACTNS COPY ADDED.DMSUPD178I Updating RTMASBLK COPY H1DMSUPD178I Applying RTMASBLK F546RM F1RTMASBLK COPY ADDED.DMSUPD181E No update files were foundRTMIOPAS COPY ADDED.DMSUPD178I Updating RTMSDATB COPY H1DMSUPD178I Applying RTMSDATB F545RM F1RTMSDATB COPY ADDED.DMSUPD178I Updating RTMSDAAD COPY H1DMSUPD178I Applying RTMSDAAD F546RM F1RTMSDAAD COPY ADDED.DMSUPD178I Updating RTMMEXBK COPY H1DMSUPD178I Applying RTMMEXBK F546RM F1RTMMEXBK COPY ADDED.DMSUPD178I Updating RTMASCBK COPY H1DMSUPD178I Applying RTMASCBK F546RM F1RTMASCBK COPY ADDED.DMSUPD178I Updating RTMDDITB COPY H1DMSUPD178I Applying RTMDDITB F546RM F1RTMDDITB COPY ADDED.RTMMESA5 COPY ADDED.PRT FILE 3 SENT FROM 5798DWDC PRT WAS 3 RECS 896 CPY1 A NOHOLD NOKEEP80 RTM VM/ESA Program Directory

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.VMFASM276I VMFHASM processing startedDMSUPD178I Updating RTMCMD ASSEMBLE H1DMSUPD178I Applying RTMCMD F541RM F1DMSUPD178I Applying RTMCMD F544RM F1DMSUPD178I Applying RTMCMD F546RM F1VMFASM197I Assembling RTMCMDVMFASM257I RTMCMD TEXT created on your A-disk for use in a non-VMSES/EenvironmentVMFASM276I VMFHASM processing completed successfullyPRT FILE 31 SENT FROM 5798DWDC PRT WAS 31 RECS 1K CPY 1 A NOHOLD NOKEEPVMFASM276I VMFHASM processing startedDMSUPD178I Updating RTMCMP ASSEMBLE H1DMSUPD178I Applying RTMCMP F544RM F1DMSUPD178I Applying RTMCMP F546RM F1VMFASM197I Assembling RTMCMPVMFASM257I RTMCMP TEXT created on your A-disk for use in a non-VMSES/EenvironmentVMFASM276I VMFHASM processing completed successfullyPRT FILE 32 SENT FROM 5798DWDC PRT WAS 32 RECS 11K CPY 1 A NOHOLD NOKEEPVMFASM276I VMFHASM processing startedDMSUPD178I Updating RTMDAT ASSEMBLE H1DMSUPD178I Applying RTMDAT F544RM F1DMSUPD178I Applying RTMDAT F546RM F1VMFASM197I Assembling RTMDATAppendix D. Sample Non-VMSES/E Install with CORrective Service Tape. 81

VMFASM257I RTMDAT TEXT created on your A-disk for use in a non-VMSES/EenvironmentVMFASM276I VMFHASM processing completed successfullyPRT FILE 33 SENT FROM 5798DWDC PRT WAS 33 RECS 8519 CPY 1 A NOHOLD NOKEEPVMFASM276I VMFHASM processing startedDMSUPD178I Updating RTMDRV ASSEMBLE H1DMSUPD178I Applying RTMDRV F544RM F1DMSUPD178I Applying RTMDRV F546RM F1VMFASM197I Assembling RTMDRVVMFASM257I RTMDRV TEXT created on your A-disk for use in a non-VMSES/EenvironmentVMFASM276I VMFHASM processing completed successfullyPRT FILE 34 SENT FROM 5798DWDC PRT WAS 34 RECS 12K CPY 1 A NOHOLD NOKEEPVMFASM276I VMFHASM processing startedDMSUPD178I Updating RTMDSL ASSEMBLE H1DMSUPD178I Applying RTMDSL F544RM F1DMSUPD178I Applying RTMDSL F546RM F1VMFASM197I Assembling RTMDSLVMFASM257I RTMDSL TEXT created on your A-disk for use in a non-VMSES/EenvironmentVMFASM276I VMFHASM processing completed successfullyPRT FILE 35 SENT FROM 5798DWDC PRT WAS 35 RECS 6257 CPY 1 A NOHOLD NOKEEPVMFASM276I VMFHASM processing startedDMSUPD178I Updating RTMDSP ASSEMBLE H1DMSUPD178I Applying RTMDSP F544RM F1DMSUPD178I Applying RTMDSP F546RM F1VMFASM197I Assembling RTMDSPVMFASM257I RTMDSP TEXT created on your A-disk for use in a non-VMSES/EenvironmentVMFASM276I VMFHASM processing completed successfullyPRT FILE 36 SENT FROM 5798DWDC PRT WAS 36 RECS 12K CPY 1 A NOHOLD NOKEEPVMFASM276I VMFHASM processing startedDMSUPD178I Updating RTMDSU ASSEMBLE H1DMSUPD178I Applying RTMDSU F544RM F1DMSUPD178I Applying RTMDSU F526RM F1DMSUPD178I Applying RTMDSU F546RM F1VMFASM197I Assembling RTMDSUVMFASM257I RTMDSU TEXT created on your A-disk for use in a non-VMSES/Eenvironment82 RTM VM/ESA Program Directory

VMFASM276I VMFHASM processing completed successfullyPRT FILE 37 SENT FROM 5798DWDC PRT WAS 37 RECS 1K CPY 1 A NOHOLD NOKEEPVMFASM276I VMFHASM processing startedDMSUPD178I Updating RTMDSV ASSEMBLE H1DMSUPD178I Applying RTMDSV F544RM F1DMSUPD178I Applying RTMDSV F546RM F1VMFASM197I Assembling RTMDSVVMFASM257I RTMDSV TEXT created on your A-disk for use in a non-VMSES/EenvironmentVMFASM276I VMFHASM processing completed successfullyPRT FILE 38 SENT FROM 5798DWDC PRT WAS 38 RECS 8966 CPY 1 A NOHOLD NOKEEPVMFASM276I VMFHASM processing startedDMSUPD178I Updating RTMDSW ASSEMBLE H1DMSUPD178I Applying RTMDSW F516RM F1DMSUPD178I Applying RTMDSW F544RM F1DMSUPD178I Applying RTMDSW F546RM F1VMFASM197I Assembling RTMDSWVMFASM257I RTMDSW TEXT created on your A-disk for use in a non-VMSES/EenvironmentVMFASM276I VMFHASM processing completed successfullyPRT FILE 39 SENT FROM 5798DWDC PRT WAS 39 RECS 771 CPY 1 A NOHOLD NOKEEPVMFASM276I VMFHASM processing startedDMSUPD178I Updating RTMDSX ASSEMBLE H1DMSUPD178I Applying RTMDSX F543RM F1DMSUPD178I Applying RTMDSX F544RM F1DMSUPD178I Applying RTMDSX F546RM F1VMFASM197I Assembling RTMDSXVMFASM257I RTMDSX TEXT created on your A-disk for use in a non-VMSES/EenvironmentVMFASM276I VMFHASM processing completed successfullyPRT FILE 4 SENT FROM 5798DWDC PRT WAS 4 RECS 6183 CPY 1 A NOHOLD NOKEEPVMFASM276I VMFHASM processing startedDMSUPD178I Updating RTMERM ASSEMBLE H1DMSUPD178I Applying RTMERM F546RM F1VMFASM197I Assembling RTMERMVMFASM257I RTMERM TEXT created on your A-disk for use in a non-VMSES/EenvironmentVMFASM276I VMFHASM processing completed successfullyPRT FILE 41 SENT FROM 5798DWDC PRT WAS 41 RECS 464 CPY 1 A NOHOLD NOKEEPAppendix D. Sample Non-VMSES/E Install with CORrective Service Tape. 83

VMFASM276I VMFHASM processing startedDMSUPD178I Updating RTMIOP ASSEMBLE H1DMSUPD178I Applying RTMIOP F545RM F1DMSUPD178I Applying RTMIOP F544RM F1DMSUPD178I Applying RTMIOP F546RM F1VMFASM197I Assembling RTMIOPVMFASM257I RTMIOP TEXT created on your A-disk for use in a non-VMSES/EenvironmentVMFASM276I VMFHASM processing completed successfullyPRT FILE 42 SENT FROM 5798DWDC PRT WAS 42 RECS 11K CPY 1 A NOHOLD NOKEEPVMFASM276I VMFHASM processing startedDMSUPD178I Updating RTMOUT ASSEMBLE H1DMSUPD178I Applying RTMOUT F546RM F1VMFASM197I Assembling RTMOUTVMFASM257I RTMOUT TEXT created on your A-disk for use in a non-VMSES/EenvironmentVMFASM276I VMFHASM processing completed successfullyPRT FILE 43 SENT FROM 5798DWDC PRT WAS 43 RECS 2873 CPY 1 A NOHOLD NOKEEPVMFASM276I VMFHASM processing startedDMSUPD178I Updating RTMSDA ASSEMBLE H1DMSUPD178I Applying RTMSDA F545RM F1DMSUPD178I Applying RTMSDA F544RM F1DMSUPD178I Applying RTMSDA F546RM F1VMFASM197I Assembling RTMSDAVMFASM257I RTMSDA TEXT created on your A-disk for use in a non-VMSES/EenvironmentVMFASM276I VMFHASM processing completed successfullyPRT FILE 44 SENT FROM 5798DWDC PRT WAS 44 RECS 9769 CPY 1 A NOHOLD NOKEEPVMFASM276I VMFHASM processing startedDMSUPD178I Updating RTMSRV ASSEMBLE H1DMSUPD178I Applying RTMSRV F546RM F1VMFASM197I Assembling RTMSRVVMFASM257I RTMSRV TEXT created on your A-disk for use in a non-VMSES/EenvironmentVMFASM276I VMFHASM processing completed successfullyPRT FILE 45 SENT FROM 5798DWDC PRT WAS 45 RECS 11K CPY 1 A NOHOLD NOKEEPVMFASM276I VMFHASM processing started84 RTM VM/ESA Program Directory

DMSUPD178I Updating RTMSYS ASSEMBLE H1DMSUPD178I Applying RTMSYS F544RM F1DMSUPD178I Applying RTMSYS F546RM F1VMFASM197I Assembling RTMSYSVMFASM257I RTMSYS TEXT created on your A-disk for use in a non-VMSES/EenvironmentVMFASM276I VMFHASM processing completed successfullyPRT FILE 46 SENT FROM 5798DWDC PRT WAS 46 RECS 8347 CPY 1 A NOHOLD NOKEEPVMFASM276I VMFHASM processing startedDMSUPD178I Updating RTMSYT ASSEMBLE H1DMSUPD178I Applying RTMSYT F544RM F1DMSUPD178I Applying RTMSYT F546RM F1VMFASM197I Assembling RTMSYTVMFASM257I RTMSYT TEXT created on your A-disk for use in a non-VMSES/EenvironmentVMFASM276I VMFHASM processing completed successfullyPRT FILE 47 SENT FROM 5798DWDC PRT WAS 47 RECS 8713 CPY 1 A NOHOLD NOKEEPVMFASM276I VMFHASM processing startedDMSUPD178I Updating RTMUSR ASSEMBLE H1DMSUPD178I Applying RTMUSR F544RM F1DMSUPD178I Applying RTMUSR F546RM F1VMFASM197I Assembling RTMUSRVMFASM257I RTMUSR TEXT created on your A-disk for use in a non-VMSES/EenvironmentVMFASM276I VMFHASM processing completed successfullyPRT FILE 48 SENT FROM 5798DWDC PRT WAS 48 RECS 13K CPY 1 A NOHOLD NOKEEPVMFASM276I VMFHASM processing startedDMSUPD181E No update files were foundVMFASM197I Assembling RTMVMCVMFASM257I RTMVMC TEXT created on your A-disk for use in a non-VMSES/EenvironmentVMFASM276I VMFHASM processing completed successfullyPRT FILE 49 SENT FROM 5798DWDC PRT WAS 49 RECS 3396 CPY 1 A NOHOLD NOKEEP RTM build completed successfully. Copying all TEXT files, MACLIB, and/or MODULE to the test disk.DASD 11 DETACHEDAppendix D. Sample Non-VMSES/E Install with CORrective Service Tape. 85

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:57vmcloadReady; T=.1/.2 13:48:28Note: In this example, the user issues VMCLOAD to create a new VMC MODULE since RTMBLD doesnot 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).86 RTM VM/ESA Program Directory

Reader's CommentsRealtime Monitor VM/ESA Release 5.2You may use this form to comment about this document, its organization, or subject matter with the understanding thatIBM may use or distribute whatever information you supply in any way it believes appropriate without incurring anyobligation to you.For each of the topics below please indicate your satisfaction level by circling your choice from the rating scale. If astatement does not apply, please circle N.RATING SCALEvery very notsatisfied dissatisfied applicable1 2 3 4 5 NSatisfactionEase of product installation 1 2 3 4 5 NContents of program directory 1 2 3 4 5 NInstallation Verification Programs 1 2 3 4 5 NTime to install the product 1 2 3 4 5 NReadability and organization of program directory tasks 1 2 3 4 5 NNecessity of all installation tasks 1 2 3 4 5 NAccuracy of the definition of the installation tasks 1 2 3 4 5 NTechnical level of the installation tasks 1 2 3 4 5 NEase of getting the system into production afterinstallation1 2 3 4 5 NDid you order this product as an independent product or as part of a package?IndependentPackageIf this product was ordered as part of a package, what type of package was ordered?CustomPacFunctionPacSystemPacSystem Delivery Offering (SDO)Other - Please specify type: . . . . . . . . . . . . . . . . .Is this the first time your organization has installed this product?YesNo© Copyright IBM Corp. 1985, 1992 87

Were the people who did the installation experienced with the installation of VM products?YesNoIf yes, how many years? __If you have any comments to make about your ratings above, or any other aspect of the product installation, pleaselist them below:Please provide the following contact information:Name and Job TitleOrganizationAddressTelephoneThank you for your participation.Please send the completed form to (or give to your IBM representative who will forward it to the Realtime MonitorVM/ESA Development group):IBM CorporationDept G321701 North St.Endicott, NY 1376088 RTM VM/ESA Program Directory

IBMProgram Number: 5798-DWD 589158925702Printed in U.S.A.XXXX-YYYY-ZZ