IBM Support

IJ38318: UNABLE TO SAVE LOCATION RECORD AFTER RE-ADDING A CLASSIFICATION THAT PREVIOUSLY HAD A VALUE FOR AN ATTRIBUTE

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

  • In Locations applications if a classification which already has
    a value entered for one of its attributes is removed from a
    location and then readded, an error message is displayed when
    trying to save the location.
    
    STEPS TO REPRODUCE:
    1.	Open the Locations application and click to add a new
    location.
    
    2.	Fill in the following information:
    a.	Location: L-1001
    b.	Type: OPERATING
    c.	Click on tab Specifications
    i.	Click on Select Value button and select a classification,
    e.g. OIL
    ii.	Enter a value for the first attribute, Type for OIL
    classification
    3.	Save the location
    4.	In the tab Specifications remove the specification and Save
    5.	In the same tab click on Select Value button and select the
    same classification ? the attribute which had a value (Type) has
    2 records, one with the previous value
    6.	Click on Save ? the following error message is displayed:
    BMXAA4129E - The record for Location=L-1000, Attribute=TYPE,
    Section=, Site=BEDFORD already exists. Ensure that the key value
    for the given record is unique.
    7.	Delete one or both Type attribute rows and click on Save ?
    the same error message is displayed
    RESULT:
    The location cannot be saved after reading the classification
    EXPECTED RESULT:
    The location should be saved after reading the classification
    REPORTED IN VERSION:
    Tivoli's process automation engine 7.6.1.2
    

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

    IJ38318

  • 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-09

  • Closed date

    2023-02-22

  • Last modified date

    2023-02-22

  • 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:
22 February 2023