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

Figure 8 (Page 2 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 4E2 3390
3380
9345 45
54
54 64800 8100 This is the test build disk which will
contain the production files after the
service process completes. Once
testing is complete, files must be copied
to the production disk.
SFS directory not recommended.
(1*)
5654A09A 191 3390
3380
9345 1
1
1 1200 150 5654A09A user ID's 191 minidisk
VMSYS:5654A09A.
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.
12
Tivoli ADSM for VM Program Directory