Thanks for your reply Rob
Item 1 of 2: Give myself a dope slap - never thought of a stored procedure (the noise you hear in the background is me slapping myself)
Item 2 of 2: Quote " For example, if you call that function from the web, and the job that connects and gets that data is over, aren't the files then closed?" end quote
That's what I was thinking, but then I started questioning myself, and then I wasn't too sure. Always nice to get confirmation.
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 rob@xxxxxxxxx
Sent: Thursday, March 15, 2012 11:20 AM
To: Midrange Systems Technical Discussion
Subject: RE: Creating an SQL UDF on a procedure
Item 1 of 2: Instead of calling the function, could they call a stored procedure instead?
Item 2 of 2: Is the sql called from 5250, web, C/S, etc? Basically I am asking just how persistent is the open anyway? For example, if you call that function from the web, and the job that connects and gets that data is over, aren't the files then closed?
Rob Berendt
--
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From: Alan Shore <ashore@xxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>,
Date: 03/15/2012 11:04 AM
Subject: RE: Creating an SQL UDF on a procedure
Sent by: midrange-l-bounces@xxxxxxxxxxxx
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.
midrange.com
