SHOW

Description

The SHOW command is used to display breakpoints, environmentally dependent data, or default options. A record of the command is written to the session log.

Input

When a breakpoint parameter is used with the SHOW command, all lines in the Source window not containing the specified breakpoint are temporarily excluded. Use the D (Delete) line command to remove any of the breakpoints displayed. Use the DELETE EXCLUDE or RESET command to restore the source lines. Use the LOCATE * command to scroll to the point where execution stopped. Alternatively, if PF3 is mapped to the END command, it can be used to reset the excluded lines.

The following are the parameter descriptions for the SHOW command:

ABBRev

Displays any abbreviations assigned by Code Debug to long CSECT names within Program Objects.

ACTive

Displays the general purpose register contents, Program Status Word (PSW), and some control block information.

AFTers

Displays all after breakpoints set in the current module. Not valid in unattended batch mode.

ALLOCates

Displays all allocated files or data sets.

AT

Displays all breakpoints set with the AT command for the current module. Not valid in unattended batch mode.

BEFores

Displays all before breakpoints set in the current module. Not valid in unattended batch mode.

BReaks

Displays all breakpoints set with the AFTER, BEFORE, and ONETIME commands for the current module. Not valid in unattended batch mode.

COMPopts (COBOL only)

Displays the correct compile and run-time options in effect. The options are:

SHOW COMPOPTS

Displays compile and run-time options for the active module.

SHOW COMPOPTS *

Displays compile and run-time options for all loaded modules.

SHOW COMPOPTS program-name

Displays compile and run-time options for the specified program.

COUnts

Displays all the statements with associated execution counters. All other lines are excluded. In the session log, the entire COBOL Procedure Division and PL/I code statements are printed, including the counts. The option is:

NOLOG

Displays all the statements with associated execution counters. All other lines are excluded. Nothing is printed in the session log.

DATA

Displays all the statements changed to data lines by the SET DATA command. These lines can no longer have breakpoints set on them.

DCBs (COBOL only)

Displays a file status report for each COBOL module.

FILEs (COBOL only)

Same as the SHOW DCBs option.

FPREGS

Displays the floating-point registers.

Gpregs

Displays the general-purpose registers.

IMSfunc

Displays a summary report of IMS activity broken down by PCB, function code, and number of calls.

INDEX (COBOL only)

Displays all index cells in the current module and the present values of each index.

INTercept

Displays all modules for which INTERCEPT commands have been entered and not deleted by the DELETE INTERCEPT command. The intercepts listed should still be active unless the intercept breakpoints have been reset. For dynamically called modules, all breakpoints would be reset if a fresh copy of the module was loaded into storage.

An example of how this might occur with COBOL is noted as follows:

An application program wants to load a fresh copy of a module at some point in time, so a COBOL CANCEL is then issued prior to the dynamic call of the module. Through interactive testing with Code Debug, a SOURCE or LOAD command is then issued against the module prior to the dynamic call.

The SOURCE/LOAD command causes a new copy to get loaded into storage without any breakpoints. The subsequent dynamic call will not get the opportunity to re-establish the breakpoints because a copy was previously found to be in existence.

Keeps

Displays all kept items and their data definitions.

LINKlist

Displays the names of all libraries defined in the system linkage list. Use this to help determine which versions of various products are being used. The options are:

CURRENT

Displays the names of all libraries defined in the currently active system linkage list set. This is the default.

BASEIPL

Displays the names of all libraries defined in the system linkage list at IPL time.

LISTING

Displays the listing that comes from the BMC language processor. Not valid in unattended batch mode.

MODules

Displays all application modules loaded during the current test.

ONEtime

Displays all onetime breakpoints set in the current module. Not valid in unattended batch mode.

OPTions

Displays a list of all SET command options for the test session and their current values. See SETs as follows.

PFkeys

Displays all the PF key values in effect for the test session. Invalid values can be displayed in interactive batch if you are connected through a TSO terminal.

PREVious

Displays the last nnnn known breakpoint statements, where nnnn is a number between 0001 and 9999, as specified with the SET PREVIOUS command.

PROgram

Displays a hexadecimal dump of the requested program-name, or a dump of the active program if no program is requested.

PSW

Displays the content of the program status word.

PTFs

Lists significant information on currently applied PTFs and Usermods.

REGion

Displays memory available for testing.

SETs

Displays a list of all SET command options for the test session and their current values. For a complete description of the SET command and its parameters, see SET. A few values are environmental settings implemented by other methods and have no corresponding SET command. The settings displayed by SHOW SETs include the following:

• 
  
  • ABENDSCR: Identifies the abend script that was specified for an unattended batch test.
  • ABNDEXIT: Indicates whether Code Debug will intercept abends.
  • AUTOCAN: Indicates whether dynamically called COBOL modules will be automatically deleted when control is returned to the calling module.
  • AUTOCLOS: Indicates whether Code Debug will automatically perform closes on certain user DCBs left open when a test is prematurely terminated by an EXIT command.
  • AUTOKEEP: Indicates whether data referenced in the current statement will be automatically displayed in a Keep window.
  • AUTOSCRL: Indicates whether automatic scrolling of the Keep window is enabled.
  • BRCOV: Indicates whether branch coverage has been enabled for Code Coverage testing.
  • BRKPOINT: Indicates the type of Code Debug breakpointing in effect.
  • CARRAY: Indicates how a C language character variable will be displayed: as an array (OFF), or as a character string (ON).
  • CAPS: Indicates whether Code Debug will convert lowercase characters to uppercase when displayed values are overtyped.
  • CBLTRAP: Indicates whether Code Debug will detect missing DD statements and open windows at the bottom of the screen for files allocated to the terminal.
  • CMDSIZE: Indicates the number of lines used for the primary command field.
  • CMDDLM: Lists the character used as a command delimiter in the Batch Connect environment.
  • COLS: Indicates whether Code Debug displays a column template when browsing a data set, ddname, or AA SNAP output.
  • COMPARE: Indicates whether Code Debug will use padding characters (PAD)—or not (NOPAD)—when doing comparisons using Code Debug TSO commands. The values PAD,NONOVR and NOPAD,NONOVR may be displayed. The NONOVR value indicates that the SET COMPARE command cannot be used to override the PAD/NOPAD setting. The non-override setting NONOVR is controlled by the CTLCOMO keyword in the CMSC PARMLIB and is set during installation. See Configuration Parameters in the Code Debug TSO and Code Debug IMS Advanced Configuration Guide for more information.
  • CONFIRM: Indicates whether Code Debug will display a confirmation message when the D line command is entered.
  • DATAFIND: Indicates whether Code Debug will find the next or all data names when the FIND data-name command is entered within a COBOL test.
  • DATETIME: Indicates the processing option when a date-stamp/time-stamp conflict is detected: terminate (ON), or warning (OFF).
  • DBCS: Indicates whether Code Debug will translate double-byte character set (DBCS) characters on terminals that support their display.
  • DELAY: Indicates the amount of delay time, in seconds, that will occur during execution of the TRACE command.
  • DUMP: Indicates whether a dump will be allowed when an abend occurs.
  • DYNTRAP: Indicates whether Code Debug will intercept dynamically loaded COBOL modules.
  • ESPIE: Indicates whether Code Debug will activate its own ESPIE processing routine to detect and handle a S0C1 abend condition (possible breakpoint).
  • GEN: Indicates whether Assembler macro statements and COBOL EXEC DLI and EXEC SQL statements will be expanded during initial source display.
  • HANDLER: Indicates Code Debug’s method of intercepting application abends when a user condition handler exists.
  • HEXMODE: Indicates whether any non-displayable characters from a KEEP or PEEK command will be shown as hex in the session log.
  • LANGUAGE: Indicates the language Code Debug will use for messages.
  • LESTOROV: Indicates whether Code Debug will allow the Language Environment run-time STORAGE option to be overridden.
  • LETRAP: Indicates whether Code Debug will set the Language Environment run-time TRAP option ON or OFF.
  • LOG: Indicates whether writing to Code Debug’s session log data set is active.
  • LOG AUTOKEEP: Indicates whether writing to the session log data set is active for Code Debug’s autokeep function.
  • LOG FIND: Indicates whether writing to the session log data set is active for Code Debug’s find function.
  • LOG INSERT: Indicates whether writing to the session log data set is active for Code Debug’s inserted line function.
  • LOG KEEP: Indicates whether writing to the session log data set is active for Code Debug’s keep function.
  • LOG MEMORY: Indicates whether writing to the session log data set is active for Code Debug’s memory function.
  • LOG PEEK: Indicates whether writing to the session log data set is active for Code Debug’s peek function.
  • LOG VERIFY: Indicates whether writing to the session log data set is active for Code Debug’s verify function.
  • LOGSIZE: Indicates the size, 80 or 132, of data that will be written to the session log file.
  • LOWCASE: Indicates the way in which lowercase letters found in the values of items will be displayed.
  • MODE: Indicates whether Code Debug will display only the low-order 32 bits or all 64 bits of General Purpose Registers and addresses for programs running on a z/Architecture processor.
  • MONITOR: Indicates whether the MONITOR command has been used to activate Code Debug’s review mode.
  • NESTED: Indicates the limits on the number of levels of nested application program calls that Code Debug will accept.
  • NOINIT: Indicates whether a COBOL linkage section will be initialized to binary zeros or to spaces and zeros when a subroutine is tested standalone.
  • NONDISP: Indicates the character Code Debug will use to represent nondisplayable characters.
  • PFK1 through PFK24: Shows the settings of the PF keys.
  • PREINIT: Indicates whether Code Debug is expecting the user application to pre-initialize the Language Environment.
  • REFRESH: Indicates whether the entire screen will be updated at every write to the terminal.
  • REVSIZE: Indicates the size of the review log for Code Debug’s review mode.
  • RTEREUS: Indicates whether Code Debug will force the COBOL run-time option RTEREUS to OFF if it was found ON.
  • STATIC: Indicates if and when Code Debug will intercept resolved and unresolved external references (static calls).
  • TDO: Indicates whether Test Data Optimization is enabled for Code Coverage testing.
  • TEMPLATE: Indicates whether a column template will be added to displays of data appearing in the source or session log.
  • TRANSLAT: Indicates the override setting for Code Debug’s display of non-alphanumeric characters.
  • UNCHNGED: Indicates whether CODE DEBUG will write to the session log the values of kept items unchanged since the last interrupt.
  • USERSVC: Indicates the decimal SVC number, selected by the site, when either the SVC or TRAP breakpoint methodology is in use.
    • TRAPBP: Indicates whether TRAP breakpoints are selected.
    • SVCBP: Indicates whether SVC breakpoints are selected.
    • SVCTCBU: Indicates whether Code Debug breakpointing is using the TCBUSER field.
  • WINDOW SOURCE: Indicates the minimum number of lines in the source window.
  • WINDOW KEEP: Indicates the number of lines (or maximum number of lines) in the Keep window.
  • WINDOW AUTOKEEP: Indicates the number of lines (or maximum number of lines) in the Automatic Keep window. A zero indicates that automatically kept data will be displayed in the Keep window.
  • TRANSFER: Indicates the name of an interface module that dynamically loads application modules.
  • DYNAMIC MODULES: Lists modules Code Debug has been requested to dynamically load during application execution.
  • EXCLUDE MODULES: Lists modules Code Debug has been requested to not intercept when called.
  • NOCANCEL MODULES: Lists modules Code Debug has been requested to not automatically cancel when AUTOCAN is active.
  • NOCOVER: Lists modules Code Debug has been requested to not monitor during a code coverage test.
  • ONLYCOV: Lists modules Code Debug has been requested to monitor during a code coverage test.
  • SKIPPED MODULES: Lists modules Code Debug has been requested to not execute when called.
  • TRACED MODULES: Lists modules Code Debug has been requested to trace when called.
  • DDIGNORE AT CLOSE: Lists the DDNAMEs that Code Debug will not attempt to close if left open at the end of a test session.
  • TDODDXCL DDNAMES: Lists the DDNAME/DBDNAMEs that Code Debug will ignore during file monitoring in a Test Data Optimization test session.

SKips

Displays all outstanding SKIP commands for the current module. Not valid in unattended batch mode.

TRAces

Displays all trace breakpoints for the current module.

USING (Assembler only)

Displays outstanding USING commands that have been issued.

VERify (Assembler only)

Displays outstanding verified items and their values in the current module.

WHENs

Displays a list of all active WHEN commands for the current module.

WHERE (COBOL, PL/I, and C language only)

Displays a list of active modules, statements, and procedures.

ZAPs

Lists significant information on currently applied PTFs.

Examples

The following subsections contain examples illustrating the use of various SHOW commands.

Displaying a List of the Active Breakpoints

The SHOW BREAKS command displays a list of the after, before, and onetime breakpoints set in each module. SHOW AFTER, SHOW BEFORE, and SHOW ONETIME display a specific type of breakpoint.

Example of the SHOW BREAKS Command 

Displaying Execution Counts

The SHOW COUNTS command displays a list of the execution counts for each module for which count statistics are maintained. The counter is indicated by a 7-digit counter starting in column 74. See COUNT for more information on keeping execution counts.

Example of the SHOW COUNTS Command 

Displaying File Status Information

The SHOW DCBS or SHOW FILES commands display a list of the input and output files used by the application programs. This command is extremely useful in the event of an I/O abend. Most I/O abends are the result of either incorrect DCB attributes or missing file allocations. This display makes it easy to identify these types of errors.

Code Debug displays three status lines for each non-VSAM file. The first line contains the DCB information that was specified in the COBOL FD entry. The second line contains the DCB information from the allocation statement (the DD card in batch, the Code Debug generated file list, or the TSO ALLOCATE commands). The third line contains the DCB information as it exists in the catalog for the physical data set.

Example of the SHOW DCBS or SHOW FILES Command 

Displaying a List of Index Cells

The SHOW INDEX command presents a list of all index cells in the current module and the present value of each index. Code Debug displays both the index limit and entry number. A message is displayed stating that the entry exceeds the index limit when this occurs.

Example of the SHOW INDEX Command 

Displaying Kept Items

The SHOW KEEPS command presents a display of all data division lines that contain a variable for which a KEEP command was issued. All lines in the Source window not containing a kept variable are temporarily excluded. Explicitly kept items are indicated by a K in column 9 of the Keep window. The K (Keep) line command can be used to reorder the variables in the Keep window. The most recently kept items are shown at the bottom.

Example of the SHOW KEEP Command 

Displaying a List of Modules Loaded

The SHOW MODULES command displays a list of the CSECTs that were loaded during the current test. The list identifies each load module and the entry points for each CSECT, indicating whether an Code Debug source listing file exists for that program.

Example of the SHOW MODULES Command 

Displaying a List of Previously Executed Instructions

The SHOW PREVIOUS command displays a list of the last 100 known statements executed in your program. Code Debug maintains a list of encountered breakpoints. Only statements associated with the AFTER, BEFORE, COUNT, GO, ONETIME, SKIP, TRACE, and WHEN commands are displayed in the list. The most recent entry is at the bottom. The list will automatically scroll to this point.

SHOW PREVIOUS is useful in identifying loops and tracing the program’s recent activity at the point of an abend.

Example of the SHOW PREVIOUS Command 

Displaying the Options in Effect

The SHOW OPTIONS or SHOW SETS command displays a list of the current SET command values. Since there are more options than fit on the screen, you can scroll up and down to view the entire list.

Example of the SHOW OPTIONS Command 

Displaying Available Memory

The SHOW REGION command displays the largest contiguous memory available for testing. It provides the same function from within the test session as Code Debug option 5.1 does before entering the test session. Both display available memory.

Example of the SHOW REGION Command 

Displaying Trace Breakpoints

The SHOW TRACE command presents a display of all source lines in the current module for which a TRACE command is in effect.

Example of the SHOW TRACE Command 

Displaying and Deleting Active WHEN Conditions

The SHOW WHENS command displays a list of active WHEN conditions (Example of the SHOW WHENS Command). The D line command may be used to delete a WHEN condition. To use the command, type a D in the DEL field next to the WHEN condition that you want to delete, and press Enter.

Example of the SHOW WHENS Command 

Displaying Active Modules and Paragraph Nesting

The SHOW WHERE command presents the flow of execution from the beginning of the test. A list of the active modules and the associated paragraphs making the calls is displayed. SHOW WHERE is useful in revealing possible logic problems since it shows the strategic points within the execution path. It enables you to determine where you are within the execution path at any time and how you got there. SHOW WHERE is valid at any time.

Example of the SHOW WHERE Command 

Displaying Allocated Files or Data sets

An example of the SHOW ALLOCATES command is displayed as follows:

Example of the SHOW ALLOCATES Command 

Displaying USING Command Usage in an Assembler Program

The following shows an example of the SHOW USING command in a High Level Assembler program. Comments concerning the format are shown in parentheses.

Example of the SHOW USING Command