|
Nothing at all. Although the compiler is giving a warning (an AS/400 would alarm me, if there was a real problem :-), we never encountered any problem with it. We just call everything we want, and in the end we do a RCLRSC and RCLACTGRP *ELIGIBLE from another activation group (startup CL has another ACTGRP than the actual program. This one callps then a procedure in a service program which callps other procedures / functions.) We were afraid in the beginning, too. We are no longer afraid. There's just the "normal" close missing. I suggest OS/400 to handle this. The whole application was written from scratch in ILE, its in production for more than a year, and serves about 2.000 clients. Best regards, Anton Gombkötö ----- Original Message ----- From: "Mark Walter" <mwalter@netrax.net> To: <RPG400-L@midrange.com> Sent: Thursday, April 06, 2000 4:46 PM Subject: RE: Service Program Question. > but what happens if your service program does not set LR on? > > -----Original Message----- > From: Anton Gombkoto [SMTP:Gombkoetoe@ASsoft.com] > Sent: Thursday, April 06, 2000 2:57 AM > To: RPG400-L@midrange.com > Subject: Re: Service Program Question. > > > Suppose I had a service program that accessed a file that was also > accessed > > by the program that uses the service program. > > > > What kind of problems if any would this cause? > > We did this and had no additional problems to the problems that arose when a > called program accesses the same file as the calling program. There is the > risk of locking the record in your own job, when two programs try to read a > record for update, with a lock. But that isn't new and is avoided by using > the (N) - no lock -extension on the read operations when it's not necessary > to lock the record read. > > 0.02 Euro > -- > Anton Gombkoto > > > > +--- > | 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 > +--- > +--- > | 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 > +--- +--- | 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 +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.