RE: working with the value of integer variables in debug

Possible work arounds include storing the results of %founds and whatnots into 
temporary 
variables, (at least during debugging).  Example:  eval filestatus = 
%found(filename).  
Another workaround is to use indicators instead of %found.  If IBM wanted you 
to use bif's 
they'd support them in the debugger, (just sarcasm).

Have you submitted this as a Design Change Request to Kevin Toliver, the DCR 
Coordinator, 
at V234334@us.ibm.com? I'll give you a clue.  This position changes fast.  
These people 
move on to different positions as soon as they can.  Keep the phone numbers and 
addresses 
of the old people in a file.  I've had to call them up and say 'Do you remember 
when you 
were the DCR coordinator?  Who is doing that now?'  I've submitted a DCR in 
March to add 
support for nested /copy in SQLRPGLE.  Still waiting to see if it has been 
accepted.  I 
was loathe to give this info out for fear of burdening a resource I figure not 
many people 
knew about.







mcalabro@commsoft.net on 05/11/99 03:31:53 PM
Please respond to MIDRANGE-L@midrange.com@Internet
To:     MIDRANGE-L@midrange.com@Internet
cc:      

Subject:        RE: working with the value of integer variables in debug

I used scientific notation; BREAK 5 when index = 4.00e00  It was a stab in
the dark.  I did an ATTR index and it told me CARDINAL, 2 bytes.  I can
find no manual reference for this behaviour...

As for Mr Enzien trying to eval %found(filename), I don't believe this is
supported.  The only BIFs that the debugger seems to support are %SUBSTR,
%INDEX and %VAR.  Documentation seems scanty.

Buck Calabro

> -----Original Message-----
> From: Joel Fritz 
> Sent: Tuesday, May 11, 1999 11:50 AM
> To:   'MIDRANGE-L@midrange.com'
> Subject:      RE: working with the value of integer variables in debug
> 
> Here's an example of integer problems with a silly test program:
> *************************************************************************
> ***
>                             Display Module Source
> 
> Program:   INTLOOP        Library:   JEFTST         Module:   INTLOOP
> 
>      1           *MODULE ENTRY AND MAIN PROCEDURE ENTRY
>      2          1 Dindex            s              5u 0
>      3          2 Dnumber           s              5  0
>      4          3 C                   do        10            index
>      5          4 C                   eval      number = index
>      6          5 C                   enddo
>      7          6 C                   eval      *inlr = *on
>      8           *MAIN PROCEDURE EXIT
>  
> Bottom
> Debug . . .   BREAK 5 when index = 4
> *******Type compatibility error occurred.*******
> 
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---