IBM DB group reviewing this issue.
They had me create these objects, as a test.
CRTLIB QSPL0002.
Object QASPLINFO in QSPL0002 type *FILE created.
Object QASPOUTQ in QSPL0002 type *FILE created.
SQL now works by creating these objects.
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of CRPence
Sent: Wednesday, July 05, 2017 3:04 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Spool file SQL failing on R&D LPAR
On 05-Jul-2017 09:41 -0600, Steinmetz, Paul wrote:
[...] Based on the message/recovery actions-reason code 01 -
Should I create QSPL0002/QASPOUTQ?
Recovery . . . : Do one of the following based on the reason code
shown, and try the request again:
01 - Change the library name with an appropriate override file
command, or create [...] a file with the appropriate name.
I am confident the effect for the existence of the file is something that the UDTF or the system Spool (SP) component/feature should have [in]directly accomplished; i.e. the system code should have done something, such that there was no cause for an Open request of that file to fail, be that due to having previously created the file, or due to having ignored the lack the presence of that file.
A SWAG, that if there were no spool files on [an Output Queue (OUTQ)] on ASP2, then perhaps the file might, nor or even possibly should not, exist; i.e. perhaps the UDTF could be improperly coded for lack of ability to ignore the lack of the file.? Thus, as a potential circumvention, create an output queue (CRTOUTQ) in a library [if that is the type of ASP supporting that action] assigned per Create Library
(CRTLIB) with ASP(2), and then create a spooled file that resides on that output queue -- perhaps immediately after, check for the existence of that file, and again after the UDTF is invoked again.
Note: I previously referred to the QSPL0002 being indicative of an Independent ASP (iASP), but that naming [i.e. QSPL00## as name, with the ## representing the two-digit numbers between 02 and 32, inclusive,] is probably for the traditional User ASP ASP02.
--
Regards, Chuck
--
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.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
http://amzn.to/2dEadiD
midrange.com
