You are on page 1of 4

REPORT ON XPEDITER 1.

INTRODUCTION XPEDITER is an interactive testing and debugging tool which can be used to test COBOL programs in TSO or BATCH mode. This option can be accessed by going into USER 1 (U1) and in that Re-engineering and Re-development tools(V) and XPEDITER (Option 5) in that menu. Some of the options available under XPEDITER are PREPARE - for preparing programs for debugging, TSO - to debug programs under TSO, BATCH - for debugging program s in batch environment, CICS - to connect to a CICS region. 2. PREPARE This option is used to prepare the programs for debugging. Either an existing CO MPILE JCL can be converted or the compile facility can be used to compile the program for XPE DITER. For converting an existing JCL Specify the compile JCL. This can be edited or browsed. Specify the DDIO file. If it does not exist, create it by typing C in the comma nd prompt. Change the PREPARATION on the Create/Format DDIO file to FOREGROUND for testi ng interactively. Reduce the Average Size and Average Number Of Members to suit need. Convert the JCL by processing it. The modified JCL which compiles with XPEDITER is displayed. Submit or run this JCL. Be sure to check the condition codes after compile.. For using the compile facility, SEtup the Job card and other information. Specify the COBOL source. Change the PREPARATION to FOREGROUND to run the program in foreground. Select the steps necessary (DB2 precompile, CICS translation, Compile and Linked it). Set the necessary compile, link and other options. Specify the DDIO file in the Compile options panel. Create a file if one does no t exist. Change the PREPARATION on the Create/Format DDIO file to FOREGROUND for testin g interactively. Reduce the Average Size and Average Number Of Members to suit need. When processed, the results of the selected steps are displayed. Once, this is done the program is ready for interactive debugging. 3. TSO - DEBUG PROGRAMS INTERACTIVELY UNDER TSO For debugging under TSO, SEtup the environment by going into environment option in SEtup menu. A program with Dialog manager calls or IMS/DB calls can be tested. A program can also be tested usin g BTS. SEtup the necessary LOADLIBS, INCLUDES, DDIOs and other libraries as necessary. Specify the program name, load module name. The source listing of the program is displayed. If there are subroutines in the program and that has to be debugged, specify a b reakpoint before the procedure division. The following can be done from this screen Control program execution by setting breakpoints using the BEFORE, AFTER, GO, IN TERCEPT, PAUSE,

TRACE, AT, WHEN, COUNT MAX, SOURCE, and LOCATE commands. Inspect and manipulate program data (variables, registers, and memory) with the PEEK, KEEP, MOVE, MEMORY, and GPREGS commands. Analyze program logic (data flow, execution path, and execution coverage) using the FIND, EXCLUDE, MONITOR, REVERSE, RESUME, TRACE, SHOW PREV. Modify program logic with the SKIP, INSERT, GOTO, and MOVE commands. Translate and expand EXEC statements using the GEN command. Debug and test programs that do not have the source (no source listing) availabl e with the AT command. Display subsystem related debugging information for VSAM, IDMS, IMS, and DB2 and environment specific run-time characteristics during a test session. Available only if yo u have Abend-AID release 7.0 and above installed at your site. For LE/370, you must also have 7.0 and above. Use test scripts (a predefined stream of XPEDITER/TSO commands) to automate the test session (INCLUDE command). 4. BATCH - DEBUG PROGRAM INTERACTIVELY UNDER BATCH For debugging a program in batch, SEtup the JOB CARD, LOADLIBS, DDIO, INCLUDES, etc. Specify the JCL to be executed. This can be browsed or edited Process the JCL. The steps in the JCL are displayed along with options for interactive and unatt ended testing. Choose one and run JCL. If interactive testing is chosen the source listing is displayed and debugging c an be started. The STatus of the submitted JCL can be displayed. 5. HELP FACILITY For getting started with XPEDITER, type HELP HOWTO on the command prompt. For get ting more details, type HELP DEBUG on the command prompt of the Source screen. For gettin g the commands in XPEDITER, type HELP on the command prompt of the source screen. @ @ > Gs@ Gs ]

SILVERLINE INDUSTRIES LIMITED

REPORT ON XPEDITER

You might also like