You must organize your debug sessions to use CA InterTest for debugging your applications on z/OS successfully. The top level of the organization hierarchy is called the InterTest project. A project defines all of the programs that are to be debugged and the server used to access the mainframe.
The InterTest project contains the following two project types:
You can have any number of batch or CICS project types configured and managed by CA InterTest.
You can create several projects that describe the same application regardless of the project type. The projects may differ in the following ways:
You can also refine the differences based on the type of debug sessions—batch or CICS.
You must first create a project and then import program listings corresponding to the debug session you want to establish. After importing program listings, CA InterTest co-ordinates the debug session settings according to the project type, and associates the appropriate server connections to initiate a debug session. When the debug session starts, you can set breakpoints, view and modify variables, and analyze storage similar to how you use the ISPF interface of CA InterTest batch or the CICS screens of CA InterTest for CICS.
Note: You can set breakpoints and configure session and program settings in CA InterTest whether you are connected to the mainframe or not.
|
This section contains the following topics: Create a Batch or CICS Project |