IJ11277: 7.6.1 INTEGRITY CHECKER REPORTS ERROR BMXAA0494E ON ALL TEXT-BASED COLUMNS

APAR status

• Closed as program error.

Error description

• Integrity Checker reports that every text-based (ALN,UPPER,
  LOWER) Maximo column is defined incorrectly.  For example:
  BMXAA0443E -- Error - BMXAA0494E -- The definition of this
  column does not match the actual column. The native column
  definition does not match the servers metadata. Run the
  Integrity Checker in repair mode.
  BMXAA6841I -- PERSONCAL.SHIFTNUM, Maximo definition is
  UPPER(8), Database column is UPPER(16)
  Integrity Checker no longer considers maxvar VARCHARMULTIPLE,
  which is used to support multi-byte character sets.  If
  VARCHARMULTIPLE=2, then all database columns should be created
  as twice the Maximo-defined length.  .  If VARCHARMULTIPLE=3,
  then all database columns should be created as three times the
  Maximo-defined length.  In the above example,
  VARCHARMULTIPLE=2, length of native column PERSONCAL.SHIFTNUM
  (16) is twice the Maximo-defined length of the column (8), yet
  Integrity Checker reports the column is incorrectly defined.
  
  STEPS TO REPRODUCE:
  Install or upgrade to Maximo 7.6.1.  Run Integrity Checker in
  report-only mode.  Note the thousands of errors that are
  reported.
  
  EXPECTED RESULTS:
  Consistently defined columns should not be reported as errors.
  
  PRODUCT VERSION:
  Maximo Asset Management 7.6.1
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Maximo Users on 761                                          *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * The VARCHARMULTIPLE MaxVar was read incorrectly and not      *
  * defaulted correctly when missing.                            *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply fixpack Release 7.6.1.0 of Base Services, or request   *
  * an interim fix                                               *
  ****************************************************************
  

Problem conclusion

• Fix has been made to correctly read the VARCHARMULTIPLE MaxVar
  and handle cases where the value is missing or not a number.
  
  The fix for this APAR is contained in the following maintenance
  package:
  | release\fix pack\interim fix for Release 7.6.1.0 of Base
  Services
  

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

  UPGRADE PROGRAM

• Fixed component ID

  5724R46UP

Applicable component levels

• R761 PSY

     UP