SAS/C Software: Changes and Enhancements, Release 6.50

Run Command File

This release of the SAS/C Debugger allows you to use a run command file to execute debugger commands at startup. The run command file is similar to the debugger's PROFILE, but is intended for use in environments that do not support REXX or CLIST, such as MVS batch. The debugger runs the commands in the run command file if it cannot find an executable startup PROFILE.

The following is a description of how the debugger searches for the startup files in each environment.

MVS
If the debugger is running under TSO, it first checks for the PROFILE in DDname DBGPROF. If it cannot open DBGPROF, or if DBGPROF is not allocated, the debugger checks for the PROFILE in the data set userid.CDEBUG.CLIST. If it cannot find or open a startup PROFILE, the debugger issues a warning message and begins checking for the run command file.
The debugger first checks for the run command file in DDname DBGRC. If it cannot open DBGRC, or if DBGRC is not allocated, the debugger checks for the run command file in the data set userid.CDEBUG.RC. If the debugger cannot find or open a run command file, a warning message is issued.
OpenEdition shell
Under OpenEdition, the PROFILE is an executable file named .cdebug. The debugger searches for the PROFILE in the directories named in the PATH environment variable and uses the first executable file it finds named .cdebug. If the debugger cannot find a PROFILE, it checks for a run command file at:
```
//hfs:initial_working_directory/.cdebug
```
If the debugger cannot find or open a PROFILE or run command file, a warning message is issued.
CMS
The debugger first checks for the PROFILE in:
```
//cms:profile cdebug *
```
If it cannot find the PROFILE, it checks for the run command file in:
```
//cms:cdebug rc *
```
If the debugger cannot find or open a PROFILE or run command file, a warning message is issued.

Chapter Contents
Previous
Next
Top of Page