How about something like this...

o Have the program leaving the file open run in a named activation group.
o Each time it runs have it check a control structure to see if it should close down.
o Your additional parameter returns a value to the invoking program telling it to reclaim the activation group and run the program again.

Using a pointer to a user space makes accessing the control structure virtually interactive. You obtain the pointer once and just check the value. When an external process changes the user space your program know about it almost instantly. It is also handy when you have copies of the program running in multiple jobs.

Gary Monnier

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Alan Shore
Sent: Thursday, March 15, 2012 8:04 AM
To: Midrange Systems Technical Discussion
Subject: RE: Creating an SQL UDF on a procedure

But then we have to inform everyone who will use this function going forward of this procedure.
I am not saying it's not feasible, just that eventually someone is not going to do that, and then we are back to my original questions.

Alan Shore
Programmer/Analyst, Direct Response
E:AShore@xxxxxxxx
P:(631) 200-5019
C:(631) 880-8640
"If you're going through Hell, keep going" - Winston Churchill


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of McGovern, Sean
Sent: Thursday, March 15, 2012 10:59 AM
To: Midrange Systems Technical Discussion
Subject: RE: Creating an SQL UDF on a procedure

Union with fixed -1 value ?

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Alan Shore
Sent: 15 March 2012 14:58
To: Midrange Systems Technical Discussion
Subject: RE: Creating an SQL UDF on a procedure

Hi Chris
Nice idea but how do we send -1 down when using this function within a view, or sql?

Alan Shore
Programmer/Analyst, Direct Response
E:AShore@xxxxxxxx
P:(631) 200-5019
C:(631) 880-8640
"If you're going through Hell, keep going" - Winston Churchill


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Chris Bipes
Sent: Thursday, March 15, 2012 10:56 AM
To: 'midrange-l@xxxxxxxxxxxx'
Subject: RE: Creating an SQL UDF on a procedure

Instead of a second parameter, could a special order number, say -1 trigger the close?

--
Chris Bipes
Director of Information Services
CrossCheck, Inc.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Alan Shore
Sent: Thursday, March 15, 2012 7:53 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Creating an SQL UDF on a procedure

Hi everyone
We have a procedure that leaves the files open until the procedure is called one final time with an extra parameter to close the files For example, within an RPG program

Ordertype = getOrderType(Ordernumber);
And then at the end of the RPG program

Ordertype = getOrderType(Ordernumber: Closefiles);

We now need to create a function on this procedure. I don't have a problem creating the function. My concern is that the "final" call - namely Ordertype = getOrderType(Ordernumber: Closefiles); - will NOT be done (or is there a way to do it).
My questions to the panel are - is this a cause for concern?
Will this be a problem at some time?

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.


Disclaimer: This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. Any views or opinions presented are solely those of the author and do not necessarily represent those of the company.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.


This thread ...

Follow-Ups:
Replies:

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

This mailing list archive is Copyright 1997-2019 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].