RE: Creating an SQL UDF on a procedure

Alan,

Will holding a lock (file and maybe record) cause a problem? Is the program buffering any file data that could be held until file close? The file does get closed at job end.

Paul Morgan

Principal Programmer Analyst
IT Supply Chain/Replenishment

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Alan Shore
Sent: Thursday, March 15, 2012 10: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?



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


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.