IJ02859: SEARCH WOS BY LOCATION FAILS DUE TO HIDDEN NON BREAKING SPACES SPECIAL CHARACTERS IN QUERY

Maximo Anywhere 7.6.2.1 Interim Fix 002

APAR status

• Closed as program error.

Error description

• In WorkExecution app you can search WOs by location. When you
  specify any value in "Location" field then search operation
  always fails.
  The problem is in MoutMobileSetLaborName Java class
  It could be compile time problem that you cannot really see
  in the source code but when you use any of java decompilers
  (only for this purpose) you will clearly notice where the
  problem.
  The source is on the Maximo end in:
  com.ibm.tivoli.mobile.oslc.MoutMobileSetLaborName.getWithComplex
  Query(MboSetRemote, String,
  String)
  This is the method which is responsible for constructing proper
  SQL statement.
  When LOCATION search criteria has been specified then this
  class builds where clause which contains invalid SQL
  characters (A) and Maximo to fails to fetch data.
  To see where exactly the problem comes from compare:
  com.ibm.tivoli.mobile.oslc.MoutMobileSetLaborName.getWithComplex
  Query(MboSetRemote, String, String)
  Decompiling the class and we can see the problems, is an core
  side OSLC processing class.
  Location of the class is:
  \IBM\SMP\maximo\applications\maximo\businessobjects\classes\com\
  ibm\tivoli
  [9/28/17 8:54:59:445 CEST] 000009b6 SystemOut     O
  28 Sep 2017 08:54:59:395 [ERROR] [MXServer] [CID-MXOSLC-64]
  select count(*) from ( select * from
  workorder  where (location like   A  '%LOC1%' or exists
  (select 1 from locancestor inner join
  <SNIP>
  com.ibm.db2.jcc.am.SqlSyntaxErrorException: An unexpected token
  "'%LOC1%'" was found following "(location like  A ".  Expected
  tokens may include:  "space".. SQLCODE=-104, SQLSTATE=42601,
  DRIVER=4.11.69  at com.ibm.db2.jcc.am.gd.a(gd.java:676)
  Note the Special character A getting inserted everywhere.
  The where clause contains invalid SQL characters that result in
  the
  failure to fetch data in Maximo.
  Client has this issue in English environment too.
  STEPS TO REPLICATE:
  1. Open Work Execution and log in
  2. From the Work List view tap "more actions" icon and select
  "Search" actions
  3. Enter any value in "Location" field and tap "Search" button
  Expected result:
  Work Orders matching Location search criteria listed
  Actual result:
  - Application reports following error to the user: The work
  list could not be downloaded because your device is not
  connected to the network.
  - No records displayed
  - Application logs error to the console
  - Maximo reports SQL error
  ENVIRONMENT:
  OS: Windows 2012 R2 (applicable to all components)
  Websphere: WebSphere Application Server 8.5.5.8
  MobileFirst: 7.1.0.00-20160726-1659
  DB: DB2 10.5
  PRODUCT VERSION:
  IBM Maximo Anywhere 7.6.2.0 Build 20170812_011458-0500 DB Build
  V7620-04,
  Tivolis process automation engine 7.6.0.7 Build 20170215-0100
  DB Build V7607-14,
  IBM TPAE Integration Framework 7.6.0.7 Build 20170130-1250 DB
  Build V7607-03,
  TPAE OSLC Object Structure 7.6.2.0 Build 20170812_011444-0500
  DB Build V7620-02,
  IBM Maximo Asset Management Scheduler 7.6.4.0 Build
  20170215-0100 DB Build V7640-53,
  IBM Maximo for Service Providers 7.6.3.0 Build 20170221-2101 DB
  Build V7630-21,
  IBM Maximo Asset Management Work Centers 7.6.0.1 Build
  20161104-1046 DB Build V7601-41,
  Coor Maximo Customizations 2.5.0.0 Build r2885 DB Build
  V7600-00,
  IBM Maximo Asset Management 7.6.0.7 Build 20170215-0100 DB
  Build V7604-01
  

Local fix

• Dev to provide fix
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * all                                                          *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * SEARCH WOS BY LOCATION FAILS DUE TO HIDDEN NON BREAKING      *
  * SPACES SPECIAL CHARACTERS IN QUERY                           *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• Fixed
  

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

  ANYWHERE APPS

• Fixed component ID

  5725M39MA

Applicable component levels