| CICS |
Target CICS Region |
Select the CICS region
name. You need to have defined at least one CICS connection to be able to view CICS regions. This field is required. |
| |
Transaction name |
Specify the CICS transaction
to debug. This field, or the Program name field,
is required. |
| |
Program name |
Specify the program or programs that you want
to debug. This field, or the Transaction name field,
is required.Note: This option appears if your site is running IBM Debug Tool version 9.1 on the
remote system. Use the CICS Debug
Configuration preference page to specify the IBM Debug Tool version. To open this preference
page, click the Preferences link.
|
| |
Load Module and Compile Unit |
Specify the load module name and compile unit
name combination(s) that you want to debug. This field, or the Transaction
Name field, is required. Use the Add, Edit,
and Remove buttons to specify the load module
name and compile unit name combination that you want to debug. Note: This
option appears if your site is running IBM Debug
Tool version 10.1 on the remote system. Use the CICS Debug Configuration preference page
to specify the IBM Debug Tool
version. To open this preference page, click the Preferences link.
|
| |
User ID |
Specify the user identifier associated with
the transaction you want to debug. |
| |
Netname |
Specify the four-character name of a CICS terminal or a CICS system that you want to use to run your
debugging session. |
| |
IP |
The client IP name or IP address that is associated
with a CICS application. All
IP names are treated as uppercase. you can specify wildcard characters
(* and ?). Debug Tool is invoked for every task that is started for
the client. |
| |
Profile activation |
Select one of the following radio buttons to
activate or inactivate the current profile:- Activate this configuration as the debug profile on
the remote system
- Inactivate this configuration
Although you can create multiple CICS debug
configurations on the client, only one profile associated with your
user ID can be active on the remote system. When you activate one
debug configuration, all others are automatically inactivated. |
| Debug Options |
Test option |
Specify TEST or NOTEST. This
option specifies the conditions under which Debug Tool assumes control
during the initialization of your application. |
| |
Test level |
Specify ALL, ERROR, or NONE. This
option specifies what conditions need to be met for Debug Tool to
gain control. |
| |
Commands file |
A valid fully qualified data set name that specifies
the primary commands file for this run. Do not enclose the name of
the data set in quotation marks (") or apostrophes ('). |
| |
Prompt level |
Specifies whether Debug Tool is started at Language Environment® initialization.
|
| |
Preference file |
A valid fully qualified data set name that specifies
the preferences file to be used. Do not enclose the name of the data
set in quotation marks (") or apostrophes ('). |
| |
Language
Environment options |
Any other valid Language Environment options.
You can change any Language
Environment option that your site allows you to override except
the STACK option. For additional information about Language Environment options,
see the z/OS Language Environment Programming
Reference or contact your CICS system
programmer. |
| Connection |
Workstation IP |
Either the IP address or host name of the workstation
that will display the debug screens. This field is filled automatically
by using the Java™ API (InetAddress)
to retrieve the client's TCP/IP address. There are a few scenarios
in which the Java API might
fail to give the correct IP address, such as double firewalls and
NAT. If the correct IP address is not recorded, you must update the
IP address manually. |
| |
Port |
Specifies the TCP/IP port number that is listening
for debug sessions on your workstation. The default is 8001. The port
number is retrieved using the Debug Tool client API (that is, the
Debug Daemon port specified in the Debug
Daemon preference page). |
| Advanced |
COMMAREA Offset |
The offset of data in a COMMAREA passed to a
program on invocation. The offset can be given in character format
(such as 12) or in hexadecimal (such as X'C'). |
| |
COMMAREA Data |
A data pattern to be matched against a COMMAREA
passed to a program on invocation. The data pattern can be given in
character format (such as ABC) or in hexadecimal (such as X'C1C2C3')
with an even number of digits. |
| |
Container Name |
The name of a container within the current channel
passed to a program on invocation. The container name is case sensitive.
|
| |
Container Offset |
The offset of data in the named container passed
to a program on invocation. The offset can be given in character format
(such as 12) or in hexadecimal (such as X'C'). |
| |
Container Data |
A data pattern to be matched against a container
within the current channel passed to a program on invocation. The
data pattern can be given in character format (such as ABC) or in
hexadecimal (such as X'C1C2C3') with an even number of digits. |
| |
URM Debugging |
A flag that specifies whether to include the
debugging of URMs as part of the debug session. |