Using IBM Application Development Tools for z/OS and OS/390

416 Using IBM Application Development Tools for z/OS and OS/390

20.1 CICS application program considerations

To compile your COBOL and PL/I CICS-applications, we recommend using the CICS

(CICS-TS V2.1 and up) integrated translator for two reasons:

򐂰 Debugging becomes much more comfortable, because you will not be presented with the

inserted resolution of your EXEC CICS statements.

򐂰 If you use the external translator, you will need to save the translator output (which

becomes the input to the compiler) to a permanent data set, if you use VisualAge PL/I

(and later compilers). This is not needed if you compile with the integrated translator,

since your source is directly the input to the compilers.

We also recommend using dynamic debugging and a separate debug file, and separate

special RACF® authorization is needed if your applications are loaded in protected storage,

as they are in CICS if linked REENTRANT and if the CICS System Initialization Table (SIT)

includes RENTPGM=PROTECT.

20.2 Invoking Debug Tool

In this section we describe how to use Debug Tool with CICS.

To invoke Debug Tool in CICS, issue the DTCN transaction. DTCN is a full-screen CICS

interface that allows you to modify any Language Environment runtime option for your

application program. For this to work, you need to have included EQADCCXT during link.

Figure 20-1 shows the panel displayed after the DTCN transaction is issued. To use the HELP

function, put the cursor at any field on the screen and press PF1. Help information for the field

NetName is shown in Figure 20-2.

Figure 20-1 Primary Menu

Chapter 20. Using Debug Tool with CICS 417

Figure 20-2 Help information

The DTCN transaction is used to create profiles for the resource IDs you want to debug.

Specify the combination of resource IDs that you want to debug on the primary menu.

򐂰 Terminal ID:

Specify the CICS terminal to debug. By default, this ID is set to the terminal that is

currently running DTCN.

򐂰 Transaction ID:

Specify the CICS transaction to debug. If you specify a transaction ID without any other

resource, Debug Tool is started

every time that transaction is run, including times when

other users run the transaction.

򐂰 Program IDs:

Specify the CICS program or programs to debug. If you specify a program ID without any

other resource, Debug Tool is started

every time the program is run, including times when

other users run the program.

򐂰 User ID:

Specify the CICS user ID to debug. All programs that are run by this user will start Debug

Tool.

򐂰 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.

You can use any combination of these parameters.

For example, if you enter the terminal ID and the program ID, Debug Tool will only be started

if both match exactly.

418 Using IBM Application Development Tools for z/OS and OS/390

򐂰 Session Type: Select one of the following options:

– MFI: Indicates that Debug Tool initializes on a 3270 type of terminal.

– TCP: Indicates that you want to interact with Debug Tool from your workstation using

TCP/IP and the VisualAge Remote Debugger or the IBM Distributed Debugger, which

is shipped with most VisualAge compiler products.

– WSD: Indicates that you want to interact with Debug Tool from your workstation using

TCP/IP and the Compiled language debugger, which is shipped with WebSphere

Studio Enterprise Developer.

– Port Number: Specifies the logical connector between the CICS terminal and TCP/IP.

– Display Id: Identifies the target destination for Debug Tool information. Depending on

the session type that you’ve selected, the display ID is one of the following:

• If you selected MFI, the display ID is a CICS 3270 terminal ID. This ID is set by

default to the terminal ID that is currently running DTCN, but you can change this to

direct MFI screens to a different CICS terminal.

• If you selected TCP or WSD, enter either the IP address or host name of the

workstation that will display the debug screens. For the debug session to start, the

appropriate software must be running on that workstation.