April 1, 1981 CMSGEND CMSGEND Use the CMSGEND EXEC procedure to generate a new CMS module from a text
file and place the new eMS module on the A-disk.
The format of the CMSGEND EXEC command is:
r I I CMSGEND I I I I I fn CTLCMS CTLALL NOCLEAR ,
r
,
fn I CTLCMS I I CTLALL I I NOCLEAR I I MAP I I NOINV I L J is the filename of the CMS module that is to
the CMSGEND EXEC. Only one filename may be CMSGEND command line.
be generated by
specified in the
The filenames that may be specified in the CMSGEND command are
any disk-resident CMS commands and service proqrams. You can also use the CMSGEND EXEC to regenerate the ASSEMBLE command when you move the CMS system disk. When you specify ASSEMBLE, CMSGEND prompts you to enter a disk mode
letter so it can refresh the assembler's auxiliary directory. Use the ASMGEND EXEC procedure if you are updating the
assembler.
displays each CMS command EXEC procedure. This is &CONTROL CMS. displays every executable CMSGEND EXEC procedure.
statement &CONTROL ALL= as it is
equivalent
executed in the CMSGEND to the EXEC statement
statement as it is executed in the
This is equivalent to the EXEC specifies that the CLEAR option is not to be issued when CMSGEND invokes the LOAD command. MAP specifies that the NOMAP option is not to be issued when CMSGEND invokes the GENMOD command. NOINV issues the NOINV option when CMSGEND invokes the LOAD command;
this suppresses the displaying of invalid cards at the
terminal. If the text deck was created with the VMFASM EXEC, it may contain update listing information; these records are
displayed during the loading process unless you specify NOINV. CMSGEND keeps a list of the eMS disk-resident modules, the filenames of
the text files used to create them, and any special attributes required
to qenerate them. For example, the RELEASE command must be generated Part 5. Updating VM/370 377

Ii p.L..L.L I, I :7 0 , CMSGEND with the ORIGIN TRANS and the SYSTEM options. It is composed of the
text files DMSARE and DMSALU. To generate a new RELEASE module, you
issue:
cmsgend release
you may receive messages such as the following:
*** CURRENT STATUS: FILE ' RELEASE MODULE A2' EXISTS FILE' RELEASE MODOLD A1' DOES NOT EXIST *** LOADING: INVALID CARD - X9999DMS - (PTF description) DMSARE SD OOEOOO DMSALU SD OOE3B8 RELUFD OOE3B8 S0R'!'FS'!' 00EE 25 END$RELU OOEE48 *** RESULTS: FILE' RELEASE MODULE A2' RENAMED TO ' RELEASE MODOLD A1' , RELEASE MODULE A2' CREATED FROM TEXT DECK ( S ) DMSARE DMSALU WITH ATTRIBUTES TRANS SYSTEM NOMAP The CMSGEND EXEC procedure displays status and error messages.
*** CURRENT STATUS: r , I 'fn MODULE A2' EXISTS I I 'fn MODULE A2' DOES NOT EXISTI L .J r , I'fn MODOLD A1' EXISTS I I 'fn MODOLD A1' DOES NOT EXISTI L .J
This message indicates whether a generated module already exists.
*** LOADING:
This message indicates that CMSGEND is loading the text decks.
*** (UNDEF. NAMES NORMAL FOR EDINIT)
*** NOW WE HAVE A SECOND PASS FOR EDINIT MODULE. These messages indicate that the EDIT command requires two passes
to resolve undefined names.
378 IBM VM/370 Planning and System Generation Guide