IJ30261: WHEN USING START TIMER IN SR APPLICATION YEAR SHOWING A 0002 AND CAUSING AN INTEGRATION ERROR.

APAR status

• Closed as program error.

Error description

• Problem Description:
  When using START TIMER in SR application
  YEAR showing a 0002 and causing an INTEGRATION error.
  
  STEPS TO
  REPRODUCE:
  
  1) Configure the integration framework to send
  MXGLTXNInterface transactions to the interface table and enable
  the event listener on the publish channel.
  
  2) Go to Service
  Desk -> Service Request.
  
  3) Create a new Service Request and
  change the status to "IN PROGRESS".
  
  4) Click Start Timer.
  
  5)
  Click Stop Timer.
  
  The integration cron task throws an error
  while trying to deliver the message from the queue to the
  endpoint.
  
  Stack:
  [12/9/20 11:38:03:660 PST] 000000f1 SystemOut
  O 09 Dec 2020 11:38:03:660 [ERROR] [MAXIMO] [CID-CRON-432591]
  BMXAA4210E - Database error number {0} has occurred. Invalid
  SQL queries are logged in the log file. Check the SQL query to
  identify the error.
  BMXAA4144E - The date/time format is not
  valid. Make sure the date/time is specified in a valid format
  supported by the current locale setting.
  BMXAA4143E - The date
  format is not valid. Use the date format defined by your
  locale, or use the calendar control to enter a
  date.
  psdi.util.MXSystemException: BMXAA4210E - Database error
  number {0} has occurred. Invalid SQL queries are logged in the
  log file. Check the SQL query to identify the error.
  BMXAA4144E
  - The date/time format is not valid. Make sure the date/time is
  specified in a valid format supported by the current locale
  setting.
  BMXAA4143E - The date format is not valid. Use the
  date format defined by your locale, or use the calendar control
  to enter a date.
  at psdi.iface.intertables.WriteToIfaceTable.set
  IfaceTabledata(WriteToIfaceTable.java:556)
  at psdi.iface.router.
  IfaceTableHandler.invoke(IfaceTableHandler.java:127)
  at psdi.ifa
  ce.jms.QueueToDestManagerProcessor.processMessage(QueueToDestMan
  agerProcessor.java:97)
  at psdi.iface.jms.JMSQueueCronTask.getMes
  sage(JMSQueueCronTask.java:466)
  at psdi.iface.jms.JMSQueueCronTa
  sk.cronAction(JMSQueueCronTask.java:284)
  at psdi.server.CronTask
  Manager.callCronMethod(CronTaskManager.java:2519)
  at psdi.server
  .CronTaskManager.access$1100(CronTaskManager.java:105)
  at psdi.s
  erver.CronTaskManager$CronThread.run(CronTaskManager.java:3429)
  
  at java.util.concurrent.Executors$RunnableAdapter.call(Executors
  .java:522)
  at
  java.util.concurrent.FutureTask.run(FutureTask.java:277)
  at java
  .util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask
  .access$201(ScheduledThreadPoolExecutor.java:191)
  at java.util.c
  oncurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Sc
  heduledThreadPoolExecutor.java:304)
  at java.util.concurrent.Thre
  adPoolExecutor.runWorker(ThreadPoolExecutor.java:1160)
  at java.u
  til.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.
  java:635)
  at java.lang.Thread.run(Thread.java:811)
  Caused
  by:
  psdi.util.MXApplicationException: BMXAA4144E - The
  date/time format is not valid. Make sure the date/time is
  specified in a valid format supported by the current locale
  setting.
  BMXAA4143E - The date format is not valid. Use the
  date format defined by your locale, or use the calendar control
  to enter a date.
  at
  psdi.util.MXFormat.jmigStringToDateTime(MXFormat.java:1016)
  at p
  sdi.iface.mos.ConversionUtil.stringToDate(ConversionUtil.java:10
  3)
  at psdi.iface.intertables.WriteToIfaceTable.setBindValue(Writ
  eToIfaceTable.java:647)
  at psdi.iface.intertables.WriteToIfaceTa
  ble.setIfaceTabledata(WriteToIfaceTable.java:474)
  ... 14
  more
  Caused by:
  psdi.util.MXApplicationException: BMXAA4143E -
  The date format is not valid. Use the date format defined by
  your locale, or use the calendar control to enter a date.
  at
  psdi.util.MXFormat.jmigStringToDateTime(MXFormat.java:1011)
  ...
  17 more
  
  RESULTS:
  BMXAA4144E - The date/time format is not
  valid. Make sure the date/time is specified in a valid format
  supported by the current locale setting.
  BMXAA4143E - The date
  format is not valid. Use the date format defined by your
  locale, or use the calendar control to enter a date.
  In the XML
  transaction is possible to see the date in wrong format. The
  year is 0002
  <FINISHTIME
  changed="1">0002-12-31T11:55:12-08:00</FINISHTIME>
  
  EXPECTED
  RESULTS:
  The transaction should not generate an error.
  
  
  REPORTED IN VERSION:
  Tivoli's process automation engine
  7.6.1.2
  

Local fix

• NA
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Maximo users                                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Users encounter error BMXAA4144E when MIF tries to save the  *
  * date of a TIME field to an interface table                   *
  ****************************************************************
  

Problem conclusion

• The fix for this APAR is contained in the following maintenance
  package: release\fix pack for Release 7.6.1.3 Product
  

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:

Fix information

• Fixed component name

  MAXIMO ASST MGM

• Fixed component ID

  5724R46AM

Applicable component levels