stack execute before a read request is presented to the terminal. When you enter mUltiple equal signs, the subcommand is stacked once for each
equal sign you enter. You can also stack an additional EDIT subcommand following an equal
sign. The subcommand line is also stacked, but it is stacked LIFO (last-in, first-out) so that it executes before the stacked subcommand.
For example, if you enter:
delete
= next
a DELETE subcommand is executed, then a DELETE subcommand is stacked,
and a NEXT subcommand is stacked in front of it. Then the stacked lines
are read in and executed. The above sequence has the same effect as if
you enter:
delete
next
delete
In addition to stacking the last
find out what it was, using the?
enter:
subcommand executed, you can also
subcommand. For example, if you
next 10 ?
the editor displays: NEXT 10 Since the subcommand line NEXT 10 you enter an = subcommand, it is
subcommand.
was the last subcommand entered, if
executed again. You cannot stack a ? !Qte: The ? subcommand,
subcommand into the user
re-entering it.
on a display terminal,
input area, where you
copies the
may modify
last EDIT
it before WHAT TO DO WHEN YOU RUN OUT OF SPACE There are two situations that may prevent you from continuing an edit
session or from writing a file onto disk. You should be aware of these
situations, know how to avoid them, and how to recover from them, should
they occur. When you issue the EDIT command to edit a file, the editor copies the
file into virtual storage. If it is a large file, or you have made many
additions to it, the editor may run out of storage space. If it does, it
issues the message:
AVAILABLE STORAGE IS NOW FULL When this happens, you cannot make any
unless you first delete some lines. If
editor issues the message: NO ROOM changes or additions to the file
you attempt to add a line, the
If you were entering data in input mode, your virtual machine is
returned to edit mode, and you may receive the message:
88 IBM VM/370 CMS User's Guide

STACKED LINES CLEARED
which indicates that any additional lines you entered are cleared and will not be processed. You should use the FILE subcommand to write the file onto disk. If
you want to continue editing, you should see that the editor has more
storage space to work with. To do this, you can find out how large your
virtual machine is and then increase its size. To find out the size,
issue the CP QUERY command:
cp query virtual storage
If the response is: STORAGE = 256K You might want to redefine your storage to 512K. Use the CP command
DEFINE, as follows:
cp define storage 512k
This command resets your virtual machine, and you must issue the CP IPL command to reload the CMS system before you can continue editing.
If a file is very large, the editor may allow you to edit it using the EDIT command. DMSEDI132S FILE 'fn ft fm' TOO LARGE
not have enough
The message: space to
indicates that you must obtain more storage space before you can edit
the file. If this is the case, or if you are editing large files, you
should redefine your storage before beginning the terminal session. If
this happens consistently, you should see your installation support
personnel about having the directory entry for your userid updated so
that you have a large storage size to begin with.
If the file you are editing is too large, and the data it contains does
not have to be in one file, you can split the file into smaller files,
so that it is easier to work with. Two of the methods you can use to do
this are described below. Command: You can use the COPY FILE command to copy
portions of a file Into-separate files, and then delete the copied lines
from the original file. For example, if you have a file named TEST FILE
that has 1000 records, and you want to split it into four files, you
could enter:
copy file test file a test1 file a (from 1 for 250 copy file test file a test2 file a (from 251 for 250 copyfile test file a test3 file a (from 501 for 250 copyfile test file a test4 file a (from 751 for 250 When these COPYFILE commands are complete, you have four files
containing the information from the original TEST FILE, which you can
erase:
erase test file Edi12E: If you use the editor to create smaller files, you can
edit them as you copy them, that is, if you have other changes that you Section 5. The CMS Editor 89