IBM Support

IJ50349: INCORRECT WHERE CLAUSE GENERATED BY USING NOT EQUAL OPERATOR IN MAXIMO QUERY

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

  • ERROR DESCRIPTION:
    Incorrect WHERE clause generated by using Not Equal operator in
    Maximo query
    
    PROBLEM:
    Use of multiple criteria with the Not Equal operator on the List
    tab of any application generates an incorrect WHERE clause in
    the SQL query.
    The following results of single and multiple criteria in the
    Site field of the Assets application illustrate the issue:
    
    =BEDFORD generates (siteid = 'BEDFORD')
    !=BEDFORD generates (siteid != 'BEDFORD')
    =BEDFORD,=BOSTON generates ((siteid = 'BEDFORD' or siteid =
    'BOSTON'))
    !=BEDFORD,!=BOSTON generates (siteid != 'BEDFORD,!=BOSTON')
    --> should be (siteid != 'BEDFORD' and siteid != 'BOSTON')
    
    STEPS TO REPRODUCE:
    1. Open Maximo as maxadmin
    2. Go to Assets app
    3. In the List tab, with the Filter for the Site field type the
    following:
    	!=BEDFORD,!=BOSTON
    
    4. Hit ENTER
    5. Click the Combo Drop down arrow from Advanced Search and
    select Where Clause
    6. You will see that the current query is displayed as:
    	(siteid != 'BEDFORD,!=BOSTON')
    
    This is wrong. The query should be :   (siteid != 'BEDFORD' and
    siteid != 'BOSTON')
    
    CURRENT ERRONEOUS RESULT:
    You will see that the current query is displayed as:
    
    	(siteid != 'BEDFORD,!=BOSTON')
    
    EXPECTED RESULT:
    The query should be :   (siteid != 'BEDFORD' and siteid !=
    'BOSTON')
    
    ENVIRONMENT VERSION:
    App Server IBM WebSphere Application Server 9.0.5.17
    Version Tivoli's process automation engine
    7.6.1.3-IFIX20231130-1347 Build 20220823-0909 DB Build V7613-344
    HFDB Build HF7613-130
    IBM Maximo Application Framework 8.8.0 Build 20220823-1257 DB
    Build V7600-23
    IBM Maximo Asset Management Scheduler 7.6.8.2 Build
    20220823-0909 DB Build V7682-23 HFDB Build HF7682-10
    IBM Tpae Integration Framework 7.6.1.3 Build 20231130-0805 DB
    Build V7613-61
    LabelPro for Maximo by Asset Partners 7.6.0.0 Build
    20710413-0001 DB Build V7600-11 MT DB Build V7600-11
    IBM Maximo Asset Management 7.6.1.3 Build 20220823-0909 DB Build
    V7611-01
    IoT Connection Utility 7.6.0.4 Build 20220303-1642 DB Build
    V7604-01
    Server OS Windows Server 2019 10.0
    Server DB Oracle 19.1 (Oracle Database 19c Enterprise Edition
    Release 19.0.0.0.0 - Production Version 19.21.0.0.0)
    

Local fix

Problem summary

Problem conclusion

  • A fix for this APAR will be included in a future release.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ50349

  • Reported component name

    SYSTEM CONFIG

  • Reported component ID

    5724R46S1

  • Reported release

    761

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2024-03-05

  • Closed date

    2024-04-09

  • Last modified date

    2024-04-09

  • 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

    SYSTEM CONFIG

  • Fixed component ID

    5724R46S1

Applicable component levels

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"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:
10 April 2024