IBM Mainframe Forum

Hi,
Can we use expeditor to debug eztrieve code? If not, is there any other way or tool for this??

Hello mrudulam and welcome to the forums,

Sorry for the late reply - i missed this post. . .

No, we cannot debug easytrieve with xpeditor.

The way most people debug easytrieve is by adding diagnostic code and commenting or removing it after all is working as needed.

dick scherrer wrote:No, we cannot debug easytrieve with xpeditor.

Really? I thought xpeditor could operate as a debugger even without the current source, couldn't get nice data area displays back or set breakpoints, but won't it catch and display data abends?

Hello,

I've never tried it. . .

Been told for a long time that it is not a way to go. I have trouble trying to imagine running interpreted code thru xpeditor.

With no data layouts and no really meaningful instruction info, i'm not sure how helpful it would be (if it would run at all).

I didn't either, and the only xpeditor I ever did was CICS COBOL/Assembler....But before I got it to work (first time I didn't know that th source listing needed to be put somewhere special) I did get interaction with it.....
All the EZT modules I've worked with were compiled and bound and were just Assembler real time, not interperted......

You can try inline run for easytrev program i.e. you can add display and diagonise the program without compiling !!Please some one corrcet me if i am not correct !!!

Hello bajshas and welcome to the forum,

You can try inline run for easytrev program i.e. you can add display and diagonise the program without compiling !!

How does this relate to the question about debugging Easytrieve using xpeditor?

It is important to read the enbtire topic . . .