ESERV

Authorization

General User

Purpose

Use the ESERV EXEC procedure in CMS/DOS to copy edited VSE macros from system or private source statement E sublibraries to CMS files, or to list de-edited macros.

Operands

fn

specifies the file name of the CMS file that contains the ESERV control statements; it must have a file type of ESERV. The logical unit SYSIPT must be assigned to the disk or directory on which the ESERV file resides. The file name is the fn of the LISTING and MACRO files produced by the ESERV program.

Usage Notes

1. The input file can contain any or all of the ESERV control statements as defined in Guide to the DOS/VSE Assembler.
2. You must have a read/write disk or directory accessed as A when you use the ESERV command.
3. To copy macros from the system source statement library, you must have entered the CMS/DOS environment specifying the mode letter of the VSE system residence. To copy from a private source statement library, you must assign the logical unit SYSSLB and issue a DLBL command for the ddname IJSYSSL.
4. The output of the ESERV program is directed (as in VSE/AF) to devices assigned to the logical units SYSLST and SYSPCH. If either SYSLST or SYSPCH is not assigned, the following files are created:

   Unit

   Output File

   SYSLST

   fn LISTING mode

   SYSPCH

   fn MACRO mode

   where mode is the mode letter of the disk or directory on which the source file, fn ESERV, resides. If fn ESERV is on a read-only disk or directory, the files are written to your disk or directory accessed as A.

   You can override default assignments made by the ESERV EXEC, if you assign:

   • SYSIPT to TAPE or READER, the source statements are read from that device.
   • SYSLST or SYSPCH to another device, the SYSLST or SYSPCH files are written to that device.
5. The ESERV EXEC procedure clears all DLBL definitions, except those entered with the PERM option.
6. When you use the ESERV control statements PUNCH or DSPCH, the ESERV program may generate CATAL.S, END, or /* records in the output file. When you add a MACRO file containing these statements to a CMS macro library using the MACLIB command, the statements are ignored and are not read into the MACLIB member.
7. If you want to issue ESERV from an exec program, you should precede it with the EXEC command; that is, specify

   exec eserv

8. If a MACRO or LISTING file with the specified file name exists before the ESERV command is issued, the file(s) are renamed:
   • fn CMSUT1 for the MACRO file
   • fn CMSUT2 for the LISTING file

   This preserves the original file authorities. If an error occurs these temporary files may be left on your disk or directory. You may want to rename them to your original MACRO or LISTING file.

   File authorities are not maintained if you specify a DLBL with a file type other than MACRO or LISTING for the output macro or listing files.

Responses

None.

The CMS ready message indicates the ESERV program completed execution successfully. You may examine the SYSLST output to verify the results of the ESERV program execution.

Messages and Return Codes

• DMS001E No filename specified. [RC=24]
• DMS002E File fn ESERV not found. [RC=28]
• DMS006E No read / write filemode accessed. [RC=36]
• DMS027E Invalid devicedevtype for SYSaaa [RC=24]
• DMS037E Filemode mode is read only. [RC=36]
• DMS070E Invalid argument argument [RC=24]
• DMS099E CMS/DOS environment not active. [RC=40]

For more information on the non-CMS error messages produced by the VSE ESERV program, see Guide to the DOS/VSE Assembler.