8464ch11_Monitoring.fm Draft Document for Review February 7, 2020 3:15 pm The reasons why a volume moves to the immediate-deferred state are included in the Error  Recovery Action (ERA) 35 sense data. The codes are divided into unexpected and expected  reasons. From a z/OS host view, the ERA is part of message  IOS000I  (see Example 11-24). Example 11-24 Message IOS000I IOS000I 1029,F3,EQC,0F,0E00,,**,489746,HADRMMBK 745 .50408035000000206011(B3100001 1C 005800)2182(50000FFF)CE1F0720EED40900 IMMEDIATE MODE COPY - EXPECTED FAILURE - REASON CODE = 82 COPY COUNT - 1 OF 2 COMPLETED SUCCESSFULLY The following new failure content is introduced into the CCW(RUN) ERA35 sense data: GLYPH<SM590000> Byte 14 FSM Error. If set to 0x1C (Immediate Copy Failure), the extra new fields are  populated. GLYPH<SM590000> Byte 18 Bits 0:3. Copies Expected: Indicates how many RUN copies were expected for  this volume. GLYPH<SM590000> Byte 18 Bits 4:7. Copies Completed: Indicates how many RUN copies were verified as  successful before surfacing Sense Status Information (SNS).  GLYPH<SM590000> Byte 19. Immediate Copy Reason Code: – Unexpected - 0x00 to 0x7F: The reasons are based on unexpected failures: GLYPH<129> 0x01: A valid source to copy was unavailable. GLYPH<129> 0x02: Cluster that is targeted for a RUN  copy is not available (unexpected outage). GLYPH<129> 0x03: A total of 40 minutes have elapsed and one or more copies have timed out. GLYPH<129> 0x04: Is reverted to immediate-deferred  because of health/state of RUN target  clusters. GLYPH<129> 0x05: Reason is unknown. – Expected - 0x80 to 0xFF: The reasons are based on the configuration or a result of  planned outages: GLYPH<129> 0x80: One or more RUN target clusters are out of physical scratch cache. GLYPH<129> 0x81: One or more RUN target clusters are low on available cache (95%+ full). GLYPH<129> 0x82: One or more RUN target clusters are in service-prep or service. GLYPH<129> 0x83: One or more clusters have copies  that are explicitly disabled through the  Library Request operation. GLYPH<129> 0x84: The volume cannot be reconcile d and is “Hot” against peer clusters. The extra data that is contained within the CCW(RUN) ERA35 sense data can be used within  a z/OS custom user exit to act on a job moving to the immediate-deferred state.  Because the requesting application that results in the mount received successful status  before sending the CCW(RUN) command, it cannot act on the failed status. However, future  jobs can be suspended or other custom operator actions can be taken by using the  information that is provided within the sense data. For each volume that cannot be replicated in the immed-Deferred mode, an IOS000I  message can be reported in the system log. Although that message allows a message  automation on the host to detect possible problems, the thousands of messages that are  generated might overflow the host log. This issue is especially true in maintenance situations.  Chapter 11. Monitoring  697 Handling of the Immed-Deferred related messages