IJ11104: BDI NULL POINTER EXCEPTION WHEN ATTEMPTING TO VALIDATE AN ASSET

APAR status

• Closed as program error.

Error description

• When attempting to validate an asset that has an
  LCN/Label/Position that does not match the associated model, a
  null pointer exception is logged. A more informative error
  message (eg Asset LCN/Label/Position does not match model
  <model>) would be more informative.
  
  Application effected
  ====================
  Models
  
  Steps to reproduce
  ==================
  
  1) In the Models application create a new Model: TM1.
  
  2) Create 2 Build Items with associated Labels and Part
  Numbers. E.g TBI1 and TBI2.
  
  3) In the Configurations tab change the status of the Base
  Configuration to ACTIVE and mark it as non-abstract.
  
  4) On the Build Hierarchy and Position Rules tab add two new
  build positions to the model for TB1 and TB2.
  
  5) On the "Position List" sub tab select the row for TB2 and
  expand the table row. Untick the checkbox "Skip BDI Checks?"
  
  6) Create a new Aircraft record from this Model using the New
  Aircraft and Equipment application ensuring that the "Create
  Sub Assemblies from CM Build"
  
  action is chosen to create the child equipment records
  corresponding to the TB1 and TB2 build positions.
  
  7) Open the newly create Aircraft record in the Aircraft
  application.
  
  8) In the Aircraft Hierarchy tab expand the top level node and
  select the equipment record in the TB2 position. Right click
  the node and select the "Install/Remove" action.
  
  9) In the Install/Remove dialog click ok to remove the
  Equipment.
  
  10). Open the removed equipment record in the Equipment
  application.
  
  11) In the Equipment Hierarchy tab right click the top level
  node and open the BDI Status dialog.
  
  12) In the BDI Status dialog click Validate Configuration.
  
  Expected Result:
  ================
  
  The BDI log should show that the Equipment is validated but
  with a warning message to state that Skip BDI Checks is enabled
  for this build position that the Equipment is validated against.
  
  Actual Result:
  ===============
  
  Null pointer exception is record in the bdi log file. For
  example:
  
  java.lang.NullPointerException: null
  
   at vrex.VMStatus.validate(VMStatus.java:536) ~[classes/:?]
  
   at vrex.VMStatus.VFBOM(VMStatus.java:245) ~[classes/:?]
  
   at
  v8.V8ServiceRequestHandler.v8stat(V8ServiceRequestHandler.java:5
  10) ~[classes/:?]
  
   at
  v8.V8ServiceRequestHandler.v8stat(V8ServiceRequestHandler.java:3
  60) ~[classes/:?]
  
   at
  v8.V8ServiceRequestHandler.handleRequest(V8ServiceRequestHandler
  .java:186) ~[classes/:?]
  
  Product Version
  ===============
  Tivoli's process automation engine 7.6.0.8-IFIX20180619-1154
  Build 20170512-0100 DB Build V7608-63 HFDB Build HF7608-15
  
  IBM Maximo Asset Management Work Centers 7.6.0.2 Build
  20170509-0906 DB Build V7602-57
  
  IBM Maximo for Aviation 7.6.6.0-20180706-1338 Build
  20170914-0936 DB Build V7660-60 HFDB Build HF7660-62
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Users of Maximo for Aviation and ACM BDI Service.            *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * When attempting to validate an asset that has an             *
  * LCN/Label/Position that does not match the associated model, *
  * a null pointer exception is logged. A more informative error *
  * message (eg Asset LCN/Label/Position does not match model)   *
  * would be more informative.                                   *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Install the interim fix to correct this issue.               *
  ****************************************************************
  

Problem conclusion

• BDI will now log a warning in its log file if it encounters a
  top level asset where the determined model build position has
  the Skip BDI Checks? set to true.
  (PLUSACMBUILD.SKIPBDICHECKS=1).
  

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:

Fix information

• Fixed component name

  MAXIMO FOR AVIA

• Fixed component ID

  5725U8700

Applicable component levels