IV59141: INVALID TIMESTAMP WITH *TIME FUNCTION RESULTS IN ERRORS

IBM Tivoli Monitoring 6.3.0 Fix Pack 4 (6.3.0-TIV-ITM-FP0004)

APAR status

• Closed as program error.

Error description

• ********************** START OF APAR OPEN TEMPLATE
  *********************
  * Please open an apar with the following severity and
  information:     *
  *
         *
  APAR Type:            Field
  Approver Initials:    RB
  Severity:             3
  Reported Release:     623
  Compid:               5724C04MS Tivoli Enterprise Management
  Server
  ABSTRACT:             Invlaid timestamp with *TIME function
  results in errors
  
  PROBLEM DESCRIPTION:
  Using the *TIME function in a situation, nine trace messages
  appear in the TEMS log if an invalid timestamp is encountered.
  This is a warning messages only, but it can cause a lot number
  of messages in the log. The messages are similar to the
  following:
  
   ..."VXO2_MakeTime") MKTIME result is not a valid timestamp
  (mktime
      returned -1)
   ..."VXO2_MakeTime") Rejected timestamp fields:
   ..."VXO2_MakeTime")   Years since 1900 ... 0
   ..."VXO2_MakeTime")   Months ............. 0
   ..."VXO2_MakeTime")   Days ............... 0
   ..."VXO2_MakeTime")   Hours .............. 0
   ..."VXO2_MakeTime")   Minutes ............ 15
   ..."VXO2_MakeTime")   Seconds ............ 0Page 13 of 13
   ..."VXO2_MakeTime")   Milliseconds ....... 1
  
  RECREATE INSTRUCTIONS:
  LOCAL FIX:
  These message can be ignored.
  
  *********************** END OF APAR OPEN TEMPLATE
  **********************
  

Local fix

• These message can be ignored.
  

Problem summary

• The monitoring server issues many error level trace messages
  related to the use of the *TIME function.
  
  
  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 ............  15
                            ...  kdsxoc2.c,2074,"VXO2_MakeTime")
  Seconds ............  0
                            ...  kdsxoc2.c,2075,"VXO2_MakeTime")
  Milliseconds .......  1
  

Problem conclusion

• The code has been changed to not write the trace messages when
  the mktime() returns a value of -1 unless tracing is set to
  Detail.
  
  
  The fix for this APAR is contained in the following maintenance
  packages:
  
    | fix pack | 6.3.0-TIV-ITM-FP0004
  

Temporary fix

Comments

APAR Information

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

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

  OA46581

Fix information

• Fixed component name

  TEMS

• Fixed component ID

  5724C04MS

Applicable component levels

• R630 PSY

     UP