Rational Developer for System z, Version 7.6

Starting Debug Tool under CICS

This topic compares the different methods you can use to start Debug Tool and gives instructions on each method. This topic assumes you have completed the following tasks:

Comparison of methods for starting Debug Tool under CICS

There are several different mechanisms available to start Debug Tool under CICS. Each mechanism has a different advantage and are listed below:

If your program uses several of these methods, the order of precedence is determined by Language Environment. For more information about the order of precedence for Language Environment run-time options, see z/OS Language Environment Programming Guide.

Starting Debug Tool under CICS by using DTCN

If a DTCN profile exists, when a CICS program starts, Debug Tool analyzes the program's resources to see if they match a profile. If Debug Tool finds a match, Debug Tool starts a debugging session for that program. If multiple profiles exist, Debug Tool selects the profile with the greatest number of resources that match the program. If two programs have an equal number of matching resources, Debug Tool selects the older profile.

Before you begin, verify that you prepared your CICS program as instructed in Preparing a CICS program.

To start Debug Tool under CICS by using DTCN, do the following steps:

  1. If you chose screen control mode, start the DTSC transaction on the terminal you specified in the Display Id field.
  2. Run your CICS programs. If Debug Tool identifies a task that matches a DTCN profile, Debug Tool starts. If you chose screen control mode, press Enter on the terminal running the DTSC transaction to connect to Debug Tool.

Ending a CICS debugging session that was started by DTCN

After you have finished debugging your program, use DTCN again to turn off your debug profile by pressing PF6 to delete your debug profile and then pressing PF3 to exit. You do not need to remove EQADCCXT from the load module; in fact, it’s a good idea to leave it there for the next time you want to start Debug Tool.

Example: How Debug Tool chooses a CICS program for debugging

For example, consider the following two profiles:

When PROG1 is run by USER1, profile A is used.

If this situation occurs, an error message is displayed on the system console, suggesting that you should specify additional resource IDs. In the above example, each profile should specify both a user ID and a program ID.

Refer to the following topics for more information related to the material discussed in this topic.

Starting Debug Tool for CICS programs by using CADP

Before you begin, verify that you prepared your CICS program as instructed in Preparing a CICS program.

To start Debug Tool under CICS by using CADP, do the following steps:

  1. If you chose screen control mode, start the DTSC transaction on the terminal you specified in the Display Id field.
  2. Run your CICS programs. If Debug Tool identifies a task that matches a CADP profile, Debug Tool starts. If you chose screen control mode, press Enter on the terminal running the DTSC transaction to connect to Debug Tool.

Refer to the following topics for more information related to the material discussed in this topic.

Starting Debug Tool under CICS by using CEEUOPT

To request that Language Environment start Debug Tool every time the application is run, assemble a CEEUOPT module with an appropriate TEST run-time option. It is a good idea to link-edit the CEEUOPT module into a library and just add an INCLUDE LibraryDDname(CEEUOPT-MemberName) statement to the link-edit options when you link your application. Once the application program has been placed in the load library (and NEWCOPY'd if required), whenever it is run Debug Tool will be started.

Debug Tool runs in the mode defined in the TEST run-time option you supplied, normally Single Terminal mode, although you could provide a primary commands file and a log file and not use a terminal at all.

To start Debug Tool, simply run the application. Don't forget to remove the CEEUOPT containing your TEST run-time option when you have finished debugging your program.

Refer to the following topics for more information related to the material discussed in this topic.

Starting Debug Tool under CICS by using compiler directives

When compile-directives are processed by your program, Debug Tool will be started in single terminal mode (this method supports only single terminal mode).

Refer to the following topics for more information related to the material discussed in this topic.


Terms of use | Feedback

This information center is powered by Eclipse technology. (http://www.eclipse.org)