Debugger PROFILEs, Configuration Files, and EXECs

Setting Up a Configuration File

The configuration file controls the initial configuration of the PF keys and windows when you invoke the debugger. It is processed after your PROFILE, and you can specify a user-defined configuration file in a number of ways as described in Specifying a Configuration File. If no configuration file is specified, the debugger uses a default initial configuration that is supplied with the SAS/C Debugger.

The commands that are valid in a configuration file and the methods of saving configurations are described in Creating Configuration Files.

Specifying a Configuration File

You can specify a user-defined configuration file in the following ways:

If more than one user-defined configuration file exists, the order of precedence for determining which file to use is as listed above.

Specifying a Configuration File from a PROFILE

The format of the config command that is used in your PROFILE to specify a user-defined configuration file depends on your operating environment. See config for a complete description of the config command.

Under CMS You use the following format of the config command to specify a configuration file in your PROFILE:

config file filename

See the code sample in Setting Up a PROFILE under CMS for an example of this format. filename can be any valid CMS filename.

Under OS/390 You use the following format of the config command to specify a configuration file in your PROFILE:

config file filename
(member)

See the code sample in Setting Up a PROFILE under TSO for an example of the first form of this format. In the first form, filename can be any OS/390 data set name. The second form is used to specify the member name of a file that is stored in a partitioned data set named userid.CDEBUG.CONFIG.

Associating a Configuration File with a Program

You can create configuration files that are selected for processing by the debugger according to a name that is generated during compilation of your program. The method of creating and specifying these configuration files depends on your operating environment.

Under CMS Create a configuration file that contains the desired configuration information. The file must have a valid CMS filename, a filetype of DBCONFIG, and a filemode of *, as in the following example:

program-name DBCONFIG *

When you compile the program, specify program-name with the sname option. Refer to the SAS/C Compiler and Library User's Guide, Third Edition for information about using the sname compiler option to specify a program name under CMS.

Under OS/390 Create a partitioned data set that is named userid.CDEBUG.CONFIG. You can add members to this PDS that are selected by member name when you compile your program. For example, you can create a configuration file that is named userid.CDEBUG.CONFIG(myconfig), which is associated with your compilation by the sname option when you compile a program in userid.source.C(mycode). See the SAS/C Compiler and Library User's Guide, Fourth Edition for information about using the sname compiler option to specify a program name under OS/390.

Creating Your Own Default Configuration File

You can create a user-defined configuration file that sets your default initial configuration. This configuration is used only if you do not specify a configuration file in your PROFILE or as described in Associating a Configuration File with a Program.

User-specific configuration files are created in the same manner as described for program-specific configuration files. The only difference is the name of the file. You must name your user-specific configuration file UNKNOWN. Under CMS it is created with the following filename, filetype, and filemode:

UNKNOWN DBCONFIG *

Under OS/390, it is created as the following PDS member:

'first_level_qualifier.CDEBUG.CONFIG(UNKNOWN)'

If your TSO profile specifies NOPREFIX, then your userid is the first_level_qualifier, otherwise, if a PREFIX is specified, then that prefix is the first_level_qualifier.

Creating Configuration Files

A configuration file can be created in the following ways:

Use a text editor to type commands into the file
Modify your configuration with the Keys and Configuration windows and then save the configuration with the config save command.

The second method offers the easier way of creating a new configuration file.

Note: When you use the config save command to save a configuration, the existing configuration file is replaced by the new one. [cautionend]

Valid Commands in the Configuration File

The configuration file may contain only keys define commands and a certain subset of window commands. Invalid commands or errors in your configuration file usually cause the debugger to display messages. Under CMS, errors in your configuration file cause the debugger to pause with a MORE prompt.

PF key customization Any of the PF keys may be customized by issuing appropriate keys define commands, as described in Using PF Keys. You can type these commands directly into a configuration file by using a text editor, or you can use the config save command after modifying PF key assignments with the Keys window. See Saving Your Configuration.

Window customization In the configuration file, window commands have several purposes, some of which are the following:

to specify the size, location, presence of borders, and color of windows
to specify characters that are used for window borders
to determine which windows are present.

The following subcommands of the window command are valid in the configuration file:

autopop: automatically pops up (makes unobscured) any window of the type that is specified when the file is updated.
border: specifies the characters to be used to form the borders of windows with borders.
color: customizes the color, attributes, and intensity of the border and the different areas in the named window.
config: customizes the configuration (size, position, and presence of borders) of the named window. The subcommand does not open a window.
context: controls the amount of context information around the highlighted line in the Source window.
intercepts: specifies the status of the input and the output intercepts and the processing of intercepted I/O.
memory: specifies the amount of memory to be allocated for various window buffers.
open: causes the named window to be present in the initial configuration.
scroll: sets the scroll amount displayed in the Status window.
trace: controls the production of trace lines in the Log window.

Note: The autopop, color, config, context, open, and trace commands take a window name as a parameter. [cautionend]

Saving Your Configuration

The effect of specifying window commands outside the configuration file is discussed in Windowing Interface and Command Execution. Certain commands have the effect of changing the configuration (window colors, window position and size, number of windows, scroll amount, and so on) of the debugger. Similarly, keys define commands that are issued during execution (see Using PF Keys) may also change the configuration. The debugger enables you to save this configuration by issuing the config file and config save commands. For example, the following command displays the name of the current configuration file in the Log window:

config file

Then, when you issue the following command, your configuration is saved to that file:

config save

You can save your configuration to a file other than the current configuration file by issuing the config save command with a FILENAME argument. For example, under CMS, the following command saves the configuration to a configuration file that is named config1:

config save config1

This command also changes the current configuration file to config1.

Both the config file and config save commands are described in Command Directory.

Chapter Contents
Previous
Next
Top of Page