Nice idea but how do we send -1 down when using this function within a view, or sql?
Programmer/Analyst, Direct Response
"If you're going through Hell, keep going" - Winston Churchill
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Chris Bipes
Sent: Thursday, March 15, 2012 10:56 AM
Subject: RE: Creating an SQL UDF on a procedure
Instead of a second parameter, could a special order number, say -1 trigger the close?
Director of Information Services
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Alan Shore
Sent: Thursday, March 15, 2012 7:53 AM
Subject: Creating an SQL UDF on a procedure
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,
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.