Running the Debugger under TSO

General Instructions

This section provides specific instructions for running the SAS/C Debugger under TSO. See Quick Start to Using the Debugger under TSO for more general information.

Compiling Your Source Files

Compile each source file that you want to debug with the debug compiler option. Use the LC370 CLIST in order to compile your program. If you use the recommended naming conventions for your source data set and debugger data set (userid.pdsname.C and userid.pdsname.DBGLIB) and you do not fully qualify your source data set when you invoke the CLIST, the CLIST automatically associates your debugger file with the DDname SYSDBLIB. Otherwise, you are first prompted for the name of your debugger data set, and then the CLIST associates it with the DDname SYSDBLIB.

Linking Your Programs

Use the CLK370 CLISTin order to link your programs. For detailed instructions, see the SAS/C Compiler and Library User's Guide.

Linking C++ template programs requires the SYSDBLIB DD statement as well. The default option format for SYSDBLIB is dbglib(ddn:sysdblib), and the default filename format is ddn:sysdblib(sname).

Invoking the Debugger under TSO

Allocate data sets that are needed at run time, and call the debugger.

Issue a TSO ALLOCATE command for the debugger symbol file table. This is the same data set name that is defined as DDname SYSDBLIB in the compile step. When you invoke the debugger, this data set should have a DDname of DBGLIB. If you do not allocate DBGLIB before you invoke the debugger, the debugger prompts you for it. Note that if you compile with the sname option, the member name in DBGLIB is the section name that you specify. Otherwise, the member name is the default section name.
If you have moved your source in the time since you compiled the program, associate the DDname DBGSRC with the data set that contains the source.
Invoke the debugger by using one of the following routines:
- Issue the TSO CALL command and pass the parameter =d with the following command:
```
call dsname '=d'
```
  The dsname names the load module and must follow standard TSO naming conventions.
  If you need to examine portions of your program by using TSO TEST, invoke the SAS/C Debugger under TSO TEST. Here is a sample command that uses the same data set as the previous example:
```
test dsname '=d'
```
  Note that you need to pass the option =d to TEST. Once the debugger has been invoked, you can escape to TSO TEST by pressing the attention key (PA1).
- If your site has installed the SAS/C TSO command processor support, you can call your program under TSO as a command processor with the following commands:
```
program-name =d <arguments>
```
  or
```
c program-name =d <arguments>
```
  You can also use TEST with a command processor by issuing the following command:
```
test dsname cp
```
  Then TEST prompts you with ENTER COMMAND FOR CP, and you type
```
program-name  =d <arguments>
```
  In these examples of calling a program as a command processor, arguments are run-time options, redirections, or values to be passed to the program.
  As previously described, once the debugger has been invoked, you can escape to TSO TEST by pressing the attention key (PA1).
In a line-mode session, you can save TSO output. The TSO Session Manager enables you to copy output from your screen (TSOOUT) to a sequential data set or a partitioned data set member using the TSO SMCOPY (Session Manager Copy) command. For example, to copy debugger output to a member OUT5 of a partitioned data set, type the following:
```
smc fs(tsoout) tds('userid.group.type (out5)') asis
```
where TSOOUT is the TSO output stream (that is, your terminal screen), and userid.group.type identifies a partitioned data set. OUT5 is the data set member.
For details about the SMCOPY command, see the IBM publication OS/390 V2R9.0 SC28-1969 TSO Command Reference.

Chapter Contents
Previous
Next
Top of Page