Page of GC20-1819-2 As Updated April 1, 1981 by TNL add records to the file, as you would if you are creating a new file,
issue the EDIT subcommand:
input
to enter input mode. Every line that you enter is considered a data line
to be into the disk file. For most filetypes, the editor
translates all of your input data to uppercase characters, regardless of
how you enter it. For example, if you create a file and enter input
mode as follows:
edit myfile test NEW FILE:
EDIT:
input INPUT: This is a file I am
learninq to create with the CMS editor.
the lines are written into the file as: THIS IS A FILE I AM LEARNING TO CREATE WITH THE eMS EDITOR. You can use the VM/370 logical line editing symbols to modify data
lines as you enter them.
To return to edit mode to modify a file or to terminate the edit
session, you must press the Return key on a null line. If you have just
entered a data line, for example, and your terminal's typing element or
cursor is positioned at the last character you entered, you must press
the Return key once to enter the data line, and a second time to enter a
null line. You may also use the logical line end symbol to enter a null line;
for example:
last line of input#
#
Both of these lines cause you to return to edit mode from input mode.
If you do not enter a null line, but enter an EDIT sUbcommand or CMS command, the command line 1S written into your file as input. The only
exception to this is a line that begins with the characters #CP. These
characters indicate that the command is to be passed immediately to CP for processinq.
Althouqh you can interrupt the CMS editor when it is processing
input, be wary of stacking unwanted subcommands or null lines. If you
should hit either the attention or enter key while the editor is
running, processing will stop and any lines subsequently entered (except
for CMS Immediate commands) will be stacked in a console buffer. CMS processes these stacked lines when it is finished processing the current
in put. (See the topic "virtual Machine Inter ruptions" for further
r.elevant information.)
62 IBM VM/370 CMS User's Guide
Paqe of GC20-1819-2 'S Updated April 1, 1981 by TNL GN25-0826 WRITING A FILE ONTO DISK A file you create and the modifications that you make to eiit session are not automatically written to a disk file.
results, yaa can do the followinq:
it during an
To save the • issue the subcommand:
save
to write onto disk the contents of the file
issue the subcommand. Periodically issuinq your data against a system failure;
chanqes you make are not lost.
as it exists when you
this EDIT subcommand
you can be sure that Section 5. The C!S Editor 62.1
Previous Page Next Page