On 13-Mar-2014 07:10 -0700, Mark Murphy wrote:
The CPF6968 is the message causing the SQL0901 I can not currently
replicate this error with existing views, so I cannot tell if it is
the same context, but with the view in question, here is the context
info:
FWiW: The most complete contextual information [outside of the SQL
request itself per the CREATE VIEW statement not being a CL
command-request; i.e. not being a request-message] is available from the
spooled output either from a DSPJOBLOG OUTPUT(*PRINT) taken with the
specified JOB() having LOG(4 0 *SECLVL) in effect, or from the
combination of F1=Help plus F6=Print on the successive messages since
the failing request. The implication being, that a Copy\Paste of [only
the user-selected] message details from anything other than the spooled
output is likely to be missing potentially worthwhile information.
This is first level text in job log:
Journal entry cannot be associated with file WBOODV100.
Function check. CPF6968 unmonitored by QDBCRTME at statement *N,
instruction X'05CB'.
SQL system error.
The above suggests that the DSPJOBLOG output would have shown, in
symptom kwd form, the following:
msgCPF6968 F/QJOSNDJE T/QDBCRTME x/05CB
msgCPF9999 F/QMHUNMSG T/QDBCRTME x/05CB
msgSQL0901 F/QSQCRTV
Note: The spooled Display Job Log output would have shown the
second-level text which may include more\important details such as
return codes which can not be similarly inferred so generally as can be
attempted [or done] with the symptom strings.
<<Display Message Details pared down; text was not included>>
Message ID: CPF6968
From program: QJOSNDJE
To program: QDBCRTME
Message ID: CPF9999
Message type: Escape
From program: QMHUNMSG
To program: QSQCRTV
To module: QSQCRTV
To procedure: QSQCRTV
To statement: 11527
Message ID: SQL0901
However the copy\paste of the displayed F1=Help + F9=Details
information indicates something slightly different:
msgCPF6968 F/QJOSNDJE x/06F9 T/QDBCRTME x/05CB
msgCPF9999 F/QMHUNMSG T/QSQCRTV TM/QSQCRTV TP/QSQCRTV stmt/11527
msgSQL0901 F/QSQCRTV presumably: rcCPF9999 and et58004 aka rc58004
Note: The spooled information from F1=Help + F6=Print would have
provided the full text, including any replacement variables which would
include at a minimum, any return codes. The given copy\paste of the
message details from just above is a clear mismatch with the copy\paste
of the active job message queue [that shows first level text only] given
further above; a spooled joblog combine everything in sequence, so is
ideal to portray the effects over just about any other means.
Regardless that information is missing, clearly there is a *defect*
that should be reported to the service provider; most likely, for the
lack of a monitor for the CPF6968 in the program QDBCRTME, for which the
*FC is manifest instead of a proper percolation of an acknowledged
condition back to the SQL as invoker. Thus, the defect will [whether
directly or indirectly] have to be addressed by IBM via a PMR. Still,
it would be nice to see the full text of at least the CPF6968 appearing
somewhere in this message thread.
Another comment included later, inline to the older quoted messages:
CRPence on 03/12/2014 03:06PM wrote:
On 3/12/2014 1:39 PM, Mark Murphy/STAR BASE Consulting Inc. wrote:
Let's get this out of the way first, V7.1 TR
I am having trouble creating a specific view. The error is CPF6968
Journal entry cannot be associated with file WBOODV100.
Please provide the full context of the message, beyond just the
failing SQL request; i.e. the DSPJOBLOG OUTPUT(*PRINT) version [best
with LOG(4 0 *SECLVL) active for the job], or the F6=Print version taken
from F1=Help on the message viewed in an [inter]active joblog.
<<SNIP>> Being a -901, there are instructions about where more
information for that generic SQL failure is tracked\logged;
probably a TechNote, and include the follow search kwd to narrow
the topics: QRECOVERY
The term "SQL0901 Logger" is used to describe the feature alluded
above. The qualified file name QRECOVERY/QSQ901S or instead QSQ901S in
QRECOVERY is included here as reference; the library name may be
QRCY##### for the iASP per "QRCYnnnnn/QSQ901S *FILE, where nnnnn is the
iASP number". Some column names of the file: SERVERNAME FAILTIME
FAILRSN CURUSER JOBNAME STMTTEXT VRM DBGROUP MSGS. Some documentation
can be found in the "IBM i 7.1 Technical Overview with Technology
Refresh Updates", IBM Redbook Form Number: SG24-7858-02 Publication
Date: 20-Mar-2013, from a download link here:
<
http://ip.com/redbook/SG24785802>
<<SNIP>>
midrange.com
