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

More documents

Recommendations

Info

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
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: 6.1.2.2 Pre-installation instructio
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 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?