IBM Support

IV50626: MKTIME FUNCTION ERRORS WHEN A ZERO TIME VALUE IS PROVIDED.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Approver Initials:  HT
    
    The MQ monitoring application returns a zero value for a
    timestamp for the QLASTPUT column in the KMQ.QMQUEUES
    table which is associated to the
    Queue_Statistics.Last_Put_Date_and_Time attribute.
    
    Messages like the following will be issued to the TEMS RAS1
    trace log:
    
    (52415F4C.0001-166C:kdsxoc2.c,2062,"VXO2_MakeTime") MKTIME
    result is not a valid timestamp (mktime returned -1)
    (52415F4C.0002-166C:kdsxoc2.c,2068,"VXO2_MakeTime") Rejected
    timestamp fields:
    (52415F4C.0003-166C:kdsxoc2.c,2069,"VXO2_MakeTime")   Years
    since 1900
    ... 0
    (52415F4C.0004-166C:kdsxoc2.c,2070,"VXO2_MakeTime")   Months
    ............. 0
    (52415F4C.0005-166C:kdsxoc2.c,2071,"VXO2_MakeTime")   Days
    ............... 0
    (52415F4C.0006-166C:kdsxoc2.c,2072,"VXO2_MakeTime")   Hours
    .............. 6
    (52415F4C.0007-166C:kdsxoc2.c,2073,"VXO2_MakeTime")   Minutes
    ............ 0
    (52415F4C.0008-166C:kdsxoc2.c,2074,"VXO2_MakeTime")   Seconds
    ............ 0
    (52415F4C.0009-166C:kdsxoc2.c,2075,"VXO2_MakeTime")
    Milliseconds
    ....... 0
    
    RECREATE INSTRUCTIONS:
    Execute SQL like the following using kdstsns:
    
    SELECT QMQUEUES.QLASTPUT,
           QMQUEUES.ORIGINNODE
    FROM   KMQ.QMQUEUES, O4SRV.LOCALTIME
    WHERE  QMQUEUES.ORIGINNODE = "Q7G1:SYS:MQESA" AND
           MKTIME(QMQUEUES.QLASTPUT, '-', '6M') < LOCALTIME.SYSTIME;
    
    The above is a specific example to a particular TEMS and MQ
    agent.  Some values will need to be modified.
    

Local fix

  • N/A
    

Problem summary

  • The monitoring server issues many messages like the following to
     the trace log file:
    
    ... kdsxoc2.c,2062,"VXO2_MakeTime") MKTIME result is not a valid
    timestamp (mktime returned -1)
    ... kdsxoc2.c,2068,"VXO2_MakeTime") Rejected timestamp fields:
    ... kdsxoc2.c,2069,"VXO2_MakeTime") Years since 1900 ... 0
    ... kdsxoc2.c,2070,"VXO2_MakeTime") Months ............. 0
    ... kdsxoc2.c,2071,"VXO2_MakeTime") Days ............... 0
    ... kdsxoc2.c,2072,"VXO2_MakeTime") Hours .............. 0
    ... kdsxoc2.c,2073,"VXO2_MakeTime") Minutes ............ 30
    ... kdsxoc2.c,2074,"VXO2_MakeTime") Seconds ............ 0
    ... kdsxoc2.c,2075,"VXO2_MakeTime") Milliseconds ....... 0
    

Problem conclusion

  • The code has been changed to not generate any error level trace
    messages if a TIMESTAMP value of 0000000000000000 is provided to
     the *TIME function.
    
    The fix for this APAR is contained in the following maintenance
    packages:
    | fix pack | 6.2.3-TIV-ITM-FP0005
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV50626

  • Reported component name

    TEMS

  • Reported component ID

    5724C04MS

  • Reported release

    622

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-10-09

  • Closed date

    2013-12-17

  • Last modified date

    2014-05-06

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

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

    OA44514

Fix information

  • Fixed component name

    TEMS

  • Fixed component ID

    5724C04MS

Applicable component levels

  • R623 PSY

       UP

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSCTLMP","label":"ITM Tivoli Enterprise Mgmt Server V6"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"622","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
06 May 2014