Default Member XDGB00

This section describes each global parameter. The default values listed are those in DBUGGBL.

Where default values are given within parenthesis, the value:

• XPED_USER corresponds to the setting for users of the Code Debug CICS transaction XPED
• XPRT_USER corresponds to the setting for users of the Code Debug CICS transaction XPRT
• XPSP_USER corresponds to the setting for users of the Code Debug CICS transaction XPSP.

Where parameter names end with:

• XPED_USER, the value is the setting for users of the Code Debug CICS transaction XPED
• XPRT_USER, the value is the setting for users of the Code Debug CICS transaction XPRT
• XPSP_USER, the value is the setting for users of the Code Debug CICS transaction XPSP.

ACTIVATE_CODE_COVERAGE_AT_INITIALIZATION

Default:YES

Controls whether or not Code Coverage will be activated for use with Code Debug CICS. Valid values are:

• YES: Code Coverage should be activated at Code Debug CICS initialization. Your site must be licensed for Code Coverage in order for it to be activated.
• NO: Code Coverage should not be activated at Code Debug CICS initialization.

ALLOW_FORCE_PARM_FOR_XPOF

Default:YES

The risk inherent in forcing Code Debug termination may be unacceptable in some environments. Enter NO to disallow the use of the FORCE parameter with the product termination transaction XPOF.

ALLOW_RESUME_FROM_ABEND

Default:YES

Enter YES to be able to resume from an abend condition. This has no effect on resuming from breakpoints.

AUTO_SELECT_ABENDS_FROM_ANOTHER_TERMINAL

Default:YES

Enter NO to disable automatic selection of abends generated from another terminal.

AUTOMATIC_TRAP_ACTIVATION_CHECK_SECURITY

Default:YES

Enter YES to make Code Debug check the security access of the user before trapping a transaction abend with Automatic Trap Activation (ATA). Enter NO to make Code Debug skip the security access check, but remember that this can result in an unauthorized user being given access to Code Debug features when ATA traps an abend.

AUTOMATIC_TRAP_ACTIVATION_EXCLUDE_PROGS

Default:No entries

Enter the name of a program to be excluded from Automatic Trap Activation (ATA) trapping. If multiple programs are to be excluded, code multiple occurrences of this parameter. For example:

AUTOMATIC_TRAP_ACTIVATION_EXCLUDE_TRANS

Default:No entries

Enter the transaction identifier to be excluded from Automatic Trap Activation (ATA) trapping. If multiple transactions are to be excluded, code multiple occurrences of this parameter. For example:

AUTOMATIC_TRAP_ACTIVATION_NOTIFY_USER

Default:YES

Enter YES to display a user notification screen when Automatic Trap Activation (ATA) traps a transaction abend. Enter NO to not display the screen. The user notification screen tells the user their transaction has abended and explains how to continue. It can be customized with the AUTOMATIC_TRAP_ACTIVATION_TEXT_LINE_1, AUTOMATIC_TRAP_ACTIVATION_TEXT_LINE_2, and AUTOMATIC_TRAP_ACTIVATION_TEXT_LINE_3 global parameters. A help screen is available by entering HELP in the COMMAND field or by pressing the HELP PF key (default PF1).

AUTOMATIC_TRAP_ACTIVATION_TEXT_LINE_1
AUTOMATIC_TRAP_ACTIVATION_TEXT_LINE_2
AUTOMATIC_TRAP_ACTIVATION_TEXT_LINE_3

Default:‘ ’, ‘ ’, ‘ ’

Enter any three lines of text, one per parameter, to be displayed on the Automatic Trap Activation (ATA) user notification screen described in AUTOMATIC_TRAP_ACTIVATION_NOTIFY_USER above. Up to 75 characters can be entered for each parameter, or up to 72 characters if using the Global Override Facility.

The text is centered and highlighted by default. To turn off highlighting, enter a period (.) as the first character. To turn off centering, enter a left brace ({) as the first character. To turn off both highlighting and centering, enter a left parenthesis ( as the first character.

AUTOMATIC_TRAP_ACTIVATION_TRAN_TO_RUN

Default:OFF

Enter the Code Debug initialization transaction (XPED, XPRT, or XPSP) to be run when a user transaction abend is trapped by Automatic Trap Activation (ATA). Enter OFF to disable ATA.

CAN_ACCESS_NEWCOPY_SCREEN

Default:YES

Controls whether Code Debug CICS users can specify programs for PHASEIN using the NEWCOPY Programs (1.N) screen. Enter YES to make the 1.N screen accessible to all users. Enter NO to make the 1.N screen inaccessible to all users.

CAN_UPDATE_DATA_IN_DIAGNOSIS_MODE

Default:(XPED_USER,XPRT_USER,XPSP_USER)

Enter XPED_USER, XPRT_USER, or XPSP_USER to cause the corresponding transaction to start Code Debug in Normal Mode. The user will be able to update storage values or perform certain other standard operating mode functions. Omitting a value will cause Code Debug to start in Diagnosis Mode for the specified transaction. As an example, (XPED_USER,XPSP_USER) will cause XPRT users to start Code Debug in Diagnosis Mode. The user will be unable to update storage values or perform certain other standard operating mode functions. To cause all users to run in diagnostic mode, enter ().

 For more information about restricted operating modes, see Configuring-Restricted-Operating-Modes.

CAN_USE_ACCESS_COMMAND

Default:(XPED_USER,XPRT_USER,XPSP_USER)

Enter XPED_USER, XPRT_USER, or XPSP_USER to enable use of the ACCESS command for the specified transaction. Omitting a value will disable use of the command for the specified transaction. As an example, (XPED_USER,XPSP_USER) will disable use of the command for users of the XPRT transaction. To disable all users, enter ().

CAN_USE_ALLOW_COMMAND

Default:(XPSP_USER)

Enter XPED_USER, XPRT_USER, or XPSP_USER to enable access to the ALLOW command for the specified transaction. Omitting a value will disable use of the command for the specified transaction. The default is to enable only XPSP users to use the ALLOW command. To disable all users, enter ().

CAN_USE_MONITOR_AND_REVERSE_COMMANDS

Default:YES

Enter NO to disable use of the MONITOR and REVERSE commands. For information about controlling storage utilization, see MONITOR_MAX_STG_ABOVE_BAR. For information about MONITOR and REVERSES, see Code Debug CICS Reference space.

CHECK_ASSEMBLER_PROGRAM_TIMESTAMP

Default:YES

Indicates whether the time stamp will be checked when source listings are loaded. Enter YES if the time stamp information is required to match an Assembler module to a source listing. If no time stamp is found in the module or CSECT, and CHECK_ASSEMBLER_PROGRAM_TIMESTAMP=YES, it is treated as a time stamp mismatch, and source support will not be available.

If you postprocess using the Assembler option LOAD, enter a CWPLOAD DD statement in the language processor JCL to place a time stamp in the module. If you postprocess with the DECK option, enter CWPDECK and CWPWRK5 DD statements in the language processor JCL to place a time stamp in the module.

CHECK_FOR_SUBSCRIPT_OUT_OF_BOUNDS

Default:YES

If the value of CHECK_FOR_SUBSCRIPT_OUT_OF_BOUNDS is YES, then Code Debug CICS will check if the upper bound of subscripts has been exceeded. If it has, the informational message SUBSCRIPT OUT OF BOUNDS will be displayed. If the value of CHECK_FOR_SUBSCRIPT_OUT_OF_BOUNDS is NO, the upper bounds check will not be performed.

CHECK_PL1_PROGRAM_TIMESTAMP

Default:YES

Indicates whether the time stamp will be checked when source listings are loaded. Enter YES if time stamp information is required to match a PL/I module to a source listing. If no time stamp is found in the module, and CHECK_PL1_PROGRAM_TIMESTAMP=YES, it is treated as a time stamp mismatch, and source support will not be available for the module. The PL/I compiler installation option TSTAMP determines whether the compiler places a time stamp in the module.

When postprocessing with the TSTAMP installation option not active:

• If you use the PL/I option OBJECT, enter a CWPLOAD DD statement in the language processor JCL to place a time stamp in the module.
• If you use the PL/I option DECK, enter a CWPDECK DD statement in the language processor JCL to place a time stamp in the module.

CODE_COVERAGE_START_XPEDITER_NORMALLY

Default:YES

Enter NO to cause Code Coverageto start Code Debug CICS in Diagnosis Mode. The user will be unable to update storage values or perform certain other standard operating mode functions.

For more information about restricted operating modes, see Configuring-Restricted-Operating-Modes.

COMMAND_AUDIT_TRAIL_ENABLED

Default:NO

Enter YES to enable an audit trail for selected Code Debug debugging commands. If the debugging audit trail is enabled, MXDAUnnnn messages will be written to the transient data queue specified by the COMMAND_AUDIT_TRAIL_TDQUEUE_NAME global parameter.

COMMAND_AUDIT_TRAIL_TDQUEUE_NAME

Default:CSMT

Enter a four-character transient data destination for the debugging audit trail messages if COMMAND_AUDIT_TRAIL_ENABLED is YES. Member CSDXDFIL in SMXDSAMP contains a sample resource definition named XAUD.

DBPA_REPORT_ALLOCATION

This parameter has been deprecated.

DBPA_REPORT_DDNAME

Default:XDBR

A one- to four-character transient data queue name that the BMC PARMLIB report (Code Debug CICS System Facilities and Code Coverage Test Parameters) is written to.

DBPA_REPORT_SYSOUT_CLASS

This parameter has been deprecated.

DEFAULT_SCROLL_VALUE

Default:CSR

Enter a scroll type. Valid entries are:

• CSR: Scrolling based on the cursor location
• HALF: Half-screen scrolling
• nnnn: Number of lines to scroll
• PAGE: Full-screen scrolling.

DISPLAY_LISTING_WHEN_LANG_PROC_MAX_RC

Default:4

Enter the maximum return code allowable from the compile or BMC AMI Common Shared Services language processor. If the return code in the source listing file exceeds the specified value,Code Debug CICS will not display the source listing. Valid values are 0 to 8.

DOCUMENT_PACKAGING_UTILITY_DESTINATION

This parameter has been deprecated.

DYNAMIC_TRANSACTION_ROUTING_SUPPORT

Default:NO

Enter YES to activate support for dynamic transaction routing under Code Debug CICS CICSPlex support. The XSIT transaction cannot be used to override this parameter.

DYNAMIC_TRANSACTION_ROUTING_TRACE

Default:NO

Enter YES to activate support for dynamic transaction routing trace under Code Debug CICS CICSPlex support when DYNAMIC_TRANSACTION_ROUTING_SUPPORT=YES.

ENABLE_DYNAMIC_FILE_DEF_FOR_SLS_FILES

Default:NO

SLS (source listing support) file definitions can be created dynamically during Code Debug CICS initialization. This option requires an SLS file with a data set name that relates to the load library data set name with “SSD” either replacing the last qualifier or being appended to it. For example, if a load library is named ACME.PAYROLL.LOADLIB, then the related SLS file would be named either ACME.PAYROLL.SSD or ACME.PAYROLL.LOADLIB.SSD. Enter YES to enable the dynamic file definitions or NO to disable this feature.

ENABLE_GLOBAL_USER_SIGN_OFF_EXIT

Default:NO

Enter YES to enable the XSNOFF global exit when Code Debug CICS initializes. Valid values are:

• YES: Code Debug CICS should enable the XSNOFF exit
• NO: Code Debug CICS should not enable the XSNOFF exit.

ENABLE_SETTING_BREAKPOINTS

Default:YES

Enter NO to prohibit setting breakpoints.

ENABLE_TERMINAL_READ_FULL_BUFFER

Default:YES

Enter NO to prohibit Code Debug CICS from reading full buffers from 3270 control units. Specifying NO disables the Last 3270 Screen facility. TCAM users must specify ENABLE_TERMINAL_READ_FULL_BUFFER=NO.

ENABLE_UPDATE_PASSWORD_FIELD

Default:()

Enter XPED_USER, XPRT_USER, or XPSP_USER to enable the display and use of an update password on selected screens. Omitting a value will disable access for the specified transaction. As an example, (XPED_USER,XPSP_USER) will disable the display and use of an update password on selected screens for users of the XPRT transaction. To disable all users, enter (). For information on password security and this parameter, see Implementing the Memory Update Security Exit.

ENABLE_UTILITIES_MODE

Default:NO

Enter YES to designate Utilities Mode operation. Users will only have access to the file utility, storage display facility, and source listing utility, and Code Debug’s exits will be disabled.

For more information about restricted operating modesSee Configuring-Restricted-Operating-Modes . The XSIT transaction cannot be used to override this parameter.

END_SESSION_FIELD_VALUE_ON_EXIT_SCREEN

Default:NO

Enter NO to make NO the default value displayed in the END SESSION field of the EXIT SESSION screen (X). Enter YES to make YES the value displayed.

ESD_CACHE_BUFFER_SIZE

Default:500

Designates the cache buffer size in kilobytes. The storage is acquired above the 16MB line. The cache buffer saves the ESD information in most recently used order. The minimum size should be at least 100K. If you set the parameter to 0, the ESD information is not cached. The XSIT transaction cannot be used to override this parameter.

EXCLUDE_ABEND_CODE_FROM_BEING_TRAPPED

Default:No user entries

Enter one or more abend codes to be excluded from Code Debug’s automatic abend trapping function using the following format:

EXCLUDE_ABEND_CODE_FROM_BEING_TRAPPED=abend_code

Repeated lines can be used to build a list of excluded abend codes. An asterisk (*) can be used to specify all abend codes starting with the same characters, but full wildcarding is not supported. For example:

Previous entries added with the override facility or the XSIT transaction can be deleted by specifying the following entry on a single line:

In addition to the abend codes specified, there are system-defined entries that cannot be removed.

EXIT_COMMAND_GOES_BACK_TO_CICS

Default:YES

Enter NO to go to the Exit Session screen on an EXIT command. Enter YES to go directly to CICS on an EXIT command.

FILE_UTILITY_AUDIT_TRAIL_ALLOC_TYPE

Default:CYL

Enter CYL to specify cylinders as the space unit for the primary and secondary allocation of the File Utility Audit Trail GDG data set. Enter BLK to specify blocks or TRK to specify tracks.

FILE_UTILITY_AUDIT_TRAIL_BASE_DSN

Default:XD.LOG.DATA SET.GDGNAME

Enter the base data set name to be used for the File Utility Audit Trail GDG data set. Each time the data set is allocated, its generation number is incremented by 1, effectively creating a new generation of the data set. Before the data set can be used, its model DSCB must be defined with the JCL in member DEFLOGDG.

For more information, see Configuring-the-File-Utility-Audit-Trail.

FILE_UTILITY_AUDIT_TRAIL_BLKSIZE

Default:27930

Enter a decimal integer value (2-byte binary value), divisible by 133, in the range of 133 to 32718 for the blocksize of the File Utility Audit Trail GDG data sets. If the value entered is not divisible by 133, the closest value which is will be substituted. The default of 27930 sets up half track blocking on 3390 DASD.

FILE_UTILITY_AUDIT_TRAIL_DDNAME

Default:DYNAMIC

Enter DYNAMIC to specify dynamic allocation of the File Utility Audit Trail GDG data sets. The data set will be given the name specified in FILE_UTILITY_AUDIT_TRAIL_BASE_DSN.

Enter a 1- to 8-character ddname only if dynamic allocation is not allowed at your site. If a ddname is used, you must add a DD statement to your CICS startup JCL indicating the name of your File Utility Audit Trail GDG data set.

For more information, see Configuring-the-File-Utility-Audit-Trail.

FILE_UTILITY_AUDIT_TRAIL_DELETED_RECORDS

Default:FULL

Enter FULL to write File Utility Audit Trail entries that include the entire contents of deleted records when those records are deleted using the Code Debug File Utility. This logging does not include mass deletes such as those of temporary storage queues or child segments deleted when a parent segment is deleted. Enter NONE to write those entries with only the report heading and the record key.

FILE_UTILITY_AUDIT_TRAIL_ENABLE

Default:NO

Enter YES to enable the File Utility Audit Trail. Enter NO to disable the File Utility Audit Trail.

For more information, see Configuring-the-File-Utility-Audit-Trail.

FILE_UTILITY_AUDIT_TRAIL_NEW_RECORDS

Default:FULL

Enter FULL to write File Utility Audit Trail entries that include the entire contents of new records when those records are created using the Code Debug File Utility. Enter NONE to write those entries with only the report heading and the record key.

FILE_UTILITY_AUDIT_TRAIL_NON_SMS_DSCB

Default:blanks

If your site wants to allocate a File Utility Audit Trail GDG data set on non-SMS controlled DASD, enter a 1- to 44-character name for the DSCB on which to model the GDG data set. You can specify either a model DSCB residing on the same catalog volume as your base GDG definition, or a fully qualified existing GDG data set name. For information on the definition and use of GDG data sets in a non-SMS environment, see to the z/OS MVS JCL User’s space.

FILE_UTILITY_AUDIT_TRAIL_PRIMARY_ALLOC

Default:10

Enter a decimal integer value (3 byte binary value) in the range of 3 to 8,388,607 to specify the number of space units (cylinders, tracks, or blocks) in the primary allocation of the File Utility Audit Trail GDG data set.

FILE_UTILITY_AUDIT_TRAIL_SECONDARY_ALLOC

Default:5

Enter a decimal integer value (3 byte binary value) in the range of 1 to 8,388,607 to specify the number of space units (cylinders, tracks, or blocks) in the secondary allocation of the File Utility Audit Trail GDG data set.

FILE_UTILITY_AUDIT_TRAIL_UNIT

Default:SYSDA

Enter a 1- to 8-character unit name designating the disk unit on which to allocate the File Utility Audit Trail GDG data set. Unless this parameter is set to blanks (=NULL), it overrides the value specified for FILE_UTILITY_AUDIT_TRAIL_VOLUME. To set this parameter to blanks with the global override facility, specify a value of NULL.

FILE_UTILITY_AUDIT_TRAIL_UPDATED_RECORDS

Default:FULL

Enter FULL to write File Utility Audit Trail entries that include the entire contents of updated records when those records are updated using the Code Debug File Utility. This setting allows users to see the context in which even small changes have been made. Enter SHORT to write entries that include only the modified contents of the updated records. SHORT only applies to data set, temporary storage, and DL/I segment updates. Db2 row updates are not abbreviated in any way. Enter NONE to write those entries with only the report heading and the record key.

FILE_UTILITY_AUDIT_TRAIL_VOLUME

Default:NULL

Enter a 1- to 6-character volume serial number designating the disk unit on which to allocate the File Utility Audit Trail GDG data set. Unless the parameter FILE_UTILITY_AUDIT_TRAIL_UNIT is set to blanks (=NULL), it overrides the value specified for this parameter. To set this parameter to blanks with the global override facility, specify a value of NULL.

FILE_UTILITY_CAN_ACCESS_QUEUED_TEMPSTG

Default:(XPED_USER,XPRT_USER,XPSP_USER)

Enter XPED_USER, XPRT_USER, or XPSP_USER to enable access to QUEUED (multiple record) temporary storage queues in the file utility for the specified transaction. Omitting a value will disable access for the specified transaction. As an example, (XPED_USER,XPSP_USER) will disable access for users of the XPRT transaction. To disable all users, enter ().

FILE_UTILITY_CAN_ACCESS_TRANSIENT_DATA

Default:(XPED_USER,XPRT_USER,XPSP_USER)

Enter XPED_USER, XPRT_USER, or XPSP_USER to enable access to transient data queues in the file utility for the specified transaction. Omitting a value will disable access for the specified transaction. As an example, (XPED_USER,XPSP_USER) will disable access for users of the XPRT transaction. To disable all users, enter ().

FILE_UTILITY_DATA SET_ALLOW_READ

Default:(XPED_USER,XPRT_USER,XPSP_USER)

Enter XPED_USER, XPRT_USER, or XPSP_USER to enable read access to data sets in the file utility for the specified transaction. Omitting a value will disable access for the specified transaction. As an example, (XPED_USER,XPSP_USER) will disable read access for users of the XPRT transaction. To disable all users, enter ().

FILE_UTILITY_DATA SET_CAN_OPEN_CLOSE

Default:(XPED_USER,XPRT_USER,XPSP_USER)

Enter XPED_USER, XPRT_USER, or XPSP_USER to enable explicit and implicit opening and closing of data sets in the file utility for the specified transaction. Omitting a value will disable access for the specified transaction. As an example, (XPED_USER,XPSP_USER) will disable access for users of the XPRT transaction. To disable all users, enter ().

FILE_UTILITY_DATA SET_ENABLE_UPDATES

Default:(XPED_USER,XPRT_USER,XPSP_USER)

Enter XPED_USER, XPRT_USER, or XPSP_USER to enable updates of data sets in the file utility for the specified transaction. Omitting a value will disable access for the specified transaction. As an example, (XPED_USER,XPSP_USER) will disable the ability to update data sets for users of the XPRT transaction. To disable all users, enter ().

FILE_UTILITY_DATA SET_SERVREQ_UPDT

Default:(XPED_USER,XPRT_USER,XPSP_USER)

Enter XPED_USER, XPRT_USER, or XPSP_USER to enable updates of service request fields on the CICS data set List screen (5.1.1) for the specified transaction. Omitting a value will disable access for the specified transaction. As an example, (XPED_USER,XPSP_USER) will disable the ability to update service request fields for users of the XPRT transaction. To disable all users, enter ().

FILE_UTILITY_DATA SET_READ_UPDATE_LOCKED

Default:0

Specifies the length of time in seconds that a CICS data set record is locked when a READ UPDATE command is used on the Edit CICS data set Record screen (5.1.3). Valid values are 0 to 255. The default is 0, which means that no lock occurs and the system does not require READ UPDATE before issuing a REWRITE command.

FILE_UTILITY_DB2_AUTHTYPE

Default:NONE

Enter the appropriate value to match your site’s Db2 security setting for the XPED, XPRT, and XPSP transactions. Users should match the AUTHTYPE() DB2CONN/DB2ENTRY resource definition parameter. Valid entries are:

• NONE: Code Debug displays a list of all tables and views in the Db2 catalog. No checks are made to determine whether the user is authorized to access the resource. When the resource is actually selected, Db2 performs any necessary checking.
• USERID: Code Debug uses eight-byte SNT userID. BMC strongly recommends using NONE instead of USERID. For more information, see Implementing-Support-for-the-Db2-File-Utility.
• GROUP: Code Debug uses the same logic as used for NONE. See description of NONE above. For more information, see Implementing-Support-for-the-Db2-File-Utility.
• USER: Code Debug uses three-byte SNT operator ID.
• TERM: Code Debug uses terminal ID.
• TXID: Code Debug uses transaction ID.
• SIGNID: This value is from the DB2CONN SIGNID() parameter.
• STRING: Code Debug uses the value from DB2ENTRY AUTHID() parameter.

FILE_UTILITY_DB2_CREATOR_LIMIT

Default:* (asterisk)

Enter a one to eight-character value that you want to use as the default CREATOR limit field on the DB2 Table/View List screen (5.5.1) in the Db2 file utility. A user can override this value on the DB2 Setup (5.5.0) and DB2 Table/View List (5.5.1) screens.

FILE_UTILITY_DB2_DATABASE_LIMIT

Default:* (asterisk)

Enter a one to eight-character value that you want to use as the default DATABASE limit field on the DB2 Table/View List screen (5.5.1) in the Db2 file utility. A user can override this value on the DB2 Setup (5.5.0) and DB2 Table/View List (5.5.1) screens.

FILE_UTILITY_DB2_DBCTL_PSB_NAME

Default:XPEDPSB2

Enter the PSB to be scheduled by Code Debug CICS for DBCTL support.

FILE_UTILITY_DB2_DECIMAL_CHARACTER

Default:PERIOD

Enter PERIOD to change the display character for a decimal point in the Db2 file utility to a period. Enter COMMA to change the display character for a decimal point to a comma. A user may override this value on the DB2 Setup screen (5.5.0). This value should be set to the same value specified during generation of your Db2 subsystem.

FILE_UTILITY_DB2_EXCLUSIVE_LOCK_SYSTEM

Default:NO

Enter YES to allow exclusive locking of a Db2 table during editing within the Db2 file utility. Enter NO to prohibit a user from placing an exclusive lock on the table. This parameter is a system programmer override. It can be used to prohibit users from exclusively locking a Db2 table during editing, even if exclusive locking is requested.

FILE_UTILITY_DB2_EXCLUSIVE_LOCK_USER

Default:NO

Enter YES to specify that the user wants exclusive locking of a Db2 table during editing within the Db2 file utility. Enter NO to specify that the user does not want exclusive locking. A user can specify YES or NO for this parameter on the DB2 Setup screen (5.5.0); however, specifying YES allows exclusive locking only if the system programmer override value (FILE_UTILITY_DB2_EXCLUSIVE_LOCK_SYSTEM) is also YES.

FILE_UTILITY_DB2_MAX_ROWS_SYSTEM

Default:1000

Enter a value to specify the maximum number of rows a user can access in the Db2 file utility. A user can also specify a smaller value through the DB2 Setup screen (5.5.0) (see the FILE_UTILITY_DB2_MAX_ROWS_USER parameter). Valid values are 1 to 32767.

FILE_UTILITY_DB2_MAX_ROWS_USER

Default:250

Enter a value between 1 and the value specified in the FILE_UTILITY_DB2_MAX_ROWS_SYSTEM parameter. This value is the default value used when returning rows from Db2 tables in the Db2 file utility. It allows a user to specify a value smaller than the FILE_UTILITY_DB2_MAX_ROWS_SYSTEM value when fewer rows are desired in the Db2 file utility. A user can override this value through the DB2 Setup screen (5.5.0).

FILE_UTILITY_DB2_NULL_CHARACTER

Default:@

Enter the character you want used as the default character when displaying null columns in the Db2 file utility. A user can override this parameter on the DB2 Setup screen (5.5.0).

FILE_UTILITY_DB2_SQL_DDNAME

Default:DBUGSQL

Enter a one to seven-position ddname of the data set used to save SQL calls generated in the Db2 file utility. This data set allows a user of the Db2 file utility to develop Db2 queries (SELECT statements) and save the generated code. The Code Debug CICS offline utility, DBSQLUTL, can then be used to write this information to a user-specified data set for inclusion into program code.

FILE_UTILITY_DB2_STRING_DELIMITER

Default:APOST

Enter APOST to set the default string delimiter in the Db2 file utility to an apostrophe ('). Enter QUOTE to set the default string delimiter to a quotation mark ("). A user can override this value on the DB2 Setup screen (5.5.0). This value should be set to the same value specified during generation of your Db2 subsystem.

FILE_UTILITY_DB2_TABLE_LIMIT

Default:* (asterisk)

Enter a one to eight-character value that you want to use as the default TABLE/VIEW NAME limit field on the DB2 Table/View List screen (5.5.1) in the Db2 file utility. A user can override this value on the DB2 Setup (5.5.0) and DB2 Table/View List (5.5.1) screens.

FILE_UTILITY_DB2_TABLESPACE_LIMIT

Default:* (asterisk)

Enter a one to eight-character value that you want to use as the default TABLESPACE limit field on the DB2 Table/View List screen (5.5.1) in the Db2 file utility. A user can override this value on the DB2 Setup (5.5.0) and DB2 Table/View List (5.5.1) screens.

FILE_UTILITY_DB2_TIMESTAMP_LOCALE

Default:LOCAL

Enter LOCAL to use the local time, date, and time stamp values when inserting columns into new rows in the Db2 file utility. Enter GMT to use Greenwich Mean Time values if you have generated this feature in your Db2 subsystem. A user can override this parameter on the DB2 Setup screen (5.5.0).

FILE_UTILITY_DB2_TRUNC_TRAILING_BLANKS

Default:YES

Enter YES to truncate trailing blanks on input for variable length column data in the Db2 file utility. Enter NO to cause variable length fields to retain trailing blanks upon input. A user can override this parameter on the DB2 Setup screen (5.5.0).

FILE_UTILITY_DB2_TYPE_LIMIT

Default:* (asterisk)

Enter TABLE to specify a default value of tables only in the TYPE limit field on the DB2 Table/View List screen (5.5.1) in the Db2 file utility. Enter VIEW to specify a value of views only. Enter an asterisk (*) to get both tables and views. A user can override this value on the DB2 Setup (5.5.0) and DB2 Table/View List (5.5.1) screens.

FILE_UTILITY_DB2_VARCHAR_END_OF_STRING

Default:|

Enter the character you want used as the default end of string character when entering variable length column data in the Db2 file utility. A user can override this parameter on the DB2 Setup screen (5.5.0).

FILE_UTILITY_DLI_ALLOW_READ

Default:(XPED_USER,XPRT_USER,XPSP_USER)

Enter XPED_USER, XPRT_USER, or XPSP_USER to enable read access to DL/I segments in the file utility for the specified transaction. Omitting a value will disable this facility for the specified transaction. As an example, (XPED_USER,XPSP_USER) will disable read access to DL/I segments for users of the XPRT transaction. To disable all users, enter ().

FILE_UTILITY_DLI_ENABLE_PCB_TERM_CALLS

Default:(XPED_USER,XPRT_USER,XPSP_USER)

Enter XPED_USER, XPRT_USER, or XPSP_USER to enable PCB/TERM calls for DL/I PSBs in the file utility for the specified transaction. Omitting a value will disable this facility for the specified transaction. As an example, (XPED_USER,XPSP_USER) will disable the ability to use PCB/TERM calls for DL/I PSBS for users of the XPRT transaction. To disable all users, enter ().

FILE_UTILITY_DLI_ENABLE_UPDATES

Default:(XPED_USER,XPRT_USER,XPSP_USER)

Enter XPED_USER, XPRT_USER, or XPSP_USER to enable updates of DL/I segments in the file utility for the specified transaction. Omitting a value will disable this facility for the specified transaction. As an example, (XPED_USER,XPSP_USER) will disable the ability to update DL/I segments for users of the XPRT transaction. To disable all users, enter ().

FILE_UTILITY_DLI_PSB_SCHEDULE_MAX

Default:2

Specifies the length of time in minutes that a PSB remains scheduled between DL/I calls on the Edit DL/I Segment screen (5.4.4) when the PCB command is used to schedule a PSB. Valid values are 1 to 59.

FILE_UTILITY_DLI_SHOW_ACCESS_COMMANDS

Default:()

Specifying XPED_USER, XPRT_USER, or XPSP_USER will cause the Edit DL/I Segment screen (5.4.4) to show all DL/I access commands as valid. However, when you use a command that is not valid for a PCB or even segment level processing options, DL/I will return a bad status code indicating this access is not valid. Omitting a value will disable this facility for the specified transaction. As an example, (XPED_USER,XPSP_USER) will disable the ability to override the processing options for users of the XPRT transaction. To disable all users, enter ().

FILE_UTILITY_MAX_NOT_FOUND_COUNT

Default:100

Enter the number of data set and/or temporary storage records to scan before the system displays the NOT FOUND message for the FIND command on the 5.1.2, 5.2.2, 5.5.2, and 5.5.4 screens. Valid values are 1 to 99999.

FILE_UTILITY_MQ_CAN_ACCESS_QUEUE_LIST

Default:(XPED_USER,XPRT_USER,XPSP_USER)

Enter XPED_USER, XPRT_USER, or XPSP_USER to enable access to the list of IBM MQ for z/OS (MQ) queues in the File Utility for the specified transaction. Omitting a value will disable access for the specified transaction. As an example, (XPED_USER,XPSP_USER) will disable access for users of the XPRT transaction. To disable all users, enter ().

FILE_UTILITY_MQ_DYNAMIC_QUEUE_NAME

Default:MXD.*

The File Utility screen List MQ Queues (5.6.1) opens a dynamic queue. This parameter specifies the prefix for the name of that dynamic queue. The following variables may be used within the FILE_UTILITY_MQ_DYNAMIC_QUEUE_NAME parameter:

• %A - The APPLID of the CICS region
• %S - The SYSID of the CICS region
• %U - The UserID of the user associated with the current task.

The parameter length, after variable substitution, must not exceed 33 characters and must end with an asterisk (*).

FILE_UTILITY_MQ_READ_ALLOWED

Default:(XPED_USER,XPRT_USER,XPSP_USER)

Enter XPED_USER, XPRT_USER, or XPSP_USER to enable read access to IBM MQ for z/OS (MQ) queues in the File Utility for the specified transaction. Omitting a value will disable access for the specified transaction. As an example, (XPED_USER,XPSP_USER) will disable access for users of the XPRT transaction. To disable all users, enter ().

FILE_UTILITY_MQ_UPDATE_ALLOWED

Default:(XPED_USER,XPRT_USER,XPSP_USER)

Enter XPED_USER, XPRT_USER, or XPSP_USER to enable update access to IBM MQ for z/OS (MQ) queues in the File Utility for the specified transaction. Omitting a value will disable access for the specified transaction. As an example, (XPED_USER,XPSP_USER) will disable access for users of the XPRT transaction. To disable all users, enter ().

FILE_UTILITY_TEMPSTG_QUEUE_FOR_REQUESTS

Default:XPED

Enter the name of the Temporary Storage Queue ID that the file utility must use. This queue communicates between the screen and file processors.

GO_COMMAND_MAX_STMTS_DELAY_NONZERO

Default:99

Enter the maximum number of statements to execute with a GO command if the delay interval is greater than 0 seconds. Valid values are 1 to 32767.

GO_COMMAND_MAX_STMTS_DELAY_ZERO

Default:5000

Enter the maximum number of statements to execute with a GO command if the delay interval is equal to 0 seconds. Valid values are 1 to 32767.

GO_COMMAND_MAXIMUM_WAIT_TIME

Default:6

Enter the number of seconds that provides a high limit (maximum) wait time to be used on the GO command. Valid values are 1 to 59.

HAVE_USER_PROGRAMS_WITH_VP_PREFIX

This parameter has been deprecated.

INACTIVE_SESSION_TERMINATION_FREQUENCY

Default:0

Enter how frequently, in minutes, XTMO should be restarted for inactive session termination checking. This means that whenever the number of minutes specified for INACTIVE_SESSION_TERMINATION_FREQUENCY have elapsed, transaction XTMO will be started via Interval Control to check for possible inactive sessions. If the value is set to 0, inactive session termination is disabled. Valid values are 0 to 240.

INACTIVE_SESSION_TERMINATION_INTERVAL

Default:0

Enter the interval, in minutes, used to define when a session is considered inactive. If no activity has occurred in a debugging session within this interval, the session will be deemed inactive and will be terminated. If the value is set to 0, inactive session termination is disabled. Valid values are 0 to 240.

INACTIVE_SESSION_TERMINATION_TERM_RTV

Default:NO

Enter YES to terminate Runtime Visualizer sessions that have timed out. If you enter YES, any Runtime Visualizer sessions that are deemed to be inactive will be terminated. If you enter NO, Runtime Visualizer sessions will never timeout.

ISSUE_WRITE_STRUCTURED_FIELD_LAST_3270

Default:YES

Enter YES to issue a WRITE STRUCTURED FIELD (Set Reply Mode Extended) command and make any extended attributes available for the Last 3270 Screen (2.8). Enter NO to prevent the command from being issued. Extended attributes are only returned by Code Debug CICS if CICS has issued a query for this terminal and indicated extended attributes are supported. For more information on the QUERY parameter of the TYPETERM definition, see to the IBM documentation site.

LOAD_TRAPS_FROM_PROFILE_AT_SESS_START

Default:NO

Enter YES to load saved traps at session start. This parameter is ignored if the profile data set is in the old format. Valid values are:

YES: Loads saved traps at session start.

NO: Do not load saved traps at session start.

MAX_SUBTASKS_FOR_PDSE_SUPPORT

Default:4

Designates the maximum number of subtasks that can be attached when multiple requests are made against a PDSE data set. This parameter is utilized only when a site has PDSE data sets in its DFHRPL concatenation or in an installed LIBRARY. Entering 0 disables PDSE support and should only be done if there are no PDSE data sets in your DFHRPL concatenation or installed LIBRARY. The value specified must be an unsigned integer in the range of 0 to 10. Setting MAX_SUBTASKS_FOR_PDSE_SUPPORT to a higher value will make it more resource intensive. The XSIT transaction cannot be used to override this parameter.

MAX_SVCDUMPS_FOR_PAE_ERRORS

Default:1

Designates the maximum number of SVC dumps that will be taken if a PAE* (* being a letter or number) abend is detected during storage protection, trace, code coverage, or stepping. These types of abends are indicative of a logic error. These errors require more than a transaction dump to evaluate, so an SVC dump will be produced. To limit the number of SVC dumps, the MAX_SVCDUMPS_FOR_PAE_ERRORS parameter can be set to an unsigned integer value between 0 and 10. To suppress all SVC dumps for these type of errors, specify 0.

MAXIMUM_SLS_FILES_TO_SEARCH

Default:8

Enter the maximum number of SLS files to search. Valid values are 1 to 255.

MONITOR_MAX_STG_ABOVE_BAR

Default:100

Specify the maximum container storage above the bar, in megabytes, for MONITOR data per task. Once the maximum storage specified has been reached, MONITOR data in containers will wrap and you may receive an AT OLDEST RETAINED EXECUTION POSITION message when doing REVERSE. Valid entries are 1 to 100, in increments of 1MB. If you experience a Short on Storage (SOS) condition using MONITOR/REVERSE, reduce MONITOR_MAX_STG_ABOVE_BAR or increase the EDSA limit. The XSIT transaction cannot be used to override this parameter.

NLS

Default:ASIS

Changes the character translation table that is used to display data. Options are: ASIS, ENGLISH, CANADAB, HEBREWNC, ARABIC, and KATAKANA. See also NLS_UPPERCASE_ENGLISH_STATIC_TEXT.

NLS_UPPERCASE_ENGLISH_STATIC_TEXT

Default:NO

Enter YES to convert lowercase English characters to uppercase English characters for static portions of screens and help modules. Valid values are YES and NO.

NUMBER_CONCURRENT_PDSE_REQUESTS

Default:4096

Designates the number of concurrent requests against PDSEs that Code Debug CICS will support. This parameter is utilized only when a site has PDSE data sets in its DFHRPL concatenation or in an installed LIBRARY. The value specified must be an unsigned integer in the range of 4096 to 16384. The default value of 4096 allows approximately 500 concurrent requests. Do not alter this value unless recommended by BMC Support. The XSIT transaction cannot be used to override this parameter.

OK_TO_USE_XPEDITER_WITHIN_CRTE_SESSION

Default:YES

Enter NO to prevent the start of an Code Debug session within a CRTE explicit routing session. If OK_TO_USE_XPEDITER_WITHIN_CRTE_SESSION=NO, an attempt to start an Code Debug session within a CRTE session will result in transaction abend XRTE.

PARMLIB_REPORT_ALLOCATION

This parameter has been deprecated.

PARMLIB_REPORT_DDNAME

Default:XGBR

A one- to four-character transient data queue name that the BMC PARMLIB report (Code Debug CICS Parameters) is written to.

PARMLIB_REPORT_SYSOUT_CLASS

This parameter has been deprecated.

PF01_COMMAND
PF01_DESCRIPTION
.
.
.
PF24_COMMAND
PF24_DESCRIPTION

Default:  For default PF key values, see Standard Global Table Parameters PARMLIB Parameter.

Enter the PF key parameters in the following format:

• nn: PF key number. Valid entries are 01 to 24. A leading 0, for example 01, is required for PF keys 1 through 9.
• command: Command to execute when you press the PF key.
• description: Label to display for this PF key in the footing area of the screen. It must be no longer than eight characters. If the description is blank, it is the same as the command.

PRIMARY_MENU_SITE_CONTACT_INFO

Default:' '

Specify a message to display on the Code Debug CICS Primary Menu. Enter the name and/or telephone number of your site’s BMC Supportrepresentative. Normally, this is an on-site systems programmer or information center representative. Enter a maximum of 60 free-form characters, enclosed in quotes.

PRODUCE_DUMP_ON_EXIT

Default:NO

Enter YES to produce a dump when exiting Code Debug CICS.

PROFILE_DEFAULT_AUTO_ABEND_TRAPPING

Default:(XPED_USER,XPRT_USER)

Enter XPED_USER, XPRT_USER, or XPSP_USER to enable automatic abend trapping when using the specified transaction. This parameter sets the default value used for the specified transaction when a profile record does not exist for a user. Omitting a value will disable automatic abend trapping for the specified transaction. The default will enable the feature for XPED and XPRT users, but disable it for XPSP users. To disable this feature for all users, enter (). A user can override this parameter on the Set Profile Defaults screen (0.1).

If global parameter WORKSTATIONS_USE_UNIQUE_IP_ADDRESSES is enabled for a transaction, PROFILE_DEFAULT_AUTO_ABEND_TRAPPING also controls whether Code Debug will trap any abends or breakpoints that occur at your TCPIP-based workstation during a debugging session. (For more information, see WORKSTATIONS_USE_UNIQUE_IP_ADDRESSES.) This function can also be controlled from the Set Profile Defaults screen (0.1).

PROFILE_DEFAULT_AUTO_DISPLAY_SOURCE

Default:(XPED_USER)

Enter XPED_USER, XPRT_USER, or XPSP_USER to allow automatic display of the Source Listing screen (2.L) upon entering Code Debug CICS, or when a breakpoint or abend occurs while using the specified transaction. This parameter sets the default value used for the specified transaction when a profile record does not exist for a user. Omitting a value will cause the Break/Abend screen (2.1) to be displayed for the specified transaction. The default will cause XPED users to go to the 2.L screen, while XPRT and XPSP users to will go the 2.1 screen. To disable this feature for all users, enter (). A user can override this parameter on the Set Profile Defaults screen (0.1).

PROFILE_DEFAULT_AUTO_SEL_CSECT_XPED_USER
PROFILE_DEFAULT_AUTO_SEL_CSECT_XPRT_USER
PROFILE_DEFAULT_AUTO_SEL_CSECT_XPSP_USER

Default:NONE

Enter NONE to suppress automatic selection of CSECTs when debugging multiple CSECT programs for the specified transaction. This parameter sets the default value used for the specified transaction when a profile record does not exist for a user. Enter ALL to select all CSECTs when debugging multiple CSECT programs. A user can override this parameter on the Set Profile Defaults screen (0.1).

PROFILE_DEFAULT_COMMAND_DELIMITER

Default:;

Enter the delimiting character to be used to separate multiple Code Debug CICS primary commands entered together. Any character is a valid delimiter except alphanumeric characters (a to z, A to Z, and 0 to 9), period (.), comma (,), blank ( ), underscore (_), and equal (=).

PROFILE_DEFAULT_FOOTING_XPED_USER
PROFILE_DEFAULT_FOOTING_XPRT_USER
PROFILE_DEFAULT_FOOTING_XPSP_USER

Default:OFF

Enter the default footing values that are displayed for the specified transaction. This parameter sets the default value used for the specified transaction when a profile record does not exist for a user. Valid values are: MENU, KEYS, DATA, STATUS, REGISTERS, ANALYZE, FLOAT, SOURCE, or OFF. A user can override this parameter on the Set Profile Defaults screen (0.1).

PROFILE_DEFAULT_GO_DELAY_XPED_USER
PROFILE_DEFAULT_GO_DELAY_XPRT_USER
PROFILE_DEFAULT_GO_DELAY_XPSP_USER

Default:0

Enter a value to specify the default delay value in seconds for the GO command while using the specified transaction. This parameter sets the default value used for the specified transaction when a profile record does not exist for a user. A user can override this parameter on the Set Profile Defaults screen (0.1). Valid values are 0 to 59.

PROFILE_DEFAULT_GO_MAX_STMTS_XPED_USER
PROFILE_DEFAULT_GO_MAX_STMTS_XPRT_USER
PROFILE_DEFAULT_GO_MAX_STMTS_XPSP_USER

Default:20

Enter a value between 0 and the value specified in the GO_COMMAND_MAX_STMTS_DELAY_NONZERO parameter. This parameter sets the default value used for the specified transaction when a profile record does not exist for a user. This value specifies the maximum number of statements to execute if the DELAY factor set in the GO command is greater than zero. A user can override this parameter on the Set Profile Defaults screen (0.1).

PROFILE_DEFAULT_INTELLIGENT_AUTOKEEPS

Default:YES

Controls the default setting for the usage of the Intelligent Autokeeps feature. Enter YES to allow the use of this feature. Enter NO to disable this feature. The Intelligent Autokeeps feature is configured as a subset of the AUTOKEEP profile option, and to use this feature, the AUTOKEEP profile parameter must be set to ON. A user can override this parameter on the Set Profile Defaults screen (0.1).

PROFILE_DEFAULT_KEEP_SIZE_XPED_USER
PROFILE_DEFAULT_KEEP_SIZE_XPRT_USER
PROFILE_DEFAULT_KEEP_SIZE_XPSP_USER

Default:ON for PROFILE_DEFAULT_KEEP_SIZE_XPED_USER
ON for PROFILE_DEFAULT_KEEP_SIZE_XPRT_USER
OFF for PROFILE_DEFAULT_KEEP_SIZE_XPSP_USER

Enter OFF to disable the display of the keep window on the Source Listing screen (2.L) for the specified transaction. This parameter sets the default value used for the specified transaction when a profile record does not exist for a user. Valid values are: OFF, ON, 5, 7, 9, and 11. Specifying ON sizes the keep window to 5 lines. The values 5, 7, 9, or 11 sizes the keep window to that number of lines. A user can override this parameter on the Set Profile Defaults screen (0.1).

PROFILE_DEFAULT_PROGRAM_TRACE

Default:()

Enter XPED_USER, XPRT_USER, or XPSP_USER to enable statement-level program tracing when using the specified transaction. This parameter sets the default value used for the specified transaction when a profile record does not exist for a user. Omitting a value will disable screen optimization for the specified transaction. As an example, (XPED_USER,XPSP_USER) will disable statement-level program tracing for users of the XPRT transaction. To disable all users, enter (). A user can override this parameter on the Set Profile Defaults screen (0.1).

PROFILE_DEFAULT_SCREEN_OPTIMIZATION

Default:(XPED_USER,XPRT_USER,XPSP_USER)

Enter XPED_USER, XPRT_USER, or XPSP_USER to enable Code Debug CICS screen optimization for the specified transaction. This parameter sets the default value used for the specified transaction when a profile record does not exist for a user. Specifying these values can decrease the amount of data sent to the screen by 60 percent with only a small additional cost in CPU time. Omitting a value will disable screen optimization for the specified transaction. As an example, (XPED_USER,XPSP_USER) will enable screen optimization for users of the XPED and XPSP transactions, but disable it for the XPRT transaction. To disable all users, enter (). A user can override this parameter on the Set Profile Defaults screen (0.1).

PROFILE_DEFAULT_SOURCE_JUSTIFICATION

Default:(XPED_USER,XPRT_USER)

Enter XPED_USER, XPRT_USER, or XPSP_USER to enable justification of the source listing for the specified transaction. This parameter sets the default value used for the specified transaction when a profile record does not exist for a user. Justification causes the Source Listing screen (2.L) to display only the source portion from the listing instead of the entire compiler listing. Omitting a value will disable access for the specified transaction, and for the default value, XPSP users will not have the source listing justified. To disable all users, enter (). A user can override this parameter on the Set Profile Defaults screen (0.1).

PROFILE_DEFAULT_STORAGE_PROTECTION

Default:()

Enter XPED_USER, XPRT_USER, or XPSP_USER to automatically enable storage protection when using the specified transaction. This parameter sets the default value used for the specified transaction when a profile record does not exist for a user. Omitting a value will disable this feature storage protection for the specified transaction. As an example, (XPED_USER,XPSP_USER) will automatically enable storage protection for users of the XPED and XPSP transactions, but disable it for users of the XPRT transaction. To disable all users, enter (). A user can override this parameter on the Set Profile Defaults screen (0.1).

PROFILE_DEFAULT_TERMINAL_ALARM_ON_ERROR

Default:(XPED_USER,XPRT_USER,XPSP_USER)

Enter XPED_USER, XPRT_USER, or XPSP_USER to enable the terminal alarm when an error occurs for the specified transaction. This parameter sets the default value used for the specified transaction when a profile record does not exist for a user. Omitting a value will disable this feature for the specified transaction. As an example, (XPED_USER,XPSP _USER) will enable the terminal alarm when an error occurs for users of the XPED and XPSP transactions, but disable it for users of the XPRT transaction. To disable all users, enter (). A user can override this parameter on the Set Profile Defaults screen (0.1).

PROFILE_DEFAULT_USE_ALT_SCREEN_SIZE

Default:()

Enter XPED_USER, XPRT_USER, or XPSP_USER to enable use of alternate screen sizes for the specified transaction. This parameter sets the default value used for the specified transaction if a user’s profile record does not exist. When XPED_USER, XPRT_USER, or XPSP_USER is specified, the Code Debug CICS screens always use the alternate screen size for display. Omitting a value will disable this feature for the specified transaction. As an example, (XPED_USER,XPSP _USER) will enable alternate screen size for users of the XPED and XPSP transactions, but disable it for users of the XPRT transaction. To disable all users, enter (). A user can override this parameter on the Set Profile Defaults screen (0.1).

PROGRAM_STATEMENT_TRACE_TABLE_SIZE

Default:500

Enter the number of entries that the program statement trace table is to contain. Entering zero prohibits trace table creation. Valid values are 0 to 32767.

PROGRAM_TRACE_DDNAME

Default:XDTRCRPT

Enter a one to eight-character ddname for the dynamically allocated SYSOUT data set containing the program trace print output.

ROI_REPORT_INTERVAL

Default:42

• If zAdviser is enabled, this parameter is superseded by the BMC global parameter ZADVISER_SMF_BUFF_INT. zAdviser support is enabled using BMC global parameters as described in the Enterprise Common Components Advanced Configuration space.
• If zAdviser is not enabled and classic ROI data is being collected, enter a value between 1 and 60 which represents the number of minutes that will occur between writing the ROI data that is used by the Value Improvement Program (VIP).

SAVE_TRAPS_TO_PROFILE_AT_SESS_END

Default:YES

Enter YES to save traps automatically at session end. This parameter is ignored if the profile data set is in the old format. Valid values are:

YES: Saves traps automatically at session end.

NO: Do not save traps automatically at session end.

SCRIPT_FACILITY_ENABLE

Default:YES

Enter YES to enable the Script Facility. This also enables the CAPTURE and INCLUDE commands. Enter NO to disable the Script Facility as well as the CAPTURE and INCLUDE commands.

For more information, see Configuring-the-Script-Facility.

SCRIPT_FACILITY_SAVE_AS_NAME

Default:********

Enter a 1- to 8-character script name for the default value to be displayed in the “If YES save as” field on the Script Data set Allocation screen (0.6). The value established as the default for this field can be overridden by the user, and the new value will be saved in their profile data set. This parameter has no effect unless the SCRIPT_FACILITY_SESS_TERMINATION_STATUS parameter is set to SAVE. The default of eight asterisks (********) is translated by Code Debug to the current userID. With the default, if a user’s debugging session is terminated while they are capturing a script, their userID will be used as the script name.

For more information, see Configuring-the-Script-Facility.

SCRIPT_FACILITY_SESS_TERMINATION_STATUS

Default:SAVE

Enter SAVE to make YES the default value displayed in the “Save script if CAPTURE ON at session termination?” field on the Script Data set Allocation screen (0.6). The value established as the default for this field can be overridden by the user, and the new value will be saved in their profile data set. If this field is set to YES and a script is being captured when the user’s debugging session is terminated, Code Debug will attempt to save the script. The value in the If YES save as field will be used as the script name. If a script with that name already exists, it will be overwritten.

Enter DISCARD to make NO the default value displayed. If this field is set to NO and a script is being captured when the user’s debugging session is terminated, the captured script commands will be discarded.

For more information, see Configuring-the-Script-Facility.

SCRIPT_FACILITY_SYSTEM_SCRIPT_AUTOPLAY

Default:********

Enter a value for the site-wide Code Debug system script auto-play member you want to be read and processed at startup of each session. That value must exist in the system script data set specified by global parameter SCRIPT_FACILITY_SYSTEM_SCRIPT_DSN.

The SCRIPT_FACILITY_SYSTEM_SCRIPT_AUTOPLAY parameter allows you to establish a common script that will be run at session startup for all users site-wide. This script can be used to set profile options for all users. Additional user-specified scripts are run after the system script.

If the SCRIPT_FACILITY_SYSTEM_SCRIPT_AUTOPLAY value starts with a space or an asterisk (*), the parameter is considered to have no value, and no action is taken. For more information, see SCRIPT_FACILITY_SYSTEM_SCRIPT_DSN and Configuring-the-Script-Facility.

SCRIPT_FACILITY_SYSTEM_SCRIPT_DDNAME

Default:DYNAMIC

Enter DYNAMIC to specify dynamic allocation of your system script data set. The data set will be given the name specified in parameter SCRIPT_FACILITY_SYSTEM_SCRIPT_DSN.

Enter a 1- to 8-character ddname only if dynamic allocation is not allowed at your site. If a ddname is used, you must submit JCL to allocate your system script data set and add a DD statement to your CICS startup JCL indicating the name of your system script data set. Other batch or CICS regions may be prevented from updating this system script data set while your CICS region is active.

For more information, see Configuring-the-Script-Facility.

SCRIPT_FACILITY_SYSTEM_SCRIPT_DSN

Default:XD.SYSTEM.SCRIPT.DATA SET

Enter a 1- to 44-character system script data set name to be used if your site allows dynamic allocation of data sets. The selected data set name is displayed in the System Data set Name field on the Script Data set Allocation screen (0.6). If parameter SCRIPT_FACILITY_SYSTEM_SCRIPT_DDNAME is not set to DYNAMIC, this parameter is ignored. To set this parameter to blanks with the global override facility, specify a value of NULL.

For more information, see Configuring-the-Script-Facility.

SCRIPT_FACILITY_SYSTEM_SCRIPT_STATUS

Default:WRITE

Enter WRITE to give Script Facility users read and update access to the system script data set. Enter READONLY to give Script Facility users read-only access to the system script data set.

For more information, see Configuring-the-Script-Facility.

SCRIPT_FACILITY_USER_SCRIPT_BLKSIZE

Default:27960

Enter a decimal integer value (2 byte binary value), divisible by 120, in the range of 0 to 32760 for the default value to be displayed in the Block Size field on the Script Data set Allocation screen (0.6). The default value for this field can be overridden by the user, and the new value will be saved in their profile data set. The value in the Block Size field will be used when a new user script data set is dynamically allocated.

For more information, see Configuring-the-Script-Facility.

SCRIPT_FACILITY_USER_SCRIPT_CLASS

Default:NULL

If dynamically allocating SMS-controlled user script data sets, enter a 1- to 8-character data class name for the default value to be displayed in the Data Class field on the Script Data set Allocation screen (0.6). The default value for this field can be overridden by the user, and the new value will be saved in their profile data set. The value in the Data Class field will be used when a new SMS-controlled user script data set is dynamically allocated. To set this parameter to blanks with the global override facility, specify a value of NULL.

For more information, see Configuring-the-Script-Facility.

SCRIPT_FACILITY_USER_SCRIPT_DDNAME

Default:DYNAMIC

Enter DYNAMIC to enable dynamically allocated user-defined user script data sets.

Enter a 1- to 8-character ddname only if dynamic allocation of data sets in CICS regions is not allowed at your site or if your site wants to restrict all its users to a single shared user script data set. If a ddname is used, you must submit JCL to allocate your user script data set and add a DD statement to your CICS startup JCL indicating the name of your user script data set. Other batch or CICS regions may be prevented from updating this user script data set while your CICS region is active.

For more information, see Configuring-the-Script-Facility.

SCRIPT_FACILITY_USER_SCRIPT_DIR_BLOCKS

Default:44

Enter a decimal integer value (3 byte binary value) in the range of 1 to 8,388,607 for the default value to be displayed in the Directory Blocks field on the Script Data set Allocation screen (0.6). The default value for this field can be overridden by the user, and the new value will be saved in their profile data set. The value in the Directory Blocks field will be used when a new user script data set is dynamically allocated.

For more information, see Configuring-the-Script-Facility.

SCRIPT_FACILITY_USER_SCRIPT_DSN

Default:NULL

Enter a 1- to 44-character user script data set name suffix for the default value to be displayed in the User data set Suffix field on the Script Data set Allocation screen (0.6). The value in this field is appended to the value in the User Data set Prefix field (see parameter SCRIPT_FACILITY_USER_SCRIPT_DSN_PREFIX) when a new user script data set is dynamically allocated. The resulting user script data set name must be no longer than 44 characters. The value established as the default for this field can be overridden by the user, and the new value will be saved in their profile data set. This parameter is ignored unless SCRIPT_FACILITY_USER_SCRIPT_DDNAME is set to DYNAMIC and SCRIPT_FACILITY_USER_SCRIPT_ENABLE is set to SHARED. To set this parameter to blanks with the global override facility, specify a value of NULL.

For more information, see Configuring-the-Script-Facility.

SCRIPT_FACILITY_USER_SCRIPT_DSN_PREFIX

Default:NULL

Enter a 1- to 44-character user script data set name prefix for the default value to be displayed in the User Data set Prefix field on the Script Data set Allocation screen (0.6). The value in this field is combined with the value in the User Data set Suffix field (see parameter SCRIPT_FACILITY_USER_SCRIPT_DSN) when a new user script data set is dynamically allocated. The resulting user script data set name must be no longer than 44 characters. The value established as the default for this field can be overridden by the user, and the new value will be saved in their profile data set. This parameter is ignored unless SCRIPT_FACILITY_USER_SCRIPT_DDNAME is set to DYNAMIC and SCRIPT_FACILITY_USER_SCRIPT_ENABLE is set to SHARED. To set this parameter to blanks with the global override facility, specify a value of NULL.

For more information, see Configuring-the-Script-Facility.

SCRIPT_FACILITY_USER_SCRIPT_ENABLE

Default:YES

Enter YES to enable user-defined user script data sets. Your site must allow dynamic allocation of data sets in CICS regions, and parameter SCRIPT_FACILITY_USER_SCRIPT_DDNAME must also be set to DYNAMIC. Enter NO to prohibit user script data sets. Enter SHARED to restrict all users to a single shared user script data set defined during Code Debug installation. This parameter also controls the default value to be displayed in the Data set to use field on the Script Data set Allocation screen (0.6). If SCRIPT_FACILITY_USER_SCRIPT_ENABLE=YES or SHARED, the default in the Data set to use field will be U for user. If SCRIPT_FACILITY_USER_SCRIPT_ENABLE=NO, the default in the Data set to use field will be S for system. The default value for this field can be overridden by the user, and the new value will be saved in their profile data set. The value in the Directory Blocks field will be used when a new user script data set is dynamically allocated.

For more information, see Configuring-the-Script-Facility.

SCRIPT_FACILITY_USER_SCRIPT_LIBRARY

Default:NO

If dynamically allocating SMS-controlled user script data sets, enter YES to make YES the default value to be displayed in the Library field on the Script Data set Allocation screen (0.6). Enter NO to make NO the default value displayed. The value in this field is used when a new user script data set is dynamically allocated. If the Library field is set to YES, an SMS-controlled PDSE user script data set will be allocated. If the Library field is set to NO, a PDS user script data set will be allocated. The value established as the default for this field can be overridden by the user, and the new value will be saved in their profile data set.

For more information, see Configuring-the-Script-Facility.

SCRIPT_FACILITY_USER_SCRIPT_MGMT_CLASS

Default:NULL

If dynamically allocating SMS-controlled user script data sets, enter a 1- to 8-character management class for the default value to be displayed in the Management Class field on the Script Data set Allocation screen (0.6). The default value for this field can be overridden by the user, and the new value will be saved in their profile data set. The value in the Management Class field will be used when a new user script data set is dynamically allocated. To set this parameter to blanks with the global override facility, specify a value of NULL.

For more information, see Configuring-the-Script-Facility.

SCRIPT_FACILITY_USER_SCRIPT_PRIMARY_ALLO

Default:15

Enter a decimal integer value (3 byte binary value) in the range of 1 to 8,388,607 for the default value to be displayed in the Primary field on the Script Data set Allocation screen (0.6). The default value for this field can be overridden by the user, and the new value will be saved in their profile data set. The value in the Primary field will be used as the number of space units (cylinders, tracks, or blocks) in the primary allocation when a new user script data set is dynamically allocated.

For more information, see Configuring-the-Script-Facility.

SCRIPT_FACILITY_USER_SCRIPT_SECOND_ALLO

Default:15

Enter a decimal integer value (3 byte binary value) in the range of 1 to 8,388,607 for the default value to be displayed in the Secondary field on the Script Data set Allocation screen (0.6). The default value for this field can be overridden by the user, and the new value will be saved in their profile data set. The value in the Secondary field will be used as the number of space units (cylinders, tracks, or blocks) in the secondary allocation when a new user script data set is dynamically allocated.

For more information, see Configuring-the-Script-Facility.

SCRIPT_FACILITY_USER_SCRIPT_SMS

Default:NO

Enter YES to make YES the default value displayed in the Allocate SMS data set field on the Script Data set Allocation screen (0.6). Enter NO to make NO the default value displayed. The value in this field is used when a new user script data set is dynamically allocated. If the Allocate SMS data set field is set to YES, an SMS-controlled user script data set will be allocated. If the Allocate SMS data set field is set to NO, the user script data set allocated will not be SMS-controlled. The value established as the default for this field can be overridden by the user, and the new value will be saved in their profile data set.

For more information, see Configuring-the-Script-Facility.

SCRIPT_FACILITY_USER_SCRIPT_STG_CLASS

Default:NULL

If dynamically allocating SMS-controlled user script data sets, enter a 1- to 8-character storage class for the default value to be displayed in the Storage Class field on the Script Data set Allocation screen (0.6). The default value for this field can be overridden by the user, and the new value will be saved in their profile data set. The value in the Storage Class field will be used when a new user script data set is dynamically allocated. To set this parameter to blanks with the global override facility, specify a value of NULL.

For more information, see Configuring-the-Script-Facility.

SCRIPT_FACILITY_USER_SCRIPT_TYPE

Default:TRK

Enter TRK to make TRK the default value displayed in the Space Units field on the Script Data set Allocation screen (0.6). Enter BLK to make BLK the default value displayed, or CYL for a default of CYL. The value established as the default for this field can be overridden by the user, and the new value will be saved in their profile data set. The value in the Space Units field will be used to designate whether cylinders, tracks, or blocks will be used when a new user script data set is dynamically allocated.

For more information, see Configuring-the-Script-Facility.

SCRIPT_FACILITY_USER_SCRIPT_UNIT

Default:SYSDA

Enter a 1- to 8-character unit name for the default value to be displayed in the Unit field on the Script Data set Allocation screen (0.6). The default value for this field can be overridden by the user, and the new value will be saved in their profile data set. The value in the Unit field designates the unit name on which a new user script data set is to be dynamically allocated. To set this parameter to blanks with the global override facility, specify a value of NULL.

For more information, see Configuring-the-Script-Facility.

SCRIPT_FACILITY_USER_SCRIPT_VOLUME

Default:NULL

Enter a 1- to 6-character volume serial for the default value to be displayed in the Volume Serial field on the Script Data set Allocation screen (0.6). The default value for this field can be overridden by the user, and the new value will be saved in their profile data set. The value in the Volume Serial field designates the volume serial number on which a new user script data set is to be dynamically allocated. To set this parameter to blanks with the global override facility, specify a value of NULL.

For more information, see Configuring-the-Script-Facility.

SECONDS_TO_WAIT_FOR_DBFL_TO_COMPLETE

Default:14

Enter the number of seconds to wait for the DBFL transaction to complete. Code Debug CICS starts an asynchronous task (default is DBFL) for all file I/O in the file utility. If the attached task fails to return to Code Debug CICS within the specified time, the system issues a message. This may happen if, for example, you request a record that has a read for update still in effect. The system would queue Code Debug CICS until the record was available. Valid values are 1 to 44.

SERVICE_PROVIDER_SUBSYSTEM_NAME

Default:XDSS

Enter a four-character MVS subsystem name, such as XDSS, to make the Code Debug CICS subsystem available. This should be a new subsystem ID defined specifically for use by the Code Debug CICS subsystem. You may optionally specify the Code Debug CICS subsystem ID in SYS1.PARMLIB(IEFSSNxx) for system documentation purposes. Consult your site’s MVS system programmer. For more information, see Specifying Code Debug Service Provider Parameters.

SEVERITY_OF_IVP_MESSAGES_TO_CSMT_QUEUE

Default:ERROR

Controls whether IVP messages should be written to transient data destination CSMT at product initialization. Enter ALL to specify that all messages produced by the IVP should be written to CSMT. Enter NONE to specify that no messages should be written to CSMT. Enter WARN to specify that messages should be written to CSMT only if warnings and/or errors are detected. Enter ERROR to specify that messages should be written to CSMT only if errors are detected.

SLS_DDNAME_TEMPLATE

Default:SLSF001

Enter a 4-character alphabetic prefix and 3-digit suffix to be used as a template for the ddnames associated with SLS (source listing support) files. The resource definition for the file must specify this name. Any additional ddnames are built by adding 1 to the suffix portion. For example, if the default is used, the second ddname will be SLSF002, the third SLSF003, and so on until the maximum number of files specified in MAXIMUM_SLS_FILES_TO_SEARCH is reached. If any SLS files are allocated with DD statements in the CICS startup JCL, they should be given ddnames with the first four characters matching the 4-character prefix of SLS_DDNAME_TEMPLATE. The XSIT transaction cannot be used to override this parameter.

SLS_DSN

Default:blanks

Enter up to 255 SLS (source listing support) data set names to be dynamically allocated to CICS. The default is blanks. The XSIT transaction cannot be used to override this parameter.

Examples of valid entries are:

If data set names are also specified in the CICS startup JCL, those data sets will be allocated prior to the data sets specified in this parameter.

SLS_SHARED_DATABASE_TEMPLATE

Default:SLSD

Enter a 4-character alphabetic prefix to be used as a template for the ddnames associated with SLS (source listing support) Shared Data Base files. The four characters specified for SLS_SHARED_DATABASE_TEMPLATE will be used as the ddname template for the sequentially numbered SLS Shared Data Base files which are dynamically allocated during SLS member open processing. The XSIT transaction cannot be used to override this parameter.

STORAGE_PROTECTION_MAX_CONCURRENT_PGMS

Default:100

Enter a number of concurrent programs to be protected. This value is for a shared storage GETMAIN done at system startup.

STORAGE_PROTECTION_PROTECT_CWA

Default:NO

Enter YES to mark the CWA for storage protection. When protection is activated through the Storage Protection screen (9.8), Code Debug CICS treats the CWA as part of the CSA and prevents modifications. The Monitor Exceptions (9.4.1) and Storage Protection Exceptions (9.7) screens are used to override protection for the CWA.

STORAGE_PROTECTION_UNPROTECT_TERM_FIELD

Default:NO

Enter YES to unprotect the TERM field on the Storage Protection screen (1.8) and allow it to function as it does on the Storage Protection (9.8) screen. The YES value allows users to set storage protection on asynchronous tasks without having to be given access to the 9.8 screen. If the value of STORAGE_PROTECTION_UNPROTECT_TERM_FIELD is NO, the TERM field is protected and the user’s terminal ID is automatically used.

STORAGE_PROTECTION_VIOLATION_MSG_QUEUE

Default:CSMT

Enter the transient data destination to which the system sends Code Debug CICS storage violation messages.

SUPPORT_CICS_OPEN_TRANSACTION_ENV

Default:YES

Controls Code Debug CICS support of CICS Open Transaction Environment (OTE). The default of YES provides full CICS OTE support, allowing the debugging of CICS transactions on the CICS Open TCBs (L8) as well as the CICS QR TCB. In CICS regions that do not exploit CICS OTE, Code Debug CICS storage utilization can be reduced by specifying NO for this parameter.

SUPPRESS_SESSIONS_NOT_ACTIVE_MESSAGE

Default:NO

The message “Code Debug CICS SESSIONS NOT ACTIVE” will be suppressed from being written to the CSMT queue if all of the following occur:

• The value of SUPPRESS_SESSIONS_NOT_ACTIVE_MESSAGE is YES.
• The customer has AUTO SESSION TERMINATION active.
• A terminal is disconnected or logged off and does not have an Code Debug CICS session active.

If the value of SUPPRESS_SESSIONS_NOT_ACTIVE_MESSAGE is NO, the above message will be written as designed.

TERMINATE_SESSION_AT_DISCONNECT

Default:YES

Enter NO to leave Code Debug CICS sessions active if a terminal is disconnected or logged off. See Configuring-Automatic-Session-Termination.

TRANSID_DBFL

Default:DBFL

Enter a four-character transaction ID to substitute for the DBFL transaction. Changing the value of TRANSID_DBFL requires changing the resource definitions.

TRANSID_DBPA

This parameter has been deprecated. See Overriding-Session-Initialization-Transactions for more information about specifying a substitute transaction ID.

TRANSID_DBXG

Default:DBXG

Enter a four-character transaction ID to substitute for the DBXG transaction. Changing the value of TRANSID_DBXG requires changing the resource definitions.

TRANSID_DMAP

Default:DMAP

Enter a four-character transaction ID to substitute for the DMAP transaction. Changing the value of TRANSID_DMAP requires changing the resource definitions. DMAP is used to invoke the Code Debug CICS BMS mapset display utility.

TRANSID_NEWC

Default:NEWC

Enter a four-character transaction ID to substitute for the NEWC transaction. Changing the value of TRANSID_NEWC requires changing the resource definitions.

TRANSID_XDBP

Default:XDBP

Enter a four-character transaction ID to substitute for the XDBP transaction. Changing the value of TRANSID_XDBP requires changing the resource definitions. XDBP is used to refresh the System Facilities and Code Coverage Test parameters from XDDBxxxx PARMLIB members.

TRANSID_XIVP

Default:XIVP

Enter a four-character transaction ID to substitute for the XIVP transaction. Changing the value of TRANSID_XIVP requires changing the resource definitions. XIVP is used to invoke the Code Debug CICS Installation Verification Program.

TRANSID_XLGI

Default:XLGI

Enter a four-character transaction ID to substitute for the XLGI transaction. This transaction is internally invoked and should not be executed from a terminal.

TRANSID_XLOG

Default:XLOG

Enter a four-character transaction ID to substitute for the XLOG transaction. Changing the value of TRANSID_XLOG requires changing the resource definitions. XLOG is used to start, stop, or switch the data set of the Code Debug CICS File Utility Audit Trail.

TRANSID_XPED

This parameter has been deprecated. See Overriding-Session-Initialization-Transactions for more information about specifying a substitute transaction ID.

TRANSID_XPFS

Default:XPFS

Enter a four-character transaction ID to substitute for the XPFS transaction used for SLS data set processing. The XSIT transaction cannot be used to override this parameter.

TRANSID_XPGD

Default:XPGD

Enter a four-character transaction ID to substitute for the XPGD transaction used to limit access to Code Debug CICS debugging facilities through the use of Code Debug/Eclipse.

TRANSID_XPND

Default:XPND

Enter a four-character transaction ID to substitute for the XPND transaction used for debugging session termination.

TRANSID_XPN0

Default:XPN0

Enter a four-character transaction ID to substitute for the XPN0 transaction. Changing the value of TRANSID_XPN0 requires changing the resource definitions.

TRANSID_XPOF

Default:XPOF

Enter a four-character transaction ID to substitute for the XPOF transaction used to invoke the Code Debug CICS shutdown facility.

TRANSID_XPON

This parameter has been deprecated. See Overriding-Session-Initialization-Transactions for more information about specifying a substitute transaction ID.

TRANSID_XPRT

This parameter has been deprecated. See Overriding-Session-Initialization-Transactions for more information about specifying a substitute transaction ID.

TRANSID_XPSP

This parameter has been deprecated. See Overriding-Session-Initialization-Transactions for more information about specifying a substitute transaction ID.

TRANSID_XREL

Default:XREL

Enter a four-character transaction ID to substitute for the XREL transaction. Changing the value of TRANSID_XREL requires changing the resource definitions.

TRANSID_XROI

Default:XROI

Enter a four-character transaction ID to substitute for the XROI transaction. Changing the value of TRANSID_XROI requires changing the resource definitions. XROI is used to export Code Debug CICS data for use by zAdviser’s KPI reporting component.

TRANSID_XSIT

Default:XSIT

Enter a four-character transaction ID to substitute for the XSIT transaction. Changing the value of TRANSID_XSIT requires changing the resource definitions. XSIT is used to invoke the Code Debug CICS Global Table Override Update Utility.

TRANSID_XSRE

Default:XSRE

Enter a four-character transaction ID to substitute for the XSRE transaction. Changing the value of TRANSID_XSRE requires changing the resource definitions. XSRE is used to initiate remote event notifications when using Code Debug Eclipse.

TRANSID_XTMO

Default:XTMO

Enter a four-character transaction ID to substitute for the XTMO transaction. Changing the value of TRANSID_XTMO requires changing the resource definitions. XTMO is used to initiate inactive session termination checking, which would be started when Code Debug CICS is started in any region. If either INACTIVE_SESSION_TERMINATION_FREQUENCY or INACTIVE_SESSION_TERMINATION_INTERVAL is 0, the XTMO transaction (or equivalent) will not be started, effectively disabling inactive session termination.

TRAP_ABEND_FIELD_VALUE_ON_TRAP_SUMMARY

Default:YES

Enter NO to change the initial setting of the TRAP ABEND field on the Trap Summary screens (1.6 and 9.6) to NO. The NO setting can be useful for debugging handle abend routines and UCHs.

TRAP_SUMMARY_USE_TERM

Default:YES

Enter YES to make the current terminal ID the default for the TERM field on the Trap Summary screens (1.6 and 9.6). Enter NO to make ALL (asterisks) the default.

TRAP_SUMMARY_USE_TERM_NETNAME

Default:NO

Enter YES to make the current terminal NETNAME the default for the NETNAME field on the Trap Summary screens (1.6 and 9.6). Enter NO to make ALL (asterisks) the default.

TRAP_SUMMARY_USE_USERID

Default:NO

Enter YES to make the current userID the default for the USERID field on the Trap Summary screens (1.6 and 9.6). Enter NO to make ALL (asterisks) the default.

TRAPS_USE_TERM_USERID_IN_IP_TRAPS

Default:NO

Enter YES to make the terminal’s user ID the default value in the USERID field for any TCPIP-based traps. TRAPS_USE_TERM_USERID_IN_IP_TRAPS may be set to YES regardless of the value for parameter WORKSTATIONS_USE_UNIQUE_IP_ADDRESSES. (See WORKSTATIONS_USE_UNIQUE_IP_ADDRESSES for more information.)

TRAPS_USE_TERM_USERID_IN_IP_TRAPS should be set to YES when:

• All TCPIP-based transactions in your environment require sign on.
• The same user ID is used for TCPIP transactions and the 3270 debugging session.
• That user ID is not shared by multiple CICS users.

The user ID will uniquely identify TCPIP-based traps even when the IP address does not.

UPDATE_INTERNAL_BRANCH_TRACE_TABLE

Default:YES

When this option is set to YES or FULL, Code Debug CICS updates an internal branch trace table to help diagnose any Code Debug CICS issues. Unless BMC Supporthas requested that you run with this option set to YES or FULL, it may be set to NO to save CPU.

UPPERCASE_TRANSID_ON_SCREENS

Default:YES

Enter YES to uppercase the transaction identifier on the Trap Summary, Program Trace, and Storage Protection screens. Enter NO if you want the case to remain as you typed it on these screens.

USE_COMPUWARE_WALLPAPER_3270_WEB_BRIDGE

Default:YES

Enter NO to suppress the BMC background wallpaper used for Code Debug CICS screens while running the 3270 Web Bridge.

USE_TERMINAL_READ_TIMEOUT_FOR_TASK

Default:YES

Enter YES to have Code Debug CICS use the terminal read timeout value (RTIMOUT) of the user transaction being debugged for its own conversations. If the user transaction being debugged has a terminal read timeout value of two minutes, Code Debug CICS and the user transaction converses both time out after two minutes. Enter NO to have Code Debug CICS ignore the terminal read timeout value of the user transaction during its converses. Entering NO causes Code Debug CICS converses to not be subjected to a read timeout value.

USER_PROFILE_DDNAME

Default:DBUGPRF

Enter a name for the user profile file. Changing USER_PROFILE_DDNAME requires changing the CSD entry. The XSIT transaction cannot be used to override this parameter.

USER_PROFILE_USERID_IS_KEY

Default:YES

Enter YES to use the userID field as the key for the profile record to load when starting an Code Debug CICS session. Specifying YES eliminates the need to enter XPED/XPRT/XPSP P=profilename, which obtains profile overrides when starting a session.

A profile is created for each userID sign on to CICS. The profiles are updated whenever a profile option is changed. Profile options are listed on the Set Profile Defaults screen (0.1).

VERIFY_OPTIONAL_FILES_AT_INITIALIZATION

Default:YES

Enter YES to have Code Debug CICS verify the presence of the Code Debug files DBUGPRF, DBUGSQL, and DBUGEMP. If these file do not exist in the CICS JCL, warning messages will be issued during the IVP. Because Code Debug issues an open of these files during initialization, DFHFC0951 messages will also be logged. Enter NO to have Code Debug not verify the files.

WAIT_TIME_REMOTE_TRAP_AUTO_SELECT

Default:6

Enter the maximum number of seconds to wait after resuming a remotely trapped task in the event that it reaches another breakpoint or abend and is automatically reselected. Valid values are 1 to 99.

WORKSTATIONS_USE_UNIQUE_IP_ADDRESSES

Default:NO

If automatic abend trapping is on (see PROFILE_DEFAULT_AUTO_ABEND_TRAPPING) and each of your TCPIP-connected workstations has a unique IP address, enter YES, and Code Debug will automatically generate unique TCPIP-based traps for individual debugging sessions.

Various techniques and hardware are used to connect workstations to the mainframe. If the connection method used in your environment provides a unique IP address for each TCPIP-connected workstation, change this parameter to YES to automatically generate unique TCPIP-based traps. If multiple TCPIP-connected workstations share the same IP address, and user IDs are also not unique (see parameter TRAPS_USE_TERM_USERID_IN_IP_TRAPS), enter NO.

XPOF_TERMINAL_SEND_RECEIVE_WAIT_TIME

Default:0

Enter the number of seconds Code Debug is to wait prior to each terminal SEND/RECEIVE issued during execution of the XPOF transaction. Valid values are 0 to 9.

Default Member XVGB00

Code Coverage parameters all relate to CICS and are delivered with Code Debug CICS.

AUTO_SUBMIT_JCL_DURING_EXTRACTION

Default:YES

Whether or not to automatically submit the Code Coverage template JCL during extraction. Enter NO to disable the automatic submission during extraction. If AUTO_SUBMIT_JCL_DURING_EXTRACTION is set to NO, the JCL to write the extracted data to the Code Coverage repository would need to be submitted manually.

CAPTURE_SYSTEM_FLOW_USING_GMT_TIME

Default:YES

Optionally capture System Flow data with local time (CAPTURE_SYSTEM_FLOW_USING_GMT_TIME=NO). Specifying CAPTURE_SYSTEM_FLOW_USING_GMT_TIME=YES will capture System Flow data with GMT/UTC.

CODE_COVERAGE_PARMLIB_REPORT_ALLOCATION

This parameter has been deprecated.

CODE_COVERAGE_PARMLIB_REPORT_DDNAME

Default:XVGR

A one- to four-character transient data queue name that the BMC PARMLIB report (Code Debug CICS Code Coverage Parameters) is written to.

CODE_COVERAGE_PARMLIB_REPORT_SYSOUT_CLS

This parameter has been deprecated.

DATA_EXTRACTION_INTERVAL

Default:42

The number of minutes between automatic data extractions. Valid values are from 1 to 1440.

INCREMENT_VERB_COUNTS

Default:YES

When this option is set to YES, Code Coverage will monitor application programs and increment verb counts as each instruction is executed. This is a very CPU-intensive process.

Set this option to NO when it is not necessary to count each time a verb is executed. When INCREMENT_VERB_COUNTS=NO, Code Coveragewill count each verb only the first time it is executed. To maximize the potential performance benefit of INCREMENT_VERB_COUNTS=NO, rules for Storage Protection and Program Trace are ignored when INCREMENT_VERB_COUNTS=NO and a Code Coverage test is active.

KEEP_PROGRAM_COUNTS_FOR_USERID

Default:********

Specifying KEEP_PROGRAM_COUNTS_FOR_USERID=******** causes program counts for a program to be kept separate by userID. Specifying KEEP_PROGRAM_COUNTS_FOR_USERID=USER1234 causes program counts to be kept under userID USER1234 for programs being covered, regardless of the userIDs that executed the programs.

LOG_INFO_MESSAGES

Default:YES

Used to disable the write to transient data queue function for Informational Data Extraction messages (XVTC4nnnI). The queue name is specified by the LOG_TDQ_NAME parameter. Enter NO to disable.

LOG_TDQ_NAME

Default:CSMT

The four-character name of the transient data queue to which Code Coverage is to direct error messages. This parameter cannot be changed when Code Coverage is active. It may be changed at Code Coverage initialization when the BMC PARMLIB is initially processed.

PRIME_OWNER_FILTER_WITH_CURRENT_USERID

Default:NO

Prime the Owner column filter value with the current userID (PRIME_OWNER_FILTER_WITH_CURRENT_USERID=YES). Prime the Owner column filter with asterisks (PRIME_OWNER_FILTER_WITH_CURRENT_USERID=NO).

TRANSID_XVCC

Default:XVCC

A four-character transaction ID to substitute for the XVCC transaction. Changing the value of TRANSID_XVCC requires changing the supplied resource definition.

TRANSID_XVKP

Default:XVKP

A four-character transaction ID to substitute for the XVKP transaction. Changing the value of TRANSID_XVKP requires changing the supplied resource definition.

TRANSID_XVSC

Default:XVSC

A four-character transaction ID to substitute for the XVSC transaction. Changing the value of TRANSID_XVSC requires changing the supplied resource definition.

TRANSID_XVSI

Default:XVSI

A four-character transaction ID to substitute for the XVSI transaction. Changing the value of TRANSID_XVSI requires changing the supplied resource definition.

TRANSID_XVTQ

Default:XVTQ

A four-character transaction ID to substitute for the XVTQ transaction. Changing the value of TRANSID_XVTQ requires changing the supplied resource definition.

WRITE_DATA_EXTRACTION_MSGS_TO_JES_LOG

Default:YES

Used to disable the write-to-operator (WTO) function for the XVTC4001 Data Extraction complete message and other Informational Data Extraction messages (XVTC4nnnI). A WTO is normally issued each time a data extraction is performed. Enter NO to disable.