Milestone 7: Specifying Additional Configuration Parameters

This section contains details regarding configuration of Code Debug CICS to suit your site’s needs.

If you are performing a new installation of Code Debug CICS (as opposed to an upgrade), you may want to go to Milestone 9: Verify Product Installation before addressing this milestone. If you choose to do so, make sure to perform product verification after performing any additional configuration.

The Code Debug CICS Installer role is involved in this task.

Complete the following tasks to specify additional configuration parameters.

Task 7.1 Specifying Configuration Parameters at Product Initialization

Code Debug CICS includes a facility that allows you to specify most configuration parameter values using BMC PARMLIB at product initialization. Most parameter values can be refreshed while Code Debug is active by entering the transaction XSIT.

Restrictions regarding particular parameters that are not eligible for processing from BMC PARMLIB, and alternative means to specify them, are detailed in “Overriding-Session-Initialization-Transactions” in the Code Debug CICS Advanced Configuration Guide.

Task 7.2 Enabling Restricted Operating Modes

In addition to its standard operating mode, Code Debug CICS can be activated in three restricted modes of operation:

• Diagnosis Mode
• Utilities Mode
• Diagnosis/Utilities Mode.

These modes allow a site to tailor its Code Debug implementation to suit the processing integrity and response time requirements of its various CICS regions. In this way, a customer can eliminate unnecessary processing overhead while preventing any potentially disruptive user activity.

Details about configuring restricted operating modes can be found in “Configuring-Restricted-Operating-Modes” in the Code Debug CICS Advanced Configuration Guide.

Task 7.3 Parameter Processing Overview

Parameters are read from the BMC PARMLIB.

As the input is processed, a BMC PARMLIB Report (Code Debug CICS Parameters) is written to a transient data queue which must be defined as Extrapartition. The default queue name for this report is XGBR. The PARMLIB_REPORT_DDNAME configuration parameter can be used to change the name of the report queue.

Parameters are processed in the order in which they are read. Blank records and comment records are ignored. Parameters are written to the output report.

If an error is detected in a parameter, processing continues and an error message is written to the output report. For a list of possible messages, see to the Code Debug CICS Messages and Codes space.

Task 7.4 Code Debug CICS Parameters Report

The following figure is a sample Code Debug CICS Parameters report. The highlighted numbered references are discussed following the figure.

Sample Code Debug CICS Parameters Report 

[1] The third heading line indicates the CICS region applid, date, time, terminal, and userID of the user logged on to the terminal when program DBUGSIT was run.

[2] These heading lines indicate the transient data queue used for the report. In addition, they indicate whether the queue used is the default name or has been overridden by the user.

[3] Input parameters are displayed from here down. This provides a complete audit of the parameters processed.

[4] Comments in the BMC PARMLIB member are not displayed.

[5] The CMSC ID of the BMC AMI Mainframe Services Controller (CMSC) where the BMC PARMLIB memory objects reside.

[6] The data set where the memory object for XD$$00 was refreshed from.

[7] The concatenation order of the input members to be processed as derived from the index member XD$$00.

[8] A comment box precedes the data for each CMSC memory object read. It will display the data set where the memory object was refreshed from.

[9] When an error is detected on an input record, the error is flagged. The line that follows contains a message indicating the error detected and is also flagged. Only the first error detected for a parameter is flagged.

[10] After all parameters have been processed, the report will show values for all available parameters with the specified/default values shown. The figure shows a small sample of parameters.

Task 7.5 Code Debug CICS Parameters Log Output

Messages are written to the console log whenever the Code Debug CICS Parameter process is run. In addition to messages indicating the start and end of processing, any errors related to data set attributes are also written to the console. The following figure is a sample of output written to the console.

Messages that do not apply to a particular input parameter are displayed with two lines per message. All messages contain similar information on the first line including a message number, severity level, date, time, and region applid.

Sample Global Table Override Console Log Output

In addition to the console log output shown in above figure, the input processing program for the parameter override process will display additional informational and error messages in the CICS CSMT output queue. Following figure provides a sample display of messages that can be output.

Sample Global Table Override CICS CSMT Output Queue Messages

Task 7.6 Overriding Transaction Identifiers DBPA, XPED, XPRT, XPON, or XPSP

In extremely rare instances, your installation may already have transaction identifiers DBPA, XPED, XPRT, XPON, or XPSP assigned to other programs. If you absolutely need to change the transaction identifiers for these Code Debug CICS transactions, see the section Overriding-Session-Initialization-Transactions in the Code Debug CICS Advanced Configuration Guide for instructions on overriding transaction identifiers DBPA, XPED, XPRT, XPON, or XPSP.