Description of fields on the DTCN Primary Menu screen

This topic describes the fields that are displayed on the DTCN Primary Menu screen.

The following list describes the resources you can specify to help identify the program or transaction that you want to debug:

Terminal Id

Specify the CICS® terminal identifier associated with the transaction you want to debug. By default, DTCN sets the ID by one of the following rules:

If the type of repository is a VSAM file and the current user ID has a saved profile, DTCN fills in the field with the terminal ID that is in the repository. You can change the terminal ID to the ID of the terminal you are currently running on, by placing your cursor on the terminal ID field and then pressing PF10. Press PF4 to save the profile with this new value.
If the type of repository is a VSAM file and the current user ID does not have a saved profile, the terminal ID field is filled in with the ID of the terminal you are currently running on.
If the type of repository is a temporary storage queue, the terminal ID field is filled in with the ID of the terminal you are currently running on.
If the CICS transaction or program that you want to debug is not associated with a specific terminal (for example, the request to start a debug session comes from a browser), make this field blank.

If YES is specified for the EQAOPTS DTCNFORCETERMID command, you must specify a terminal identifier. To learn about the EQAOPTS DTCNFORCETERMID command, see the topic EQAOPTS commands in the IBM® z/OS Debugger Customization Guide or IBM z/OS Debugger Reference and Messages.

Transaction Id

Specify the CICS transaction to debug. If you specify a transaction ID without any other resource, z/OS® Debugger is started every time any of the following situations occurs:

You run the transaction.
The first program run by the transaction is started.
Any other user runs the transaction.
Any enabled DFH* module is the first program run by the transaction.

To start z/OS Debugger at the desired program that the transaction runs, specify the program name in the Program Id(s) field.

If YES is specified for the EQAOPTS DTCNFORCETRANID command, you must specify a transaction ID. To learn about the EQAOPTS DTCNFORCETRANID command, see the topic EQAOPTS commands in the IBM z/OS Debugger Customization Guide or IBM z/OS Debugger Reference and Messages.

LoadMod::>CU(s)

Specify the resource pair or pairs, consisting of a load module name and a compile unit (CU) name that you want to debug. Type in the load module name after the ==> and the corresponding CU name after the ::>. You can specify any of the following names:

LoadMod

The name of a load module that you want to debug. The load module must comply with the following requirements:

For z/OS Debugger initialization, the load module can be any CICS load module if it is invoked as an Language Environment® enclave or over a CICS Link Level. This includes the following types of load modules:
- The initial load module in a transaction.
- A load module invoked by CICS LINK or XCTL.

CU

The name of the compile unit (CU) that you want to debug. The CU must comply with the following requirements:

Any CICS CU if it is invoked as an Language Environment enclave or over a CICS Link Level. This includes the following types of CUs:
- The initial CU in a transaction
- A CU invoked by CICS LINK or XCTL
Any COBOL CU, even if it is a CU within a composite load module invoked by a static CALL or it is a CU in a load module that is invoked by a dynamic CALL.
Any Enterprise PL/I for z/OS Version 3 Release 4 CU (with the PTF for APAR PK03264 applied), or later, even if it is a CU within a composite load module invoked by a static CALL or it is a CU in a load module that is invoked by a dynamic CALL.
Any non-Language Environment assembler CU which is loaded through an EXEC CICS LOAD command.

Usage Notes:

If you specify a LoadMod and leave the corresponding CU field blank, the CU field defaults to an asterisk (*).
If you specify a CU and leave the corresponding LoadMod field blank, the LoadMod field defaults to an asterisk (*).
If you leave all LoadMod and CU fields blank and you set the Prompt Level on the z/OS Debugger CICS Control - Menu 2 to PROMPT, z/OS Debugger initializes for the first program invoked.
If you migrate from a version of z/OS Debugger prior to Version 10.1, you can obtain the same behavior produced by the DTCN Program Id resource by using the LoadMod::>CU resource pair and specifying only the CU resource. The LoadMod resource defaults to an asterisk (*).
You can specify wildcard characters (*) and (?).
If z/OS Debugger was started by another program before the EXEC CICS LOAD command that starts this non-Language Environment assembler program, you need to enter one of the following commands so that z/OS Debugger gains control of this program:
- LDD
- SET ASSEMBLER ON
- SET DISASSEMBLY ON
When you specify a CU for C/C++ and Enterprise PL/I programs (languages that use a fully qualified data set name as the compile unit name), you must specify the correct part of the compile unit name in the CU field. Use the following rules to determine which part of the compile unit name you need to specify:
- If you are using a PDS or PDSE, you must specify the member name. For example, if the compile unit names are DEV1.TEST.ENTPLI.SOURCE(ABC) and DEV1.TEST.C.SOURCE(XYZ), you must specify ABC and XYZ in the program ID field.
- If you are using a sequential data set, specify one of the following:
  - The last qualifier of the sequential data set. For example, if the compile unit names are DEV1.TEST.ENTPLI.SOURCE.ABC and DEV1.TEST.C.SOURCE.XYZ, you must specify ABC and XYZ in the program ID field.
  - Wildcards. For example, if the compile unit names are DEV1.TEST.ENTPLI.ABC.SOURCE and DEV1.TEST.C.XYZ.SOURCE, you must specify *ABC* and *XYZ* in the program ID field.
- If you compiled your PL/I program with the following compiler, you need to use the package name or the main procedure name:
  - Enterprise PL/I for z/OS, Version 3.5, with the PTFs for APARs PK35230 and PK35489 applied
  - Enterprise PL/I for z/OS, Version 3.6 or later
Specifying a CICS program in the LoadMod::>CU field is similar to setting a breakpoint by using the AT ENTRY command and z/OS Debugger stops each time you enter LoadMod::>CU.
If z/OS Debugger is already running and it cannot find the separate debug file, then z/OS Debugger does not stop at the CICS program specified in the LoadMod::>CU field. Use the AT APPEARANCE or AT ENTRY command to stop at this CICS program.
If YES is specified for the EQAOPTS DTCNFORCELOADMODID command, you must specify a value for the LoadMod field. To learn about the EQAOPTS DTCNFORCELOADMODID command, see the topic EQAOPTS commands in the IBM z/OS Debugger Customization Guide or IBM z/OS Debugger Reference and Messages.
If YES is specified for the EQAOPTS DTCNFORCEPROGID or DTCNFORCECUID commands, you must specify a value for the CU field. To learn about the EQAOPTS DTCNFORCEPROGID or DTCNFORCECUID commands, see the topic EQAOPTS commands in the IBM z/OS Debugger Customization Guide or IBM z/OS Debugger Reference and Messages.

User Id

Specify the user identifier associated with the transaction you want to debug. The following list can help you decide what to enter in this field:

If the user identifier is the same one that is currently running DTCN, use the default user identifier.
If the user identifier is different than the one currently running DTCN and you know the user identifier, enter that user identifier.
If you do not know the user identifier or the transaction is not associated with a user identifier, specify the wild character or blanks.

If YES is specified for the EQAOPTS DTCNFORCEUSERID command, you must specify a user identifier. To learn about the EQAOPTS DTCNFORCEUSERID command, see the topic EQAOPTS commands in the IBM z/OS Debugger Customization Guide or IBM z/OS Debugger Reference and Messages.

NetName

Specify the four character name of a CICS terminal or a CICS system that you want to use to run your debugging session. This name is used by VTAM® to identify the CICS terminal or system.

If YES is specified for the EQAOPTS DTCNFORCENETNAME command, you must specify a value for the NetName field. To learn about the EQAOPTS DTCNFORCENETNAME command, see the topic EQAOPTS commands in the IBM z/OS Debugger Customization Guide or IBM z/OS Debugger Reference and Messages.

IP Name/Address

The client IP name or IP address that is associated with a CICS application. All IP names are treated as upper case. Wildcards (* and ?) are permitted. z/OS Debugger is invoked for every task that is started for that client.

If YES is specified for the EQAOPTS DTCNFORCEIP command, you must specify an IP address. To learn about the EQAOPTS DTCNFORCEIP command, see the topic EQAOPTS commands in the IBM z/OS Debugger Customization Guide or IBM z/OS Debugger Reference and Messages.

The following list describes the fields that you can use to indicate which type of debugging session you want to run.

Session Type

Select one of the following options:

MFI: Indicates that z/OS Debugger initializes on a 3270 type of terminal.
TCP: Indicates that you want to interact with z/OS Debugger using a remote debugger connected with a TCP/IP host name or address.
DTC: Indicates that you want to interact with z/OS Debugger using a remote debugger connected with a z/OS Debugger Debug Manager userid.
RDS: Indicates that you want to start a debug session with IBM Z® Open Debug using Remote Debug Service.

Port Number

Specifies the TCP/IP port number that the debug daemon is listening for debug or code coverage sessions. The debug daemon default port is 8001. If you entered DTC in the Session Type field, this field must be left blank.

Display Id

Identifies the target destination for z/OS Debugger.

If you entered DTC in the Session Type field, enter the userid that your workstation is using to connect to the z/OS remote system.

If you entered TCP in the Session Type field, determine the IP address or host name of the workstation that is running the remote debugger. Change the value in the Display Id field by doing the following steps:

Place your cursor on the Display Id field.
Type in the IP address or host name of the workstation that is running the remote debugger.
To save the profile with this new value, press PF4.

If you entered MFI in the Session Type field, DTCN fills in the Display Id field according to the following rules:

If the type of repository is a VSAM file and the current user ID has a saved profile, DTCN fills in the field with the display ID that is in the repository.
If the type of repository is a VSAM file and the current user ID does not have a saved profile, DTCN fills in the field with the ID of the terminal you are currently running on.
If the type of repository is a temporary storage queue, DTCN fills in the field with the ID of the terminal you are currently running on.

You can use one of the following terminal modes to display z/OS Debugger on a 3270 terminal:

Single terminal mode: z/OS Debugger and the application program share the same terminal. To use this mode, enter the ID of the terminal being used by your application program or move the cursor to the Display ID field and press PF10.
Screen control mode: z/OS Debugger displays its screens on a terminal which is running the DTSC transaction. To use this mode, start the DTSC transaction on a terminal and specify that terminal’s ID in the Display ID field.
Separate terminal mode: z/OS Debugger displays its screens on a terminal which is available for use (not associated with any transaction) and can be located by CICS. To use this mode, specify the terminal’s ID in the Display ID field.