IBM Support

IJ37531: 7612 - SET DEFAULT TO 0 IN CLASSSTRUCTURE.GENASSETDESC.

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

  • PROBLEM DESCRIPTION:
    7612 - Set default to 0 in CLASSSTRUCTURE.GENASSETDESC.
    User changed the default value of that field in Database
    Configuration from 1 to 0. And then applied db config changes.
    However, the changedoesn't seem to be working, in the
    Classifications application, the GENASSETDESC is still
    defaulting to 1.
    STEPS TO REPLICATE:
    1 - Login in Maximo as Administrator user.Go to Database
    Configuration Application.
    2 - In database configuration application, search for
    CLASSSTRUCTURE tgable / GENASSETDESC attribute, in Attribute
    tab.
    3 - In Attribute tab, GENASSETDESC atrribute, change default
    value to 0 then put maximo in admin mode and configure changes.
    4 - After Database configuration concluded, turn off admin mode,
    go to Administration / Classifications Application.
    5 - Create a new Calassification.
    Expected behavior:
    The flag Change Asset Description is marked by default. The
    changes done in database was not effective.
    
    Expected behavior:
    The flag Change Asset Description should be blank, because
    GENASSETDESC was set the default value to 0.
    
    ENVIRONMENT:
    App Server IBM WebSphere Application Server 9.0.0.7
    Version
    Tivoli's process automation engine 7.6.1.2-IFIX20201215-1550
    Build 20200715-0100 DB Build V7612-284 HFDB Build HF7612-14
    IBM Maximo Asset Management Work Centers 7.6.0.4 Build
    20200715-0100 DB Build V7604-119 HFDB Build HF7680-10
    IBM Maximo Asset Management Scheduler 7.6.8.0 Build
    20200715-0100 DB Build V7680-148 HFDB Build HF7680-15
    IBM Maximo Anywhere 7.6.4.0 Build 20200117_195427-0500 DB Build
    V7640-12
    IBM Maximo Linear Management 7.6.1.0 Build 20200715-0100 DB
    Build V7610-04
    IBM Tpae Integration Framework
    7.6.1.2-MIF_7612_IFIX.20201202-1326 Build 20200715-1444 DB Build
    V7612-11
    IBM Maximo Transportation 7.6.2.5 Build 20180730-2210 DB Build
    V7625-10
    IBM Maximo Spatial Asset Management 7.6.1.0-20210304-2253 Build
    20200716-1706 DB Build V7610-15 HFDB Build HF7610-03
    IBM Maximo Asset Management 7.6.1.2 Build 20200715-0100 DB Build
    V7611-01
    IoT Connection Utility 7.6.0.3 Build 20200701-1409 DB Build
    V7603-32
    TPAE OSLC Object Structure 7.6.4.0 Build 20200219_092917-0500 DB
    Build V7640-04
    Server OS Windows Server 2016 10.0
    Server DB Oracle 19.0 (Oracle Database 19c Enterprise Edition
    Release 19.0.0.0.0 - Production Version 19.3.0.0.0)
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * MAXIMO                                                       *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * User changed the default value of that field in Database     *
    * Configuration from 1 to 0. And then applied db config        *
    * changes.                                                     *
    * However, the changedoesn't seem to be working                *
    ****************************************************************
    

Problem conclusion

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

Temporary fix

Comments

APAR Information

  • APAR number

    IJ37531

  • 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-01-31

  • Closed date

    2022-02-01

  • Last modified date

    2022-02-01

  • 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":"761"}]

Document Information

Modified date:
02 February 2022