Running the Debugger under OS/390 Batch

General Instructions

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

Compiling Your Source Files

Use one of the JCL cataloged procedures that are provided with the SAS/C Compiler, or write your own JCL to compile your program. If you use one of the cataloged procedures, override the SYSDBLIB card with one of your own that specifies your debugger data set name. If you write your own JCL, include a SYSDBLIB card for your debugger data set name.

If you compile with the sname option, the member name in the symbol table file is the section name that you specify. Otherwise, the member name is the default section name. See the SAS/C Compiler and Library User's Guide for more information about the compiler.

Linking Your Programs

Use one of the JCL cataloged procedures that are provided with the SAS/C Compiler, or write your own JCL in order to link your program. See the SAS/C Compiler and Library User's Guide

Invoking the Debugger under OS/390 Batch

Allocate the data sets that are needed at run time, and call the debugger. When you invoke the debugger, you need DD statements for DBGIN (the debugger input file), DBGLIB (the debugger symbol table file), and DBGLOG (the debugger output file). DBGLOG is provided automatically if you use one of the LC370 cataloged procedures. Also, if you moved your source between compile time and run time, then allocate DDname DBGSRC to the partitioned data set (or data set concatenation) that contains your source code library. Use JCL such as that shown in Sample JCL for Running the Debugger under OS/390 Batch for running the SAS/C Debugger.

Sample JCL for Running the Debugger under OS/390 Batch
//JOBNAME JOB jobcard information //*---------------------------------------------------------- //* RUN A PROGRAM, USING THE DEBUGGER //*---------------------------------------------------------- // EXEC PGM=membermono ,PARM='=D' //STEPLIB DD DISP=SHR,DSN=your.load.library // DD DISP=SHR,DSN=your.site.LINKLIB //SYSTERM DD SYSOUT=* //SYSPRINT DD SYSOUT=* //DBGLOG DD SYSOUT=* //DBGSRC DD DISP=SHR,DSN=your.source.library //DBGLIB DD DISP=SHR,DSN=your.debugger.library //DBGIN DD * break main * on main e print argc go;go;go print argc exit /*

In Sample JCL for Running the Debugger under OS/390 Batch, DBGSRC and DBGLIB are defined. Debugger commands are provided in the JCL. Also, you can put debugger commands in a data set, and you can allocate the data set to DBGIN, as in the following:

//DBGIN    DD DISP=SHR,DSN=your.debugger.commands

The debugger writes OS/390 batch output to DBGLOG.

Sample JCL for Compiling, Linking, and Running the Debugger by Using LC370CLG shows JCL for compiling, linking, and running a program under the debugger. The example uses the LC370CLG procedure.

Sample JCL for Compiling, Linking, and Running the Debugger by Using LC370CLG
//JOBNAME JOB jobcard information //*---------------------------------------------------------- //* COMPILE, LINK, AND RUN A PROGRAM WITH DEBUGGER OPTION //*---------------------------------------------------------- //STEP1 EXEC LC370CLG,PARM.C='DEBUG',PARM.GO='=D' //C.SYSIN DD DISP=SHR,DSN=your.source.library(member) //GO.DBGIN DD DISP=SHR,DSN=your.debugger.input /*

Chapter Contents
Previous
Next
Top of Page