Fields on the Create Java profile page
- Debugging Profile
- Specifies the name of the profile.
If you are working with an existing profile, and you change the name that is displayed, the application debugging profile manager 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.
You can specify a generic value if you want to debug programs that run under a set of similarly name transactions.Acceptable characters A-Z a-z 0-9 $ @ # . / - _ % & ¢ ? ! : | " = ¬ , ; < >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.
You can specify a generic value if you want to debug programs in a set of similarly-named regions.Acceptable characters A-Z 0-9 $ @ #Any lower case characters you enter are converted to upper case.
- 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.
You can specify a generic value if you want to debug programs that are being run by a group of similarly-named users.Acceptable characters A-Z 0-9 $ @ #Any lower case characters you enter are converted to upper case.
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 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:
- Java
- Select this value when you want to debug a Java program.
- EJB
- Select this value when you want to debug an enterprise bean.
- CORBA
- Select 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 stateless 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.
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.
- 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. You cannot specify a generic value for this parameter.