Although CA VM:Director does not allow anyone to move minidisks that are in use read/write, you can move minidisks that are not in use or that are in use read‑only, if you are authorized to do so.
If you need to move a minidisk, check first that no one is linked to the minidisk or that they are linked read–only.
Note: For more information, see Checking Active Links.
When you find who those users are, ask them to detach their links with the CP DETACH command.
When the links are removed, you can move the minidisk.
Note: When you move a minidisk that a user has linked read–only, CA VM:Director holds the space the minidisk occupies until you use the RECLAIM command against the minidisk. CA VM:Director maintains the minidisk by redefining it to the CA VM:Director directory entry with a virtual address in the range 600 to 6FF. For more information, see RECLAIM Command in the Reference Guide.
If your site is not using the Servant Facility and the minidisk you are moving is to remain the same size, blocking factor, and device type, your user ID must have access to the minidisk where the CMS DDR module resides.
To move a minidisk
vmdirect manage manager 6 185
The Move a Minidisk screen appears as follows:
MAN000B0 Move a Minidisk VM:Director ------------------------------------------------------------------------------ Userid: USERID Minidisk Address: 192 Device Type: 3390 Volume: VST020 Minidisk Location: 1303 Minidisk Size: 1 Label: DSK192 Utilization: 04% Number of Files: 0 + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + | | | Subpool: MAIN Device type: Size: | | | | Volume: Location: | | | + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + Enter information only in the fields you wish to change. -------------------------------------------------------------------------------- PA1: Cancel PF1: Help PF3: Quit PF10: Print PF12: End
To reallocate the minidisk according to the definition of another subpool you are authorized to use, type that subpool name.
To make the minidisk size some number of 512-byte blocks on any device type, enter an asterisk in the Type field.
To leave the minidisk allocated on its current device type, leave this field blank.
You can specify the size in either of two ways, which are explained in Step 3.
To leave the size of the minidisk unchanged, leave the Size field blank.
To allocate the minidisk from a volume according to the subpool, leave this field blank.
If there are problems with any of the values you entered, CA VM:Director returns you to that screen where you can correct the problems.
If all entries on this screen are valid, CA VM:Director displays the Format a Minidisk screen. This screen contains the minidisk specification you just entered and a default block size and label for the new minidisk.
Check the minidisk’s current block size with the new device type you assigned to it so that you can optimize the block size. For example, one cylinder of a 3380 DASD formatted with 512–byte blocks holds approximately 345K. If formatted with 4096–byte blocks, its capacity increases to 600K.
You can also change a minidisk by answering screen prompts. To do so, follow these steps:
vmdirect maint manage user45 diskmove 1A0
You can also change a minidisk by using the CA VM:Director CHGMDISK command. This command allows you to specify more parameters. For example, to change the PHEFR09 1A0 disk from 500KB on a 3380 to 2 MB on a 3390, enter the following command:
vmdirect chgmdisk phefr09 1a0 2M 3390
Note: For more information about additional parameters, see theCHGMDISK command in the Reference Guide.
|
Copyright © 2014 CA.
All rights reserved.
|
|