You are on page 1of 12

TABLE OF CONTENTS

Sr. No. 1. 2.

Topic Objective and Scope Abstract

Page No. 2 3 to 17

Objective This document is aimed at developers who are new to debug any Batch or Online program. Scope of the Document This document explains how one can debug a Batch or an Online Program Interactively line by line. Through Expeditor it is much easier to find out where exactly the error is as one can run the program in debug mode and easily see the values in the variables used in the program, value of SQL code returned (in case of DB2 programs) or CICS response codes etc. For reference, snapshots from the expeditor environment of my project are shown.

Debugging using Expeditor

Ver. Rev. 0.00a

1

Abstract Debugging batch programs using Expeditor:
1. Log on to the mainframe. On the AETNATSO AE82 PRIMARY PANEL screen, enter the option as XPED.

2. On XPEDITER/TSO 7.2 - PRIMARY MENU, enter option 3 (BATCH) Debug programs interactively under batch.

- It is to

Debugging using Expeditor

Ver. Rev. 0.00a

2

3. For First Time Set up : Enter SE for Setup in the command line : On the XPEDITER/TSO - SETUP MENU , choose option 2 (DDIO) and press enter: On the screen XPEDITER/TSO - DDIO FILES a. Specify following datasets in the user libraries: ‘R1CGPB.MTEST.CATS.SOURCE.BATSYM1’ - For Dev ‘R1CGPB.MPRODFX.CATS.SOURCE.BATSYM1’ - For Prod Fix b. Specify following datasets in installation libraries: ‘SYSB.XPEDITER.V72.DDIO’

Debugging using Expeditor

Ver. Rev. 0.00a

3

Debugging using Expeditor

Ver. Rev. 0.00a

4

4. On XPEDITER/TSO - PROCESS EXECUTE JCL, specify the jcl name in Other Partitioned or Sequential Dataset (For partitioned dataset, specify member name with parenthesis else specify the full dataset name for sequential datasets). For e.g. ‘R1CGYB.CATS.DRV.JCL (J1CGBD01)’

5. On XPEDITER/TSO - SELECT JOB STEP, specify I, in front of step name for Interactive testing, and enter RUN on the command line.

6. The job will start executing in the expeditor. To set breakpoints type B in front of a statement and press ENTER. To delete breakpoint, type D in front of statement, these have breakpoint, and press ENTER. To Step into, use PF9 and to move directly to next breakpoint, use PF12.To see the value of a particular variable type K in front of a statement or type K variable name in the command line.

Debugging using Expeditor

Ver. Rev. 0.00a

5

Debugging CICS programs using Expeditor:
1) Sign On to CICS region. 2) Enter the following command: XPED <CICS Program Name>, where CICS Program Name is the full name of CICS program e.g. N1CG0001.

3) Following Screen comes: XPEDITER/CICS - SOURCE LISTING (2.L).

Debugging using Expeditor

Ver. Rev. 0.00a

6

4) PF3 till you reach XPEDITER/CICS 07.06.00- PRIMARY MENU. On this screen, enter option 1 for SESSION CONTROL.

Debugging using Expeditor

Ver. Rev. 0.00a

7

5) On the screen XPEDITER/CICS - SESSION CONTROL MENU (1), enter option 6 for TRAP SUMMARY.

6) On the screen XPEDITER/CICS - TRAP SUMMARY (1.6), under the column TERM, set the values to **** and press <ENTER>.

Debugging using Expeditor

Ver. Rev. 0.00a

8

7) PF3 till the screen XPEDITER/CICS 07.06.00- PRIMARY MENU is displayed. Enter option 2 - DEBUGGING FACILITIES on this screen.

Debugging using Expeditor

Ver. Rev. 0.00a

9

8) On the screen XPEDITER/CICS - DEBUGGING FACILITIES MENU (2), enter option L - SOURCE LISTING.

Debugging using Expeditor

Ver. Rev. 0.00a

10

9) The following screen comes up. You can now set the break points:

Debugging using Expeditor

Ver. Rev. 0.00a

11

10) After setting the breakpoints, PF3 till the screen XPEDITER/CICS - EXIT SESSION (X) is reached. On this screen, specify END SESSION: NO and DUMP OPTION: NO, and press <ENTER>. If you want to terminate CICS Expeditor session then specify END SESSION: YES and press <ENTER>.

11) Now, to debug we need to run the transaction which has been setup in expeditor for debugging. For that open one more mainframe CICS session and type the transaction ID of that transaction which in this case happens to be EB01. The transaction will start running in expeditor. To Step into, use PF9 and to zoom, use PF12.

Debugging using Expeditor

Ver. Rev. 0.00a

12