want to make to the data. To copy files
GETFILE subcommand.Using the file TEST
enter:
edit test1 file
getfile test file a 1250 file
edit test2 file
getfile test file a 251250 with the editor, you use the
FILE as an example, you might
Again, you could erase the original TEST FILE when you are through with
your edit session.When you enter a FILE or SAVE subcommand or when an automatic save
request is issued, the editor writes a copy of the file you are editing
onto disk, and names it EDITCMSUT1. If this causes the disk to become
full, you receive the message:DMSBWR170S DISK 'mode(cuu)' IS FULL The editor erases the workfile, and issues the message:
SETNEW FILEMODE, OR ENTER CMS SUBSET AND CLEAR SOME SPACE
The original file (as last written onto disk) remains unchanged.You can use the CMS subcommand to enter CMS subset, and erase any files that
you do not need.You can use the LISTFILE command to list the files on
the disk, then the ERASE command to erase the unwanted files.
If you cannot erase any of the files on the disk, there are several
alternate recovery paths you can take:
1. If you have another read/write disk accessed, you can use theF80DE subcommand to change the filemode of the file, so that when you
file it, it is written to the other disk. If you have a read/write
disk that is not accessed, you can access it inCMS subset. After
filing the file on the second disk, erase the original copy, and
then use theCOPYFILE command to transfer the file back to its
original disk.
2. If you do not have any other read/write disk in your virtual
machine, youmay be able to transfer some of your files to another
user, using thePUNCH or DISK DUMP commands in CMS subset. When the
files have been read onto the other user's disk, you can erase them
from your disk. Then, return to edit mode and issue the FILE
subcommand.
3. InCMS subset, erase the original disk file (if it existed), then
return to edit mode and file the copy that you are editing.You should not use this method unless absolutely necessary, since any
unexpected problems may result in the loss of both the disk file
and the copy.
After you use the FILE subcommand to write the file onto disk, you
should continue erasing any files you no longer need.90 IBM VM/370 CMS User's Guide
GETFILE subcommand.
enter:
edit test1 file
getfile test file a 1
edit test2 file
getfile test file a 251
FILE as an example, you might
Again, you could erase the original TEST FILE when you are through with
your edit session.
request is issued, the editor writes a copy of the file you are editing
onto disk, and names it EDIT
full, you receive the message:
SET
The original file (as last written onto disk) remains unchanged.
you do not need.
the disk, then the ERASE command to erase the unwanted files.
If you cannot erase any of the files on the disk, there are several
alternate recovery paths you can take:
1. If you have another read/write disk accessed, you can use the
file it, it is written to the other disk. If you have a read/write
disk that is not accessed, you can access it in
filing the file on the second disk, erase the original copy, and
then use the
original disk.
2. If you do not have any other read/write disk in your virtual
machine, you
user, using the
files have been read onto the other user's disk, you can erase them
from your disk. Then, return to edit mode and issue the FILE
subcommand.
3. In
return to edit mode and file the copy that you are editing.
unexpected problems may result in the loss of both the disk file
and the copy.
After you use the FILE subcommand to write the file onto disk, you
should continue erasing any files you no longer need.