IBM Support

IJ38777: MAXIMO ALLOWS OLDER STATUS DATES ON STATUS CHANGES TO A SYNONYM OF CURRENT STATUS

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 a user is changing the status to a different value of the
    same synonym status, such as OPERATING & ACTIVE on the
    LOCASSETSTATUS domain both having an internal value of
    OPERATING, they can provide any status date including historical
    dates prior to all other status dates.
    
    
    
    
    STEPS TO REPRODUCE:
    
    
    Steps to recreate (Location):
    1) In application designer, open the LOCATION application
    2) From the Edit dialogs, open the "locstatus" dialog
    3) Change the input mode on ASOFDATE so that it's editable (it's
    set to read-only out of box). Save
    4) Go to the locations application
    5) Open a location in the OPERATING status such as ADDR2001 in
    site BEDFORD. Look at the status date of the record in the view
    history dialog (ADDR2001 has a status date of 1/14/99)
    6) Open the change status dialog. Choose a status that is a
    synonym of OPERATING (such as ACTIVE) and provide a status date
    prior to the recorded status date (IE 1/1/99).
    7) The change status will go through. Open the View History and
    you'll see your status change is recorded with the date you
    provided (1/1/99) even though it was before the previous date.
    
    
    CURRENT ERRONEOUS RESULTS:
    
    
    Changes the Record Status Date to an Earlier Date when synonym
    Statuses is used
    
    EXPECTED RESULTS:
    
    
    Should not be allowed to change the date to be earlier than
    the previous status change with or without a synonym being used
    and throw the error "BMXAA4673E - The status change date cannot
    be earlier than the date of the last status change." as when a
    NON Synonym status is used.
    
    
    PERFORMANCE ISSUE: No
    
    
    ENVIRONMENT:
    
    Tivoli's process automation engine 7.6.1.2-IFIX20211022-0031
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Maximo users                                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * MAXIMO ALLOWS OLDER STATUS DATES ON STATUS CHANGES TO A      *
    * SYNONYM OF CURRENT STATUS                                    *
    ****************************************************************
    

Problem conclusion

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

Temporary fix

Comments

APAR Information

  • APAR number

    IJ38777

  • 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

    2022-03-15

  • Closed date

    2024-02-10

  • Last modified date

    2024-02-10

  • 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

[{"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:
11 February 2024