IJ25972: SEARCH NOT WORKING FOR LOOKUP OF CUSTOM TENANT FIELD FORM LIST TAB. WORKS FROM MAIN FORM

APAR status

• Closed as program error.

Error description

• ERROR DESCRIPTION:Ø
  Problem Description:
  When new attribute and look up added it works on SR main tab,
  but not from List Tab.
  
  STEPS TO REPRODUCE:
  Make sure there is a TICKET_EXT created, if not create that
  first under GA tenant in DBCONFIG.
  1. Login as maxadmin to IBMNA tenant
  2. In Database Information application add new field WTRS_SRTYPE
  -Description: SR Type
  -TYPE: ALN Length: 50
  3. Add Lookup Map for both
  -Target Attribute: WTRS_SRTYPE
  -Source Object: ALNDOMAIN
  -Source Key: Value
  -Sequence 1
  4. Create ALNDOMAIN called SRTYPE
  Add Values RSK1 and RSK2
  5. In application Designer open SR application and add SR Type
  (Textbox)field (WTRS_SRTYPE) to Main form and List Tab(Table
  Column) In Look up field add SRTYPE save the SR app.
  6. Export Lookups.xml and add
  in LOOKUPS.xml
  <table id="srtype" inputmode="readonly" selectmode="single"
  mboname="ALNDOMAIN"
  whereclause="domainid='SRTYPE'">
  <tablebody displayrowsperpage="20" filterable="true"
  filterexpanded="true"
  id="alndomain_lookup_tablebody1">
  <tablecol dataattribute="value"
  id="alndomain_lookup_tablebody1_col_0"
  mxevent="selectrecord" mxevent_desc="Go To %1" sortable="true"
  type="link"/>
  <tablecol dataattribute="description"
  id="alndomain_lookup_tablebody1_col_1" mxevent="selectrecord"
  mxevent_desc="Go To %1"
  sortable="true" type="link"/>
  </tablebody>
  </table>
  Save and reimport.
  7. Open SR application and insert new SR. In SR Type field open
  lookup and add RSK1 and Save. that works
  8. On List Tab open the look up for SR Type field. Select RSK1
  then click the find.
  You get
  
  BMXAA6713E - The MBO fetch operation failed in the mboset with
  the SQL error code -206. The record could not be retrieved from
  the database. See the log file for more details about the error.
  
  You can manually enter and tab out, just not select from lookup.
  
  Also retried the above and changed out the List Tab attribute
  to TICKET_EXT.ALN1 in that case you get
  BMXAA4107E - Because of an implementation or customization
  problem, the system cannot determine how the attributes of
  object TICKET_EXT correspond to the attributes
  DOMAINID,VALUE,SITEID,ORGID
  of object ALNDOMAIN. You might need to populate the
  MAXLOOKUPMAP table and restart the server.
  
  If you do not use Look up and just type in RSK1 it works for
  TICKET_EXT.ALN1
  
  CURRENT ERRONEOUS RESULT:
  BMXAA6713E - The MBO fetch operation failed in the mboset with
  the SQL error code -206. The record could not be retrieved from
  the database. See the log file for more details about the error.
  from log
  BMXAA6714E - The data for the next record in the mboset could
  not be retrieved for the SQL query select * from SREXT_2001 sr
  where (aln1 = 'RSK1') order by ticketid for read only. See the
  log file for more details about the error.
  com.ibm.db2.jcc.am.SqlSyntaxErrorException: DB2 SQL Error:
  SQLCODE=-206, SQLSTATE=42703, SQLERRMC=ALN1, DRIVER=3.69.71
  OR
  BMXAA4107E - Because of an implementation or customization
  problem, the system cannot determine how the attributes of
  object TICKET_EXT correspond to the attributes
  DOMAINID,VALUE,SITEID,ORGID
  of object ALNDOMAIN. You might need to populate the
  MAXLOOKUPMAP table and restart the server.
  
  EXPECTED RESULT:
  You can find SR from List and no error occurs
  
  Product Version:
  Version Tivoli's process automation engine 7.6.1.1 Build
  20190514-1348 DB Build V7611-365 MT DB Build V7611-8
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * Any users who is doing lookup on customer filed              *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Code was checking column name instead of the extended        *
  * attribute name                                               *
  ****************************************************************
  

Problem conclusion

• Fi code to use correct attribute name
  

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

  SYSTEM CONFIG

• Fixed component ID

  5724R46S1

Applicable component levels