Re: ILE and DDS Question...

At 09:55 03/25/2000 , Julie Francis wrote:
>I have two questions.  If I have an ILE program that calls a bound
>program (repeatedly) should I set up the module to keep the files open
>or is this done automatically because it is an ILE program?

You should not turn on LR. This will allow files to stay open. It will also 
prevent static storage from being reinitialized so that you can do some 
intelligent comparisons between calls (like do I already have the requested 
record). You must take care to initialize variables when calculations 
assume that they start with default values, since they may contain the 
results from the last call. When you are ready to terminate the 
application, execute a bound call (callb) to 'CEETREC' (no parameters). 
It's like turning on a super LR indicator in that it will kill the entire 
activation group, forcing all files to close and releasing all program storage.

>Also, when I return from a called program my display file screen
>disappears unless I RSTDSP(*YES) which is not the compiled default.  Is
>there anything I can put in the DDS to overcome this?

Well, you could re-write the display, but that's probably not worth the 
effort. You could also create a copy of the CRTDSPF command and change the 
command default to RSTDSP(*YES). The reason behind this is that there is 
some additional system overhead necessitated by the RSTDSP(*YES) 
processing, as well as some extra display IO that may not be welcome in 
small systems or systems communicating over small pipes. For the most part, 
this is more a historical than a current concern.

Pete Hall
pbhall@execpc.com
http://www.execpc.com/~pbhall
+---
| 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
+---