Appendix C. Moving Tivoli ADSM for VM to SFS Directories and Creating PPF Override
This appendix describes how to move Tivoli ADSM for VM into shared file (SFS) if it was not installed into SFS at initial install time. It also gives sample instructions on creating a PPF (Product Parameter File) override.
By default, Tivoli ADSM for VM is installed to minidisks, as part of the VM/ESA Version 2 Release 4.0 System DDR; unless you choose to move Tivoli ADSM for VM to SFS during the initial VM/ESA 2.4.0 install. If you prefer to use SFS, you can move the Tivoli ADSM for VM service minidisks to SFS directories. Refer to the figure Figure 8 on page 11 to see which minidisks can reside in SFS. You can use either the default VMSYS file pool or a file pool of your choosing.
A summary of the steps that are needed to place Tivoli ADSM for VM into SFS are:
Allocate space in the
Provide the installation user ID, 5654A09A, access to the file pool
Create the necessary Tivoli ADSM for VM subdirectories
Copy files from the minidisks to the new SFS subdirectories
Create a PPF override, if not using the default file pool or subdirectory names.
Where to next
You need to do one of the following:
If you want to place Tivoli ADSM for VM into SFS directories using the defaults defined in the 5654A09A PPF file you need to continue with the instructions provided in the VM/ESA Installation Guide, in the Appendix titled &sfq.Moving Components to SFS Directories".
If you want to place Tivoli ADSM for VM into your own
If you need to just create a PPF override, continue with the instructions in C.3, “Create Product Parameter File (PPF) Override” on page 48.
After you have chosen one of the previous options and completed the steps required (whether in this appendix or in the VM/ESA Installation Guide) you need to return to the section that pointed you to this appendix and continue from there (if you were pointed to this appendix).
C.1 Setup SFS File Pool and Directories
Copyright IBM Corp. 1992, 1999 | 45 |
