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

More documents

Recommendations

Info

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
Page 1 and 2: IBMProgram Directory forRealtime Mo
Page 3 and 4: ContentsNotices . . . . . . . . . .
Page 5 and 6: Appendix D. Sample Non-VMSES/E Inst
Page 7 and 8: 1.0 IntroductionThis program direct
Page 9: Figure 2 (Page 2 of 2). Program Tap
Page 12 and 13: 4.0 Program and Service Level Infor
Page 14 and 15: Figure 8 (Page 2 of 2). DASD Storag
Page 17 and 18: USER RTMESA xxxxx 32M 32M EGUSER RT
Page 19 and 20: 5.3 System ConsiderationsIf RTM VM/
Page 21 and 22: 3. Link and access the minidisks th
Page 23 and 24: VMFINS276I VMFINS processing starte
Page 25 and 26: ACCESS VMSYS:5798DWDC.TBUILD EACCES
Page 27 and 28: 6.1.2.2 Pre-installation instructio
Page 29 and 30: 6.1.2.2.5 Example RTMDISK EXEC with
Page 31 and 32: 6.1.2.4.2 Example 2I5798DWD Please
Page 33 and 34: Enter the minidisk address to insta
Page 35 and 36: The RTM VM/ESA build process requir
Page 37 and 38: The first automatic display will oc
Page 39 and 40: 6.2.4 Customizing the SystemTwo sam
Page 41: 6.3 Building RTM VM/ESA For Multipl
Page 45 and 46: The following is an example of the
Page 47 and 48: ST:VMFBLD1851I Reading build listsS
Page 49 and 50: ACCESS 4 E/ESENDFILE VMC MODULE E T
Page 51 and 52: 5. COPYFILE all the AUXRTM5 files t
Page 53 and 54: Appendix A. Applying Local Modifica
Page 55 and 56: Appendix B. Sample output from BUIL
Page 57 and 58: VMFMLB2219I Processing object RTMVM
Page 59 and 60: VMFASM197I Assembling RTMDSLVMFASM2
Page 61 and 62: VMFASM197I Assembling RTMSDAVMFASM2
Page 63 and 64: Appendix C. Sample non-VMSES/E inst
Page 65 and 66: All the RTM VM/ESA product files ha
Page 67 and 68: DMSUPD178I Updating RTMTRACE MACRO
Page 69 and 70: The following is the list of maclib
Page 71 and 72: DMSUPD178I Applying RTMDSW F516RM F
Page 73 and 74: VMFASM257I RTMUSR TEXT created on y
Page 75 and 76: Ready; T=.1/.1 18:5:42rew 181Rewind
Page 77 and 78: Ready; T=.1/.1 13:36:57rew 181Rewin
Page 79 and 80: RTMIOP AUM2188 B1RTMIOP AUM2158 B1R
Page 81 and 82: RENAME RTMDSU AUM23 B = AUXRTM5 =ER
Page 83 and 84: D.3 Build of RTM VM/ESAAt this poin
Page 85 and 86: DMSUPD181E No update files were fou
Page 87 and 88: The following is the list of maclib
Page 89 and 90: VMFASM276I VMFHASM processing compl
Page 91 and 92: DMSUPD178I Updating RTMSYS ASSEMBLE
Page 93 and 94:
Reader's CommentsRealtime Monitor V
Page 96:
IBMProgram Number: 5798-DWD 5891589
show all

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

Create successful ePaper yourself

Delete template?

Save as template?