IBM TIVOLI ADSTAR 5697-VM3 - Manual (Page 15)

If you choose to install Tivoli ADSM for VM on a common user ID the default minidisk addresses
for Tivoli ADSM for VM may already be defined. If any of the default minidisks required by Tivoli
ADSM for VM are already in use you will have to create an override to change the default
minidisks for Tivoli ADSM for VM so they are unique.
Figure 8 (Page 1 of 2). DASD Storage Requirements for Target Minidisks
Minidisk
owner
(user ID)
Default
Address
Storage in
Cylinders
FB-512
Blocks SFS 4K
Blocks
Usage
DASD CYLS Default SFS Directory Name
5654A09A 2B2 3390
3380
9345 25
30
30 36000 4500 Contains all the base code shipped with
Tivoli ADSM for VM
VMSYS:5654A09A.ADSM.OBJECT
5654A09A 2D2 3390
3380
9345 90
108
108
129600 16200 Contains serviced files
VMSYS:5654A09A.ADSM.DELTA
5654A09A 2A6 3390
3380
9345 2
2
2 2400 300 Contains AUX files and software
inventory tables that represent the
test service level of Tivoli ADSM for VM
VMSYS:5654A09A.ADSM.APPLYALT
5654A09A 2A2 3390
3380
9345 2
2
2 2400 300 Contains AUX files and software
inventory tables that represent the
service level of Tivoli ADSM for VM
that is currently in production.
VMSYS:5654A09A.ADSM.APPLYPROD
5654A09A 491 3390
3380
9345 45
54
54 64800 8100 This is the production disk. All the files
needed by the ADSM Server and the CMS
Admin client will exist in this disk.
SFS directory not recommended.
(1*)
Notes:
1. An SFS directory SHOULD NOT be used for the production disk or the test build disk to avoid suspension of
the ADSM server. The message repository, which is read as needed by the server, will reside on these disks.
By placing the message repository in an SFS directory the ADSM Server can be suspended while the SFS
Server satisfies a read request when a message text is needed.
2. Cylinder values defined in this table are based on a 4K block size. FB-512 block and SFS values are derived
from the 3380 cylinder values in this table. The FBA blocks are listed as 1/2K but should be CMS formatted
at 1K size. 37,650 4K blocks are needed for SFS install.
3. The list of DASD in this figure does not show all devices supported by VM/ESA and you are not limited to only
these devices when installing the Tivoli ADSM for VM program product. To determine the amount of space
needed on a device not listed but supported by VM/ESA, start with the value in the "SFS 4K Blocks" column.
Installation Requirements and Considerations
11