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

That request type [kwd: OT90 or RqsTyp90 ] deals with constraint activity, which that PTF mentions, but with respect to MQT.
FWiW: If MQTs and constraints are not referenced by the job running for or after which the errors were manifest, then collecting and maintain output from DMPSYSOBJ QDBXREFQ* QSYS 0A C4 and DSPLOG QHST ((*AVAIL *BEGIN)) OUTPUT(*PRTSECLVL) /* or since a few days before the first incident, since any prior reclaim of the *DBXREF */ in advance of the Recovery action from the message, will leave some log information from that incident. At least that information [and joblogs for jobs that logged messages in QHST that implied some error condition for database activity] will invariably be requested for support to even begin to investigate the errors.

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

David Gibbs wrote:

Elvis Budimlic wrote:

Number of reasons, some due to OS issues, some due to abnormal IPL, other
reasons too (i.e. sometimes due to premature kill of index rebuild).

Thanks ... I should have check the APAR database first. :)

I don't think we ever had a abnormal IPL or killed index rebuild ... but
who knows.

I've grabbed PTF SI27050 and applied it ... we'll see if the problem
crops up again.

david