Finally broke down and created a PMR.
According to IBM: SI48523, which appears to have been super-ceded by SI48905, is the fix to events where SQL0952 errors are followed by the CPF9999 message.
Steve Needles
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Needles,Stephen J
Sent: Thursday, January 17, 2013 10:23 AM
To: midrange-l@xxxxxxxxxxxx
Subject: CPF9898 SQL CANCEL SIGNALLED BY JOB:...
I'm receiving a CPF9898 error with the text: "SQL CANCEL SIGNALLED BY JOB: 123456/QUSER/QRWTSRVR"
According to the joblog, the msg is sent by...
From user . . . . . . . . . : WWWCAC
From module . . . . . . . . : QSQEVENT
From procedure . . . . . . : CANCEL
Statement . . . . . . . . . : 6341
To module . . . . . . . . . : QSQEVENT
To procedure . . . . . . . : CANCEL
Statement . . . . . . . . . : 6341
It is followed by an SQL 0952 error
From user . . . . . . . . . : WWWCAC
From module . . . . . . . . : QSQEVENT
From procedure . . . . . . : CANCEL
Statement . . . . . . . . . : 6364
Message . . . . : Processing of the SQL statement ended. Reason code 1.
Reason codes and their meanings are: 1 -- An SQLCancel API request has been processed, for example from ODBC.
This is followed by a CPF9999:
From user . . . . . . . . . : USER
Message . . . . : Function check. SQL0952 unmonitored by QDBGETSQ at
statement *N, instruction X'0D2D'.
Cause . . . . . : An escape exception message was sent to a program which
did not monitor for that message. The full name of the program to which the
unmonitored message was sent is QDBGETSQ . At the time the message was sent
the program was stopped at higher level language statement number(s) *N. If
more than one statement number is shown, the program was a bound program.
Optimization does not allow a single statement number to be determined. If
*N is shown as a value, it means the actual value was not available.
Recovery . . . : See the low level messages previously listed to locate
the cause of the function check. Correct any errors, and then try the
request again.
And finally...the coup de grace...a CPF5257 error...
From user . . . . . . . . . : USER
To module . . . . . . . . . : HOMEGROWNPROGRAM
To procedure . . . . . . . : HOMEGROWNPROGRAM
Statement . . . . . . . . . : 533000
Message . . . . : Failure for device or member FILE01 file FILE01 in library
LIBRARY.
Cause . . . . . : An error occurred during a read or write operation. If
this is a display file, the display may not be usable. Recovery . . . :
See the previously listed messages, correct the errors, and try the request
again. If the problem continues, report the problem (ANZPRB command).
Anyone run into this scenario?
BTW...V7R1, current on latest CUME.
Steve Needles
==============================================================================
This communication, including attachments, is confidential, may be subject to legal privileges, and is intended for the sole use of the addressee. Any use, duplication, disclosure or dissemination of this communication, other than by the addressee, is prohibited. If you have received this communication in error, please notify the sender immediately and delete or destroy this communication and all copies.
midrange.com
