Endevor is a source code management and release management tool for mainframe computers running z/OS.It is part of a family of administration tools by CA Technologies (formerly Computer Associates), which is used to maintain software applications and track their versions. Note:. This was designed based on the sites & materails available through google search only.
Below are the few online expeditor useful commands for basic debugging of a program.
FOllowing screen is the CHANGE MAN mainscreen Type 1 at option prompt, you will get following screen Type 1 at OPTION prompt, you will be prompted with following screen press ENTER, It will show two screen, there you need to enter the details of package (usaually audit program details). Then it will careate the package name using APPLICATION type that you provided.
Expeditor Quick Reference →
xpediter keep window size – To increase or decrease the keep window size
SET KEEP <n>
n can be any number from 3 to 11.
SET KEEP 3 is the minimum window size and SET KEEP 11 is the maximum window size
Command line Commands:
XPED <Program Name> → Type this in the Native CICS region which open the program in Debug mode allowing user to enter break points or setup KEEP/ PEEK etc.
KEEP <variable name> → It displays the variable value throughout the program execution. This can also be set by giving K in Line next to the variable.
PEEK <variable name> → It displays the group level variable along with all sub level variables values. This can also be set by giving P in Line next to the variable.
WHEN <variable name> CHANGES → This also sets the break point but it sets when the given variable value changes.
WHEN <variable name> = <value> → This command issues a break whenever the variable value become equals to the given value
DELETE ALL → Deletes all the commands that are in effect like Break points, KEEPs etc.
DELETE BREAKS → Deletes all the break points.
DELETE S → Deletes only Skip commands
DELETE K → Deletes Keeps
ACCESS → This is used to access MAPS, MAPSETS etc while executing the program in xpeditor. PF3 takes back to the execution window.
Ex: ACCESS MAPS → It shows a screen where MAP need to enter and then it displays the named map.
Sample Command line
Line Commands
B → Break Point, Put a B on the line and press enter. Break pint will be set at that point.
O → One time break point, Once that statement executes break point will not be in effect.
K → Equivalent to KEEP<variable name>.
K2 → It displays the second variable found after K2.
Ibm Manuals Mainframe
K3, K4, K5.. etc also possible. It shows the value correspondingly.
KK → Used to set keeps for a block of variables. It can be used in procedure and working storage divisions.
K* → Sets Keep for all the variables used in that statement.
P → PEEK. It displays the group level variable along with all the sub level variables values . To come out off the PEEK window, Press PF3
GT → GO TO , It takes the control to that particular line. It skips all other lines before to GT & current execution point from execution.
D → Used to delete the break points and also used to delete the KEEPs
S → Skips that line from the execution
SS → Skips block of lines in between SS &SS from execution.
PF Keys
PF9 → Line by Line Execution
PF12 → Break Point to Break point Execution
PF3 → Exit from the program.
SHIFT PF6 → It shows the screen while execution is going on. To come back to the execution, Press SHIFt PF6 again.
Endeavor Mainframe Manual
To come back into execution window after pressing Pf3 →
Get in to L SOURCE LISTING option.( DEBUGGING FACILITIES → SOURCE LISTING)
To Enter into Sub Program from the main Program →
- One way is to put break points in all modules before entering the transaction.
- Other way is , before the execution of the sub program.. Change the module name to Sub Program name on the top Left corner and put a break point. Change it back to Main program and execute it.
To come out of the Execution Window →
- Press Pf3 thrice and then ENETRFirst PF3 you get Debugging Facilities Menu shown below
2nd PF3 →
3rd PF3 →
Endeavor Mainframe Manual Software
END Session – YES → It removes the program(s) from the xped
No → Program remains in the xped mode and if we enter the programs transaction, it gets opened in debug mode.