JR32595: ODBC CC JOBS WITH GENERATED SQL FAILING WITH "PARTITIONING TRANGE TOO NARROW"

APAR status

• Closed as program error.

Error description

• In the ODBC Connector jobs running in read mode, when the
  partitioned reads is enabled, and the partitioning type is set
  to Min/Max, the job abort with the following failure messages.
  
  "Partitioning trange too nerrow (0, 0)
  

Local fix

• This fix is included in 8.0.1 fixpack 3
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Users using the Partitioned Reads functionality in the ODBC
  Connector.
  ****************************************************************
  PROBLEM DESCRIPTION:
  In the ODBC Connector jobs running in read mode, when the
  
  partitioned reads is enabled, and the partitioning type is set
  
  to Min/Max, the job abort with the following failure messages.
  
  
  "Partitioning trange too nerrow (0, 0)
  
  ****************************************************************
  RECOMMENDATION:
  Apply the APAR.
  ****************************************************************
  

Problem conclusion

• Added the required functions in the connector code to get the
  min/max range correctly.
  

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

  WIS DATASTAGE

• Fixed component ID

  5724Q36DS

Applicable component levels

• R801 PSN

     UP