Subcommand Format
TABSet nl [n2 ••• nn] TOP r , TRUNC , n I I * I L .J r r , ,
Type I m I n I I I 1 I * I I I * I I I L L .J .J r , Up I n I I 1 I L .J r Verify ION , I rr , , Iistartcollendcoll 10FFI " 1 I * I L .J LL .J .J r , Isubcommandl I n I I 1 I L .J r r , ,
Zone I m I n I I I 1 I * I I I * I I I L L .J .J 1 { nnnnn } [text]
nnnnnnnn r , $DUP I n I I 1 I L .J $MOVE n
{ up • } Down m TO label
Function ISets logical tab stops. ,Moves the current line pointer Ito the null line at the top lof the file. ISets or displays the column of
Itruncation. An asterisk (*) lindicates the logical record
Ilength • IDisplays lines beginning Iwith the current line. Each Iline may be truncated to Icharacters. I IMoves the current line pointer Itoward the top of the file. I I ISets, displays, or resets
Iverification. An asterisk (*) lindicates the logical record Ilength. IAssigns to X or Y the given IEDIT subcommand or executes Ithe previously assigned Isubcommand times. I ISets or displays the columns
Ibetween which editing is to Itake place. I I IDisplays the last EDIT
Isubcommand, except = or 1. ILocates the line specified by Ithe given line number and linserts text, if given.
IDuplicates the current line Itimes. $DUP is an edit macro. I , IMoves uF lines or down! Ilines. $MOVE is an edit macro. I Figure 7. Summary of EDIT Subcommands and Macros (Part 4 of 4)
94 IBM VM/370 CMS User's Guide

Section 6. Introduction to the EXEC Processor
An EXEC is a CMS file that contains executable statements. The
statements may be CMS or CP commands or EXEC control statements. The
execution can be conditionally controlled with additional EXEC statements, or it may contain no EXEC statements at all. In its simplest
form, an EXEC file may contain only one record, have no variables, and
expect no arguments to be passed to it. In its most complex form, it can
contain thousands of records and may resemble a program written in a
high-level programming language. As a CMS user, you should become
familiar with the EXEC processor and use it often to tailor CMS commands
to your own needs, as well as to create your own commands.
The following is an example of a simple EXEC procedure that might be
named RDLINKS EXEC: CP LINK DEWEY 191 291 RR DEWEY CP LINK LIBRARY 192 292 RR DEWEY ACCESS 291 BIA ACC 292 CIA When you enter:
rdlinks
each command line contained in the file RDLINKS EXEC is executed. You could also create an EXEC procedure that functions like a
cataloged procedure, and set it up to receive an argument, so that it
executes somewhat differently each time you invcke it. For example, a
file named ASM EXEC contains the following: ASSEMBLE &1 PRINT &1 LISTING LOAD &1 START If you invoke the EXEC specifying the name of an assembler language
source such as:
asm myprog
the procedure executes as follows: ASSEMBLE MYPROG PRINT MYPROG LISTING LOAD MYPROG START The variable &1 in the EXEC file is substituted with the argument you
enter when you execute the EXEC. As many as 30 arguments can be passed
to an EXEC in this manner; the variables thus set range fro. &1 through
&30.
CREATING EXEC FILES EXEC files can be created with the CMS editor, ty punching cards, or by
using CMS commands or programs. When you create a file with the editor, Section 6. Introduction to the EXEC Processor 95