Xpediter is designed for programmers who want assistance in discovering the cause of an abend, a loop or logic error in a program. This course covers how to use Xpediter to debug batch Db2 COBOL programs in TSO. The student will use Xpediter to follow the logic of a program, look at the contents of a field, watch how it changes as the program executes, and change a field’s contents to see the effect. In addition the student learns how to alter program logic, trap and recover from program errors, set statement execution counts and resume execution from any point in the program. This course focuses on the specific setup and debug ging required by Db2 batch COBOL programs.XPEDITER is a debugging and abend intercept tool that runs interactively in full screen mode as well as in a batch environment. You will learn to interactively allocate files, maintain multiple test profiles, interrupt and restart execution at any point, trace logic flow, bypass undesired program code, and monitor, display and modify program variable contents. You will be able to temporarily insert XPEDITER/TSO debugging statements, and view the log that XPEDITER maintains of all user activity during test sessions.This course uses programs with a variety of typical abend and logic errors to illustrate each command. Students debug a variety of actual abends and program failures in this extensively hands-on course. This course is a prerequisite to our XPEDITER/CICS course.

SETUP: Site must have TSO logons with XPEDITER/TSO installed. Each student needs a PC or terminal with mainframe access. Access to Db2 from TSO must be available. Each student needs a TSO logon, package for Db2, and access to the Db2 sample tables: EMP and DEPT.OVERVIEW OF TOPICS:• General overview of Xpediter• Creating the test environment• Setup: Allocating libraries, creating FLISTs for I/O• Compiling with Xpediter• Setting break points• Accessing and modifying data, including table entries• Controlling execution, intercepting abends• Db2 debugging tips• Static and dynamically linked subprograms• Debugging approaches