Debugging Easytrieve program



Unicenter CA-Easytrieve Plus Report Generator: CA's information retrieval and data management tool

Debugging Easytrieve program

Postby shan111 » Tue Jun 30, 2009 7:19 pm

Hi All..

Can anyone please let me know the process to debug an Easytrieve program?
shan111
 
Posts: 6
Joined: Wed Jun 17, 2009 6:07 pm
Has thanked: 0 time
Been thanked: 0 time

Re: Debugging Easytrieve program

Postby dick scherrer » Wed Jul 01, 2009 12:24 am

Hello,

Incorporate some code to limit the operation and track the execution of the code.
Hope this helps,
d.sch.
User avatar
dick scherrer
Global moderator
 
Posts: 6269
Joined: Sat Jun 09, 2007 8:58 am
Has thanked: 3 times
Been thanked: 93 times

Re: Debugging Easytrieve program

Postby shan111 » Wed Jul 01, 2009 4:39 pm

Hi Dick,

I read somewhere that the below statement has to be included in the Environment section of the Easytrieve program to make it eligible for debugging:
PARM DEBUG (STATE FLOW)

I included it and the program executed normally. I did not find where and how to check the debugging process. Rather to say, I did not get the step that needed to be done after including the statement and executing the program.
shan111
 
Posts: 6
Joined: Wed Jun 17, 2009 6:07 pm
Has thanked: 0 time
Been thanked: 0 time

Re: Debugging Easytrieve program

Postby yallapanthula » Wed Jul 01, 2009 5:02 pm

i think only by placing display statements we can debug easytrieve program
yallapanthula
 
Posts: 1
Joined: Wed Jul 01, 2009 2:57 pm
Has thanked: 0 time
Been thanked: 0 time

Re: Debugging Easytrieve program

Postby dick scherrer » Thu Jul 02, 2009 1:11 am

Hello,

Is this ("PARM DEBUG (STATE FLOW)" the first statement in your program? If not, try it as the first statement. This:
PARM ABEXIT (SNAP) +
DEBUG (PMAP, DMAP, FLDCHK, FLOW, +
FLOWSIZ (20), STATE)
is a "debugging" example from a not current release of Easytrieve.

When the job is run is there any "DD statement missing" warning?

I've never tried to use this feature, but have discovered that diffeent releases of Easytrieve are sensitive to how a PARM is coded. . .

Which release of Easytrieve is used on your system?

I've helped people to use "display" to diagnose code.
Hope this helps,
d.sch.
User avatar
dick scherrer
Global moderator
 
Posts: 6269
Joined: Sat Jun 09, 2007 8:58 am
Has thanked: 3 times
Been thanked: 93 times

Re: Debugging Easytrieve program

Postby shan111 » Thu Jul 02, 2009 7:20 pm

Hi Dick,

Yes..PARM DEBUG (STATE FLOW) is the first statement in my Easytrieve code.

When the job is run, I did not get any "DD statement missing" warning and it ran fine and produced the correct output. But dont know how exactly it can be debugged from the start of the code.

I am using 6.4 version of Easytrieve..
shan111
 
Posts: 6
Joined: Wed Jun 17, 2009 6:07 pm
Has thanked: 0 time
Been thanked: 0 time

Re: Debugging Easytrieve program

Postby dick scherrer » Thu Jul 02, 2009 11:17 pm

Hello,

DId you try the alternate PARM statement i posted from the manual?

What happens when this is used?
Hope this helps,
d.sch.
User avatar
dick scherrer
Global moderator
 
Posts: 6269
Joined: Sat Jun 09, 2007 8:58 am
Has thanked: 3 times
Been thanked: 93 times

Re: Debugging Easytrieve program

Postby shan111 » Wed Jul 08, 2009 10:54 am

Sorry for the delay..

No Dick. I will try and let you know of the result.

Thanks.
shan111
 
Posts: 6
Joined: Wed Jun 17, 2009 6:07 pm
Has thanked: 0 time
Been thanked: 0 time

Re: Debugging Easytrieve program

Postby dick scherrer » Thu Jul 09, 2009 12:37 am

Sorry for the delay..
No to worry :)

Someone will be here . . .

d
User avatar
dick scherrer
Global moderator
 
Posts: 6269
Joined: Sat Jun 09, 2007 8:58 am
Has thanked: 3 times
Been thanked: 93 times


Return to CA-Easytrieve

 


  • Related topics
    Replies
    Views
    Last post