Specifying the JCL

If you enter a Y in the User Supplied WLM JCL field of the Code Debug TSO Process DB2 Stored Procedures screen, the following figure will be displayed. From the Process Execute JCL screen (See the following figure), specify the name of the data set that contains the Work Load Manager (WLM) JCL specific to your stored procedure. Type this name in the Data set Name field and press Enter. This JCL must execute the WLM server.

Process Execute JCL Screen

There are two steps you must perform on the Process Execute JCL screen:

1. Enter the name of the data set containing your execution JCL, either in the ISPF Library field or in the Other Partitioned or Sequential Data set field.
2. Use one of the following primary commands on the command line:

When JCL processing is completed, the job steps in the specified JCL are displayed on the Select Job Step screen shown in the following figure.

Code Debug TSO Select Job Step Screen

The Select Job Step screen is used in two ways:

1. Use the I or U line command to specify how you want each job step to execute: in interactive or unattended mode. The JCL will be converted to run with Code Debug TSO in the specified execution mode. See JCL Conversion for information about JCL conversion.
2. Use the RUN or SUBMIT primary command to convert and submit the JCL, the EDIT command to view or edit the JCL, the SETUP command to access and change your job card information, the STATUS command to display the status of submitted jobs, or the END command to exit.

The Line commands are defined as follows:

I (Interactive) testing

Selects the step to run in interactive mode.

U (Unattended) testing

Selects the step to run in unattended mode.

IC (Interactive Code Coverage)

Selects the step to run in interactive mode (with Code Coverage active).

UC (Unattended Code Coverage)

Selects the step to run in unattended mode (with Code Coverageactive).

IT (Interactive Test Data Optimization) testing

Selects the step to run in interactive mode (with Code Coverage and TDO active).

UT (Unattended Test Data Optimization) testing

Selects the step to run in unattended mode (with Code Coverage and TDO active).

IF (Interactive System Flow) testing

Selects the step to run in interactive mode (with System Flow active).

UF (Unattended System Flow) testing

Selects the step to run in unattended mode (with System Flow active).

ICF (Interactive Code Coverage/System Flow) testing

Selects the step to run in interactive mode (with Code Coverage and System Flow active).

UCF (Unattended Code Coverage/System Flow) testing

Selects the step to run in unattended mode (with Code Coverage and System Flow active).

ITF (Interactive Test Data Optimization/System Flow) testing

Selects the step to run in interactive mode (with Code Coverage, TDO, and System Flow active).

UTF (Unattended Test Data Optimization/System Flow) testing

Selects the step to run in unattended mode (with Code Coverage, TDO, and System Flow active).

blank (Reset I/U/C/T/F)

Blank the line command area and press Enter to remove any line command set on a job step.

The Primary commands are defined as follows:

Edit

Accesses the ISPF edit facility. The JCL is automatically converted and displayed on the ISPF edit screen. You can view and confirm the JCL conversion and make additional modifications to the converted JCL. However, the changes made to the converted JCL will not be saved when you select CANCEL or PF3 (END) from the edit screen. See Editing-the-JCL for more information and for an example of the ISPF Edit screen (Edit Screen).

END

Exits without converting the JCL, saving any modifications, or submitting the job, and returns you to the Process Execute JCL screen.

RUN

Converts the steps selected by the I and U line commands to predefined Code Debug TSO steps and submits the JCL. When the job processes successfully, you are automatically connected to the job steps selected to run in interactive mode and the Source screen is displayed.

If the job is a long-running job, the Connect Status screen is displayed showing the job status.

If the JCL is already converted, the RUN command (with a DSNAME) can be entered on any screen except an Code Debug  test session screen. See the Command-and-syntax-reference for more information about the RUN command.

SEtup

Displays the Setup Menu from which you can select to view and change the job card and library information, such as the DDIO file (XPSL000n) and the SCRIPT file (XINCLUDE). See Specifying Setup Options for more information.

SUBmit

Converts the steps selected by the I and U commands to Code Debug TSO steps and submits the job. A job submitted with the SUBMIT command is not automatically connected. To connect to a job submitted with the SUBMIT command, you must use the CONNECT or STATUS command. See Connecting to a Job for more information regarding the CONNECT or STATUS command.

STatus

Displays the status of a job. You can connect to the job directly from the Status screen.

The fields displayed on the Select Job Step screen are defined as follows:

Data set

This field is pre-filled with the data set name of the JCL being processed.

PROGRAM

The name of the program to be tested. The PROGRAM name does not necessarily match the EXEC PGM name.

INITSCR

The member name of the script in the INCLUDE library specified on the Setup panel. The INITSCR field can be typed over to specify a test script member, which can then be processed at the beginning of a debugging session.

POSTSCR

The member name of the script in the INCLUDE library specified on the Setup panel. The POSTSCR field can be typed over to specify a test script member which can be processed at the end of a debugging session.

STEPNAME

The job step name.

PROCNAME

The in-stream or cataloged procedure name.

PROCSTEP

The step name within the called procedure.

EXEC PGM

The name of the EXEC program that is executed for the step. XPTSO if I (Interactive) was specified for the step. XPBATCH if U (Unattended) was selected for the step. The field is left blank if the name is the same as the one entered in the PROGRAM field.

Connecting to a Job

When you use the RUN command to submit the job, the steps that are selected for interactive debugging are automatically displayed at your terminal.

When you use the SUBMIT command to submit the job, there are two ways to connect to a job: the CONNECT command and the STATUS command:

1. CONNECT Command: You can use the CONNECT command on any screen (except the source display) to connect a VTAM terminal to a job submitted through Code Debug TSO’s Batch Connect facility. You can connect to a job with multiple steps or to a single step job. For information on the CONNECT command syntax, See the Command-and-syntax-reference.
2. STATUS command: The STATUS command is used to display the Status screen containing a list of the active/inactive jobs in the system. The STATUS command can be entered from any screen.

The ATTACH line command on the Status screen is used to connect to a job and display the source of each job step for which the I (Interactive) command was specified. A message is displayed notifying you that the job step selected for testing is executing.