Preparing a CICS program
To prepare a CICS® program
for debugging, you must do the following tasks:
- Complete the program preparation tasks for assembler, C, C++,
COBOL, or PL/I, as described in the following sections:
If you are using versions of CICS earlier
than CICS Transaction Server
for z/OS® Version 3 Release
1, you can prepare non-Language Environment COBOL programs for debugging,
as described in Preparing a non-Language Environment COBOL program.
- Determine if your site uses CADP or DTCN debugging profiles and
verify that your system has been configured to use the chosen debugging
profile.
- Determine if you need to link edit EQADCCXT into your program
by reviewing the instructions in Link-editing EQADCCXT into your program.
- Do one of the following tasks:
- If your site is using DTCN debugging profiles, create and store
a DTCN debugging profile. Instructions for creating a DTCN debugging
profile are in Creating and storing a DTCN profile.
- If you are using CICS Transaction
Server for z/OS Version 2 Release
3 or later and your site uses CADP to manage debugging profiles, create
and store a CADP debugging profile. See Creating and storing debugging profiles with CADP for more
information about using CADP.
Link-editing EQADCCXT into your program
Debug Tool provides an Language Environment CEEBXITA assembler exit called
EQADCCXT to help you activate, by using the DTCN transaction, a debugging
session under CICS. You do not need to use this exit if you are running
any of the following options:
- You are running under CICS Transaction
Server for z/OS Version 2 Release
3 or later and you use the CADP transaction to define debug profiles.
- You are using the DTCN transaction and you are debugging
non-Language Environment Assembler programs.
- You are using the DTCN transaction and you are debugging COBOL programs, or
PL/I programs in the following situation:
- Compiled with Enterprise PL/I for z/OS,
Version 3 Release 4 with the PTF for APAR PK03264 applied, or later
- Running with Language Environment® Version 1 Release 6 with the PTF for APAR PK03093
applied, or later
When you use EQADCCXT, be aware of the following conditions:
- If your site does not use
an Language Environment assembler exit (CEEBXITA), then link-edit member EQADCCXT,
which contains the CSECT CEEBXITA and is in library hlq.SEQAMOD,
into your main program.
- If your site uses an existing CEEBXITA, the EQADCCXT exit provided
by Debug Tool must be merged with it. The source for EQADCCXT is in hlq.SEQASAMP(EQADCCXT).
Link the merged exit into your main program.
After you link-edit your program, use the DTCN transaction
to create a profile that specifies the combination of resources that
you want to debug. See Creating and storing a DTCN profile.
Creating and storing a DTCN profile
You can create and store DTCN profiles in the following manner:
- By using the DTCN transaction. The rest of the information in
these topics describe how to do this.
- By using the Eclipse plug-in. The Debug Tool API User's Guide and Reference (SC14-7250) describes how
to do this.
The DTCN transaction stores debugging profiles in a
repository. The repository can be either a CICS temporary storage queue or a VSAM file. The
following list describes the differences between using a CICS temporary storage queue or
a VSAM file:
- If you don't log on to CICS or
you log on as the default user, you cannot use a VSAM file. You must
use a CICS temporary storage
queue.
- If you use a CICS temporary
storage queue, the profile will be deleted if the terminal that created
the profile has been disconnected or the CICS region is terminated. If you use a VSAM file,
the profile will persist through disconnections or CICS region restarts.
- If you use a CICS temporary
storage queue, there can be only one profile on a single terminal.
If you use a VSAM file, there can be multiple profiles, each created
by a different user, on a single terminal.
Debug Tool determines which storage method is used based on the presence
of a debugging profile VSAM file. If Debug Tool finds a debugging profile
VSAM file allocated to the CICS region,
it assumes you are using a VSAM file as the repository. If it doesn't
find a debugging profile VSAM file, it assumes you are using a CICS temporary storage queue as
the repository. See the Debug Tool Customization Guide or contact your system
programmer for more information about how the VSAM files are created
and managed.
If the repository is a temporary storage queue, each profile is
retained in the repository until one of the following events occurs:
- The profile is explicitly deleted by the terminal that entered
it.
- DTCN detects that the terminal which created the profile has been
disconnected.
- The CICS region is terminated.
If the repository is a VSAM file, each profile is retained until
it is explicitly deleted. The DTCN transaction uses the user ID to
identify a profile. Therefore, each user ID can have only one profile
stored in the VSAM file.
Profiles are either active or inactive. If a profile is active,
DTCN tries to match it with a transaction that uses the resources
specified in the profile. DTCN does not try to match a transaction
with an inactive profile. To make a profile active or inactive,
use the Debug Tool CICS Control - Primary Menu panel (the
main DTCN panel) to make the profile active or inactive, then save
it. If the repository is a VSAM file, when DTCN detects that the terminal
is disconnected, it makes the profile inactive.
To create and store a DTCN profile:
- Log on to a CICS terminal
and enter the transaction ID DTCN. The DTCN transaction
displays the main DTCN screen, Debug Tool CICS Control
- Primary Menu, shown below.
DTCN Debug Tool CICS Control - Primary Menu S07CICPD
* VSAM storage method * 1
Select the combination of resources to debug (see Help for more information)
Terminal Id ==> 0090
Transaction Id ==>
LoadMod::>CU(s) ==> ::> ==> ::>
==> ::> ==> ::>
==> ::> ==> ::>
==> ::> ==> ::>
User Id ==> CICSUSER
NetName ==>
IP Name/Address ==>
Select type and ID of debug display device
Session Type ==> MFI MFI, TCP
Port Number ==> TCP Port
Display Id ==> 0090
Generated String: TEST(ALL,'*',PROMPT,'MFI%0090:*')
Repository String: No string currently saved in repository
Profile Status: No Profile Saved. Press PF4 to save current settings.
PF1=HELP 2=GHELP 3=EXIT 4=SAVE 5=ACT/INACT 6=DEL 7=SHOW 8=ADV 9=OPT 10=CUR TRM
Line 1 displays
a message to indicate that DTCN will store the profile in a temporary
storage queue or in a VSAM file. Some of the entry fields are
filled in with values from one of the following sources:
- If the temporary storage queue is the type of repository, the
fields are filled in with default values that start Debug Tool, in full-screen
mode, for tasks running on this terminal.
- If a VSAM file is the type of repository and a profile exists
for the current user, the fields are filled in with data found in
that profile. If a VSAM file is the type of repository and a profile
does not exist for the current user, the fields are filled in with
default values that start Debug Tool, in full-screen mode, for tasks running
on this terminal.
If you do not want to change these fields, you can skip the
next two steps and proceed to step 4.
If you want to change the settings on this panel, continue to the
next step.
- Specify the combination of resources that identify
the transaction or program that you want to debug. For more information
about these fields, do one of the following tasks:
- Specify the type of debugging session you want to run and the
ID of the device that displays the debugging session. For more information
about these fields, do one of the following tasks:
-
Specify the TEST runtime
options, other runtime options, commands file, and preferences file
that you want to use for the debugging session by pressing PF9 to
display the secondary options menu, which looks like the following
example:
DTCN Debug Tool CICS Control - Menu 2 S07CICPD
Select Debug Tool options
Test Option ==> TEST Test/Notest
Test Level ==> ALL All/Error/None
Commands File ==> *
Prompt Level ==> PROMPT
Preference File ==> *
Any other valid Language Environment options
==>
PF1=HELP 2=GHELP 3=RETURN
Some of the entry fields are
filled in with default values that start Debug Tool, in full-screen mode,
for tasks running on this terminal. If you do not want to change the
defaults, you can skip the rest of this step and proceed to step 5. If you want to change the settings
on this panel, continue with this step.
-
Press PF3 to return to the main DTCN
panel.
- If you want to use data passed through COMMAREA or containers
to help identify transactions and programs that you want to debug,
press PF8. The Advanced Options panel
is displayed, which looks like the following example:
DTCN Debug Tool CICS Control - Advanced Options S07CICPD
Select advanced program interruption criteria:
Commarea Offset ==> 0
Commarea Data ==>
Container Name ==>
Container Offset ==> 0
Container Data ==>
URM Debugging ==> NO
Default offset and data representation is decimal/character.
See Help for more information.
PF1=HELP 2=GHELP 3=RETURN You
can specify data in the COMMAREA or containers, but not both. You
can also use this panel to indicate whether you want to debug user
replaceable modules (URMs). For more information about these fields,
do one of the following tasks:
- Press PF3 to return to the main DTCN panel.
- Press PF4 to save the profile. DTCN performs
data verification on the data that you entered in the DTCN panel.
When DTCN discovers an error, it places the cursor in the erroneous
field and displays a message. You can use context-sensitive help (PF1)
to find what is wrong with the input.
- Press PF5 to change the status from active to inactive, or from
inactive to active. A profile has three possible states:
- No profile saved
- A profile has not yet been created for this terminal.
- Active
- The profile is active for pattern matching.
- Inactive
- Pattern matching is skipped for this profile.
- After you save the profile in the repository, DTCN shows the saved
TEST string in the display field Repository String. If you are satisfied
with the saved profile, press PF3 to exit DTCN.
Now, any tasks that run in the CICS system and match the resources that you specified
in the previous steps will start Debug Tool.
Refer to the following topics for more information
related to the material discussed in this topic.
Displaying a list of active DTCN profiles and managing DTCN
profiles
To display all of the active DTCN profiles in the CICS region, do the following steps:
- If you have not started the DTCN transaction, Log on to a CICS terminal and enter the transaction
ID DTCN. The DTCN transaction displays the main DTCN screen, Debug Tool CICS Control - Primary Menu.
- Press PF7. The Debug Tool CICS Control
- All Sessions screen displays, shown below.
DTCN Debug Tool CICS Control - All Sessions S07CICPD
Overtype "_" with "D" to delete, "A" to activate, "I" to inactivate a profile.
Owner Sta Term Tran User Id NetName Applid Display Id
_ 0090 ACT 0090 TRN1 USER1 0072 S07CICPD 0090
LoadMod::>CU(s) CIC9060 ::> CS9060 CBLAC?3 ::> *9361
________ ::> ________ ________ ::> ________
________ ::> ________ ________ ::> ________
________ ::> ________ ________ ::> ________
IP Name/Addr ____________________________________________________
The
column titles are defined below:
- Owner
- The ID of the terminal that created the profile by using DTCN.
- Sta
- Indicates if the profile is active (ACT) or inactive
(INA).
- Term
- The value that was entered on the main DTCN screen in the Terminal Id field.
- Tran
- The value that was entered on the main DTCN screen in the Transaction Id field.
- User Id
- The value that was entered on the main DTCN screen in the User Id field.
- Netname
- The value the entered on the main DTCN screen in the Netname field.
- Applid
- The application identifier associated with this profile.
- Display Id
- Identifies the target destination for Debug Tool information.
- LoadMod(s)
- The values that were entered on the main DTCN screen in the LoadMod(s) field.
- CU(s)
- The values that were entered on the main DTCN screen in the CU(s) field.
- IP Name/Addr
- The value that was entered on the main DTCN screen in the IP Name/Address field.
DTCN also reads the Language Environment NOTEST option supplied
to the CICS region in CEECOPT
or CEEROPT. You can supply suboptions, such as the name of a preferences
file, with the NOTEST option to supply additional defaults
to DTCN.
- To delete a profile, move your cursor to the underscore character
(_) that is next to the profile you want to delete. Type in "D" and
then press Enter.
- To make a profile inactive, move your cursor to the underscore
character (_) that is next to the profile you want to make inactive.
Type in "I" and then press Enter.
- To make a profile active, move your cursor to the underscore character
(_) that is next to the profile you want to make active. Type in "A" and
then press Enter.
- To leave this panel and return to the DTCN primary menu, press PF3.
Refer to the following topics for more information
related to the material discussed in this topic.
This topic describes the fields that are displayed on the DTCN
Primary Menu screen.
The following list describes the resources you can specify to help
identify the program or transaction that you want to debug:
- Terminal Id
- Specify the CICS terminal
identifier associated with the transaction you want to debug. By default,
DTCN sets the ID by one of the following rules:
- If the type of repository is a VSAM file and the current user
ID has a saved profile, DTCN fills in the field with the terminal
ID that is in the repository. You can change the terminal ID to
the ID of the terminal you are currently running on, by placing your
cursor on the terminal ID field and then pressing PF10. Press PF4 to
save the profile with this new value.
- If the type of repository is a VSAM file and the current user
ID does not have a saved profile, the terminal ID field is filled
in with the ID of the terminal you are currently running on.
- If the type of repository is a temporary storage queue, the terminal
ID field is filled in with the ID of the terminal you are currently
running on.
- If the CICS transaction
or program that you want to debug is not associated with a specific
terminal (for example, the request to start a debug session comes
from a browser), make this field blank.
If the DTCNFORCETERMID option in EQAOPTS is set to YES, you must
specify a terminal identifier. See Debug Tool Customization Guide for a description
of these options.
- Transaction Id
- Specify the CICS transaction
to debug. If you specify a transaction ID without any other resource, Debug Tool is
started every time any of the following situations
occurs:
- You run the transaction.
- The first program run by the transaction is started.
- Any other user runs the transaction.
- Any enabled DFH* module is the first program run by the transaction.
To start Debug Tool at the desired program that the transaction
runs, specify the program name in the Program Id(s) field. If the
DTCNFORCETRANID option in EQAOPTS is set to YES, this field must be
specified. See Debug Tool Customization Guide for a description of these options.
- LoadMod::>CU(s)
- Specify the resource pair or pairs, consisting
of a load module name and a compile unit (CU) name that you want to
debug. You can specify any of the following names:
- LoadMod
- The name of a load module that you want to debug. The load module
must comply with the following requirements:
- For Debug Tool initialization, the load module can be any CICS load module if it is invoked
as an Language Environment enclave or over a CICS Link
Level. This includes the following types of load modules:
- The initial load module in a transaction.
- A load module invoked by CICS LINK
or XCTL.
- Any non-Language Environment assembler load module which is loaded
through an EXEC CICS LOAD command.
- CU
- The name of the compile unit (CU) that you want
to debug. The CU must comply with the following requirements:
- Any CICS CU if it is invoked
as an Language Environment enclave
or over a CICS Link Level.
This includes the following types of CUs:
- The initial CU in a transaction
- A CU invoked by CICS LINK
or XCTL
- Any COBOL CU, even if it is a nested CU or a subprogram within
a composite load module, invoked by a static or dynamic CALL.
- Any Enterprise PL/I for z/OS Version
3 Release 4 CU (with the PTF for APAR PK03264 applied), or later,
running with Language Environment Version 1 Release 6 (with the PTF for APAR
PK03093 applied), or later, even if it is a nested CU or a subprogram
within a composite load module, invoked as a static or dynamic CALL.
- Any non-Language Environment assembler CU which is loaded through
an EXEC CICS LOAD command.
Usage Notes®:
- If you specify a LoadMod and leave the corresponding
CU field blank, the CU field defaults to an asterisk (*).
- If you specify a CU and leave the corresponding LoadMod
field blank, the LoadMod field defaults to an asterisk (*).
- If you leave all LoadMod and CU fields blank and you
set the Prompt Level on the "Debug Tool CICS Control -
Menu 2" to PROMPT, Debug Tool initializes for the first program invoked.
- You can specify wildcard characters (*) and (?).
- If Debug Tool was started by another program before the EXEC
CICS LOAD command that starts this non-Language Environment assembler
program, you need to enter one of the following commands so that Debug Tool gains
control of this program:
- LDD
- SET ASSEMBLER ON
- SET DISASSEMBLY ON
- When you specify a CU
for C/C++ and Enterprise PL/I programs (languages that use a fully
qualified data set name as the compile unit name), you must specify
the correct part of the compile unit name in the CU field. Use
the following rules to determine which part of the compile unit name
you need to specify:
- If you are using a PDS or PDSE, you must specify the member name.
For example, if the compile unit names are DEV1.TEST.ENTPLI.SOURCE(ABC)
and DEV1.TEST.C.SOURCE(XYZ), you must specify ABC and XYZ in the program
ID field.
- If you are using a sequential data set, specify one of the following:
- The last qualifier of the sequential data set. For example, if
the compile unit names are DEV1.TEST.ENTPLI.SOURCE.ABC and DEV1.TEST.C.SOURCE.XYZ,
you must specify ABC and XYZ in the program ID field.
- Wildcards. For example, if the compile unit names are DEV1.TEST.ENTPLI.ABC.SOURCE
and DEV1.TEST.C.XYZ.SOURCE, you must specify *ABC* and *XYZ* in the
program ID field.
- If you compiled your PL/I program with the following compiler
and it is running in the following environment, you need to use the
package name or the main procedure name:
- Enterprise PL/I for z/OS, Version
3.5, with the PTFs for APARs PK35230 and PK35489 applied, or Enterprise PL/I for z/OS, Version 3.6 or later
- Language Environment, Version 1.6 through 1.8 with the PTF for APAR PK33738
applied, or later
- Specifying a CICS program
in the LoadMod::>CU field is similar to setting a breakpoint by using
the AT ENTRY command and Debug Tool stops each time you enter
LoadMod::>CU.
- If Debug Tool is already running and it cannot find
the separate debug file, then Debug Tool does not stop at the CICS program specified in the LoadMod::>CU field. Use
the AT APPEARANCE or AT ENTRY command to stop
at this CICS program.
- If the DTCNFORCELOADMODID option in EQAOPTS is set
to YES, the LoadMod field must be specified. See Debug Tool Customization Guide for
a description of these options.
- If the DTCNFORCEPROGID or DTCNFORCECUID option in
EQAOPTS is set to YES, the CU field must be specified. See Debug Tool Customization Guide for a description of these options.
- User Id
- Specify the user identifier associated with the transaction
you want to debug. The following list can help you decide what to
enter in this field:
- If the user identifier is the same one that is currently running
DTCN, use the default user identifier.
- If the user identifier is different than the one currently running
DTCN and you know the user identifier, enter that user identifier.
- If you do not know the user identifier or the transaction is not
associated with a user identifier, specify the wild character or blanks.
If the DTCNFORCEUSERID option in EQAOPTS is set to YES, you must
specify a user identifier. See Debug Tool Customization Guide for a description
of these options.
- NetName
- Specify the four character name of a CICS terminal or a CICS system
that you want to use to run your debugging session. This name is used
by VTAM® to identify the CICS terminal or system. If the
DTCNFORCENETNAME option in EQAOPTS is set to YES, this field must
be specified. See Debug Tool Customization Guide for a description of these
options.
- IP Name/Address
- The client IP name or IP address that is associated with a CICS application. All IP names
are treated as upper case. Wildcards (* and ?) are permitted. Debug
Tool is invoked for every task that is started for that client. If
the DTCNFORCEIP option in EQAOPTS is set to YES, this field must be
specified. See Debug Tool Customization Guide for
a description of these options.
The following list describes the fields that you can use to indicate
which type of debugging session you want to run.
- Session Type
- Select one of the following options:
- MFI
- Indicates that Debug Tool initializes on a 3270 type of terminal.
- TCP
- Indicates that you want to interact with Debug Tool from your workstation
using TCP/IP and a remote debugger.
- Port Number
- Specifies the TCP/IP port number that is listening for debug
sessions on your workstation. By default, the following products
use port 8001:
- WebSphere Developer Debugger for zSeries
- Compiled Language Debugger component of WebSphere Developer for zSeries
- Display Id
- Identifies the target destination for Debug Tool.
If you entered TCP in
the Session Type field, determine the
IP address or host name of the workstation that is running the remote
debugger. Change the value in the Display
Id field by doing the following steps:
- Place your cursor on the Display Id field
- Type in the IP address or host name of the workstation that is
running the remote debugger
- To save the profile with this new value, press PF4.
If you entered MFI in the Session
Type field, DTCN fills in the Display
Id field according to the following rules:
- If the type of repository is a VSAM file and the current user
ID has a saved profile, DTCN fills in the field with the display ID
that is in the repository.
- If the type of repository is a VSAM file and the current user
ID does not have a saved profile, DTCN fills in the field with the
ID of the terminal you are currently running on.
- If the type of repository is a temporary storage queue, DTCN fills
in the field with the ID of the terminal you are currently running
on.
You can use one of the following terminal modes to display Debug Tool on
a 3270 terminal:
- Single terminal mode: Debug Tool and the application program share
the same terminal. To use this mode, enter the ID of the terminal
being used by your application program or move the cursor to the Display ID field and press PF10.
- Screen control mode: Debug Tool displays its screens on a terminal
which is running the DTSC transaction. To use this mode, start the
DTSC transaction on a terminal and specify that terminal's ID
in the Display ID field.
- Separate terminal mode: Debug Tool displays its screens on a terminal
which is available for use (not associated with any transaction) and
can be located by CICS. To
use this mode, specify the terminal's ID in the Display ID field.
Description of fields on the DTCN Menu 2 screen
The following list describes the fields that you can use to specify
the TEST runtime options, other runtime options, commands
file, and preferences file that you want to use for the debugging
session:
- Test Option
- TEST/NOTEST specifies the conditions
under which Debug Tool assumes control during the initialization of your
application.
- Test Level
- ALL/ERROR/NONE specifies
what conditions need to be met for Debug Tool to gain control.
- Command File
- A valid fully qualified data set name that specifies the primary
commands file for this run.
Note:
Do not enclose the name
of the data set in quotation marks (") or apostrophes (').
- Prompt Level
- Specifies whether Debug Tool is started at Language Environment initialization.
- Preference File
- A valid fully qualified data set name that specifies the preferences file to be used.
Do not enclose the name of the data set in quotation marks (")
or apostrophes (').
- Any other valid Language Environment Options
- You can change any Language Environment option that your site has defined
as overrideable except the STACK option. For additional
information about Language Environment options, see z/OS Language Environment Programming Reference or contact
your CICS system programmer.
Description of fields on the DTCN Advanced Options screen
The following list describes the fields that you can use to specify
the data passed through COMMAREA or containers that can help identify
transactions and programs that you want to debug:
- Commarea offset
- Specifies the offset of data within a commarea passed to a program
on invocation. You can specify the offset in decimal format (for
example, 13) or in hexadecimal format (for example, X'D').
If you specify data in hexadecimal format, you must specify an even
number of hexadecimal digits.
- Commarea data
- Specifies the data within a commarea that is passed to a program
on invocation. You can specify the data in character format (for
example, "ABC") or in hexadecimal format (for example, X'C1C2C3').
- Container name
- Specifies the name of a container within the current channel
passed to a program on invocation. Container names are case sensitive.
- Container offset
- Specifies the offset of data in the named container passed to
a program in the current channel on invocation. You can specify
the offset in decimal format (for example, 13) or in hexadecimal
format (for example, X'D').
- Container data
- Specified the data in the named container passed to a program
in the current channel on invocation. You can specify the data
in character format (for example, "ABC") or in hexadecimal
format (for example, X'C1C2C3'). If you specify data in hexadecimal
format, you must specify an even number of hexadecimal digits.
- URM debugging
- Specifies whether you want Debug Tool to include the debugging of
URMs as part of the debug session. Choose from the following options:
- YES
- Debug Tool debugs URMs which match normal Debug Tool debugging criteria.
- NO
- Debug Tool excludes URMs form debugging sessions.
Creating and storing debugging profiles with CADP
CADP is an interactive transaction supplied by CICS Transaction Server for z/OS Version 2 Release 3, or later. CADP helps you
maintain persistent debugging profiles. These profiles contain a pattern
of CICS resource names that
identify a task that you want to debug. When CICS programs are started, CICS tries to match the executing resources to find
a profile whose resources match those that are specified in a CADP
profile. During this pattern matching, CICS selects the best matching
profile, which is the one with greatest number of resources that match
the active task.
Before using CADP, verify that you have done the following tasks:
- Compiled and linked your program as described in Preparing a CICS program.
- Verified that your site uses CADP and that all the tasks required
to customize Debug Tool so that it can debug CICS programs described in Debug Tool Customization Guide are completed. In particular, verify that the DEBUGTOOL system
initialization parameter is set to YES so that Debug Tool uses
the CADP profile repository instead of the DTCN profile repository
to find a matching debugging profile.
See CICS Supplied Transactions for instructions on how to use the
CADP utility transaction. If you are going to debug user-replaceable
modules (URMs), specify ENVAR("INCLUDEURM=YES") in the Other Language Environment Options field.
Refer to the following topics for more information
related to the material discussed in this topic.
- Related
references
- CICS Application Programming Guide for a description of debugging profiles.
Starting Debug Tool for non-Language Environment programs under CICS
You can start Debug Tool to debug a program that does not run in the Language Environment run
time by using the existing debug profile maintenance transactions DTCN and CADP.
You must use DTCN with versions of CICS prior to CICS Transaction
Server for z/OS Version 2 Release
3.
To debug CICS non-Language Environment programs,
the Debug Tool non-Language Environment Exits must have been previously started.
To debug non-Language Environment assembler programs or non-Language Environment COBOL
programs that run under CICS,
you must start the required Debug Tool global user exits before you
start the programs. Debug Tool provides the following global
user exits to help you debug non-Language Environment applications:
XPCFTCH, XEIIN, XEIOUT, XPCTA, and XPCHAIR. The exits can be started
by using either the DTCX transaction (provided by Debug Tool), or
using a PLTPI program that runs during CICS region
startup. DTCXXO activates the non-Language Environment Exits for Debug
Tool in CICS. DTCXXF inactivates
the non-Language Environment Exits for Debug Tool in CICS.
Refer to the following topics for more information
related to the material discussed in this topic.
- Related tasks
- Debug Tool Customization Guide
Passing runtime parameters to Debug Tool for non-Language Environment
programs under CICS
When you define your debugging profile using the DTCN Options
Panel (PF9) or the CADP Create/Modify Debugging Profile
Panel, you can pass a limited set of runtime options that will take
effect during your debugging session when you debug programs that
do not run in Language Environment. You can pass the following runtime optionss:
- TEST/NOTEST: must be TEST
- TEST LEVEL: must be ALL
- Commands file
- Prompt Level: must be PROMPT
- Preferences file
- You can also specify the following runtime options in a TEST string:
- NATLANG: to specify the National Language used to communicate
with Debug Tool
- COUNTRY: to specify a Country Code for Debug Tool
- TRAP: to specify whether Debug Tool is to intercept Abends
Refer to the following topics for more information
related to the material discussed in this topic.
- Related
references
- Debug Tool Reference and Messages
|
This information center is powered by Eclipse technology. (http://www.eclipse.org)