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

More documents

Recommendations

Info

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
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: 6.2.4 Customizing the SystemTwo sam
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 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

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

Delete template?

Save as template?