|
If the service program runs in *CALLER, then each calling program has its own copy of the file handles and such and they should not interfere with one another.
*CALLER doesn't provide this. *CALLER means it runs in the caller's activation group -- if the callers all use the same named group, you'll still have the same conflicts you would've had if the srvpgm's ran in those groups.
Worse, someone who doesn't understand ACTGRP's is probably either using DFTACTGRP(*YES) or ACTGRP(QILE). So, changing to *CALLER will do nothing for them.
Again, if true independence is what's desired, I suggest using _Ropen() and friends. Then you can truly have multiple copies open in the same srvpgm, allowing the file sharing to work similarly to the way it did when you had separate programs.
If you've written a code generator to externalize these files, the generator could output the _Ropen(), _Rreadn(), _Rreadk() code as required, insulating the caller from having to understand how it works, while providing lots of great functionality.
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.
midrange.com
