ESERV 7. When you use the ESERV control statements PUNCH or DSPCH, the ESERV program may generate CATAL.S, END, or 1* records in the output
file. When vou add a MACRO file containing these statements to a CKS macro library using the MACLIB command, the statements are
ignored and are not read into the MACLIB member.
None. The ready message indicates that the ESERV program completed
execution successfully. You may examine the SYSLST output to verify the
results of the ESERV program execution. DMSERV001E NO FILENAME SPECIFIED RC=24 DMSERV002E FILE 'fn ESERV' NOT FOUND RC=28 DMSERV006E NO READ 1 WRITE DISK ACCESSED RC=36 DMSERV027E INVALID DEVICE' device' FOR SYSxxx RC=28 DMSERV037E DISK 'mode' IS READ ONLY RC=36 DMSERV010E INVALID ARGUMENT ' argument' RC=24 DMSERVOQ9E CMS/DOS ENVIRONMENT NOT ACTIVE RC=40 The ESERV EXEC calls other CMS commands to perform certain
functions, and so vou may, on occasion, receive error messages that
occur as a result of those commands. Non-eMS error messages produced by the DOS/VS ESERV program are
described in the iQ 1he 84 IBM VM/370 CMS Command and Macro Reference

EXEC EXEC Use the command to execute one or more CMS commands or EXEC control
statements contained in a specified EXEC file. The format of the EXEC command is:
r
fn [args ••• ] I L- ____________ . ________ -J [EXec] indicates that the EXEC command may be omitted if you are
executing the EXEC procedure from the CMS command environment
and have not issued the command SET IMPEX OFF. fn is the filename of a file containing one or more CMS commands
and/or EXEC control statements to be executed. The filetype of
the file must be EXEC and the file can have either fixed-or
variable-length records with a logical record length not
exceeding 130 characters. EXEC files can be created with the
EDIT command or by a user program. EXEC files created by the CMS editor have, by default, variable-length, 80-character
records.
args are any arguments you wish to pass to the EXEC. The arguments
are assigned to the special variables &1 through &30 in the
order in which they appear in the argument list.
"Section 5. EXEC Control statements" contains complete descriptions
of EXEC control statements, special variables, and built-in functions.
For information on designing EXEC procedures and examples of control
word usage, see the User'§ Guigg. The amount of information displayed during the execution of an
depends on the setting of the &CONTROL control statement, which
default displays all eMS commands, responses, and error messages.
addition, it displays nonzero return codes from CMS in the format:
+++ R(nnnnn) +++
where nnnnn is the return code from the CMS command. EXEC by
In
For jetails, see the description of the &CONTROL control statement in
"Section 5. EIEC Control Statements." Section 2. CMS Commands 85