× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: Activation Groups & File Overrides
  • From: Vanja Jovic <vanja@xxxxxxxxx>
  • Date: Fri, 12 May 2000 23:09:44 -0600

Jon,

it seams that you expect calling program to close the file using
share(*yes). Hm, that doesn't work like that. Without going deeply into
reasoning why and how to use shared access paths, that is inappropriate
for what you want to achieve. The fastest solution here would be to kill
activation group. Better way would be to create NOMAIN module, define
USROPN file and subprocedures to perform specific tasks (open file,
read, process, ..., close), bind it into your program and CALLP each
module as needed. If you want it to be reusable, make it service
program. You may pass data among modules using exported, externally
defined data structure.

Hope this helps,

Vanja Jovic,
Canada



Jon Erickson wrote:
> 
> I'm attempting to separate a common subroutine into its own module, (MOD1)
> to be bound and callable from other programs/modules.
> 
> The Module opens File1 for input.  I'd like to be able to call this module
> repeatably without the file initialization overhead, yet not have to call
> the module an additional time just to seton LR to close the file.
> 
> I've tried 'OVRDBF FILE(FILE) OVRSCOPE(*CALLLVL) SHARE(*YES)' from a calling
> RPGLE using QCMDEXC & USROPN, but the the file still is open, (Scope
> *ACTGRPDFN, Group QILE), after the calling RPGLE DLTOVR & CLOSE opcode and
> seton LR.
> 
> Any insight appreciated..
> 
> > Regards,
> > Jon A. Erickson
> > Sr. Programmer Analyst
> > 800.COM Inc.
> > 1516 NW Thurman St
> > Portland, OR  97209-2517
> >
> > Direct: 503.944.3613
> > Fax: 503.944.3690
> > Web: http://800.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
> +---
+---
| 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
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.