IBM Mainframe Forum Index
 
Log In
 
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register
 

Commands used in EXPEDITER


IBM Mainframe Forums -> Compuware & Other Tools
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
ambesh

New User


Joined: 07 Jul 2005
Posts: 6
Location: pune

PostPosted: Mon Aug 22, 2005 11:28 am
Reply with quote

Myself is Utpal. I want to know for line by line execution which PF key is used in Expediter. Send some commands in EXPEDITER. If you send the answer i will be thankful to you.
Back to top
View user's profile Send private message
BAJJI

New User


Joined: 15 Jul 2005
Posts: 47

PostPosted: Mon Aug 22, 2005 3:39 pm
Reply with quote

Utpal

To execute line by line we use the key F9.

myself, am new to Xpeditor. lets wait for someone to help us out.

Thanks.
Back to top
View user's profile Send private message
rahul_jot

New User


Joined: 17 Aug 2005
Posts: 22
Location: Pune

PostPosted: Tue Aug 23, 2005 11:08 am
Reply with quote

Following commands can be useful for expeditor:
line command B => for putting breakpoint
Keep <var name> => for monitoring variable values
F12 => for execution till the next breakpoint is encountered.
mon or monitor => to monitor the flow of execution (it is used if you want to go in reverse flow after some time)
Rev or Reverse => after typing this command and then pressing F9 will take the flow in reverse flow (but for this monitor is must otherwise it will not remember the reverse flow)
If you want to again go in forward direction, again type rev commmand.
To delete monitor command is "delete mon"
There is one more When command => It is used to keep breakpoint till a variable reaches a value. For example you want the program to execute till "A" = xyz. then command will be when A = 'xyz' and press enter. After this press F12. The execution will stop as soon as A gets value as 'xyz'. After this do not forget to give "delete when" command.
If one program calls second then you can view source for the second program from first by SO command. Syntax is SO <PGMNAME>
There are lot of more commands you can use. But I thing these are the mainly used commands and sufficient for debugging programs through expeditor.
Back to top
View user's profile Send private message
ajayvamsi

New User


Joined: 21 Jul 2005
Posts: 56
Location: Hyderabad

PostPosted: Tue Aug 23, 2005 2:43 pm
Reply with quote

HI I am little bit aware of Xpediter but I am muddled of how to execute a program if it is having sub programs....what is the procedure for compiling that in Xpediter and can any one expalin in steps how to compile and execute the program should i need to go any compilation options changed...!! please help me out on this...! thanks
Back to top
View user's profile Send private message
anuradha

Active User


Joined: 06 Jan 2004
Posts: 247
Location: Hyderabad

PostPosted: Tue Aug 23, 2005 9:34 pm
Reply with quote

Hi AjayVamsi!

Quote:
I am little bit aware of Xpediter but I am muddled of how to execute a program if it is having sub programs....


Let us take one example.

Suppose program A is as follows:

Code:
IDENTIFICATION DIVISIOON.
PROGRAM-ID. A
----
---
PROCEDURE DIVISION.
---
---
MOVE X to Y.
MOVE 'B' TO WW-000-PGM
CALL WW-000-PGM USING ----,---
EVALUATE WH-000-RTRN-CDE
WHEN WS-000-SUCCESS
---
GO BACK.
Now if you are expediting Program A and you need to see the flow of program B even. Then once u reach the CALL statement in expeditor type SOURCE B in the command prompt. Then Keep a break point at the procedure division of B and continue your expediting.

But if you need to comeback to A again, then before going to B keep a break point after the call statement ..and then say source B.

A and B should be available in the loadlib.

HTH,
Back to top
View user's profile Send private message
anuradha

Active User


Joined: 06 Jan 2004
Posts: 247
Location: Hyderabad

PostPosted: Tue Aug 23, 2005 9:47 pm
Reply with quote

Hi All!

Here are few more Expeditor commands. We generally use only few of them. I too didn't try some of the commands. Still For your information:

COMMAND & ACTION

AFTER Breakpoint after execution of line
BEFORE Breakpoint before execution of line
BOTTOM Scrolls to bottom of currently displaye data
COUNT Sets execution counters to gather test coverage statistics
DELETE Removes all XPEDITOR commands (e.g. breakpoints)
DLEFT Scroll data in Keep/Peek window to left- can specify amount
DRIGHT As above to the right
END Terminates current function and returns to previous screen
EXCLUDE Excludes data lines from displaying in the source
EXIT Terminates the current test session
FIND Searches for character strings, data names and COBOL structures.
GO 1 Walks through code (equivalent PF9)
GO Goes to next breakpoint (equivalent to PF12)
GOBACK Changes the program logic and returns higher level module
GOTO Repositions the current execution pointer
HELP Displays info about error message or gives tutorial info.
IF Establish a conditional expression in a block of inserted lines
INSERT Temporarily insert XPEDITOR/TSO commands in the program
INCLUDE Include command executes a predefined test script member
KEEP Displays the values in a chosen field in Keep window
LEFT Scrolls source listing to left by specified amount
LOCATE Scrolls to particular line number.
MEMORY Displays memory for a specified location
MONITOR Records program execution in a buffer.
MOVE Changes the contents of program variables
PAUSE Sets a pause breakpoint within inserted lines or commands
PEEK Displays values of program variables.
RESET Restores excluded lines in source screen
RETEST Begins a new test of the same program
REVERSE Reviews the execution path that led to the current breakpoint.
RIGHT Scrolls the source to the right by a specified amount
SET Overrides XPEDITOR/TSO defaults.
SHOW Displays breakpoints, diagnostic info or SKIP Temporarily bypasses the execution of a statement
SOURCE Changes the module shown on the source display during Interactive debugging
TOP Goes to the top of the data
UP Scrolls to the top of data
WHEN Indicates when a specified condition is true or when program variable changes value.
WS Displays Working storage
ACCEPT Accepts the data from I/P file or from Instream data
Back to top
View user's profile Send private message
ravikumarreddy
Warnings : 1

New User


Joined: 29 Jul 2005
Posts: 23

PostPosted: Wed Aug 31, 2005 10:39 am
Reply with quote

hi,
thanks anu ,now i am very much cofident on expeditor
thanks once again..

ravi
Back to top
View user's profile Send private message
ajayvamsi

New User


Joined: 21 Jul 2005
Posts: 56
Location: Hyderabad

PostPosted: Thu Sep 01, 2005 1:09 am
Reply with quote

HI Anu,
Thanks a lot for ur patience.!! Have a nice day...
Back to top
View user's profile Send private message
ajayvamsi

New User


Joined: 21 Jul 2005
Posts: 56
Location: Hyderabad

PostPosted: Thu Sep 01, 2005 1:31 am
Reply with quote

HI Anu ,
wat is the purpose of these DDIO files?
wat exactly they are used for ...
To execute a program in XP .....Initially MUST the program need to be complied in XP..?if not wat is the reason .?
Please advice on this ...Thanks..!!
Back to top
View user's profile Send private message
anuradha

Active User


Joined: 06 Jan 2004
Posts: 247
Location: Hyderabad

PostPosted: Thu Sep 01, 2005 3:59 pm
Reply with quote

Hi Ajayvamsi!

DDIO is a VSAM file which contains the Source listing information, along with timestamp information.

Quote:
To execute a program in XP .....Initially MUST the program need to be complied in XP..?if not wat is the reason .?


Yup. We have to compile in XP. We use ENDEVOR as the version control tool in our shop and we use the processor group accordingly to compile the program with expeditor option. If the program is not compiled in expeditor option and if you try to expedite that, u will get error message "NO SOURCE LISTING INFORMATION FOUND FOR MODULE".

HTH,
Back to top
View user's profile Send private message
deepak.venkataraman

New User


Joined: 07 Sep 2005
Posts: 8
Location: Bangalore

PostPosted: Wed Sep 07, 2005 11:02 am
Reply with quote

COMMAND & ACTION

AFTER Breakpoint after execution of line
BEFORE Breakpoint before execution of line
BOTTOM Scrolls to bottom of currently displaye data
COUNT Sets execution counters to gather test coverage statistics
DELETE Removes all XPEDITOR commands (e.g. breakpoints)
DLEFT Scroll data in Keep/Peek window to left- can specify amount
DRIGHT As above to the right
END Terminates current function and returns to previous screen
EXCLUDE Excludes data lines from displaying in the source
EXIT Terminates the current test session
FIND Searches for character strings, data names and COBOL structures.
GO 1 Walks through code (equivalent PF9)
GO Goes to next breakpoint (equivalent to PF12)
GOBACK Changes the program logic and returns higher level module
GOTO Repositions the current execution pointer
HELP Displays info about error message or gives tutorial info.
IF Establish a conditional expression in a block of inserted lines
INSERT Temporarily insert XPEDITOR/TSO commands in the program
INCLUDE Include command executes a predefined test script member
KEEP Displays the values in a chosen field in Keep window
LEFT Scrolls source listing to left by specified amount
LOCATE Scrolls to particular line number.
MEMORY Displays memory for a specified location
MONITOR Records program execution in a buffer.
MOVE Changes the contents of program variables
PAUSE Sets a pause breakpoint within inserted lines or commands
PEEK Displays values of program variables.
RESET Restores excluded lines in source screen
RETEST Begins a new test of the same program
REVERSE Reviews the execution path that led to the current breakpoint.
RIGHT Scrolls the source to the right by a specified amount
SET Overrides XPEDITOR/TSO defaults.
SHOW Displays breakpoints, diagnostic info or SKIP Temporarily bypasses the execution of a statement
SOURCE Changes the module shown on the source display during Interactive debugging
TOP Goes to the top of the data
UP Scrolls to the top of data
WHEN Indicates when a specified condition is true or when program variable changes value.
WS Displays Working storage
ACCEPT Accepts the data from I/P file or from Instream data
Back to top
View user's profile Send private message
ajayvamsi

New User


Joined: 21 Jul 2005
Posts: 56
Location: Hyderabad

PostPosted: Fri Sep 09, 2005 10:34 pm
Reply with quote

Hi Anu ,
Thanks for ur help I will come with more questions ...!!
Till then Bye ...!!
Back to top
View user's profile Send private message
ajayvamsi

New User


Joined: 21 Jul 2005
Posts: 56
Location: Hyderabad

PostPosted: Fri Sep 09, 2005 10:45 pm
Reply with quote

Hi deepak,
As it is said that INCLUDE command will helps to executes a predefined test script member can u explain me in details..regarding these test script members ..!!
Thanks and Regards,
ajay
Back to top
View user's profile Send private message
prasanth_thavva

New User


Joined: 28 Jul 2005
Posts: 86
Location: Chennai

PostPosted: Sun Oct 09, 2005 10:07 am
Reply with quote

HI
WHAT DO U MEAN BY
predefined test script member can u explai
CAN U EXPLAIN ME
BYE
Back to top
View user's profile Send private message
qykzoo

New User


Joined: 05 Apr 2005
Posts: 3
Location: Singapore

PostPosted: Thu Jan 19, 2006 7:16 am
Reply with quote

Compuware Singapore has a very good educator, Rajesh Chandran whom can teach this.......

get enuf of u together and pay for the course....
Back to top
View user's profile Send private message
saranya_sn

New User


Joined: 03 Jul 2005
Posts: 12
Location: India

PostPosted: Fri Jan 20, 2006 12:06 am
Reply with quote

The cobol ver 3 does not give a DDIO load version it needs to be complied seperately and this load will be given in the DDIO library setup in the Xpeditor
Back to top
View user's profile Send private message
anuradha

Active User


Joined: 06 Jan 2004
Posts: 247
Location: Hyderabad

PostPosted: Thu Feb 09, 2006 3:14 pm
Reply with quote

badal wrote:
hai anu,
thanks for giving a good tips regarding Xped. but i have 1 doubts, on the time of comign from sub-pgm to main-pgm, will i give command of
Source main-pgm in the command prompt of sub program?

Thanks and Regards.
Badal

Am not sure if u still have this doubt.

Anyways FYI..

If we need to come back to main program from subprogram, we have to keep a break point in the main program after the call statement. We have to keep this break point before coming to sub program itself.

Hmm..Let me take an example


Let us say PGM A calls PGM B.

Code:

00001     IDENTIFICATION DIVISIOON.
00002     PROGRAM-ID. A
----
---
00100     PROCEDURE DIVISION.
---
---
00450     MOVE X to Y.
00451     MOVE 'B' TO WW-000-PGM
00452     CALL WW-000-PGM USING ----,---
00453 B   EVALUATE WH-000-RTRN-CDE
00454     WHEN WS-000-SUCCESS
---
09919     GO BACK.


After the call statement we need to keep the break point as above. And then we can say source B at the command prompt. Now from B if we need to come back to A then press F12 or even can finish B and by F9 also we can come back to A (provided we kept a break point in A)

HTH
Back to top
View user's profile Send private message
venkatnimmala

New User


Joined: 15 Mar 2006
Posts: 1

PostPosted: Wed Mar 15, 2006 8:25 pm
Reply with quote

How to bypass executing a piece of code using XPED? Can you please give me some info on this
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> Compuware & Other Tools

 


Similar Topics
Topic Forum Replies
No new posts Console Commands All Other Mainframe Topics 4
No new posts commands missing in JESMSGLG JCL & VSAM 3
No new posts ZOS Console commands through USS REXX? CLIST & REXX 5
No new posts How can I know what tso commands are ... TSO/ISPF 18
No new posts ISPF Panel commands DDLIST /LISTBOX TSO/ISPF 11
Search our Forums:

Back to Top