IBM Support

IJ35837: 7612 - AFTER UPGRADE CLIENT NOTICED THAT THERE ARE GROUPS MAXEVERYONE AND EVERIONE

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

  • Verified that, There are 5 options that are granted to EVERYONE
    group regardless of  the value maxvar ALLUSERGROUP.  This is
    wrong.  Looked at the dbc scripts and confirmed that "EVERYONE"
    was hardcoded where APPLICATIONAUTH were created.  It should
    take the value from the maxvar.
    
    
    Steps to replicate:
    There's no steps to replicate.
    
    ENVIRONMENT:
    
    System Information
    
    Systems Info:
    
    IBM Maximo Asset Management 7.6.1.2 Build 20200715-0100 DB Build
    V7611-01
    
    IBM Maximo Asset Management Work Centers 7.6.0.4 Build
    20200715-0100 DB Build V7
    
    604-119 HFDB Build HF7680-10,
    
    IBM Maximo Calibration 7.6.1.0 Build 20200715-0100 DB Build
    V7600-08
    
    IBM Tpae Integration Framework
    7.6.1.2-MIF_7612_IFIX.20210503-0858 Build 2020071
    
    5-1444 DB Build V7612-11
    
    IoT Connection Utility 7.6.0.3 Build 20200701-1409 DB Build
    V7603-32
    
    Tivoli's process automation engine 7.6.1.2-IFIX20210504-1949
    Build 20200715-0100
    
    DB Build V7612-284 HFDB Build HF7612-31
    

Local fix

  • Correct dbc script.
    

Problem summary

  • ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Few maximo database scripts include hardcoded EVERYONE group *
    * name as opposed to picking the group name from MAXVARS       *
    * table, where VARNAME = ALLUSERGROUP. As such, if the group   *
    * name has changed by the user or in maximo (and not maxdemo)  *
    * database where the group name is MAXEVERYONE instead of      *
    * EVERYONE the permissions were not granted correctly          *
    ****************************************************************
    

Problem conclusion

  • Two new database scripts are provided in this release to correct
    the issue and as such permissions to ALLUSERGROUP will be
    granted as required.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ35837

  • 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-10-28

  • Closed date

    2021-12-09

  • Last modified date

    2021-12-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

    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:
10 December 2021