Build New Levels
The build task generates the serviced level of an object and places the new object on a test BUILD disk.
Place the New Service into Production
Once the service is satisfactorily tested it is ready to put into production by copying the new service to the production disk.
7.2 Servicing Tivoli ADSM for VM
RSU Warning
If applying a Tivoli ADSM for VM RSU go to the instructions in Appendix A, “Applying an RSU Tape for Tivoli ADSM for VM” on page 36. You will return to a step in this chapter as specified in that appendix.
7.2.1 Prepare to Receive Service
The ppfname used throughout these servicing instructions is 5654A09A, which assumes you are using the PPF supplied by IBM for Tivoli ADSM for VM. If you have your own PPF override file for Tivoli ADSM for VM, you should use your file's ppfname instead of 5654A09A. The ppfname you selected should be used throughout the rest of this procedure, unless otherwise stated differently.
link MAINT 51d 51d mr access 51d d
1
2 If the Software Inventory disk (51D) was accessed R/O (read only) then establish write access to the Software Inventory disk.
Note: If the MAINT 51D minidisk was accessed R/O, you will need to have the user that has it accessed R/W link it R/O. You then can issue the following commands to obtain R/W access to it.
The 51D minidisk is where the VMSES/E Software Inventory files and other product dependent files reside.
3 Have the Tivoli ADSM for VM CORrective service tape mounted and attached to 5654A09A.
4 Establish the correct minidisk access order.
vmfsetup 5654A09A {ADSM ADSMSFS}
28Tivoli ADSM for VM Program Directory
