XPEDITER
description
Transcript of XPEDITER
Have a general knowledge sharing session about XPEDITER.
Introduction to XPEDITER Creating environment for XPEDITER to run (Settings) Expediting batch programs
Objectives of this session
Mainframe tool for debugging.
Helps to intercept and analyze abends.
Automates the tasks of identifying problems, applying solutions, analyzing the impact of changes, and testing the fixes.
Introduction
Runs interactively or in batch. Intercepts application program abends Alters logic Displays and modifies the content of program
variables Controls the program execution at any point
i.e.. tests any program or program segment
starts or stops execution at any point
Features of XPEDITER
Bypasses unwanted code Traces logic flow Analyzes program structure and data flow Automatically generates a test script library Keeps a log of the test session activity Provides online HELP
Features of XPEDITER (cont..)
Source code is displayed in a fully scrollable window.
The inner working of the program can be viewed as each step executes.
While Xpediting a program…
Allocate Xpediter data sets
Invoke Xpediter Choose the utilities Create Xpediter environment Allocate program files Xpedite the program
Exit from Xpediter
Xpediting a program…
Allocating Xpediter datasets using ISPF option 3.2
Allocate Xpediter data sets
Datasets to be allocated are as follows:
Load data set o Load module for the compiled/linked modules and
programs will be stored Script data set
o Stores the scripts that are created during an Xpediter session
Allocate data set o Stores the allocations for all the files that the program
or modules will need in order to run properly
Allocate Xpediter data sets
Type ‘XP’ on the command line and press enter to begin the Xpediter session.
Invoke Xpediter
Choose option ‘5’ for utilities. Invoke Xpediter: Choose utilities
Choose option ‘3’ for DDIO file facility.
Invoke Xpediter: Choose utilities
In this file facility, the DDIO files are allocated. This file is used to store information that allows Xpediter to display the object code during a test session. Type a ‘C’ for create in the selection field and fill the relevant data.
Invoke Xpediter: Choose utilities
Complete the screen as follows and press enter
Invoke Xpediter: Choose utilities
To create the Xpediter environment. Select option ‘6’ from the Xpediter Primary Menu
Invoke Xpediter: Create environment
Select the appropriate option based on the location of the module or program you would like to compile, COBOL in this e.g..
Invoke Xpediter: Create environment
Complete the screen as shown in the example . A job will be executed to run the compile.
Invoke Xpediter: Create environment
The next step is to allocate program files. Type ‘1’ on the command line and press enter.
Invoke Xpediter:Allocate program files
Type ‘4’ for Edit Allocation List
Invoke Xpediter:Allocate program files
Complete the Edit File List screen as shown below.
Invoke Xpediter:Allocate program files
All output from the modules/programs that are tested in Xpediter must be sent to a data set to be viewed. Enter the DDNAME, DSNAME, & DISP of the data sets which will be used to test the modules.
Invoke Xpediter:Allocate program files
The next step in executing an Xpediter session is to invoke Xpediter. Select option ‘2’ on the Xpediter Primary Menu Screen
Invoke Xpediter:Xpedite the program
Choose option ‘1’ for Load Libraries.
Invoke Xpediter:Xpedite the program
1
Enter the name of the load libraries and press enter. This will take control back to the Xpediter Setup Menu.
Invoke Xpediter:Xpedite the program
Next step is to specify the DDIO file. Enter a ‘2’ on the command line and press enter.
Invoke Xpediter:Xpedite the program
Enter the name of the DDIO file
Invoke Xpediter:Xpedite the program
Your DDIO file.
Next, step is to setup the script libraries. Type ‘3’ on the command line
Invoke Xpediter:Xpedite the program
Enter the script library and the installation library.
Invoke Xpediter:Xpedite the program
Next, setup the log data set. Select option ‘4’.
Invoke Xpediter:Xpedite the program
Enter the relevant data.
Invoke Xpediter:Xpedite the program
Next, setup the test script dataset. Select option ‘5’.
Invoke Xpediter:Xpedite the program
Enter the relevant data.
Invoke Xpediter:Xpedite the program
The last step in executing and Xpediter session is actually executing Xpediter commands. Choose option ‘2’ from the Xpediter Primary Menu
Invoke Xpediter:Xpedite the program
In this panel, choose the program that is to be Xpedited.
Invoke Xpediter:Xpedite the program
This screen will display the source code of the module that is being tested.
The arrow always points to the current statement that is executing once execution has haulted.
Invoke Xpediter:Xpedite the program
SAME: Indicates that all characters to the right of those displayed are the same.
MORE: Indicates that the characters to the right of those displayed are different.
Invoke Xpediter:Xpedite the program
SET KEEP ** : Sets size of AUTOKEEP window to **
Invoke Xpediter: Primary Commands
SHOW PFKEYS : Reset value of PFKEYS
Invoke Xpediter: Primary Commands
An example of the output for “SHOW PFKEYS”
Invoke Xpediter: Primary Commands
LOG : View log
Invoke Xpediter: Primary Commands
LOG : Output of “LOG” command.
Invoke Xpediter: Primary Commands
MOVE : Initialize or change the value of a variable
Invoke Xpediter: Primary Commands
TRACE ALL S : document each statement executed in a session
Invoke Xpediter: Primary Commands
SKIP xxx yy : Skip lines xxx to yyy.
Invoke Xpediter: Primary Commands
RETEST : Retest module without exiting Xpediter
Invoke Xpediter: Primary Commands
GO nn : Execute nn lines
Invoke Xpediter: Primary Commands
GOTO xxx : Goto the specified line number
Invoke Xpediter: Primary Commands
MONITOR ALL : prerequisite to execute REVERSE
Invoke Xpediter: Primary Commands
REVERSE : Executes the code to be tested backwards
Invoke Xpediter: Primary Commands
RESUME : Exit REVERSE mode
Invoke Xpediter: Primary Commands
INTERCEPT : Get the source code of another module in program
Invoke Xpediter: Primary Commands
SOURCE : To return to the calling module
Invoke Xpediter: Primary Commands
EXIT : End an Xpediter session
Invoke Xpediter: Primary Commands
Line Commands : A, B
Invoke Xpediter: Line Commands
B = breakpoint
The ‘A’ means execution should stop after this statement has executed.
Invoke Xpediter: Line CommandsLine Commands : C
C = count
Invoke Xpediter: Line CommandsLine Commands : D, Dx
D = delete
Invoke Xpediter: Line CommandsLine Commands : I
I = Insert
Invoke Xpediter: Line CommandsLine Commands : K
K = keep
Line Commands : P
Invoke Xpediter: Line Commands
Peek Elementary Command.
Peek Command.
Invoke Xpediter: Line CommandsLine Commands : X, XX
X = exclude
To end an Xpediter session, type ‘EXIT’ on the command line and press enter.
Exit from Xpediter
CommandsPrimary Commands
Command Description NoteSET KEEP ** Sets size of AUTOKEEP window to **SHOW PFKEYS Reset value of PFKEYSLOG View logMOVE Initialize or change the value of a
variableTRACE ALL S document each statement executed in a
session SKIP xxx yyy Skip lines xxx to yyy.
RETEST Retest module without exiting Xpediter
XPEDITER Commands
Commands Primary Commands
Command Description
GO nn Execute nn linesGOTO xxx Go To (This command should be avoided)MONITOR ALL Prerequisite to execute REVERSEREVERSE Executes the code to be tested
backwardsRESUME Exit REVERSE modeINTERCEPT Get the source code of another module in
program SOURCE To return to the calling module EXIT End an Xpediter session
XPEDITER Commands
Line Commands
Command Description Note
A Set Breakpoint After ‘A’ will appear (‘@’ if both
B Set Breakpoint Before ‘B’ will appear (‘@’ if both)
C Counts the number of times a line of code is executed
D Delete a line Block delete using DDDx Delete Breakpoint x can be A or B
or K
XPEDITER Commands
Line Commands
Command Description
I Insert a new lineK Keep operand Keep track of this on top
of screenP Peek operand Show on left of sourceX Exclude lines of code from the display screen
XPEDITER Commands
Thank You