Set the Debug Session Settings for a Batch Project

You can specify the settings to debug a batch project using the InterTest Debug Settings dialog. You can perform JCL conversion and save the converted JCL on the mainframe. You can also validate or modify the JCL to suit your requirements.

To set the debug settings for a batch project

1. Select the batch project on the InterTest Debug view.
2. Right-click and select the Configure Session Debug Settings.

   The InterTest Debug Settings dialog opens the Main tab by default.

3. Enter values in the following fields in the Main tab:
   • CA TestingTools Server

     Specifies the available servers. Select one from the drop-down list for this session.

   • Options

     Displays a set of check boxes for all the supported request breakpoints for CA InterTest batch (DBCALL, ENTRY, EXIT, and LABEL). Check the boxes next to the request breakpoints that you want to use.

     Note: For more information about request breakpoint settings, see the chapter "Debugging Panels" in the CA InterTest batch User Guide.

   • Do not show during debug startup

     Skips the display of the InterTest Debug Settings dialog when you click the Start Debug Session toolbar icon on the InterTest Debug view toolbar. Check this box if you do not want to specify your debug settings for a subsequent debug session.

     Note: To undo this option when starting a debug session, open the InterTest Debug Settings dialog, clear this check box, and click Finish.

     Default: Off

   • Session will debug PL/I

     Indicates that CA InterTest can update the debugged program to the output of a PL/I compiler.

     Default: Off

   • Execution Count

     Specifies that CA InterTest must keep track of the number of breakpoints encountered during execution.

     Default: Off

   • Statement Trace

     Indicates that CA InterTest allows you to trace the program execution.

     Default: Off

   • Monitoring

     Indicates that you can monitor the trace process during program execution. Check this box to invoke a monitoring process.

   • Notify at End of Task

     Indicates that the task is completed. Check this box if you want to be notified at the end of the task.

     Default: On

4. Select the PROTSYM tab.

   The InterTest Debug Settings dialog opens the Protsym tab page. The PROTSYM Datasets field lists the PROTSYM data sets of the CA InterTest PROTSYM VSAM file.

   Note: You must define at least one PROTSYM data set. For more information about defining PROTSYM data sets for batch projects, see the chapter "Debugging Panels" section Dynamic Symbolic Support in the CA InterTest Batch User Guide.

5. Click the following buttons if you want to use a CA Endevor SCM PROTSYM data set that is not loaded automatically:
   • Add—Adds a new PROTSYM data set using the Add Dataset Name dialog. Enter a name for the PROTSYM data set you want to add and click OK.
   • Edit—Changes the name of an existing PROTSYM data set using the Edit Dataset Name dialog. Select a data set from the list and click this button. The Edit Dataset Name dialog opens. Enter the new name for the selected PROTSYM data set and click OK.
   • Delete—Removes a selected PROTSYM data set from the list. When you select a data set from the list and click this button, a confirm message appears. Click OK to confirm deletion.
   • Enable for DSS—Assigns a selected PROTSYM data set as the data set with CA Endevor SCM support. Select a data set from the list and click this button. The CA SCM DSN field is populated with the selected PROTSYM data set name.
6. Select the JCL Settings tab.

   The InterTest Debug Settings dialog opens the JCL Settings tab page. Use this dialog to convert your existing batch JCL for debugging if necessary and identify the location of the JCL member that must be used to launch this batch application.

   After your JCL is converted, you may bypass the conversion fields using the dialog, and specify the location of the converted JCL in the Converted/Submit JCL field.

7. Type values in the following fields under JCL Conversion so that your JCL can be converted and executed by CA InterTest Batch:
   • Conversion JCL Dataset (Member Name)

     Specifies the name of the JCL data set and optionally the member name of the JCL to be converted. If you do not provide the member name, the convert JCL routine displays the list of available members so that you can choose a member and complete the field.

     Default: none

   • Dataset Type

     Lists the following data set types: Standard IBM, CA Panvalet, or CA Librarian. Select a data set type from the drop-down list.

     Default: Standard IBM PDS

   • JOB Step Name

     Specifies the name of the step in the JCL being converted that you want to debug if there are multiple steps. Type the step name.

     If you do not provide a step name and the JCL contains more than one step, the convert JCL routine displays the list of available steps so that you can choose a step name and complete the field.

   • PROCLIB List

     Specifies the data set name of the procedure library if the JCL being converted requires a PROCLIB to execute. Multiple names must be separated by semi-colons (;).

   • Convert JCL

     Converts your JCL so that CA InterTest Batch can debug it. CA InterTest modifies your JCL as required by CA InterTest Batch and places the converted results in the defined Converted/Submit file.

     Default: none

     Note: You do not need to convert JCL. This feature is provided for use only if you want to convert JCL. If you already have a JCL member ready for debugging, enter it in the Converted/Submit JCL Dataset field. If you do not enter a value for the convert JCL name, other related fields will be disabled.

8. Type a data set name in the Converted/Submit JCL field. This is the name of the JCL that will be submitted for debugging. Before starting a debug session, you must enter the name of a valid JCL member in this field.
   • Converted / Submit JCL Dataset (Member Name)

     Specifies the data set name and member name for the JCL you converted.

     Note: Values in the JCL Dataset (Member Name) fields are required whether you convert JCL or not.

   • Edit JCL

     Edits the defined JCL data set. When you click Edit JCL, the Edit JCL dialog opens. Edit the code and click OK to save the JCL data set and close the dialog.

     Note: Changes made to the Edit JCL dialog are performed on the actual member on the mainframe.

9. Click Finish to close the dialog.

Note: CA InterTest users need not convert JCL every time they debug a program. Once converted, you have to only click Submit to reuse the converted job.