OA26876: IEA494I WITH 'EXTENDED LONG BUSY' TAG LINE IS MISLEADING

APAR status

• Closed as fixed if next.

Error description

• A suspend (either via TSO CSUSPEND or via GDPS) of a PPRC device
  pair is causing
  IEA494I 0228,XE0228,PPRC PAIR SUSPENDED,SSID=0200,CCA=28,
          EXTENDED LONG BUSY STATE
  although the device isn't indicating an extended long busy
  ( ELB ) condition.
  
  The 'extended long busy' tag line is related to SSCBCGRP
  setting.
  ELB will be added to IEA494I if the SSSCB -> SSCBCGRP is ON when
  a PPRC volume pair is suspended by a host command.
  
  Note: The PPRC path (i.e. via CESTPATH or GDPS) was established
        vith CGROUP=YES (CQUERY volume report indicates
        CGRPLB(YES) ).
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: D/T2105 D/T1750 D/T3390 D/T2107 users of     *
  *                 PPRC.                                        *
  ****************************************************************
  * PROBLEM DESCRIPTION: Text "EXTENDED LONG BUSY STATE" was     *
  *                      added to message IEA494I anytime a PPRC *
  *                      pair suspended and the relationship was *
  *                      established with consistency grouping.  *
  *                      This was true even when a Suspend       *
  *                      command was issued by the host.  In     *
  *                      this case, the device is not in a long  *
  *                      busy condition even though the message  *
  *                      implies that it is.                     *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The text "EXTENDED LONG BUSY STATE" will only be appended to
  message IEA494I if the device signals that it is in a State
  Change Pending state at the same time that it indicates the pair
  is suspended.  Thus, a Suspend command issued from the host will
  not cause this text to appear.
  

Problem conclusion

Temporary fix

Comments

• CONTROL NUMBER: K1B0675
  This APAR is being closed as FIN with the concurrence of the
  submitting customer. A solution to this problem will be
  delivered in a future DFSMS release, if there is one, within
  the next 18 to 24 months.
  
  This problem is fixed in z/OS DFSMS V1R11
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

• RA10 PSN

     UP