Re: What caused this: CPF32A6 - Cross-reference notification 1131 for request 90, problem type 1.

That message [in the replied to post, not the original post & subject] is informational as it implies. The noted condition indicates that some SQL Long File Name activity had transpired during an IPL. Since the database cross-reference featured alluded to in the message text is not available during an IPL, one could safely infer that the condition of being unable to process some long names would be normal. That gives rise to another question: What code is performing what activity against a long named file in that library during an IPL? A review of the QPJOBLOG [and for any other spools for the job seen with DSPSPLFA for that SPLF; find the jobnbr used, then WRKJOB jobnbr/QSYS/SCPF OPTION(*SPLF)] for the time of the message can be done by 5=Display on the spool file in WRKSPLF (QSYS *N *N SCPF).

Kwds: WDBX_Free msgCPI32A6 ntfy10 rqstyp303 OT303 rc2 lib QUSRDIRDB

Regards, Chuck
-- All comments provided "as is" with no warranties of any kind whatsoever and may not represent positions, strategies, nor views of my employer

Guy Terry wrote:

Seeing this jogged my memory - we get several of these during IPL:

CPI32A6 - Cross-reference notification 10 for request 303, type 2
Message . : Cross-reference notification 10 for request 303, type 2.
Cause . . : An unexpected condition was detected while processing
the system cross-reference files. This message does not indicate the
existence of a problem, but may be valuable to IBM developers if a cross-reference problem occurs at a future time. The Unexpected condition type is 2.
The condition types and their meanings follow:
0 -- Context recovery
1 -- Inconsistent data was discovered in the cross-reference files for
library QUSRDIRDB.
2 -- The server recovered from an unexpected error.
3 -- Exit condition.
Recovery . . . : No recovery is required.

Is it really nothing to worry about?