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

More documents

Recommendations

Info

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
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: ACCESS VMSYS:5798DWDC.TBUILD EACCES
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 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?