IBM Support

PI55585: WARNING MESSAGE EKYB229W IS RECEIVED FROM THE SELECTOR. 16/04/14 PTF PECHANGE

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The Selector issued warning message EKYB229W indicating that
    an unlogged time period is followed by a period for which
    archived logs exist and that it considers that (IMS) log
    archiving may have failed.  Inspection of logging conditions
    within the environment determine that no logs are problem exist
    with logging.  The problem occured in adata sharing environment.
    

Local fix

  • The problem was avoided by manipulatin of the Selector start
    time avoiding the period during which the message was triggeed.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of the IMS DataPropagator Version 3    *
    *                 Release 1 asynchronous Selector component.   *
    ****************************************************************
    * PROBLEM DESCRIPTION: After applying PTF UI30480, MSGEKYB229W *
    *                      may be encountered when running the     *
    *                      Selector.  In different circumstances   *
    *                      MSGEKYB343E may also occur.             *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    After applying PTF UI30480 the message EKY229W may be received
    with accompanying messages indicating a likely problem with
    IMS logging for a subsystem being considered by the Selector.
    However, because of a programming error introduced associated
    with APAR PI30222 (PTF UI30480) this GAP in time where no
    IMS logs exist may be incorrectly flagged as being a period of
    concern.
    
    EKYB210I A PERIOD OF TIME EXISTS WHERE NO LOGS ARE AVAILABLE FOR
             SUBSYSTEM "subsystemid"
    EKYB222I THE UNLOGGED PERIOD IS BETWEEN THE IMS TIMESTAMPS
             "time stamp 1" and "time stamp 2"
    EKYB229W THE UNLOGGED TIME PERIOD DETAILED ABOVE IS FOLLOWED BY
             A PERIOD FOR WHICH ARCHIVED LOGS EXIST.
             LOG ARCHIVING MAY HAVE FAILED
    EKYB224I THE SELECTOR STOP TIME IS DETERMINED TO BE THE POINT OF
             DISCONTINUITY OF THE IMS LOG FILES
    
    Because of the above conditions being identified by the
    Selector, further processing ends and the Selector terminates.
    
    Additionally, after applying PTF UI304980 in circumstances
    where IMS logs being processed by the Selector where DBRC is
    still reporting timestamps one tenth of a second precision
    (e.g. in IMS V9 subsystem), then the message EKYB343E
    may occur, indicated an error was encountered reading IMS log
    files.  i.e. error message:
    EKYB343E ERROR OCCURED WHILE READING THE IMS LOG FILES
    

Problem conclusion

  • The problem resulted because of a programming error in the
    Selector module which performs validation off the IMS logging
    environment in which it is functioning for the period of time in
    which it is interested in capturing IMS changed data from IMS
    logs.  As a result of this programming error the Selector may
    incorrectly identify a legitimate period of time when IMS is
    down as being a potential invalid gap in the IMS logs in which
    it is interested.  Selector module EKYB215X has been changed to
    avoid the Selector flagging an otherwise legitimate gap in IMS
    logging as a being a period it needs to be concerned about.
    
    In problem situation where message EKYB343E occurs this is a
    result of changes made associated with earlier PTF UI30480
    which changed Selector processing to exclusively use DBRC
    reported timestamps using microsecond precision timestamps.
    Changes are now added to Selector modules to consider the
    possibility that DBRC reported timestamps of one tenth of a
    second precision may still be encountered during Selector and
    not exclusively microsecond timestamp precision values.
    When the Selector encountered one tenth of a second DBRC
    reported timestamps prior to the changes made associated
    with this APAR, it is possible that all applicable IMS log
    records may not be written to ULR during Selector processing.
    This sets up the possible conditions where message EKYB343E may
    occur on the following Selector run because the prior Selector
    did not write all appropriate records to the ULR and record
    sequencing problems may then be identified.
    

Temporary fix

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

Comments

APAR Information

  • APAR number

    PI55585

  • Reported component name

    IMS DATA PROPAG

  • Reported component ID

    5655E5200

  • Reported release

    310

  • Status

    CLOSED PER

  • PE

    YesPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-01-18

  • Closed date

    2016-08-09

  • Last modified date

    2016-09-02

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

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

    UI39982

Modules/Macros

  • EKYB200X EKYB215X EKYB250X EKYB260X EKYB300X
    EKYB310X EKYB315X EKYB320X EKYB330X
    

Fix information

  • Fixed component name

    IMS DATA PROPAG

  • Fixed component ID

    5655E5200

Applicable component levels

  • R310 PSY UI39982

       UP16/08/19 P F608 «

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.

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.1.0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
02 September 2016