Re: CPF5009 , CPF5026, SQL9015 , MCH3601, MCH0601

On 08-May-2014 14:54 -0500, Steinmetz, Paul wrote:

Our one 3rd party RELUPDATE job is throwing the following errors.
We ran the process 4 times, the last time the MCH3601, MCH0601
disappeared, the other 3 errors remain?
No PTFs were applied, nor IPL.
Any thoughts from the group.

<ed> reformatted given joblog data as symptom kwd strings: </ed>
msgCPF5009 Diag 10
F/QDBSIGEX x/0EBB
T/QSQPROCR TM/QSQPROCR TP/PUT_SYSROUTINES_RCD stmt/11602
"Duplicate record key in member SYSRO00001."
msgCPF5026 SndCpy 30
F/QDBSIGEX x/0252
T/QDBSIGEX x/0252
"Duplicate key not allowed for member SYSRO00001."
msgCPF5026 Notify 30
F/QDBSIGEX x/0252
T/QSQPROCR TM/QSQPROCR TP/PUT_SYSROUTINES_RCD stmt/11602
"Duplicate key not allowed for member SYSRO00001.
msgSQL9015 Info 30
F/QSQPROCR FM/QSQPROCR FP/SENDMSGD stmt/24137
T/QLICRDUP x/0522
"<ed> Program or service program &1 restored [¿or duplicated;
per CRTDUPOBJ implied by QLICRDUP?] but not </ed> created as
SQL object PNL00473 in UPIC08XXP."
msgMCH3601 Escape 40
F/#rmsacs x/001F58
T/QSQPROCR TM/QSQPROCR TP/PREPARE_SYSROUTINES_RCD stmt/16636
"Pointer not set for location referenced."
msgMCH0601 Escape 40 < gHighUse4K
F/stringHighUse4K x/000328
T/QSQPROCR TM/QSQPROCR TP/PREPARE_SYSROUTINES_RCD stmt/17411
"Space offset X'00000000' or X'0000000000600000' is outside
<ed> missing data; i.e. not provided </ed>

The database and SQL messaging are fairly normal; i.e. simply logging that the SQL already had the routine [the PROCEDURE] tracked to the SQL Catalog TABLE SYSROUTINE [aka SYSROUTINES]. Some additional work apparently had some difficulties, but the effect of the errors is not conspicuous without knowing if the data in the catalog is accurate [or knowing what the PREPARE_... code intended to effect or even how far that work progressed. Those difficulties were /machine exceptions/ rather than messaging from the OS features, indicating the errors are within the OS code itself.

There is an APAR and its PTF possibly preventive to what appears to be a near match for the symptoms [for restore, but should apply equally to Create Duplicate Object]; the recorded-as failing procedure is different: PREPARE_SYSROUTINES_RCX, though there is a conspicuous typo so...?.? That error apparently originates from prior release data stored Program Associated Space (PAS) SQL information not being recognized or otherwise processed improperly by the IBM i 7.1 for the SQL routine tracking. Thus reasons the error could have disappeared would be having invoked or recompiled the routine since the error that was diagnosed when the object was being duplicated; i.e. the PAS would have been updated.

<http://www.ibm.com/support/docview.wss?uid=nas39bc5e9cfe17d566e862577ee005268ca>
SI41617 - OSP-DB-OTHER-F/QSQPROCR-T/QSQPROCR-MSGMCH3601
"... CORRECTION FOR APAR SE45470 ..."