The default installation procedure places the DSE utility program in a directory specified by the logical name GTM$DIST . The installation also creates command files that define GTM$DIST and assign the symbol DSE to be the $GTM$DIST:DSE foreign command.

Invoke DSE using the GT.M symbol DSE at the DCL prompt . If this does not work, consult your system manager to investigate setup and file access issues.

Example:

$ DSE
File USER:[NAME]MUMPS.DAT;
Region $DEFAULT
DSE>

DSE displays the current database file and region in use, followed by the DSE> prompt.

When used as a foreign command, DSE may be followed by a command.

Example:

$ DSE DUMP /FILEHEADER

This command displays the header of the file for the $DEFAULT region, then returns to the DCL prompt.

While DSE can operate concurrently with other processes that access the same database file, FIS strongly recommends using DSE in standalone mode when modifying the database, unless you are very knowledgeable about DSE and about how your application uses database files. Some DSE operations can adversely impact the database when they occur during active use of the database. Other DSE operations may be difficult to perform in a logically sound fashion because a DSE operator works on a block at a time, while normal database operations update all related blocks almost simultaneously.

In a logical dual-site environment, FIS recommends using DSE on the secondary whenever possible.

Use the DSE EXIT, or QUIT command to leave DSE.