Chapter Contents
Previous
Next
Running the Debugger under OS/390 Batch

Data Sets Needed by the Debugger

When you run the debugger under OS/390 batch, you must allocate a data set for the debugger symbol table file. This partitioned data set, which is created as a result of compiling with the debug option, contains a member for each compilation. The data set member contains debugging information for that compilation, including the name of the source for the compilation.

For this file, create a partitioned data set, unformatted (U), with a block size of 4080. This data set is then associated with the DDname SYSDBLIB at compile time and the DDname DBGLIB at run time. See Quick Start to Using the Debugger under TSO for more details on these DDnames.

When you run the debugger, it looks for the source at the same location as at compile time (the compile-time data set). If you move your source between compile time and run time, you must indicate the new location. You can allocate the DDname DBGSRC in order to define a partitioned data set (PDS) as the location of the source file or files.

The debugger goes through the following steps in order to find the source file:

  1. If the DDname DBGSRC is not defined, the debugger assumes that the source file is in the compile-time data set.

  2. If DBGSRC is defined, the debugger checks whether the source file is allocated to a member of a PDS. If it is, the debugger ignores the member name but uses the PDS as the location of the source file.

  3. The debugger checks whether the source file was a PDS member at compile time. If it was, the debugger looks for a member with the same name. Otherwise, the debugger looks for a member with the sname name.

  4. If the source file is not found by this search, the debugger looks for it in the compile-time data set.

The debugger also uses a data set that contains information that is displayed by the hypertext help system. If the debugger is properly installed, you do not have to allocate this data set in order to access the debugger help system.

In addition the debugger uses a temporary data set in order to maintain symbol tables. Do not be concerned about this data set unless the debugger runs out of space in it. If this happens, you receive an abend (B37, D37, or E37) at run time. Then you must allocate more space to the file.

One way to allocate more disk space to the debugger work file in TSO or OS/390 batch is to allocate a temporary file of sufficient size to the DDname SYSTMPDB. If this DD statement is defined, the debugger uses this file as its work file rather than allocating its own. The normal space allocation for the debugger work file is 50 tracks, unless this was changed at your site when the SAS/C Debugger was installed. Contact your SAS Software Representative for C Compiler products for more information.


Chapter Contents
Previous
Next
Top of Page

Copyright © 2001 by SAS Institute Inc., Cary, NC, USA. All rights reserved.