Re: DoW (WAS DoU...)

Hi Paul -

>Yup.  And add the USROPN keyword, and open it on the 
>first call to the procedure.  There was a debate a 
>while back as to whether %OPEN or a static variable 
>was the better approach to determining whether the 
>file has been opened yet.  The other burning question 
>is whether the add a cleanup procedure to close the 
>file, or to allow it to be closed when the activation
>group ends.

The problem with using a static variable is that if the service program is
running in the default activation group and RCLRSC is run, the files are
closed but static variables are not changed.  I'm writing my first service
program that uses files so I've been doing some experimenting.

I did not check if %OPEN works properly, instead I wrote an open and close
procedure since I need some additional processing anyway.  The open
procedure does a CLOSE *ALL to close any of the files that happen to be
open, does some other special processing not directly related to the files,
then opens the files.  The close procedure does a CLOSE *ALL then some other
special processing not directly related to the files.

Each client program is responsible for calling the open procedure before
calling any of the procedures that use the files and calling the close
procedure before ending.

BTW, these procedures are not actually called open and close.  They are
named in such way that each service program can have uniquely named open and
close procedures with a consistent naming convention.

Ken
Southern Wine and Spirits of Nevada, Inc.
Opinions expressed are my own and do not necessarily represent the views of
my employer or anyone in their right mind.

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