The Create Compiled Debugging Profile screen

Use the "Create Compiled Debugging Profile" screen to work with the contents of a debugging profile for compiled language 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.
Figure 8. The CADP Create Compiled Debugging Profile screen
 CADP      -    CICS Application Debugging Profile Manager   -     IYK2Z2T1     
                                                                                
 Create Compiled Debugging Profile ==>           for CICSUSER                         
                                                                                
                                                                                
 CICS Resources To Debug (use * to specify generic values e.g. *, A*, AB*, etc.)
 Transaction      ==>                                  Applid   ==> IYK2Z2T1    
 Program          ==>                                  Userid   ==> CICSUSER    
 Compile Unit     ==>                                  Termid   ==> TC15        
                                                       Netname  ==> IYCWTC15    
                                                                                
 Debug Tool Language Environment Options                                        
 Test Level       ==> All                                     (All,Error,None)  
 Command File     ==>                                                           
 Prompt Level     ==> PROMPT                                                    
 Preference File  ==>                                                           
                                                                                
 Other Language Environment Options                                             
 ==>                                                                            
 ==>                                                                            
 ==>                                                                            
 ==>                                                                            
                                                                                
 Enter=Create PF1=Help 2=Save options as defaults 3=Exit 10=Replace 12=Return   

Fields on the Create Compiled Debugging Profile screen

The fields on the "Create Compiled Debugging Profile" screen are:

Create Compiled Debugging Profile
Specify 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 $ @ # . / - _ % & ¢ ? ! : | " = ¬ , ; < >

Because transaction ids are case-sensitive, any lower case characters you enter are not converted to upper case.

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.
Program
Start of changeSpecify a value in this field when you want to debug only the specified program. In this context the program is the program as known to CICS, such as a load module name, initial program in a transaction or a program that has been XCTL'd or LINKed to.
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 a set of similarly-named programs.End of change
Compile unit
Start of changeSpecify a value in this field when you want to debug only the specified compile unit. You can specify a generic value if you want to debug a set of similarly-named compile units. In this context the compile unit is the program as known to the compiler; for example, PROGRAM-ID for COBOL and the main PROCEDURE name for PL/I.
Acceptable characters
A-Z a-z 0-9 $ @ # . / - _ % & ¢ ? ! : | " = ¬ , ; < >

Because compile unit names are case-sensitive, any lower case characters you enter are not converted to upper case.

End of change
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 who 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.
Termid
Specify a value in this field when you want to confine debugging to programs that are being run at the specified terminal.
Acceptable characters
A-Z a-z 0-9 $ @ # . / - _ % & ¢ ? ! : | " = ¬ , ; < >
Restriction:
You cannot specify a terminal ID that consists entirely of blanks
You can specify a generic value if you want to debug programs that are being run at a number of similarly-named terminals.
Important:
The terminal specified here is not necessarily the terminal at which the debugging session is conducted. The terminal used for the debugging session is specified in the "Set Compiled Debugging Display Device" screen.
Netname
Specify a value in this field when you want to confine debugging to programs that are being run at terminals with the specified netname.
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 at a number of terminals with similar netnames.

The following fields specify suboptions of the TEST run-time option, and are passed to Debug Tool. See the Debug Tool for z/OS and OS/390 User’s Guide for more information. You can save the values that you specify; the saved values are used by default each time you create a debugging profile for a compiled language (Language Environment) program. For more information, see Specifying default values for Debug Tool and Language Environment options.

Test level
Specifies which conditions raised by your program will cause Debug Tool to gain control. You can enter the following values:
Command file
Specifies the primary commands file associated with the profile. You can specify the fully qualified name of a sequential dataset or a member of a partitioned data set.
Prompt level
Specifies whether an initial commands list is unconditionally executed during program initialization. Enter one of the following:
Preference file
Specifies the preference file that Debug Tool uses when debugging programs that match this profile. You can specify the fully qualified name of a sequential dataset or a member of a partitioned data set.
Other Language Environment options
Specifies Language Environment run-time options for programs that match this profile. When a program is selected for debugging because it matches the profile, the run-time options specified will override other run-time options that you may have in effect. For more information, see the CICS® Application Programming Guide.

Function keys for the Create Compiled Debugging Profile screen

The function keys for the "Create Compiled Debugging Profile" screen are:

PF1
Display the help screen
PF2
Save the contents of the Debug Tool options, and the Language Environment options. See Specifying default values for Debug Tool and Language Environment options.
PF3
End the debugging profile manager
PF10
Update an existing profile with the information on the screen
PF12
Return to the "List Debugging Profiles" screen

Specifying default values for Debug Tool and Language Environment options

You can specify default values for the following Debug Tool options, and the Language Environment options. The saved values are used by default each time you create a debugging profile for a compiled language program. The Debug Tool options are:

To save the default values, start with the "Create Compiled Debugging Profile" screen, and follow these steps:

  1. Type the default values that you want to specify for the Debug Tool options and Language Environment options
  2. Press PF2. CICS saves the values that you have specified.

The values that you save will be used by default each time you create a new profile.

Related concepts
the CICS Application Programming Guide
Related tasks
Using the application debugging profile manager 3270 interface
Creating a debugging profile with the 3270 interface
Changing a debugging profile with the 3270 interface
the CICS Application Programming Guide
Related references
The List Debugging Profiles screen
The Create Java Debugging Profile screen
The Set Compiled Debugging Display Device screen
[[ Contents Previous Page | Next Page Index ]]