Re: Recursive Calls

I am not very happy with your user-interface-approach "disable function key" to 
"keep users from getting lost". It is correct IMHO
to maintain a hieracial view with the menu-system at the top and programs, 
subprograms and sub-sub-programs below, but I think that
you should - if possibly - allow users to jump from one program to another 
without the extra keypresses of returning to the menu.
This is what started this thread. To avoid the problem with a huge call-stack 
(expressed by the 'subject' Recursive calls) the
recommandations in this thread (do an return to top level program and a new 
AUTOMATIC call to 'Program B') can be followed. If you
want to pass through some information from Program A to Program B (examp. last 
cust# / last date worked on) you can make a system
wide standard for where to save this. *LDA is one possibility (include a code 
'The content of this LDA follows the standard'). 

About the call stack: The tread "Find a CL program's library - While it is 
running" said that there is a MI-instr 'Materialize call
stack'. I don't know much about MI. Another solution is to write a CL-program 
that sends a pgmmsg up (xxxx *PRV) and recieves it
again. This will give the name of the program above any other program. In that 
way you can find the NAMES of the program in the
stack (but not the library). 

----------
Fra: zylka.marc@westpoint-stevens.com
Til: MIDRANGE-L@midrange.com
Emne: Re:RE: Recursive Calls
Dato: 8. juli 1999 19:29



We were thinking about doing the same thing.  If I could read the stack, though,
I could
check to see if the program is already running before I call it.  That would
make it quicker
for me to make the changes if that's not a big deal.

Marc Zylka 
WestPoint Stevens, Inc.


>We use a parm to tell when we call program b from another program, say a.
>We disable the function keys in program b when not called from a menu but
>from another program using a function key.  The users are forced to return
>to program a.  This keeps the users from getting lost...  This is much
>simpler than trying to read/control the program stack.  One level of JUMP
>only.  You can also have your parm allow for several levels, each one
>holding the from program name, say 10 levels with a second parm being an
>array of 10 element of 10 chars to hold each program name.
>
>Christopher K. Bipes                mailto:ChrisB@Cross-Check.com
>Sr. Programmer/Analyst                mailto:Chris_Bipes@Yahoo.com
>CrossCheck, Inc.                    http://www.cross-check.com
>6119 State Farm Drive                Phone: 707 586-0551 x 1102
>Rohnert Park  CA  94928                Fax: 707 586-1884




+---
| 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
+---