-
ABBREVIATION
-
conf{ig}
-
FORMATS
-
-
DESCRIPTION
-
The
config
command can be used to assign a configuration file, display the name of the
current configuration file, or save the current configuration. The FILENAME
argument is used to specify the configuration file; under CMS it is a filename
and under OS/390 it is an OS/390 data set name. Under OS/390 you can specify
MEMBER instead of FILENAME. MEMBER specifies a member name in a data set named userid.CDEBUG.CONFIG.
Format 1: This format is
valid during a
debug session; it cannot be used in the PROFILE. The file
keyword displays the name of the current configuration file.
Format 2: This format is valid only in
the PROFILE; it cannot be used during a debug session. The FILENAME argument
is used to assign a current configuration file to your debug session, which
sets the initial configuration of your windows and PF keys. If running under
OS/390, the MEMBER argument can be used instead of the FILENAME argument.
Format 3: This format is used only during
a debug session; it is not valid in a PROFILE. The save
keyword is used with the config command to
save your session configuration to a configuration file. If issued without
the FILENAME or MEMBER argument, this command saves the configuration to the
current configuration file. You can use the FILENAME argument, or the MEMBER
argument if running under OS/390, to specify a file other than the current
configuration file. This new file then becomes your current configuration
file.
The following information is saved to your current configuration
file:
-
EXAMPLES
-
-
config file
-
displays the name of the current configuration
file. (This cannot be used in a PROFILE.)
-
config file myconfig
-
assigns myconfig
to be the current configuration file, assuming that myconfig is a valid CMS configuration filename. (This is only valid
in a PROFILE.)
-
config file
'userid.config.files(myconfig)'
-
assigns userid.config.files(myconfig) to be the current configuration file, assuming that the member myconfig
is a valid configuration file under OS/390. (This
is only valid in a PROFILE.)
-
config file (myconfig)
-
assigns userid.CDEBUG.CONFIG(myconfig) to be the current configuration file, assuming that
the member myconfig is a valid configuration
file under OS/390. (This is only valid
in a PROFILE.)
-
config save
-
saves the configuration of your session
to your current configuration file. (This is not valid in a PROFILE.)
-
config save
myconfig
-
saves your session configuration to myconfig, assuming that myconfig
is a valid CMS configuration filename. The current configuration file becomes myconfig. (This is not valid in a
PROFILE.)
-
config save
-
config.files(myconfig) saves your session configuration to the data set
userid.config.files(myconfig), assuming that the member myconfig
is a valid configuration file under OS/390. The current configuration file
becomes userid.config.files (myconfig). (This is not valid in a
PROFILE.)
-
ADDITIONAL DISCUSSION AND EXAMPLES
-
Setting Up a Configuration File
-
SYSTEM DEPENDENCIES
-
The name of the file used as the FILENAME
argument depends on the operating system. See DESCRIPTION.
Under OS/390, you can specify the MEMBER argument instead
of the FILENAME argument. MEMBER must refer to a member in a partitioned
data set named userid.CDEBUG.CONFIG.
Under CMS, the config file
command cannot be followed by another debugger command on the same line. That
is, the arguments to the config file command
are assumed to extend to the end of the line, including any semicolons on
the line.
-
COMMAND CAN BE ISSUED FROM
-
-
SCOPE
-
The
config
command is not affected by changes in scope.
-
RETURN CODES SET
-
