IJ26747: INTEGRITY CHECKER RAISES TWO SETS OF WARNINGS RELATED TO THE TOKEN LICENSE, BMXAA0471W AND BMXAA0521W.

APAR status

• Closed as program error.

Error description

• ERROR DESCRIPTION:
  After upgrading from Maximo 7.6.0.9 to 7.6.1.1, the Integrity
  Checker raises two sets of WARNINGs related to the Token
  License functionality:
  BMXAA0442W -- Warning - BMXAA0471W -- No primary key sequence
  is defined on the table. Review the table and decide if a
  primary key sequence is required. Tue Jun 23 16:34:48 PDT 2020
  TOKENLICAHIUSERNAME
  TOKENLICUSERNAME
  BMXAA0442W -- Warning - BMXAA0521W -- All applications should
  be mapped to a table. The following apps are not mapped. Tue
  Jun 23 16:35:18 PDT 2020
  TOKENLIC
  These messages also appear when running the Integrity Checker
  in a fresh 7.6.1.1 MaxDemo database.
  You can replicate the problem in  Maximo 7.6.1.1 and Maximo
  7.6.1.2
  PROBLEM: After running Integrity Checker script the customer
  gets some Warnings
  message about no primary key sequence is defined on the table.
  STEPS TO REPLICATE :
  Run Integrity Checker script in all Maximo Versions 7.6.1.1 and
  7.6.1.2 environment
  CURRENT ERRONEOUS RESULT: When running the integrityui.bat
  (Maximo Integrity Checker) the customers gets some Warnings:
  BMXAA0442W -- Warning - BMXAA0471W -- No primary key sequence
  is defined on the table. Review the table and decide if a
  primary key sequence is required. Tue Jul 28 14:34:57 PDT 2020
     BUDGETRULEPROC
     BUDGETRULEPROCTRANS
     PLUSTDEPSCHEDHISTORY
     REPORTATTACHUNCPATH
     TOKENLICAHIUSERNAME
     TOKENLICUSERNAME
  EXPECTED RESULT: update the tables without erros when integrity
  checker (integrityui.bat) runs.
  ENVIRONMENT (SYSTEM INFO):
  App Server IBM WebSphere Application Server 9.0.0.7
  Version
  Tivoli's process automation engine 7.6.1.1-IFIX20200522-1523
  Build 20190514-1348 DB Build V7611-365 HFDB Build HF7611-13
  IBM Maximo Asset Management Work Centers 7.6.0.4 Build $build$
  DB Build V7604-119
  IBM Maximo Asset Management Scheduler 7.6.7.3 Build
  20190514-1348 DB Build V7673-78 HFDB Build HF7673-12
  IBM Tpae Integration Framework
  7.6.1.1-MIF_7611_IFIX.20200504-1653 Build 20190422-1259 DB
  Build V7611-01
  IBM Maximo Asset Management 7.6.1.1 Build 20190514-1348 DB
  Build V7611-01
  IoT Connection Utility 7.6.0.2 Build 20190426-2206 DB Build
  V7602-07
  Server OS Windows Server 2016 10.0
  Server DB Microsoft SQL Server 13.0 (13.00.5622)
  

Local fix

• NA
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Administrator users                                          *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Integration checker shows warning                            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• Fixed in Release 7613
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Modules/Macros

• MAXIMO
  

Fix information

• Fixed component name

  SYSTEM CONFIG

• Fixed component ID

  5724R46S1

Applicable component levels