SET

Description

Use the SET command to override Code Debug TSO defaults. Some values are set only for the duration of the test session, while others are maintained across test sessions. All SET commands that affect module management must be in effect before loading your program into memory. This can be done by editing an INCLUDE script that contains the SET commands and specifying it on the test screen as an initial script, before entering the test session.

Parameter Group 1

Parameter Group 2

Parameter Group 3

The following are the parameter descriptions for the SET command:

ABBREV

Controls whether Code Debug will create an abbreviation for each long CSECT name it encounters (ON), or simply truncate the name (OFF).

ABBRCHAR

Species the hex representation of the character included by Code Debug when it assigns abbreviations for long CSECT names.

ABENDSCR

Valid only in an unattended batch test. Specifies an abend script to be executed when an abend occurs. Provide the member name for the abend-script. It can be any name up to eight characters. The abend script must be a member of a PDS allocated to the ddname XINCLUDE.

ABNDEXIT

Controls whether Code Debug TSO intercepts abends. If ABNDEXIT is set to ON (the default), abends are intercepted and the user is given the opportunity to correct the error if the source for the failing module is available to Code Debug. If ABNDEXIT is OFF, abends are not intercepted. Be aware that setting ABNDEXIT to OFF can result in unwanted dumps if any of the standard dump DD files have been allocated to the test session. The SET DUMP ON command is the recommended method for producing a dump. ABNDEXIT should never be SET to OFF except by Code Debug TSO technicians using it for diagnostic purposes.

For additional information about SET ABNDEXIT, see to SET#Usage Notes#Usage Notes, note 1.

AUTOCAN (COBOL only)

When AUTOCAN is set to ON, any dynamically called module not designated by the SET NOCANCEL command is deleted when control is returned to the calling module unless a breakpoint is set in it. A SET AUTOCAN command can be issued at any point within a test session. This command is valid in relation to modules compiled with OS/VS COBOL or CA-OPTIMIZER. It is not valid in VS COBOL II. The default is OFF.

SET AUTOCAN can be issued in both batch and interactive modes.

For additional information about SET AUTOCAN, see to SET#Usage Notes, note 1.

AUTOCLOS

With complex programs, an SC03 abend will occasionally occur when exiting an Code Debug test. This abend is an indication that a file has not been closed and the system is having problems closing it. This may be prevented, in certain cases, by setting AUTOCLOS ON prior to issuing EXIT from the test. This will cause Code Debug to perform closes on any DCBs left open at the end of the test, as long as the DCBs are still available. The default is OFF.

For additional information about SET AUTOCLOS, see to Usage Notes, note 1 and note 2.

AUTOKEEP

Controls whether the data referenced in the current statement is automatically displayed in a Keep window. The default is ON. To configure the window size and placement of the automatically kept items, see to the SET WINDOW AUTOKEEP/KEEP/SOURCE nnn commands.

For additional information about SET AUTOKEEP, see to SET#Usage Notes, note 1 and note 2.

AUTOSCRL

If the Automatic Keep window is off (SET WINDOW AUTOKEEP 0) but Autokeep is still active (SET AUTOKEEP ON), the automatically kept data is placed at the bottom of the regular Keep window. Enter SET AUTOSCRL ON to activate automatic scrolling of the Keep window. The Keep window will scroll to the bottom, displaying the last portion of the automatically kept data. With AUTOSCRL OFF (the default), the Keep window must be manually scrolled to display any data not currently visible.

For additional information about SET AUTOSCRL, see to SET#Usage Notes, note 1 and note 2.

BRCOV

Controls Branch Coverage for a Code Coverage test. The site default setting is determined during the installation of Code Debug using the CTLBRCOV keyword in the CMSC PARMLIB. Use this SET command to override the site default for a specific test and place it in the initial script for that test.

For additional information about SET BRCOV, see to SET#Usage Notess, note 1 and note 3.

CAPS

Controls whether Code Debug TSO converts lowercase characters to uppercase when they are entered by typing over displayed values. If the setting is changed to OFF, conversion does not take place. Use SET CAPS OFF in conjunction with SET LOWCASE ASIS if your terminal supports lowercase. Otherwise, Code Debug TSO defaults to converting user-modifiable fields to uppercase before writing to the terminal. The default is ON.

For additional information about SET CAPS, see to SET#Usage Notes, note 1 and note 2.

CARRAY

Controls how Code Debug TSO treats character arrays in the C language. Use SET CARRAY OFF to display only one character of the array at a time. Use SET CARRAY ON to convert the array to a character string, using the full array size as the data item’s length. The default is ON.

For additional information about SET CARRAY, see to SET#Usage Notes, note 1.

CBLTRAP (COBOL only)

Changing the setting from the default of ON to OFF deactivates both the Code Debug TSO support that detects missing DD statements and the support that opens windows at the bottom of the screen for files allocated to the terminal. CBLTRAP should never be SET to OFF except by Code Debug TSO site technicians using it for diagnostic purposes.

For additional information about SET CBLTRAP, see to SET#Usage Notes, note 1 and note 5.

CMDDLM (Batch Connect only)

Specifies a single character to be used as a command delimiter in the Code Debug Batch Connect environment. The default is a semicolon (;). In a chain of Code Debug commands, the specified delimiter indicates the end of one command and that any subsequent data should be treated as a new command. In the ISPF environment, the ISPF command delimiter is used instead of the CMDDLM value.

For additional information about SET CMDDLM, see under SET#Usage Notes to the portion of note 2 concerning Batch Connect.

CMDSIZE

Changes the primary command line so that it consists of one, two, or three lines. The default value is one. This keyword allows input of commands of up to 255 characters. You can default the primary command area to other than a single line by editing an INCLUDE script to contain SET CMDSIZE n and specifying the INCLUDE member as the initial script on the test screen.

For additional information about SET CMDSIZE, see to SET#Usage Notes, note 1 and note 2.

COLS

Controls whether Code Debug TSO displays a column template when browsing a data set, ddname, or AA SNAP output. The default is OFF.

For additional information about SET COLS, see to SET#Usage Notes, note 1 and note 2.

COMPARE

Controls whether Code Debug TSO uses padding characters (PAD)—or does not (NOPAD)—when doing comparisons using Code Debug TSO commands. If SET COMPARE is set to PAD and two items are compared, padding characters are used to extend the length of the shorter item to match the length of the longer one. Code Debug TSO behaves this way by default. If SET COMPARE is set to NOPAD, no padding characters are added, and Code Debug uses the length of the shorter item for the comparison. The default is PAD.

Consider an example with the variables

the WHEN statement

and the following IF statement inserted into the source:

With SET COMPARE PAD in effect, the VAR1 value is expanded to the right with blanks, and the comparison is based on the length of the longer variable:

The values are not equal, so the WHEN command will not stop the execution of the program, and the IF statement will not stop at the PAUSE statement.

With SET COMPARE NOPAD in effect, the VAR1 value is not expanded, and the comparison is based on the length of the shorter variable:

The values are equal, so the WHEN command will stop execution of the program, and the IF statement will stop at the PAUSE statement.

CONFIRM

Controls whether Code Debug TSO displays a confirmation message to remind you that breakpoints and keeps are removed when D (Delete) line commands are entered. The default is ON.

For additional information about SET CONFIRM, see to SET#Usage Notes, note 1 and note 2.

DATA xx yy (Assembler only)

Designates a line or a block of executable lines of code as data lines. Any lines that have been changed to data lines cannot have breakpoints set on them, either internally as a result of GO processing or explicitly by the user. xx indicates the starting line number and yy optionally indicates the ending line number.

If a breakpoint is set on a line, it cannot be changed to a data line. These source lines are indicated by a D on the source display. If necessary, the SET INSTR command can be used to reset these lines to executable lines of code.

For additional information about SET DATA, see to SET#Usage Notes, note 1.

DATAFIND (COBOL only)

Indicates whether the next or all data names are found on the FIND data-name command. If ALL (the default) is specified, a long message indicates the total number found. If NEXT is specified, the cursor moves to the next data name found and highlights it with an informative message in column 74.

For additional information about SET DATAFIND, see to SET#Usage Notes, note 1 and note 2.

DATETIME

If the value of DATETIME is set to OFF, a warning message (rather than a fatal message) is issued for all date/time stamp conflicts, allowing processing to continue. Date/time conflicts are detected by Code Debug TSO whenever you are setting a qualified breakpoint, or whenever the SOURCE command and the INTERCEPT command are issued.

In interactive mode, SET DATETIME can be issued at any time during a test session. It remains in effect until either another SET DATETIME command or an EXIT command is issued. The value of SET DATETIME will be reset to ON with a RETEST command. If the value of DATETIME is set to OFF and you have a conflict between the program and the source listing (the program has been altered and the source listing no longer matches the program), you can have unpredictable results, including abends. The default is ON.

For additional information about SET DATETIME, see to SET#Usage Notes, note 1.

DBCS

Controls Code Debug’s display translation of double-byte character set (DBCS) characters. The default of OFF causes DBCS characters to be removed as unprintable. Use the ON setting only if your terminal supports the display of DBCS characters. Except under Batch Connect, Code Debug automatically sets DBCS based on the value of ISPF variable ZDBCS. The Batch Connect setting is determined during the installation of Code Debug using the CTLSDBCS keyword in the CMSC PARMLIB.

For additional information about SET DBCS, see to SET#Usage Notes, note 1.

DDIGNORE

A total of 100 DDNAMEs can be specified. Code Debug TSO will not attempt to close these files if they are left open at the end of a test session.

The DDNAME-list parameter allows from 1 to 8 file names per SET command. DDNAME lists containing greater than 8 names will be truncated. The entire DDNAME-list will be ignored for a SET command that would cause the total number of specified DDNAMEs to exceed 100.

This command will replace the default DDIGNORE DDNAME list specified during the installation process, if one exists, for the current test session.

Use the SET DDIGNORE command when another program or product requires that certain files be left open after the Code Debug debugging session has finished.

DELAY

Sets the amount of time between execution of statements during a trace. You can specify a delay-value between 0 and 6 seconds in tenth of a second increments. You can omit leading and trailing zeros and a trailing decimal point. For example, the entries 0.5 and .5 are the same, as are 2.0 and 2. The default is 0.

The delay time takes effect only during a trace. You must enter the SET DELAY and TRACE commands before you press PF12 or enter GO and execute your program.

SET DELAY is not valid in an unattended batch test.

For additional information about SET DELAY, see to SET#Usage Notes, note 1 and note 2.

DUBPROCS

Workbench for Eclipseruns in a POSIX environment. When a program attempts to create another one, it fails. SET DUBPROCS ON/OFF controls the use of the set_dub_default service.
If DUBPROCS is set to ON, the current default dub setting is changed to DUBPROCESS.
If DUBPROCS is set OFF (or defaults to OFF), the default dub setting is used.
In a POSIX(ON) environment, SET DUBPROCS ON may allow for a test to run successfully, avoiding a U4083 with message CEE5101C.

DUMP

Controls whether or not a dump is produced. It has no effect on the abend intercept processing within Code Debug TSO. If DUMP is set to ON, Code Debug TSO then allows a dump to be taken when an abend occurs. A dump will only be produced if one of the standard dump DD files (SYSUDUMP, SYSMDUMP, or SYSABEND) is currently allocated to the test session. The default is OFF.

When requesting a dump, it is best to issue the SET DUMP ON command just prior to execution of the actual code that is leading to the failure so that the size and number of dumps is limited. Correctable or expected conditions may produce unwanted dumps. Once the dump has been obtained, SET DUMP OFF or EXIT the test.

In the case of an abend that occurs prior to the display of source, it may be necessary to place the SET DUMP ON command in an initial script. Under LE/370, a dump will be taken at the next breakpoint or abend.

For additional information about SET DUMP, see to SET#Usage Notes, note 1.

DYNAMIC

Allows a list of 1 to 100 module names, which are dynamically loaded during application execution.

Normally, this command is not needed if the modules are dynamically called by COBOL programs or by the module specified with a SET TRANSFER command. SET DYNAMIC is used to get control of dynamically called programs that are called by Assembler programs.

DYNTRAP (COBOL only)

Code Debug TSO loads modules dynamically called within a COBOL program, provided that Code Debug has initiated the initial program in the run-time environment. This functionality is required for full System Flow data collection.

If DYNTRAP is set to OFF, Code Debug TSO does not detect dynamically called modules. However, the specified COBOL or Assembler modules are dynamically loaded if a SET DYNAMIC module-list command is executed in conjunction with SET DYNTRAP OFF. SET DYNTRAP OFF does not override SET DYNAMIC. The default is ON.

SET DYNTRAP OFF must be included within an initial test script.

For additional information about SET DYNTRAP, see to SET#Usage Notes, note 1 and note 3.

EOTWTIME

During a Workbench test, it is possible for an END-OF-TEST (EOT) indication to be sent from the mainframe batch job to the Workbench, and for the response to get ‘lost’. This results in a ‘hang’ condition. The SET EOTWTIME command allows the user to specify the number of seconds the mainframe batch will wait for a response before ending the test. The default, if no SET command is entered, is 5 seconds. The allowable values are from 1 to 99 seconds inclusive.

ESPIE

Code Debug TSO activates its own ESPIE (SET ESPIE ON) processing routine to detect S0C1 abend conditions (possible breakpoint) and to handle the condition if it is a breakpoint. An S0C1 abend that is not identified as a breakpoint will then be handled according to the setting of ABNDEXIT (ON or OFF). If needed, the SET DUMP ON command can be used to get a dump of an S0C1 abend, assuming that a dump DD file has been allocated. The default is ON.

For additional information about SET ESPIE, see to SET#Usage Notes, note 1.

EXCLUDE

A total of 100 modules can be excluded. Code Debug TSO will not intercept calls to these modules or any call to subordinate modules.

The module-list parameter allows 1 to 8 module names per SET command. Module name lists containing more than 8 names will be truncated. The entire module-list will be ignored for a SET command if it would cause the total number of excluded modules to exceed 100.

The SET EXCLUDE command will replace, for the current test session, the default exclude module list specified during the installation process, if one exists.

Use the SET EXCLUDE command when testing programs that use nonstandard communications between modules, such as a statically-linked assembly program loading an address and branching to a subprogram, or a COBOL or PL/I program for which you have stubbed out subroutines at link time.

The SET EXCLUDE command must be in effect before the module is loaded in memory. To do this, create an INCLUDE script to contain SET EXCLUDE module-list and specify that INCLUDE member as the initial script on the test screen.

For additional information about SET EXCLUDE, see to SET#Usage Notes, note 3.

GEN (Assembler and COBOL only)

Assembler macro statements as well as COBOL EXEC DLI and EXEC SQL statements can be automatically displayed either collapsed or expanded during the initial source display. The default is OFF. The setting of this option, prior to displaying the source, determines if these statements should be expanded (GEN ON) or collapsed (GEN OFF). This option only affects automatic statement expansion or collapse upon the initial display and does not affect the current source display. The GENERATE and DELETE GEN commands can be used to interactively expand or collapse these statements either globally, individually, or in groups.

For additional information about SET GEN, see to SET#Usage Notes, note 1 and note 2.

HANDLER

Changes Code Debug’s method of intercepting application abends. The default value is 0 (zero) in environments without a VisualAge PL/I element. This causes Code Debug to wait until all applicable user condition handlers (UCHs) have been executed before it presents a program-check abend to the user.

A setting of 1 will cause a program-check abend to be presented to the user after a single execution of the handlers, when the condition would typically get promoted. This is intended for use in environments such as Visual-Age PL/I, where the user intends to interactively recover from a program-check before any cleanup is done by Language Environment. This setting is only effective when LETRAP is set to ON.

For additional information about HANDLER, see to SET#Usage Notes, note 1.

HEXMODE

When HEXMODE is set to ON, any nondisplayable characters resulting from a KEEP or PEEK command entry are represented in hexadecimal format in the session log. The hexadecimal characters are presented beneath the character used to depict a nondisplayable character. The SET HEXMODE command affects only the session log display. The default is OFF.

The SET HEXMODE ON command is equivalent in function to using the KEEPH and PEEKH commands. Setting HEXMODE to ON is especially useful in batch mode. Since the session log is reviewed after the test, SET HEXMODE ON ensures that sufficient information is provided when an unexpected nonrepresentable character is encountered in a displayed value.

For additional information about SET HEXMODE, see to SET#Usage Notes, note 1 and note 2.

INSTR xx yy (Assembler only)

Resets as executable code a data line or a block of data lines previously changed using the SET DATA command. xx indicates the starting line number and yy optionally indicates the ending line number. After entering this command, breakpoints can once again be set on these lines.

For additional information about SET INSTR, see to SET#Usage Notes, note 1.

LANGUAGE

Sets the language that Code Debug will use for its messages. The default for the SET LANGUAGE command is ENGLISH. Code Debug automatically sets LANGUAGE based on the value of ISPF variable ZLANG, except under Batch Connect. The Batch Connect setting is determined during the installation of Code Debug using the CTLSLANG keyword in the CMSC PARMLIB.

For additional information about SET LANGUAGE, see to SET#Usage Notes, note 1.

LELNKLST

When LELNKLST is set to ON, Code Debug TSO will attempt to load Language Environment modules from the LINKLIST when they cannot be found in the libraries specified in the user's setup.

LESTOROV

To support ATTENTION key processing when LETRAP is ON, the Reserve_Size value in the Language Environment STORAGE option must be at least 8K. Code Debug sets this value and marks the setting NONOVR, which implies that the STORAGE option cannot be overridden during the test. If a site or user wishes to change any sub-option of the STORAGE option during a test, the Code Debug default behavior must also be changed. This is done by setting LESTOROV to ON in an initial script, or by using the CTLLESTO keyword in the CMSC PARMLIB. The default if OFF.

For additional information about SET LESTOROV, see to SET#Usage Notes, notes 1 and 3.

LETRAP

Sets the run-time Language Environment TRAP option. If LETRAP OFF is specified, TRAP is set to OFF and Code Debug’s abend and interrupt usage of ESPIE and ESTAE processing is activated. This prevents the LE handlers and user handlers that rely on ESPIE and ESTAE from getting control. Signal conditions are unaffected. If the SET LETRAP OFF option is to be used for the current test, it must have been placed in an initial script that was executed at run time or stored in the user profile from a previous test. The default is ON.

For additional information about SET LETRAP, see to Usage Notes.

LNKLST

When LNKLST is set to ON, Code Debug TSO will attempt to load modules from the LINKLIST when they cannot be found in the libraries specified in the user's setup.

LOG

Specifies if writing to the session log data set is active. The default is ON. This option is not maintained across test sessions.

If one of the following additional parameter is specified, writing to the session log data set will be activated for only that function:

• 
  
  • AUTOKEEP
  • FIND (default is OFF)
  • INSERT
  • KEEP
  • MEMORY
  • PEEK
  • VERIFY

Notice that the default for SET LOG FIND is OFF.

For additional information about SET LOG, see to SET#Usage Notes, note 1 and note 2.

LOGSIZE

Determines the size of the data generally written to the session log file. The SET LOGSIZE command can be used to override the default session log size. The default for batch mode testing is 132. For TSO, the default is 80. You can change the size of the session log file at any point within a test session.

Left and right scrolling is supported when viewing the session log.

For additional information about SET LOGSIZE, see to SET#Usage Notes, note 1.

LOWCASE

Specifies how lowercase letters found in the values of items are to be displayed. The Batch Connect default is determined during the installation of Code Debug using the CTLLOWCS keyword in the CMSC PARMLIB. The current setting for all other test environments is kept as a variable in the user’s profile, associated with Code Debug, and retained until specifically altered. The options are:

CONVERT

Show lowercase characters from the user source code in uppercase.

ASIS

Display all lowercase characters if they exist.

NONE

Show source display and all Code Debug secondary source screens in uppercase, allowing no lowercase English characters to be displayed on the screen.

KANA

Does everything that option NONE does, as well as specifies all uppercase using the Katakana character translation tables.

LOCAL

Displays characters in their native representation. The command can be used for international language character sets and forces Code Debug not to translate non-English characters to blanks. SET TRANSLATE can be used for any additional characters that do not display.

For additional information about SET LOWCASE, see to SET#Usage Notes, note 1 and note 2.

MODE

Controls whether Code Debug displays only the low-order 32 bits or all 64 bits of General Purpose Registers and addresses for programs running on a z/Architecture processor. The default is 32.

NESTED

Limits the number of levels of nested application program calls that Code Debug will accept. Program nesting is when one program calls another program that subsequently calls a third program, etc. When a called program returns to its caller, the level of nesting is reduced by one. The default is 99.

For additional information about SET NESTED, see to SET#Usage Notes, notes 1, 2, and 3.

NOCANCEL (COBOL only)

Excludes listed modules from automatic cancellation. You need to use this setting only if you are using SET AUTOCAN ON to cancel dynamically called modules.

From one to 100 module names can be specified. A module specified with NOCANCEL can contain the wildcard character (*). For example, if you enter SET NOCANCEL ABC*, then modules beginning with the characters ABC are not cancelled.

NOCOVER

Allows a list of one to 100 module names which are not to be monitored during a code coverage test. Code Debug TSO does not record execution statistics or write any results to a repository for the specified modules.

Use the SET NOCOVER command when performing a code coverage test with multiple modules to exclude any modules from the code coverage process. This might occur because a module has already been thoroughly tested, statistics are not desired, another user is responsible for testing the module, or the module was coded using non-standard practices or attributes not supported by Code Debug.

If there are modules within a test which have no corresponding DDIO member allocated to the test, performance can be improved by specifying the SET NOCOVER command for such modules, because the DDIO files won’t be scanned for the existence of source.

In order to exclude a module from monitoring during a code coverage test, the SET NOCOVER command must be issued before the module is loaded. This can be assured by including the command in an initial script.

The slash (/) character can be used as a terminating wildcard to cause the match to occur only on the prefix characters preceding the slash. For example:

could be used to exclude from monitoring any module whose name begins with the characters PGM12 (such as PGM123, PGM12ABC, PGM12, etc.).

The NOCOVER setting and the ONLYCOV setting are mutually exclusive. Setting one will cause previous settings of the other to be deleted, and thus ignored from that point in a test session.

ONLYCOV

Allows a list of one to 100 module names that are to be monitored during a code coverage test. Code Debug TSO will record execution statistics and write any results to a repository only for the specified modules.

Use the SET ONLYCOV command when performing a code coverage test with multiple modules to limit the number of modules included in the coverage process. This is generally done to reduce execution time and resource utilization.

In order to avoid including undesired modules in the coverage process, the SET ONLYCOV command must be issued before the module is loaded. This can be assured by including the command in an initial script.

The slash (/) character can be used as a terminating wildcard to cause the match to occur only on the prefix characters preceding the slash. For example:

could be used to only include in the monitoring process any module whose name begins with the characters PGM12 (such as PGM123, PGM12ABC, PGM12, etc.).

The ONLYCOV setting and the NOCOVER setting are mutually exclusive. Setting one will cause previous settings of the other to be deleted, and thus ignored from that point in a test session.

NOINIT (COBOL only)

Controls whether a linkage section is initialized to binary zeros or to spaces and zeros when a subroutine is tested standalone. The default is OFF. This parameter must be used in an initial script.

For additional information about SET NOINIT, see to SET#Usage Notes, note 1 and note 3.

NONDISP

Changes the character used to represent nondisplayable characters. You can change the default value, a period (.), to any displayable character. Both the session log and the interactive display show the specified character in replacement of any nondisplayable character encountered whenever a KEEP or PEEK command is entered.

The current value of char can be displayed with a SHOW OPTIONS or SHOW SETS command.

For additional information about SET NONDISP, see to SET#Usage Notes, note 1 and note 2.

PFnn

Changes the setting of the specified PF key. To see the current settings, enter the SHOW OPTIONS, SHOW PFKEYS, or SHOW SETS command.

The following table lists the default values for each of the PF keys. 

The SET PFnn command has no effect when used under ISPF Batch Connect. It is only applicable to ROSCOE Batch Connect users.

For additional information about SET PFnn, see to SET#Usage Notes, note 1 and note 2.

PREINIT

Informs Code Debug whether LE pre-initialization is going to be employed in the user’s application. If CEEPIPI is going to be invoked to pre-initialize the LE environment of a module which is going to be debugged, SET PREINIT ON must be specified in an initial script. The default is OFF.

PREVIOUS

Sets the number, nnnn, of previous breakpoint statements that will be displayed when the SHOW PREVIOUS command is entered. Valid values are from 0001 to 9999. The default is 0100.

REFRESH

Controls whether the entire screen should be updated at every write to the terminal. The default is OFF.

For additional information about SET REFRESH, see to SET#Usage Notes, note 1.

REVSIZE (COBOL only)

If MONITOR is set ON, you can use the SET REVSIZE command to set the review log to a size appropriate to your program. The default is 1M. K represents 1024 bytes, and M represents 1024K (1048576 bytes). The maximum value allowed is 2047M. It is recommended that you reduce the size only if you have storage constraints above the 16MB line. If REVSIZE is set too low and you use up the available space, the buffer is overwritten and you receive the message AT OLDEST RETAINED EXECUTION POSITION.

For additional information about SET REVSIZE, see to SET#Usage Notes, note 1.

RTEREUS

At some sites, the COBOL run-time option, RTEREUS, is set to ON by default. This may have adverse effects on your Code Debug TSO test. To disable it, include the SET RTEREUS OFF command in an initial script. This command will have no effect if the COBOL run-time option is already OFF.

The SET RTEREUS ON command allows the default setting of the RTEREUS COBOL run-time option to be used during the test. It does not set the RTEREUS COBOL run-time option to ON.

For additional information about SET RTEREUS, see to SET#Usage Notes, note 1 and note 2.

STATIC

Code Debug TSO intercepts external references within a load module or program object which was loaded by Code Debug. This functionality is required for full System Flow data collection.

SET STATIC IGNORE0 (the default) allows Code Debug TSO to intercept all resolved external references, but not the unresolved external references. If STATIC is set to ON, Code Debug TSO will replace all external references with the address of Code Debug TSO’s Static Control Block. If STATIC is set to OFF, Code Debug TSO leaves all external references alone.

For additional information about SET STATIC, see to SET#Usage Notes, note 1 and note 3.

TDODDXCL

A total of 100 DDNAME/DBDNAMEs can be specified. Code Debug TSO will ignore files with these names when collecting Test Data Optimization information.

The DDNAME/DBDNAME-list parameter allows from 1 to 8 file names per SET command.

Lists containing greater than 8 names will be truncated. The entire list will be ignored for a SET command that would cause the total number of specified DDNAME/DBDNAMEs to exceed 100.

This command will replace the default CTLDDTDX DDNAME/DBDNAME list specified during the installation process, if one exists, for the current test session.

TEMPLATE

By default, Code Debug TSO displays a column template when displaying data items in both the source and session log displays. The template is a dashed line showing column positions and is helpful for aligning characters during data entry. The length of the column template corresponds to the length of the data area. You can disable this feature with the SET TEMPLATE OFF command. Once issued, any items added to the KEEP window will not have a column template. At any time, you may add a column template to an item in the KEEP window with the T line command. You can also remove the column template with the DT line command.

For additional information about SET TEMPLATE, see to SET#Usage Notes, note 1 and note 2.

TERMPAGE (COBOL only)

The TERMPAGE value is used as the source code page value when converting COBOL data items to COBOL National (Unicode) data items. The target code page value is always 1200.

The TERMPAGE value must be numeric, greater than zero but less than 65536, and 1 to 5 digits long. The original value for TERMPAGE is retrieved from the ISPF variable ZTERMCID. If the ZTERMCID value is zeros, the TERMPAGE value will default to 037. Verification of the TERMPAGE as a valid code page is not done.

For additional information about SET TERMPAGE, see to SET#Usage Notes, note 1.

TRANSFER

SET TRANSFER is used to specify the name of an interface module that dynamically loads application modules. The transfer module must be an Assembler module that dynamically calls a program. The first parameter passed to it must be the eight-character name of the program it is to call, followed by any parameters needed by that program.

TRANSLATE

Allows you to override how non-alphanumeric characters are displayed. The hexadecimal value yy is substituted for hex value xx. Specifying ND causes the current NONDISP character to be substituted for hex value xx. RESET causes any previously entered TRANSLATE command for hex value xx to be undone, allowing the original default substitution to occur. Omitting the second parameter causes hex value xx to be replaced with hex value xx, which might be used when the NONDISP character defaults as the replacement character for hex value xx.

Setting TRANSLATE OFF causes all previously-entered TRANSLATE overrides to be disabled, while retaining the previously-requested values.

The current settings of TRANSLATE can be displayed with a SHOW OPTIONS or SHOW SETS command.

For additional information about SET TRANSLATE, see to SET#Usage Notes, note 1 and note 2.

UNCHNGED

When the value of one or more kept items has changed since the most recent interrupt (breakpoint, when, etc.), those values are written to the session log. The values of any other kept items are shown in the session log as UNCHANGED. Specifying SET UNCHNGED OFF causes Code Debug to write the values of all kept items to the session log regardless of whether or not those values have changed. The default is ON.

For additional information about SET UNCHNGED, see to SET#Usage Notes, note 1.

WIDEHEX

Controls whether Code Debug TSO uses entire lines to show HEX data. The default, OFF, will display data in the Keep window to the right of the variable name. SET WIDEHEX ON will use the entire lines under the variable name to display the data. If WIDEHEX is set to ON, a minimum Keep window size of 5 lines is required. The Keep window can be adjusted with the SET WINDOW KEEP command. The current setting for this option is retained across test sessions until it is specifically changed.

WINDOW

Allows you to adjust the size of the Automatic Keep window, the Keep window, or the minimum size of the source display. SET WINDOW requires one of the following parameters:

AUTOKEEP

Allows you to adjust the size of the Automatic Keep window and determine the placement of the automatically kept items. The variable nnn specifies the number of lines in the window. SET WINDOW AUTOKEEP 0, the default, displays automatically kept data in the Keep window at the top of the source display. If you want a separate window for automatically kept items, specify SET WINDOW AUTOKEEP nnn to set a fixed size Automatic Keep window of nnn lines at the bottom of your source display. If you want a separate window but want to see as much of your source as possible, you can use the MAX parameter and specify SET WINDOW AUTOKEEP MAX nnn to set an adjustable size Automatic Keep window at the bottom of the screen that dynamically expands up to nnn lines.

KEEP

Allows you to adjust the size of the Keep window. The variable nnn specifies the number of lines in the window. If the MAX parameter is specified (for example, SET WINDOW KEEP MAX nnn), an adjustable size Keep window that dynamically expands up to nnn lines is set. If the MAX parameter is not specified (for example, SET WINDOW KEEP nnn), a fixed size Keep window of nnn lines is set. If the OFF parameter is specified for the window size (for example, SET WINDOW KEEP OFF), the Keep window is not displayed. The default is 5.

SOURCE

Allows you to set the minimum size of the source display. The variable nnn specifies the minimum number of lines to display. For example, SET WINDOW SOURCE 3 sets a minimum of three source lines to be displayed. The source window will expand as much as possible depending on the maximum size of the Keep and Automatic Keep windows. The default is 3.

For additional information about SET WINDOW, see to SET#Usage Notes, note 1 and note 2.

Usage Notes

1. Defaults for all SET commands are in effect until values are changed.
2. The current setting for this option is kept in the user’s ISPF profile, allowing this option to be retained across test sessions initiated through ISPF. Thus, the setting is retained until it is specifically changed. Batch Connect settings always return to their default values when a new test is initiated.

3. The following SET commands, if used, must be entered within an initial test script that is executed before run time:

   SET STATIC OFF
   SET EXCLUDE module-list
   SET DYNTRAP OFF
   SET NESTED nnn
   SET NOINIT ON
   SET LESTOROV ON
   SET LETRAP OFF (unless it was previously stored in the profile)
   SET BRCOV OFF
   SET PREINIT ON
   SET DUBPROCS ON
4. The SET LETRAP ON/OFF option controls the trap option of LE. ESPIE exits are not used to capture abends by LE when LETRAP is OFF. With LETRAP OFF, LE will not interfere with normal Code Debug TSO breakpoint processing. With LETRAP ON, LE will get control at each breakpoint and then pass control to Code Debug TSO. Specifying LETRAP ON also allows the user to diagnose condition handling routines within an LE environment and is recommended in an XPLINK environment in which stack-extension could occur.
   A limitation to Code Debug TSO with LETRAP ON and condition handling debugging exists. The user must set a breakpoint at the beginning of the condition handling routine and cannot set a breakpoint on the instruction that causes the abend for the condition handler. This includes the use of GO 1 to enter the condition handler abend. This restriction exists as a result of conflicts between Code Debug TSO and LE in catching abends.
   When the LETRAP command is issued, that option is saved in the ISPF profile for the specific user who issued the command. That user must re-issue the LETRAP command to change the option. The LETRAP command affects all Code Debug test profiles for the user who issues it and remains in effect from one ISPF session to the next.
5. The SET CBLTRAP ON/OFF command is automatically set to OFF during MPP and HOGAN tests.

Examples

1. To specify a list of dynamically called modules, enter:
      SET DYNAMIC MODULE1 MODULE2 MODULE3
2. To change the value of a PF key, enter:
      SET PF16 KEEP CSR