IBM Support

IC67905: THE LOGIC OF SETTING THE NEXT EXECUTION TIME FOR A TASK MIGHT LEAD TO LOTS OF UNWANTED RUNS OF THE TASK

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • When there is a task in sysadmin:ph_task table which has
    tk_start_time set and tk_frequency set  to value less then 1
    day, this task might be run several hundred times between its
    last 'standard' schedule in a particular day and the midnight
    that day.
    This behavior can have several side effects:
    - in case the time between last 'standard' run and midnight is
    long enough (30-50 minutes), the task might return error -213
    repeatedly which finally leads to scheduler shutdown
    - in case the AUS Evaluator & Refresher are scheduled for the
    same day, they might meet in time (even thought they are
    scheduled to different times) sometime between 23:01 and
    midnight and produce various errors like -710 for aus_command
    table, -206 or -244 for aus_cmd_info table and like
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All platforms                                                *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * When there is a task in sysadmin:ph_task table which has     *
    * tk_start_time set and tk_frequency set to a value less than  *
    * 24 hours, this task might be run several times unexpectedly  *
    * between its last 'standard' schedule in a particular day and *
    * the midnight that day.                                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to IDS 11.50.xC7                                     *
    ****************************************************************
    

Problem conclusion

  • The problem is first fixed in 11.50.xC7. When there is a task in
    sysadmin:ph_task table which has tk_start_time set and
    tk_frequency set to a value less than 24 hours, this task will
    be run only at the expected execution times.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC67905

  • Reported component name

    IBM IDS ENTRP E

  • Reported component ID

    5724L2304

  • Reported release

    B15

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-04-14

  • Closed date

    2011-01-20

  • Last modified date

    2011-01-20

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

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

Fix information

  • Fixed component name

    IBM IDS ENTRP E

  • Fixed component ID

    5724L2304

Applicable component levels

  • RB15 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSGU8G","label":"Informix Servers"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"B15","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
20 January 2011