JR30552: CLIENT DOESN'T CODE 2ND RANGE LOOKUP CORRECTLY.

APAR status

• Closed as program error.

Error description

• According to
  the documentation multiple range lookups are supported.
  However as shown in the sample job Range_lookup2a when we add
  second
  range for the lookup, it is ignored and as we already needed to
  allow
  multiple records the number of records is multiplied. The
  generated OSH
  clearly ignores the second lookup. If we change the order of the
  lookup
  the lookup switches accordingly from one to another but never
  together.
  We are unable to find a work around for this.
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Use of multiple range lookups
  ****************************************************************
  PROBLEM DESCRIPTION:
  Multiple range lookups were not supported by the client.
  ****************************************************************
  RECOMMENDATION:
  Apply patch
  This change is included in 8.0.1 Fix Pack 2
  This change is included in 8.1 FP1
  ****************************************************************
  

Problem conclusion

• Added code to support multiple range lookup at client side.
  

Temporary fix

Comments

• This change is included in 8.0.1 Fix Pack 2
  

APAR Information

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

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

Modules/Macros

• CLIENT
  

Fix information

• Fixed component name

  WIS DATASTAGE

• Fixed component ID

  5724Q36DS

Applicable component levels

• R801 PSY

     UP