OA28047: SMF CANNOT CONNECT TO ITS DASDONLY LOGSTREAM AFTER LOGGER'S REQUEST TO RECALL ITS STAGING DATASET FAILED

A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Customer started SMF initiating a connect request to the
    SMF logstream.  The staging dataset for the logstream had
    been migrated, and Logger attempted to recall the staging
    dataset for recovery.  Because HSM was not active, WTOR
    ARC0055A was issued. Operations replied CANCEL to the
    message, and the staging dataset recall failed.  Logger
    then proceeded to fail the recovery for the SMF logstream
    and turned off the indicator to re-drive the recovery on
    a subsequent connect.  This resulted in the loss of
    data contained in the migrated staging dataset.
    .
    Logger should mark the logstream for recovery on subsequent
    connection attempts.
    .
    Verification:
    Observe ARC0055A after starting SMF -
      2009047 01:14:19.84
       *65 ARC0055A REPLY 'GO' OR 'CANCEL'
    .
    Note the reply of CANCEL to the message -
      2009047 01:15:49.56
        R 65,CANCEL
    .
    The staging dataset recall fails with rc64 rsn4 -
      2009047 01:15:49.57
       IXG260I ARCHRCAL FAILED FOR
       SOFTSPV.IFASMF.IPRO.RACF.WDPCPLX1.
       RC=00000064 RSN=00000004
    .
    Logger fails the recovery for the SMF logstream -
      2009047 01:15:49.57
       IXG210E RECOVERY FOR LOGSTREAM IFASMF.IPRO.RACF
       IN STRUCTURE *NOT APPLICABLE* WAS NOT SUCCESSFUL.
       DATA MAY BE LOST FOR THE CONNECTION ON SYSTEM IPRO
       DUE TO:
       ERRORS ENCOUNTERED DURING STAGING DATASET PROCESSING.
    .
    The connect to the logstream gets back rc8 rsn812 -
      2009047 01:15:49.65
       IFA707I SMF CANNOT CONNECT TO LOGSTREAM
       IFASMF.IPRO.RACF REASON=DATA LOSS, 08-0812
      2009047 01:15:49.65
       IXG231I IXGCONN REQUEST=CONNECT TO LOG STREAM
       IFASMF.IPRO.RACF DID NOT SUCCEED FOR JOB SMF.
       RETURN CODE: 00000008  REASON CODE: 00000812
    .
    Subsequent attempts to connect to the logstream gets
    back rc4 rsn407 -
      2009047 01:33:48.52
       IFA707I SMF CANNOT CONNECT TO LOGSTREAM
       IFASMF.IPRO.RACF REASON=DATA LOSS, 04-0407
    .
    May also observe IXG251I if the migrated dataset was
    removed from the Catalog:
    .
    IXG251I NOT DEFINED BECAUSE DUPLICATE NAME EXISTS IN CATALOG
    .
    Additional keywords:
     IXGRSNCODELOGSTREAMRECOVERYFAILED 812 407
     00000812 00000407 3A5414
     SMFLGS/K
    

Local fix

  • Bring up HSM and allow HSM to recall the staging dataset.  Do
    not reply CANCEL to ARC0055A.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of HBB7730 and above supported         *
    *                 releases using System Logger Services        *
    *                 using DASD-only logstreams.                  *
    ****************************************************************
    * PROBLEM DESCRIPTION: An application attempts to connect to   *
    *                      a DASD-only log stream which had a      *
    *                      failed persistent connection.           *
    *                                                              *
    *                      During connect processing, System       *
    *                      Logger encounters a problem with the    *
    *                      existing staging data set.  System      *
    *                      Logger incorrectly deletes the          *
    *                      existing staging data set (from the     *
    *                      prior connection to this attempt)       *
    *                      which cause the log stream to be        *
    *                      damaged due to a possible loss of       *
    *                      data.                                   *
    *                                                              *
    *                      System Logger fails the connect attempt *
    *                      and issues msgIXG231I indicating the    *
    *                      connect failed with RC8 RSN812          *
    *                      (IxgRsnCodeLogStreamRecoveryFailed).    *
    ****************************************************************
    * RECOMMENDATION: Install the PTFs.                            *
    ****************************************************************
    An application attempts to connect to a DASD-only log stream
    which had a failed persistent connection.
    
    During connect processing, System Logger encounters a problem
    with the log streams existing staging data set.  System Logger
    issues msgIXG210E indicating that recovery failed for the log
    stream due to:
     ERRORS ENCOUNTERED DURING STAGING DATASET PROCESSING.
    
    System Logger then fails the connect attempt and issues
    msgIXG231I indicating the connect failed with RC8 RSN812
    (IxgRsnCodeLogStreamRecoveryFailed). During the breakdown of
    this connect attempt, Logger attempts to leave the log stream
    in a failed persistant state. This would allow for further
    recovery attempts; however, Logger erroneously deletes the
    staging data set.
    
    On the next connect attempt (for this log stream), Logger will
    attempt to allocate the existing staging data set shared (to
    recover the data) because it has been deleted, Logger will mark
    the log stream damaged due to a possible loss of data. Logger
    will allow the connect request and will allocate a new staging
    data set instance. The connect request will return a warning
    (RC4 RSN407). Some applications (such as SMF) may not tolerate
    using damaged log streams.
    
    Additional keywords: SMFLGS/K
    

Problem conclusion

  • During DASD-only recovery processing, if System Logger fails
    the connect attempt because it cannot recovery from the
    staging data set, the staging data set will not be deleted.
    
    Recovery will again be attempted on the next log stream
    connect request.
    
    Note that this PTF does not repair existing occurences of
    this defect. It is only a preventitive PTF.
    
    This fix may be applied to one system at a time in the sysplex.
    
    Systems with and without the fix activated can coexist in the
    same sysplex, although the problem may persist on those systems
    running without the fix.
    
     Additional Searchable keywords:
      LOGRSERVICE
      SYSPLEXDS
      SMFLGS/K
    

Temporary fix

  • *********
    * HIPER *
    *********
    

Comments

APAR Information

  • APAR number

    OA28047

  • Reported component name

    SYSTEM LOGGER

  • Reported component ID

    5752SCLOG

  • Reported release

    740

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-02-20

  • Closed date

    2009-02-26

  • Last modified date

    2010-10-26

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

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

    UA46120 UA46121 UA46122

Modules/Macros

  •    IXGC4LBR
    

Fix information

  • Fixed component name

    SYSTEM LOGGER

  • Fixed component ID

    5752SCLOG

Applicable component levels

  • R730 PSY UA46120

       UP09/03/11 P F903

  • R740 PSY UA46121

       UP09/03/11 P F903

  • R750 PSY UA46122

       UP09/03/11 P F903

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

z/OS family

Software version:

740

Operating system(s):

MVS, z/OS

Reference #:

OA28047

Modified date:

2010-10-26

Translate my page

Machine Translation

Content navigation