Failed mount due to selected MC criteria should not require looking up diagnostic codes

Note that this is tied to TS003826059 but the PMR field doesn't accept that value. Not sure where I need to go to submit an RFE for the RFE site to accept a case number rather than a PMR number:)

We had a VTS MC specification that did not have the 'Synchronous Deferred On Write Failure.' option selected. This was not intentional on our part and caused failures when the sync partner was put into service. The messages that came out required digging into obscure error return and reason codes messages and the specific reason code was not even documented.

Here's an example of one that we received:
CBR4195I LACS RETRY POSSIBLE FOR JOB H2KTOAA1: 863
IEE763I NAME= CBRLLACS CODE= 140394
CBR4000I LACS WAIT PERMANENT ERROR FOR DRIVE CB14.
CBR4171I MOUNT FAILED. LVOL=86I026, LIB=TCVTS95C, PVOL=??????, RSN=27.

Since this is a valid condition when a cluster is out of service we would expect a message that gives more immediate information to an end business partner. Perhaps something to the effect of 'VTS MC xxxxxxxx specifies enforcement of synchronous mode and partner cluster is unavailable'. This would have immediately pointed us to the MC in question and directly tied the message to the fact that the cluster was temporarily out of service. While we don't have the immediate business need to require synchronous mode we would expect that kind of message to be issued in these situations so our business partners would understand why their jobs are not working.