The Create Java Debugging Profile screen
Use the "Create Java Debugging Profile" screen to work with the contents
of a debugging profile for Java programs. You can use the screen to perform
the following functions:
- Create a new profile
- Initially, the screen contains default values for some of the fields.
You must supply other values to complete the profile.
- Edit an existing profile
- Initially, the screen contains the values that were previously defined
for the profile.
The screen is in two parts; use PF7 and PF8 to scroll between them.
Figure 9. The CADP Create Java Debugging Profile screens
CADP - CICS Application Debugging Profile Manager - IYK2Z2T1
Create Java Debugging Profile ==> for CICSUSER
CICS Resources To Debug (use * to specify generic values e.g. *, A*, AB*, etc.)
Transaction ==> Applid ==> IYK2Z2T1
Userid ==> CICSUSER
Debugging Options
JVM Profile ==>
Java Resources To Debug
Type ==> J (J=Java Applications, E=Enterprise Beans, C=Corba)
Class (Java Applications or Corba)
==>
==>
==>
==>
Press PF8 to set Bean and Method
Enter=Create PF1=Help 2=Save options as defaults 3=Exit 8=Forward
10=Replace 12=Return
CADP - CICS Application Debugging Profile Manager - IYK2Z2T1
Java Resources To Debug
Bean (Enterprise Beans only)
==>
==>
==>
==>
Method (Enterprise Beans or Corba)
==>
==>
==>
==>
Enter=Create PF1=Help 3=Exit 7=Back 10=Replace 12=Return
Fields on the Create Java Debugging Profile screen
The fields on the "Create Java Debugging Profile" screen are:
- Create Java Debugging Profile
- Specifies the name of the profile. If you change the name of an existing
profile, CADP creates a new profile with the new name, and leaves the original
profile unchanged.
Acceptable characters
A-Z 0-9 $ @ #
Any lower case characters you enter are converted to upper case.
The following fields specify which programs should trigger the
start of a debugging session when the profile is active.
- Transaction
- Specify a value in this field when you want to debug only those programs
that run under the specified transaction id.
Acceptable characters
A-Z a-z 0-9 $ @ # . / - _ % & ¢ ? ! : | " = ¬ , ; < >
You can specify a generic value if you want to debug programs that
run under a set of similarly-named transactions.
Note:
Do not specify
an alias transaction name in this field; CICS does not support the use of
alias transaction names to select programs for debugging.
- Applid
- Specify a value in this field when you want to confine debugging to
programs that run in the specified CICS region. The default value is the applid
of the region where the Debugging Profile Manager is running.
Acceptable characters
A-Z 0-9 $ @ #
Any lower case characters you enter are converted to upper case.
You can specify a generic value if you want to debug programs in a
set of similarly-named regions.
- Userid
- Specify a value in this field when you want to confine debugging to
programs that are being run by the specified user. The default value is the
ID of the user that is using the debugging profile manager.
Acceptable characters
A-Z 0-9 $ @ #
Any lower case characters you enter are converted to upper case.
You can specify a generic value if you want to debug programs that
are being run by a group of similarly-named users.
Important:
The user ID specified here is not necessarily the owner of the profile:
the owner of the profile is the user who created it.
The following field specifies the debugging options for this profile.
You can save the value that you specify; the saved value is used by default
each time you create a Java debugging profile. To save the value, press PF2.
- JVM profile
- Specifies the name of the JVM profile that is used for Java programs
that match this profile. The profile should specify that the Java program
is to run in debug mode. For more information about the JVM profile, see the Java™ Applications in CICS®.
The following fields specify which Java resources should trigger
the start of a debugging session when the profile is active:
- Type
- Specifies the type of Java resource that you want to debug:
- J
- Enter this value when you want to debug a Java program.
- E
- Enter this value when you want to debug an enterprise bean.
- C
- Enter this value when you want to debug a stateless CORBA object.
- Class
- For Java programs and stateless CORBA objects only, specify a value
in this field when you want to debug only the specified class. You can specify
a generic value if you want to debug a set of similarly-named classes.
- Bean
- For enterprise beans only, specify a value in this field when you want
to debug only the specified bean. You can specify a generic value if you want
to debug a set of similarly-named beans.
- Method
- For enterprise beans and CORBA objects only, specify a value in this
field when you want to debug only the specified method.
When an inbound
request initiated by a Java remote method invocation is received, the value
specified is compared with the mangled name in the inbound request to determine
if the profile matches the request. If it is possible that mangling can take
place, do not specify a method name in the debugging profile, but specify
a generic method instead. For more information about mangling of method names,
see the Java Applications in CICS.
Function keys for the Create Java Debugging Profile screen
The function keys for the "Create Java Debugging Profile" screen are:
- PF1
- Display the help screen
- PF2
- Save the contents of the JVM profile field. The
saved value is used by default each time you create a Java debugging profile.
- PF3
- End the debugging profile manager
- PF7
- Scroll forward
- PF8
- Scroll backward
- PF10
- Update an existing profile with the information on the screen
- PF12
- Return to the "List Debugging Profiles" screen
the CICS Application Programming Guide
[[ Contents Previous Page | Next Page Index ]]