PK64790: TSM SCHEDULE EVENT GETS REPORTED AS FAILED WITH RESULT "-99" THOUGH THE SCHEDULE RUNS SUCCESSFULLY TO END

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • A TSM schedule may get reported as failed with a result code of
    "-99" though the schedule runs successfully to end. This
    happens, if a TSM client session (SessType=4) of the schedule
    gets terminated outside the backup schedule window due to
    getting into an IDLETIMEOUT. This gets misleadingly interpreted
    as the end of the schedule and the TSM server event table gets
    updated with an end time for the schedule with an undefined
    result code ("-99").
    .
    The schedule itself does not abort and runs till the end, but
    when the TSM server event table should get updated correctly,
    this fails with following message as the event table for this
    schedule has already a status:
    ANR2576W An attempt was made to update an event record for a
    scheduled operation which has already been executed - multiple
    client schedulers may be active for node <NODENAME>.
    .
    .
    Customer/L2 Diagnostics:
    A typical sequence in the ACTLOG would look like the following:
    ===============================================================
    02/08/2008 17:25:53      ANR0406I Session 1130 started for node
    WIN2003 (WinNT) (Tcp/Ip tsm2003(1760)). (SESSION: 1130)
    [...]
    02/08/2008 17:36:26      ANR0482W Session 1131 for node WIN2003
    (WinNT) terminated - idle for more than 10 minutes. (SESSION:
    1131)
    [...]
    02/08/2008 17:52:37      ANE4952I (Session: 1130, Node: WIN2003)
    Total number of objects inspected:   26,795 (SESSION: 1130)
    02/08/2008 17:52:37      ANE4954I (Session: 1130, Node: WIN2003)
    Total number of objects backed up:   15,861 (SESSION: 1130)
    02/08/2008 17:52:37      ANE4958I (Session: 1130, Node: WIN2003)
    Total number of objects updated:          0 (SESSION: 1130)
    02/08/2008 17:52:37      ANE4960I (Session: 1130, Node: WIN2003)
    Total number of objects rebound:          0 (SESSION: 1130)
    02/08/2008 17:52:37      ANE4957I (Session: 1130, Node: WIN2003)
    Total number of objects deleted:          0 (SESSION: 1130)
    02/08/2008 17:52:37      ANE4970I (Session: 1130, Node: WIN2003)
    Total number of objects expired:         41 (SESSION: 1130)
    02/08/2008 17:52:37      ANE4959I (Session: 1130, Node: WIN2003)
    Total number of objects failed:         261 (SESSION: 1130)
    02/08/2008 17:52:37      ANE4965I (Session: 1130, Node: WIN2003)
    Total number of subfile objects:          0 (SESSION: 1130)
    02/08/2008 17:52:37      ANE4961I (Session: 1130, Node: WIN2003)
    Total number of bytes transferred:  3.20 GB (SESSION: 1130)
    02/08/2008 17:52:37      ANE4963I (Session: 1130, Node: WIN2003)
    Data transfer time:                  463.66 sec (SESSION: 1130)
    02/08/2008 17:52:37      ANE4966I (Session: 1130, Node: WIN2003)
    Network data transfer rate:        7,245.66 KB/sec (SESSION:
    1130)
    02/08/2008 17:52:37      ANE4967I (Session: 1130, Node: WIN2003)
    Aggregate data transfer rate:      2,094.31 KB/sec (SESSION:
    1130)
    02/08/2008 17:52:37      ANE4968I (Session: 1130, Node: WIN2003)
    Objects compressed by:                    0% (SESSION: 1130)
    02/08/2008 17:52:37      ANE4969I (Session: 1130, Node: WIN2003)
    Subfile objects reduced by:               0% (SESSION: 1130)
    02/08/2008 17:52:37      ANE4964I (Session: 1130, Node: WIN2003)
    Elapsed processing time:            00:26:44 (SESSION: 1130)
    02/08/2008 17:52:38      ANR2579E Schedule TEST in domain
    STANDARD for node WIN2003 failed (return code 12). (SESSION:
    1130)
    02/08/2008 17:52:38      ANR2576W An attempt was made to update
    an event record for a scheduled operation which has already been
    executed - multiple client schedulers may be active for node
    WIN2003. (SESSION: 1130)
    02/08/2008 17:52:38      ANR0403I Session 1130 ended for node
    WIN2003 (WinNT). (SESSION: 1130)
    
    A "query event" shows something like the following:
    ===================================================
    Policy Domain Name    STANDARD
    Schedule Name         TEST
    Node Name             WIN2003
    Scheduled Start       02/08/2008 17:25:00
    Actual Start          02/08/2008 17:25:53
    Completed             02/08/2008 17:36:23
    Status                Failed
    Result                -99
    Reason                Failed
    .
    .
    TSM Versions Affected:
    TSM 5.3, 5.4 and 5.5 servers
    .
    .
    Initial Impact:
    Medium
    .
    .
    Additional Keywords:
    ANR2576W session lost interrupt timeout time out SessType
    SESS_NODE_GEN
    

Local fix

  • Increasing the value for IDLETIMEOUT decreases the likelihood of
    the problem to occur.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: TSM server customers.                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: See ERROR DESCRIPTION.                  *
    ****************************************************************
    * RECOMMENDATION: Apply fixing level when available.           *
    *                 This problem is currently projected to be    *
    *                 fixed in levels 5.4.4 and 5.5.1.             *
    *                 Note that this is subject to change at the   *
    *                 discretion of IBM.                           *
    ****************************************************************
    *
    

Problem conclusion

  • The TSM server has been corrected.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK64790

  • Reported component name

    TSM FOR OS/390

  • Reported component ID

    5698ISMVS

  • Reported release

    550

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-04-21

  • Closed date

    2008-04-21

  • Last modified date

    2008-08-02

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

    IC55610

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

Fix information

  • Fixed component name

    TSM FOR OS/390

  • Fixed component ID

    5698ISMVS

Applicable component levels

  • R550 PSY UK37981

       UP08/07/17 P F807

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.



Document information


More support for:

Tivoli Storage Manager

Software version:

550

Reference #:

PK64790

Modified date:

2008-08-02

Translate my page

Content navigation