|
|
|
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 © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |