6 – CMS
If CMS is installed on your system and your source files are in the
current default CMS library, MYPROG.EXE may be built from the CMS
library when you issue the following command:
$ MMS/CMS
This command causes MMS to fetch the description file, if necessary,
and source files from the CMS library, and perform the actions needed
to create an up-to-date MYPROG.EXE.
If a module, for example A.BLI, is replaced in the CMS library (by
you or anyone else), thus causing a later version of A.BLI to exist
in the library, the command
$ MMS/CMS
causes MMS to fetch the new CMS element A.BLI, compile it, add it to
the MYPROG.OLB library, and produce a new MYPROG.EXE by executing the
LINK command.
7 – FMS
If FMS (Forms Management System) is installed on your system, you can
use MMS to access forms stored in FMS libraries. To specify an FMS
form in a dependency rule, use the same syntax as for files in
OpenVMS libraries. The file type .FLB after the library name informs
FMS that the library contains FMS forms. The default file type for
FMS forms is .FRM.
The MMS default macro FMSFLAGS invokes FMS with the /REPLACE
qualifier.
MMS uses the insertion time of a form in an FMS library to determine
whether a source is newer than the target. You cannot use the
/REVISE_DATE qualifier with references to FMS forms.
8 – MMS$STATUS
Unless the qualifiers /CHECK_STATUS or /REVISE_DATE have been
selected, when MMS completes, the symbol MMS$STATUS is set to the
status value($STATUS) of the last action line executed.
9 – MMS$SEVEREST_STATUS
When MMS completes, the symbol MMS$SEVEREST_STATUS is set to the
'severest' status value($STATUS) of all action lines executed. If the
status values of more than one action line have the same severity,
then the resulting value of MMS$SEVEREST_STATUS will be that of the
last of these action lines.
10 – Oracle CDD/Plus
If the Oracle Common Data Dictionary (CDD/Plus) is installed on your
system, you can use MMS to access records and other definitions
stored in CDD/Plus. In a dependency rule, you follow the path name
of a CDD/Plus definition with a caret (^) to inform MMS that the
source is stored in CDD/Plus. For example:
A.PAS : CDD$TOP.B.C.D.E^ ! CDD record that updates A.PAS
! action to update A.PAS
To insert a remark in the CDD/Plus history list when MMS accesses a
CDD/Plus definition, use the /AUDIT qualifier after the caret in the
CDD/Plus specification. Follow the /AUDIT qualifier with a quoted
string that contains the remark to be inserted in the CDD/Plus
history file. For example:
A : CDD$TOP.B.C.D.E^/AUDIT="Accessed by MMS to update A"
! action to update A
The MMS default macro CDDFLAGS is initially defined to be the null
string, but you can redefine it so that the same remark is written to
the history file for all accesses to CDD/Plus entities.
You cannot use the /REVISE_DATE qualifier with references to CDD/Plus
definitions. The /NOACTION qualifier does not affect the /AUDIT
qualifier; that is, remarks are written to the CDD/Plus history file
even if action lines are not being executed.
11 – Release Notes
The release notes for MMS Version 4.0 are contained in the file:
SYS$HELP:MMS040.RELEASE_NOTES
You can type or print this file to read the release note information.
If you have installed prior versions of MMS, the associated release
notes up to and including Version 4.0 can be found in
SYS$HELP:MMSvvu.RELEASE_NOTES, where vv is the major version number,
and u is the update number.