Darren,
Issue a DSPJOB, then option 14. Display open files. Then, notice what activation group the file is opened in.
If it is in the *DFTACTGRP, you can issue the RCLRSC command and that should close it.
If it is in another activation group, you can try using the RCLACTGRP command.
Or, you could issue the RRTJOB command to start a new routing step -- that should close all open files, and clean up all activation groups, so that your job will appear as it did when you first signed-on.
Or, you can always just sign-off and sign-on again.
Hope that helps,
Mark S. Waterbury
On Tuesday, May 7, 2019, 11:46:33 AM EDT, Darren Strong <darren@xxxxxxxxx> wrote:
That works in STRSQL where I was testing. As I moved into a UDTF, I found that COMMIT is not permitted within a UDTF. Any alternative?
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of dlclark@xxxxxxxxxxxxxxxx
Sent: Tuesday, May 7, 2019 11:23 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: close result set from stored procedure
"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> wrote on 05/07/2019
11:19:41 AM:
I've called a stored procedure, such as below from the STRSQL
interface. If I call again, I get an error saying that a file in
QTEMP cannot be cleared because its in use. Is there an SQL command
to deallocate or close a result set to indicate back to the stored
procedure that I'm done with the result set, if I didn't use a HLL to
read the cursor?
COMMIT without HOLD closes all cursors in the activation group.
Sincerely,
Dave Clark
--
int.ext: 91078
direct: (937) 531-6378
home: (937) 751-3300
Winsupply Group Services
3110 Kettering Boulevard
Dayton, Ohio 45439 USA
(937) 294-5331
*********************************************************************************************
This email message and any attachments is for use only by the named
addressee(s) and may contain confidential, privileged and/or proprietary information. If you have received this message in error, please immediately notify the sender and delete and destroy the message and all copies. All unauthorized direct or indirect use or disclosure of this message is strictly prohibited. No right to confidentiality or privilege is waived or lost by any error in transmission.
*********************************************************************************************
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
https://amazon.midrange.com
midrange.com
