RE: What bugs you about KLISTs in RPG IV?

That was beautifully put!!!
Definitely like the:
<Quote> "F11ening" (new technical term!) <End Quote>

I agree we need to have:

1. Add the F11 for the whole key list at once.
2. Let us Watch all by ourselves, no machine watch.
3. Add Stop the interruptions (i.e., phone leaks) while deep in debug(or
deep in thot, or deep in ....).

Brad Bird
Prime, Inc.
Springfield, MO

> -----Original Message-----
> From: owner-rpg400-l@midrange.com
> [mailto:owner-rpg400-l@midrange.com]On
> Behalf Of Carol Bastien
> Sent: Thursday, June 17, 1999 1:32 AM
> To: RPG400-L@midrange.com
> Subject: Re: What bugs you about KLISTs in RPG IV?
>
>
> Scott Klement wrote:
>
> > Theres a very simple solution to the whole "debug a whole keylist"
> > problem.   Just put all of your keys in a data structure somewhere,
> > and debug THAT.
> >
> > Maybe I'm weird, but its only once in a blue moon that I need to
> > debug a keylist, and hitting F11 (or typing eval varname) for 2 or 3
> > different variables in a keylist doesn't bother me at all.
> If it did,
> > I'd make a data structure that contained all of my keys,
> just to make
> > it easier to debug them.
> >
>
> Scott -   Have you ever had to support  users on a large
> software package
> like J.D.Edwards,  CA/PRMS or the like.  One of the most
> common questions
> you're ask is, 'Why dosen't something display on the screen
> or print out on
> the report'.  That's when you open up the code on the
> program, once you've
> tracked the guilty one down, and you find out it's most
> definately a miss on
> one of maybe 20 files all of which have compound keys . . .
> so after you
> spend quite a bit of time figuring out what was in the parms
> required to call
> the program you finally get the baby up in debug.  Now you're
> at the fifth
> key list and "F11ening" (new technical term!) on the 6 key
> fields for that
> file . . . and you stop and think while chewing one recently abused
> fingernail:  I'm almost lost here, or am I?  Should I start
> over, or try to
> keep going 'cause maybe I'll get lucky?  Was that first field
> in that last
> key list left justified, or was there a blank in front of the
> 1st character?
> Yeh, maybe I should start over and first I'll just redefine
> all these keys in
> data structures so I can see them clearly . . . Oh but wait,
> they're all in
> Copy statements so I'll have to recompile first so I see what they are
> suppose to be . . . That's when the phone rings and it's the
> controller who's
> waiting anxiously for the answer to the mystery.
>     It's times like that when I'm wishing I could just F11 on
> the key list
> and see answers instead of the "That does not compute"
> message. Trouble is,
> the more flexibility the software vendors build into their
> packages, the
> worse this situation gets.
>     Anyway, that's why I want, need, require . . . dare I say
> demand the F11
> "Show me the keys", and why they just MUST put back the
> ability for me (not
> just the computer) to Watch a selected set of variables.
> That's why I'm in
> debug after all.
>     Most sincerely - Carol
>
>
> * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
> * * * * * *
> * This is the RPG/400 Discussion Mailing List!  To submit a
> new         *
> * message, send your mail to "RPG400-L@midrange.com".  To
> unsubscribe   *
> * from this list send email to MAJORDOMO@midrange.com and
> specify       *
> * 'unsubscribe RPG400-L' in the body of your message.
> Questions should *
> * be directed to the list owner / operator:
> david@midrange.com          *
> * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
> * * * * * *
>


* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* This is the RPG/400 Discussion Mailing List!  To submit a new         *
* message, send your mail to "RPG400-L@midrange.com".  To unsubscribe   *
* from this list send email to MAJORDOMO@midrange.com and specify       *
* 'unsubscribe RPG400-L' in the body of your message.  Questions should *
* be directed to the list owner / operator: david@midrange.com          *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *