MFE SCF: SCF1389I MSC GROUP HAS BECOME INCONSISTENT

Issue:
Mainframe Enablers (MFE) Informational Message: 

SCF1389I MSC - GROUP=Groupname (ccuu,aa) HAS BECOME INCONSISTENT

Explanation:
Informational Message SCF1389I occurs if internal (outside of z/OS) write I/O is performed to a SRDF/A R1 device:

Background internal copy tasks that involve SNAP operations that use the SNAP API or FLASHCOPY API drive I/O outside of SRDF/A processing. Third party software products that use SNAP or FLASHCOPY API, can also cause the SCF1389I message.

Examples of Third Party Products

- Innovation's FDR product suite 
- IBM IMS High Performance Image Copy
- IBM z/OS ADRDSSU

Mainframe Enablers Host Component Multi Session Consistency (MSC) reports global inconsistency when internal background copy tasks are performed to a R1 device. SRDF/A MSC guarantees the order that host writes go into a SRDF/A cycle. When an internal copy takes place to an SRDF/A R1 device, there is no guarantee that there is serialization of writes with this type of copy. MSC has to notify the user of this inconsistent state. 

Action:
These messages can be avoided by using a SNAP or FLASHCOPY target other than an SRDF/A R1 device. If this type of activity is necessary, global inconsistency messages should be considered normal.

Per the MFE TimeFinder/Clone mainframe Snap Facility for z/OS v8.0 and later Guide, parameters must be reviewed when using an SRDF/A R1 device as a snap target.

SRDFA_R1_TARGET

The IBM z/OS VnRn DFSMS Advanced Copy Services Guide has a section discussing FlashCopy.

Summary
In summary, when MSC reports Global Inconsistency, there exists an inconsistency in replicated data. Global Inconsistency = N is also set when MSC is first activated and remains until initial consistency is achieved. 

Disaster Recovery Impact
After receiving the message:

SCF1389I MSC - GROUP=Groupname (ccuu,aa) HAS BECOME INCONSISTENT

There is no guarantee of consistency on the R2 devices until this message is issued:

SCF1523I MSC - GROUP=Groupname GLOBAL CONSISTENCY HAS BEEN ACHIEVED.

If a disaster recovery event or test occurs during the time of this inconsistency, the R1 devices and their individual datasets must be identified. (Only the targets of the SNAP or COPY operations that are also R1 devices must be identified.) The owners of the data effected on the R1 devices and the datasets must handle the recovery of that data.

List of SNAP or COPY operations
- EMCSNAP (SNAP) operations 
- use of the SNAP API or the FLASHCOPY API  by third party products 
    - the FDR product suite
    - IBM ADRDSSU
    - IMS High Performance (HP) Image Copy 

//FLASHQY EXEC PGM=IKJEFT01,DYNAMNBR=16 
//SYSTSPRT DD SYSOUT=*                  
//SYSPRINT DD SYSOUT=*                  
//SYSTSIN DD *                          
 FCQUERY DEVN(X'ccuu') SHOWRELS(ALL)    
/*