Debugging profiles

A debugging profile specifies a set of one or more application programs which are to be debugged together. For example:

CICS uses the following information in the debugging profile to decide if an instance of a program should run under the debugger's control. The parameters specify:

Many of the parameters can be generic, allowing you to specify a set of values which begin with the same characters (for example, TRN0, TRN1, TRN2, TRNA, TRNB, ...)

Debugging profiles contain the following additional information:

Status
The status of the profile: active or inactive:
Debugging display device settings
The debugging display device settings specify how you will interact with the debugger:
The JVM profile name
For Java programs only, you can specify the JVM profile that will be used when a program is debugged
Debug Tool and Language Environment® options
For compiled language programs only, you can specify options to be passed to Debug Tool and Language Environment when a program is debugged

You can create debugging profiles for the following sorts of program:

The information stored in the profile is different for each type of program.

Profiles are stored in a CICS file which can be shared by more than one CICS region. A profile that is shared by several CICS regions is either active or inactive in all the regions: it cannot be active in some regions and inactive in others.

CICS provides a set of sample profiles which are optionally generated when your system is set up to use debugging profiles. You can use these profiles as a starting point for creating your own profiles.

[[ Contents Previous Page | Next Page Index ]]