VMS Help  —  DECset
  DECset for OpenVMS VAX and OpenVMS Alpha is a set of layered products
  that supports software developers' coding, debugging, testing, and
  maintenance activities.  These layered products are:

       Code Management System (CMS) -- provides an efficient method for
       storing project files and tracking all changes to those files.
       CMS stores any kind of file including documents, plans,
       specifications, status reports, source code files, object files,
       executable images, sixel files and other kinds of files.

       Language-Sensitive Editor (LSE) -- assists in developing
       programs faster. LSE is a multilanguage programmer's editor.
       LSE allows users to efficiently edit, compile, review diagnostic
       information from compilations, and correct compile time errors
       without exiting the editor.

       Module Management System (MMS) -- automates and simplifies
       the building of software applications.  MMS can optimize the
       build process by rebuilding only those components that have
       changed since the system was last built.

       Performance and Coverage Analyzer (PCA) -- helps users pinpoint
       execution bottlenecks in application programs.  PCA can also
       identify which parts of an application are not executed by a
       given set of test data.

       Source Code Analyzer (SCA) -- aids programmers in understanding
       the complexities of software systems.  SCA allows users to
       analyze an entire system, as opposed to individual components,
       and helps users understand unfamiliar systems.

       Digital Test Manager (DTM) -- automates the creation and
       maintenance of regression tests.  DTM also automatically
       compares  test run results with expected test results.

       DECset Environment Manager -- provides a single mechanism for
       tailoring the execution environment for a set of DECset tools.
       The Environment Manager is used to define and switch between
       software development activities in the DECset environment.

  The products in the DECset environment can be used in either a
  workstation or character-cell terminal environment.  All DECset
  components include both DECwindows Motif and command-line interfaces.

1  –  Commands

  DECset commands pertain to the use of the DECset Environment Manager
  in a character-cell terminal environment or in batch mode.

1.1  –  SET

  The SET command allows you to set the current `context' or the
  current context database for your process.

  A `context' is a named set of values that tailors the DECset tools
  to a specific software development activity (for example, fixing
  bugs or implementing enhancements).

  The SET command line has one of the following forms, depending upon
  whether a context or a context database is being set:

       DECSET SET CONTEXT context-name [/DATABASE=database-file]

       DECSET SET DATABASE database-file

  DCL wild cards may not be used in either the context-name or
  database-file argument.

  The /DATABASE qualifier allows you to set a context that is defined
  in the specified database.  If the /DATABASE qualifier is missing,
  the value of the DECSET$CONTEXT_DB logical name is used; if this
  logical name is undefined, your SYS$LOGIN directory is searched for
  a file named DECSET$KNOWN_CONTEXTS.DECSET_CONTEXT_DB.  If a database
  cannot be located, an error message is displayed.

  The DECSET SET CONTEXT command automatically defines the logical names
  DECSET$CONTEXT and DECSET$CONTEXT_DB.  The DECSET SET DATABASE command
  automatically defines the logical name DECSET$CONTEXT_DB.

1.2  –  SHOW

  The SHOW command is used to display either the description of a
  single `context' or the file specification of the current context
  database.

  A `context' is a named set of values that tailors the DECset tools
  to a specific software development activity (for example, fixing
  bugs or implementing enhancements).

  The SHOW command line has one of the following forms, depending upon
  whether information about a context or a context database is being
  shown:

       DECSET SHOW CONTEXT [context-name] [/DATABASE=database-file]

       DECSET SHOW DATABASE

  DCL wild cards may not be used in either the context-name or
  database-file argument.

  If context-name is not specified in the DECSET SHOW CONTEXT command,
  the value of the DECSET$CONTEXT logical name is used (if that logical
  name is defined).  If the context name cannot be determined, an error
  message is displayed.

  The /DATABASE qualifier allows you to show information about a
  context that is defined in the specified database.  If the /DATABASE
  qualifier is missing, the value of the DECSET$CONTEXT_DB logical name
  is used; if this logical name is undefined, your SYS$LOGIN directory
  is searched for a file named DECSET$KNOWN_CONTEXTS.DECSET_CONTEXT_DB.
  If a database cannot be located, an error message is displayed.

2  –  Context File

  A context file contains statements which assign values to the
  various attributes comprising a context.  This file may also contain
  comment lines and blank lines.

  A statement is used in the context file to assign a value to a
  particular context attribute.  A hyphen may be used in the last
  character position of a line to continue a statement on the
  following line.

  Several of the statements that may appear in a context file are
  similar to DCL commands; however, the syntax of these statements is
  more restrictive than that of DCL.

  Note that a context file is automatically generated when you save a
  context via the Environment Manager's graphical user interface.

2.1  –  CMS_SET_LIBRARY

  The CMS SET LIBRARY statement is used to specify the CMS library.

  Format:

       CMS SET LIBRARY directory[,...]

2.2  –  DTM_SET_LIBRARY

  The DTM SET LIBRARY statement is used to specify the DTM library.

  Format:

       DTM SET LIBRARY directory

2.3  –  Comments

  Comment lines must begin with an exclamation point.

  For example:

       ! This is a comment line.

2.4  –  DEASSIGN

  The DEASSIGN statement is used to deassign a logical name.

  Format:

       DEASSIGN [qualifiers] logical-name

2.4.1  –  Qualifiers

  The optional qualifiers for the DEASSIGN command are:

       /PROCESS
       /JOB
       /GROUP
       /SYSTEM
       /TABLE=name

  You should not combine any of /PROCESS, /JOB, /GROUP, /SYSTEM, and
  /TABLE.

2.5  –  DEFINE

  The DEFINE statement is used to define a logical name.

  Format:

       DEFINE [qualifiers] logical-name equivalence-string[,...]

2.5.1  –  Qualifiers

  The optional qualifiers for the DEFINE command are:

       /PROCESS
       /JOB
       /GROUP
       /SYSTEM
       /TABLE=name
       /TRANSLATION_ATTRIBUTES=CONCEALED

  You should not combine any of /PROCESS, /JOB, /GROUP, /SYSTEM, and
  /TABLE.

2.6  –  DELETE_SYMBOL

  The DELETE/SYMBOL statement is used to delete a symbol.

  Format:

       DELETE/SYMBOL symbol-name

2.7  –  SCA_SET_LIBRARY

  The SCA SET LIBRARY statement is used to specify the SCA library.

  Format:

       SCA SET LIBRARY directory[,...]

2.8  –  SET_DEFAULT

  The SET DEFAULT statement is used to specify the default directory
  for the context.

  Format:

       SET DEFAULT directory

2.9  –  SET_DIRECTORY

  The SET_DIRECTORY statement is used to specify a directory to be used
  for a particular purpose.

  Format:

       SET_DIRECTORY setting

  where setting can be one of the following:

       SOURCE directory[,...]
       EXECUTABLE directory
       LISTING directory
       OBJECT directory

2.10  –  SET_LINKER

  The SET_LINKER statement is used to set the values of linker-specific
  attributes.

  Format:

       SET_LINKER setting

  where setting can be one of the following:

       OBJECT_LIBRARY filespec
       OPTIONS_FILE filespec

2.11  –  SET_MMS

  The SET_MMS statement is used to set the values of MMS-specific
  attributes.

  Format:

       SET_MMS setting

2.11.1  –  Parameters

  Most of the SET_MMS setting options have the same syntactic forms
  and semantics of corresponding MMS command qualifiers.

2.11.1.1  –  ACTION

  This option has the same semantics as the MMS /ACTION qualifier.

  Format:

       SET_MMS [NO]ACTION

2.11.1.2  –  BUILTIN_RULES_APPLY

  This option has the same semantics as the MMS /BUILTIN_RULES_APPLY qualifier.

  Format:

       SET_MMS [NO]BUILTIN_RULES_APPLY

2.11.1.3  –  CHANGED

  This option has the same semantics as the MMS /CHANGED qualifier.

  Format:

       SET_MMS CHANGED=(source[,source...])

2.11.1.4  –  CHECK_STATUS

  This option has the same semantics as the MMS /CHECK_STATUS qualifier.

  Format:

       SET_MMS [NO]CHECK_STATUS

2.11.1.5  –  CMS

  This option has the same semantics as the MMS /CMS qualifier.

  Format:

       SET_MMS [NO]CMS

2.11.1.6  –  DESCRIPTION

  This option has the same semantics as the MMS /DESCRIPTION
  qualifier.

  Format:

       SET_MMS DESCRIPTION[=filespec]
       SET_MMS NODESCRIPTION

2.11.1.7  –  ENABLE macro

  This option enables the indicated MMS macro.

  Format:

       SET_MMS ENABLE_DEBUG (to enable the DEBUG macro)
       SET_MMS ENABLE_LIST (to enable the LIST macro)
       SET_MMS ENABLE_DIAG (to enable the DIAG macro)

2.11.1.8  –  FORCE

  This option has the same semantics as the MMS /FORCE qualifier.

  Format:

       SET_MMS [NO]FORCE

2.11.1.9  –  FROM_SOURCES

  This option has the same semantics as the MMS /FROM_SOURCES
  qualifier.

  Format:

       SET_MMS FROM_SOURCES

2.11.1.10  –  IGNORE

  This option has the same semantics as the MMS /IGNORE qualifier.

  Format:

       SET_MMS IGNORE[={WARNING|ERROR|FATAL}]
       SET_MMS NOIGNORE

2.11.1.11  –  LIST

  This option has the same semantics as the MMS /LIST qualifier.

  Format:

       SET_MMS LIST[=filespec]
       SET_MMS NOLIST

2.11.1.12  –  LOG

  This option has the same semantics as the MMS /LOG qualifier.

  Format:

       SET_MMS [NO]LOG

2.11.1.13  –  MACRO

  This option has the same semantics as the MMS /MACRO qualifier.

  Format:

       SET_MMS MACRO=(macro[,...])
       SET_MMS MACRO="macroname=expansion"

  The macro argument in the MACRO=(macro[,...]) form can be in
  either of the following forms:

       "macroname=expansion"
       macro-filespec

2.11.1.14  –  OBJECT_LIBRARY

  This option allows you to specify the object library to be used by
  the MMS description file generator.

  Format:

       SET_MMS OBJECT_LIBRARY filespec

2.11.1.15  –  OUTPUT

  This option has the same semantics as the MMS /OUTPUT qualifier.

  Format:

       SET_MMS OUTPUT[=filespec]

2.11.1.16  –  OVERRIDE

  This option has the same semantics as the MMS /OVERRIDE qualifier.

  Format:

       SET_MMS [NO]OVERRIDE

2.11.1.17  –  REVISE_DATE

  This option has the same semantics as the MMS /REVISE_DATE
  qualifier.

  Format:

       SET_MMS [NO]REVISE_DATE

2.11.1.18  –  RULES

  This option has the same semantics as the MMS /RULES qualifier.

  Format:

       SET_MMS RULES[=filespec]
       SET_MMS NORULES

2.11.1.19  –  SCA_LIBRARY

  This option has the same semantics as the MMS /SCA_LIBRARY
  qualifier.

  Format:

       SET_MMS SCA_LIBRARY[=directory]
       SET_MMS NOSCA_LIBRARY

2.11.1.20  –  SCAN_INCLUDE

  This option has the same semantics as the MMS /SCAN_INCLUDE
  qualifier.

  Format:

       SET_MMS [NO]SCAN_INCLUDE

2.11.1.21  –  SKIP_INTERMEDIATE

  This option has the same semantics as the MMS /SKIP_INTERMEDIATE
  qualifier.

  Format:

       SET_MMS [NO]SKIP_INTERMEDIATE

2.11.1.22  –  SWITCHES

  This option has the same semantics as the MMS /SWITCHES
  qualifier.

  Format:

       SET_MMS SWITCHES

2.11.1.23  –  VERIFY

  This option has the same semantics as the MMS /VERIFY qualifier.

  Format:

       SET_MMS [NO]VERIFY

2.12  –  Symbol Assignment

  A symbol assignment takes the following form:

       symbol == expression

3  –  Database File

  Each record of the context database file defines a particular
  context in terms of its name, an associated context file, its
  parent context (optional), and a description (optional).

  The format of each record is:

       context-name filespec [parent-context-name] ["description"]

  The context name and context file specification fields must be
  present.  The context name should begin in the first column and
  each field should be separated by a single blank space.

  The parent context name is the name of another context defined
  in the same database file.  The description must be enclosed in
  double quotation marks.

  Note that this file is automatically generated when you save a
  database via the Environment Manager's graphical user interface.

4  –  Release Notes

  Release notes for DECset Version 12.9 are contained in the file:

           SYS$HELP:DECSET129.RELEASE_NOTES

  Release notes for the DECset Environment Manager Version 1.9 are
  contained in the file:

           SYS$HELP:ENVMGR01.9.RELEASE_NOTES
Close Help