10. MODIFICATION › 10.4 Modification and Maintenance Tools › VMTGEN CA MICS CMS Resident File Generator
VMTGEN CA MICS CMS Resident File Generator
+----------+
| VMTGEN | CA MICS CMS Resident File Generator
+----------+
VMTGEN generates files for use in CMS. The generation
process may be program assembly, EXEC conversion, or any
function(s) required to take delivered source code and create
executable code or other production files.
FORMAT:
VMTGEN listname <ctl> <( <opts>>
where:
listname - is the name of a generation command list.
The file type must be GENLIST (Mandatory).
ctl - is the control file name. Default: VMTCTL
opts - is a generation-specific option:
RESTART
GEN name
OPTIONS:
RESTART - resumes an aborted generation sequence.
When this option is specified, the saved
listname and control file name are used.
The list must not contain a different number
of commands than when it was aborted.
NOTE: Any command that yields a non-zero
return code causes a halt in the generation
process.
GEN name - uses a specific-generation list command
sequence. The command sequence name is
searched for in the GENLIST. If found,
it is executed.
NOTE: If more than one entry for "name" is
in the GENLIST, the first one is executed.
VMTGEN GENERATION LIST FORMAT
token 1 - Generation command sequence name. The
identifier of the sequence of commands used
to generate a program or other file. If an
asterisk, the line is treated as a comment.
tokens 2-n - Generation commands. If the last token is
"+" the next line is interpreted as a
continuation. Multiple commands are
separated by a semicolon. Special variables
%N and %CTL may be embedded in the commands.
%N is changed to the value of token 1, and
%CTL is changed to the name of the control
file used in the generation process.
EXAMPLE:
* A SAMPLE
VMTCLEAR VMTASM %N %CTL; LOAD %N (RLDSAVE; +
GENMOD %N
VMTMNT CA MICS Maintenance Installation in CMS
+----------+
| VMTMNT | CA MICS Maintenance Installation in CMS
+----------+
VMTMNT loads and installs maintenance for files that reside
in CMS.
FORMAT:
VMTMNT function <( options )>
function: options:
RDR|Reader CTL fname
Tape FIX fix-num
Genonly Loadonly
FUNCTIONS:
RDR - indicates that the maintenance is to be read
Reader to disk from the reader.
Tape - indicates that the maintenance is to be read
to disk from tape.
Genonly - indicates that maintenance has already been
loaded to disk, and that only installation
is required.
OPTIONS:
CTL fname - specifies the name of the control file to be
used when updates are applied to source
files. If not specified, the default of
VMTCTL is used.
NOTE: Maintenance is not distributed as CMS
update files. This is used to allow
application of local changes, and for
determination of MACLIBS by the assembler.
Loadonly - This parameter is valid with the READER
and TAPE parameters. It indicates that the
maintenance is only to be loaded to disk,
but not installed.
FIX fix-num - This parameter is valid only with the
GENONLY parameter. It identifies which
product change to install.
USAGE NOTES:
1. The loading of maintenance to disk replaces existing
files of the same name.
2. Installation of maintenance replaces generated files.
This may cause the replacement of TEXT, MODULE, EXEC,
XEDIT, or other files.
3. The READER and TAPE parameters cause maintenance to be
both loaded and installed.
4. All maintenance is initially installed in your MVS
CA MICS complex using PSP Online. This EXEC is a tool
used to simplify the moving of changed source files to
CMS.
5. Files with a file type of VMTMNT are created during the
loading of maintenance to disk. These files have a
file name that is the same as the fix being applied, and
contain instructions that are used to complete
installation of the maintenance.
6. If tape is used to transfer the maintenance from MVS to
CMS, it must be a standard label tape. The EXEC prompts
you to have this tape mounted on virtual address 181.
The maintenance is copied from tape to your reader, and
loaded to disk. Any class Z reader files are changed to
class Y. Your virtual punch is spooled to your reader
and any unclosed file is purged. (It is not normal for
the punch to contain an unclosed file.)
7. If spool (NJE) is used to transfer the maintenance from
MVS to CMS, the EXEC lists all files in your reader and
prompts for the number of the file to be loaded.
