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:
There are several different mechanisms available to start Debug Tool under CICS. Each mechanism has a different advantage and are listed below:
This mechanism can be useful during initial testing of new code when you will want to run Debug Tool frequently.
These directives can be useful when you need to run multiple debug sessions for a piece of code that is deep inside a multiple enclave or multiple CU application. The application runs without Debug Tool until it encounters the directive, at which time Debug Tool is started at the precise point that you specify. With CALL CEETEST, you can even make the invocation of Debug Tool conditional, depending on variables that the application can test.
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.
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:
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.
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.
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:
Refer to the following topics for more information related to the material discussed in this topic.
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.
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.