The MOVE2SFS command copies data from a minidisk to an SFS file space.
MOVE2SFS userid [vaddr] [("Options"]
Options:
[DELete] [IPLstmt] [POOL ["Poolparms"]] Poolparms:
{filepool | *} [{storgroup | *} [blocks | ADDSPACE | USESPACE ]]
Note: Options can be entered in any order.
You must be the SFS manager for the user ID and you must be authorized to allocate space in the affected file pools, or you must be an SFS administrator.
Specifies the name of a user ID owning data you want to copy to SFS.
Specifies the virtual address of a single minidisk containing data you want to copy to SFS. If you do not specify vaddr, CA VM:Secure copies the data from all the user minidisks to SFS.
Deletes the user minidisks after copying their data. For minidisks on packs that are under CA VM:Secure control, this command also deletes links to the deleted minidisks from the directory.
Updates the user directory entry so that the target file pool is active at user ID logon. If a sample profile is available or specified on a *SP= special comment in the directory entry, that profile is copied to the top‑level directory for the user as PROFILE EXEC. If there is already a PROFILE EXEC file in the user’s top‑level directory, a sample profile specified on a *SP= special comment is not copied.
Specifies the file pool and user storage group to which to copy the data, and indicates the space to use for the copied data.
The file pool and user storage group must already be defined to CA VM:Secure. The defaults for filepool, storgroup, and blocks are the default enrollment values for the user’s SFS manager as specified in the SFS configuration.
blocks specifies the number of 4K blocks to allocate to the user ID and in which to copy the data. If the user ID already has a file space, the number of blocks is added to the existing file space.
ADDSPACE tells CA VM:Secure to add as much space as needed, in 4K blocks, to the user ID’s file space to accommodate the data. If the user ID is not yet enrolled in SFS, ADDSPACE gives the user ID just enough space for the copied data.
USESPACE tells CA VM:Secure to copy the data to a file space the user already has. If the data needs more space than is available or the user is not yet enrolled in SFS, the command fails.
If you specify POOL as the last option on the MOVE2SFS command, you can specify it without parameters and get the default enrollment values.
The MOVE2SFS command lets you copy user data from minidisks to directories in an SFS file space.
The MOVE2SFS command creates one directory for the contents of each minidisk it copies. Default directory names are MDSKvaddr, where vaddr is the virtual address of the minidisk from which the data is copied. For example, data on a minidisk at virtual address 0536 is copied to SFS directory MDSK0536.
The MOVE2SFS command uses the PREMOVE and the POSTMOVE user exits in its processing. You can use the PREMOVE user exit to name these destination directories yourself if you have your own directory naming scheme. The POSTMOVE user exit manipulates data that has been moved from minidisks to SFS.
The MOVE2SFS command does not fully copy certain types of minidisks to SFS. The following table explains how MOVE2SFS proceeds when it detects each type of minidisk.
|
For this type of minidisk |
MOVE2SFS does this |
|---|---|
|
Reserved or SAVEFD |
Sends you warning messages and does not copy the data from the minidisk to SFS |
|
Recomputed |
Sends you warning messages and copies only data from the CMS‑formatted portion of the minidisk to SFS |
Example
User NORMP has data on 191 and 192 minidisks. To move NORMP’s data from the existing minidisks to subdirectories under the USERS:NORMP file space, and to enroll NORMP in the USERS file pool using storage group 2, enter:
vmsecure move2sfs normp ( ipl pool users 2 addspace
The data is moved to default directory names MDSK0191 and MDSK0192.
If the PREMOVE user exit is implemented, the directory name is provided by the user exit. You can code the PREMOVE user exit to recognize the 191 virtual address and to stack a null line for its directory name. This causes the top‑level directory to be used instead of a subdirectory when copying the data from the 191 minidisk.
Note:
|
Copyright © 2014 CA.
All rights reserved.
|
|