Projects

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:

• Batch projects initiate a CA InterTest™ batch debug session and define the JCL to be submitted to start the batch job.

• CICS projects initiate a CA InterTest™ for CICS debug session.

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:

• List of monitored programs

• Set of breakpoint specifications

• Session debug settings and servers

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.

This section contains the following articles:

• Create a Batch or CICS Project

• Import Programs from PROTSYM Files

• Load Listings into a PROTSYM File