MCOMP and MCONV – Compiling Message Repositories

Read syntax diagramSkip visual syntax diagram MCOMPMCONV repos DMTVMcontrol(Options
Options
Read syntax diagramSkip visual syntax diagramOUTMODEA1OUTMODEfmKEEPListNOKEEPListNOKEEPAsmKEEPAsmASMxfHASMHLASM

Purpose

RSCS supplies two execs to compile the message repositories. The MCONV exec compiles the conversion repository (see Conversion Repository). The MCOMP exec compiles the translation repository (see Translation Repository).

Parameters

repos
is the file name of the repository to be compiled. The file type differs for each repository; the standard search order determines the file mode.

For translation repositories, the file type must be MSGS. The translation repository supplied with RSCS is DMTAMENG MSGS.

For conversion repositories, the file type must be MCONV. The conversion repository supplied with RSCS is DMTMGC MCONV.

control
is the file name of the control file used to apply updates to the repository. The default is DMTVM. The file type of the control file is CNTRL. The standard search order determines the file mode.
OUTMODE fm
specifies the file mode where the resulting TEXT deck is placed. The default value is A1.
KEEPList
NOKEEPList
specifies whether the compiler listing is kept. The default is KEEPLIST.
NOKEEPAsm
KEEPAsm
specifies whether the intermediate assembler source code is kept. The default is NOKEEPASM. If an error occurs while assembling, however, the source is kept on the disk. You can then reassemble the source code for diagnostic purposes.
ASMxf
HASM
HLASM
specifies the assembler used to assemble the source code. The default is the ASMXF assembler.

Usage Notes

  1. If you modify a message repository supplied with RSCS (DMTAMENG MSGS or DMTMGC MCONV) or create other repositories, take these steps:
    1. Issue MCOMP and MCONV to compile the source file for the appropriate repository into a TEXT deck.
    2. Rebuild the RSCS load library to include the new TEXT deck.
    3. Re-IPL RSCS to access the message repository.
  2. Each compiler exec must have access to a read/write file mode A. This file mode holds intermediate work files, including:
    • Work files used by the CMS UPDATE command
    • Updated source
    • Compiler listing
    • Intermediate assembler code
    • Text deck, before it is copied to the output file mode
  3. RSCS provides the MCOMP and MCONV execs in source and compiled form. The source form of the execs have the file type EXEC; the compiled form have the file type CEXEC.

    The execs are installed on the 400 minidisk, which is owned by the RSCS installation user ID. If you want to use the compiled form of the execs, copy and rename the CEXEC files to EXEC files on the 400 disk.

    If you have REXX compiler support at your installation, IBM recommends you use the compiled form of the execs.

  4. For every 100 lines processed in a message repository, each exec issues a progress message.
  5. z/VM: RSCS Networking Messages and Codes contains the messages that are issued by the RSCS message compilers.