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

More documents

Recommendations

Info

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
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 and 42: 6.3 Building RTM VM/ESA For Multipl
Page 43 and 44: Once the service is satisfactorily
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: 5. COPYFILE all the AUXRTM5 files t
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

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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?