Figure 8 (Page 2 of 2). DASD Storage Requirements for Target Minidisks
Minidisk |
| Storage in |
|
|
| ||
| Cylinders |
|
| Usage | |||
owner | Default | SFS 4K | |||||
|
|
| |||||
(user ID) | Address | DASD | CYLS | Blocks | Blocks | Default SFS Directory Name | |
|
|
|
|
|
|
| |
5654A09A | 4E2 | 3390 | 45 | 64800 | 8100 | This is the test build disk which will | |
|
| 3380 | 54 |
|
| contain the production files after the | |
|
| 9345 | 54 |
|
| service process completes. Once | |
|
|
|
|
|
| testing is complete, files must be copied | |
|
|
|
|
|
| to the production disk. | |
|
|
|
|
|
| SFS directory not recommended. (1*) | |
5654A09A | 191 | 3390 | 1 | 1200 | 150 | 5654A09A user ID's 191 minidisk | |
|
| 3380 | 1 |
|
|
| |
|
| 9345 | 1 |
|
| 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.
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.