IBM Support

IJ34820: VALUES WITH AMPERSAND BEING CONVERTED TO HTML ENTITY IN MESSAGE REPROCESSING

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

  • When correcting errors in JSON data in the Message Reprocessing
    application that contain other fields that have an ampersand (&)
    symbol in them, reprocessing of the message fails to convert the
    ampersand correctly.
    
    
    Steps to reproduce:
    1. In Maximo, create a location called LOC&ABC
    
    2. Create a json transaction file that contains this new
    location along with an invalid SITEID as shown below.  The
    purpose of this transaction is to first fail on the invalid
    siteid in order to display the problem:
    
    e.g.
    {
    "assetnum": "TESTBF2",
    "changedate": "2020-12-02T13:38:45.000-04:00",
    "status_description": "Active",
    "location": "LOC&ABC",
    "orgid": "EAGLENA",
    "description": "IT test",
    "itemnum": "FIRE-100",
    "siteid": "M1CLEAN",
    "islinear": false,
    "isrunning": true,
    "status": "ACTIVE",
    "statusdate": "2019-05-17T13:38:45.000-04:00",
    "itemsetid": "SET1",
    }
    
    3. Ensure the MXASSETInterface enterprise service is enabled on
    your external system.
    
    4 . Navigate to external systems, and select the
    MXASSETInterface enterprise service. Click Data Import
    
    5. result: the transaction will fail because the SITEID is
    invalid. The problem does not yet appear. The error is:
    BMXAA4153E - M1CLEAN is not a valid site. Enter a valid Site
    value as defined in the Organization Application.
    
    Also note that when clicking the edit button for the failed
    transaction, the data is still valid and the location still
    shows as LOC&ABC.
    
    6. Next, place the transaction on HOLD status. Then edit the
    error data and correct the SITEID value to MCLEAN.
    Click the Process button. Error message displays in the dialog
    as follows:
    
    BMXAA1298E - The error message failed during reprocessing.
    BMXAA2661E - Location LOC&ABC is not a valid location.
    
    7. Click OK on the dialog box, then click Save.
    
    8. The error message field in Message Reprocessing shows the
    same error:
    BMXAA2661E - Location LOC&ABC is not a valid location.
    
    Expected results: Message reprocessing would show the correct
    format for the location without the invalid html entity.
    
    Performance problem: NO
    
    Version
    Environment System Information:
    Tivoli's process automation engine 7.6.1.2-IFIX20210323-1206
    Build 20200715-0100 DB Build V7612-284 HFDB Build HF7612-20,
    IBM Maximo Asset Management Work Centers 7.6.0.4 Build
    20200715-0100 DB Build V7604-119 HFDB Build HF7680-10,
    IBM Tpae Integration Framework
    7.6.1.2-MIF_7612_IFIX.20210303-1359 Build 20200715-1444 DB Build
    V7612-11
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * MAXIMO                                                       *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * VALUES WITH AMPERSAND BEING CONVERTED TO HTML ENTITY IN      *
    * MESSAGE REPROCESSING                                         *
    ****************************************************************
    

Problem conclusion

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

Temporary fix

Comments

APAR Information

  • APAR number

    IJ34820

  • Reported component name

    MAXIMO ASST MGM

  • Reported component ID

    5724R46AM

  • Reported release

    761

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-09-02

  • Closed date

    2022-12-02

  • Last modified date

    2022-12-02

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

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

Modules/Macros

  • MAXIMO
    

Fix information

  • Fixed component name

    MAXIMO ASST MGM

  • Fixed component ID

    5724R46AM

Applicable component levels

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

Document Information

Modified date:
02 December 2022