Sandro,
In z/OS V1R8 (HBB7730), XCF introduced an optional interface that can
be exploited by components that own couple data sets (CDSes) to address
exactly this problem. When an alternate CDS is rejected because it wasn't
formatted for at least the same capacity as the existing primary CDS, XCF
calls an exit supplied by the CDS owner to allow the owning component to
report the differences between the primary and alternate in terms of the
attributes used to format the two CDSes. When the component supports this
exit, the format information is reported in message IXC255I with the header
RELEVANT typename COUPLE DATA SET FORMAT INFORMATION
All CDS types except WLM and sysplex have implemented support for this
interface. (The sysplex CDS doesn't use it because there is a very obvious
correlation between the record names that appear in IXC255I and the CDS
format keywords.) I suggest that you open a PMR or a marketing requirement
to request that WLM support the consistency failure interpretation
function-level exit for its CDS.
Without this support, the only way to determine the differences between
the in-use primary CDS and the rejected alternate CDS is to dump the
contents of both CDSes using the ADRDSSU utility, open a PMR, and submit the
results to IBM Level 2 for analysis.
Bill Neiman
IBM Parallel Sysplex development
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
