SQL0952 unmonitored by QMHPDEH

[tdavis]

I have a number of stored procedures that have been running for years, and now all of a sudden some of them go into MSGW with the following error. I thought it was an IBM issue; that is, a PTF would be required. So I tried to get some help from our hardware team, who contacted IBM, who came back and said (after looking at some of our job logs) we needed to stop using data areas in those stored procedure programs (all of ours are associated to RPG programs). I didn't believe it but made some program changes as requested, but that did not fix the problem. The error message always refers to a WRITE or an UPDATE to a physical or logical file.

Has anyone else seen of this error before?


Processing of the SQL statement ended. Reason code 1.
Function check. SQL0952 unmonitored by QMHPDEH at statement *N,
instruction X'0001'.
Failure for device or member IS1042FLOG file IS1042FLOG in library
SANCMEXTF.
I/O error CPF5257 was detected in file IS1042FLOG.
Function check. RNX1299 unmonitored by IS1042RLOG at statement 0000018200,
instruction X'0000'.
I/O error CPF5257 was detected in file IS1042FLOG (C G D F).


Message ID . . . . . . : SQL0952 Severity . . . . . . . : 30
Message type . . . . . : Escape
Date sent . . . . . . : 11/29/21 Time sent . . . . . . : 12:02:04

Message . . . . : Processing of the SQL statement ended. Reason code 1.
Cause . . . . . : The SQL operation was ended before normal completion. The
reason code is 1. Reason codes and their meanings are:
1 -- An SQLCancel API request has been processed, for example from ODBC.

[Vectorspace]

The job log shows error CPF5257. Having googled it, the only references I can find to it relate to hardware/system errors that required the attention of IBM themselves.
If IBM said stop using data areas, and now you aren't but you are still getting the error, I would suggest you trey IBM again

[tdavis]

I agree that IBM needs to be engaged, but I was hoping to find someone who may have seen this before and share what the resolution ultimately was.