When database access has not been properly terminated, RUNDOWN properly closes currently inactive databases and releases any IPC resources used. Under normal operations, the last process to close a database file performs the RUNDOWN actions, and a MUPIP RUNDOWN is not required. In a database file is already properly rundown, a MUPIP RUNDOWN has no effect. If in doubt, it is always to safe to perform a rundown. Fidelity recommends the following method to shutdown a GT.M application or the system:
Terminate all GT.M processes, and
Rundown any and all database files that may be active.
MUPIP RUNDOWN checks for version mismatch. If there is a mismatch, it skips the region and continues with the next region. This makes it easier for multiple (non-interacting) GT.M versions to co-exist on the same machine. Note that GT.M does not support concurrent access to the same database file by multiple versions of the software.
MUPIP RUNDOWN reports "RMS-%-FLK-file locked by another user" errors when it cannot get exclusive access.
The only errors considered terminal (i.e., cannot be trapped by the application program are %GTM-F- errors, and a few severe OpenVMS errors such as ACCVIO.
The format of the RUNDOWN command is:
RU[NDOWN] [/FILE file-specification |/REGION region-list]
The file-specification or region-list identifies the target of the RUNDOWN. If RUNDOWN has no parameter, it flushes the memory associated with all database files opened by the corresonding version of GT.M that currently have associated memory and no active users.
The RUNDOWN command must include one of the following qualifiers:
/FILE
/REGION
MUPIP RUNDOWN /FILE or /REGION clears certain fields in a file that is already closed. This facilitates recovery from a system crash or other operational anomaly.
Use RUNDOWN after a system crash or after the last process accessing a database terminates abnormally. RUNDOWN ensures that open databases are properly closed and ready for subsequent use. RUNDOWN has no effect on any database that is actively being accessed at the time the RUNDOWN is issued.
To ensure database integrity, all system shutdown algorithms should include scripts that stop at GT.M processes and perform RUNDOWN on all database files.
/F[ILE]
Specifies that the argument is a file-specification for a single database file. The /FILE qualifier is incompatible with the REGION qualifier. If the rundown parameter consists of a list of files, the command only operates on the first item in the list.
/R[EGION]
Specifies that the argument contains one or more region-names that identify database files mapped by the current Global Directory. Region-names may include the DCL wildcards % and *. The /REGION qualifier is incompatible with the /FILE qualifier.