IBM Support

IJ31012: MAXIMO IS DELETING THE EARLIEST MEASUREMENT FOR THE GIVEN POINTNUM, INSTEAD OF THE SPECIFIC MEASUREMENTID LISTED IN MIF

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

  • Abstract
    
    Maximo is deleting the earliest measurement for the
    given pointnum, instead of the specific measurementid listed in
    the integration message.
    
    STEPS TO REPRODUCE:
    
    The steps below
    use MAXDEMO as an example.
    
    1)Execute the query below in
    backend:
    select measurementid,pointnum,siteid,measurementvalue,a
    ssetnum,measuredate from MEASUREMENT where pointnum = '1001'
    and assetnum = '11430';
    There are eleven measures for this
    pointnum. We will try to delete the measure 18.
    
    2)Import the
    XML below using MIF:
    <?xml version="1.0"
    encoding="UTF-8"?>
    <SyncMXMETERDATA
    xmlns="http://www.ibm.com/maximo"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    creationDateTime="2018-02-15T22:47:37-06:00" baseLanguage="EN"
    messageID="1518756456960817941">
    <MXMETERDATASet>
    <METERDATA
    action="Delete" >
    <MEASUREMENTID>18</MEASUREMENTID>
    <POINTNUM
    >1001</POINTNUM>
    <SITEID >BEDFORD</SITEID>
    <ORGID
    >EAGLENA</ORGID>
    <MEASUREMENTVALUE >4478</MEASUREMENTVALUE>
    </ME
    TERDATA>
    </MXMETERDATASet>
    </SyncMXMETERDATA>
    
    RESULTS:
    MIF
    will delete the earliest measurement for the given pointnum, in
    this example measurementid 2.
    
    EXPECTED RESULTS:
    MIF should
    delete the measurementid 18.
    
    REPORTED IN VERSION:
    Tivoli's
    process automation engine 7.6.0.9
    

Local fix

  • Create a new Object Structure using the table MEASUREMENT and
    use it for delete operation only.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Maximo MIF users                                             *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Using MIF, unable to delete measurement using                *
    * MEASUREUNITID.                                               *
    ****************************************************************
    Maximo is deleting the earliest measurement for thegiven
    pointnum, instead of the specific measurementid listed inthe
    integration message.
    STEPS TO REPRODUCE:
    The steps belowuse MAXDEMO as an example.
    1)Execute the query below inbackend:select
    measurementid,pointnum,siteid,measurementvalue,assetnum,measured
    ate from MEASUREMENT where pointnum = '1001'and assetnum =
    '11430';There are eleven measures for thispointnum. We will try
    to delete the measure 18.
    2)Import theXML below using MIF:<?xml
    version="1.0"encoding="UTF-8"?><SyncMXMETERDATAxmlns="http://www
    .ibm.com/maximo"xmlns:xsi="http://www.w3.org/2001/XMLSchema-inst
    ance"creationDateTime="2018-02-15T22:47:37-06:00"
    baseLanguage="EN"messageID="1518756456960817941">
    <MXMETERDATASet>
    <METERDATAaction="Delete" >
    <MEASUREMENTID>18</MEASUREMENTID>
    <POINTNUM>1001</POINTNUM>
    <SITEID >BEDFORD</SITEID>
    <ORGID>EAGLENA</ORGID>
    <MEASUREMENTVALUE >4478</MEASUREMENTVALUE>
    </METERDATA>
    </MXMETERDATASet>
    </SyncMXMETERDATA>
    RESULTS: MIF will delete the earliest measurement for the given
    pointnum, in this example measurementid 2.
    EXPECTED RESULTS:MIF shoulddelete the measurementid 18.
    

Problem conclusion

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

Temporary fix

Comments

APAR Information

  • APAR number

    IJ31012

  • Reported component name

    MAXIMO ASST MGM

  • Reported component ID

    5724R46AM

  • Reported release

    760

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-02-24

  • Closed date

    2022-05-11

  • Last modified date

    2022-05-11

  • 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

[{"Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSLKT6","label":"Maximo Asset Management"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"760"}]

Document Information

Modified date:
12 May 2022