JR46439: ODBC CONNECTOR EXECUTING AFTER SQL STATEMENTS EVEN WHEN THE JOB ABORTS.

InfoSphere Information Server, Version 11.3 for Microsoft Windows
InfoSphere Information Server, Version 11.3 for AIX
InfoSphere Information Server, Version 11.3 for Linux
IBM InfoSphere Information Server Enterprise Edition V11.3 for Windows

APAR status

• Closed as program error.

Error description

• In the ODBC connector, if a job is configured with some SQL
  statements in the After SQL property, these statements are
  executed even in the case where the job failed when any of the
  player processes failed. Ideally, when the main SQL statement
  generates any failure and the job has to abort, there is no
  reason why the After SQL statements should be executed.
  

Local fix

• N/A
  

Problem summary

• In the ODBC connector, if a job is configured with some SQL
  statements in the After SQL property, these statements are
  executed even in the case where the job failed when any of the
  player processes failed. Ideally, when the main SQL statement
  generates any failure and the job has to abort, there is no
  reason why the After SQL statements should be executed.
  

Problem conclusion

• Do not execute After SQL statements when the job is failing.
  This change has been made under the scope of an environment
  variable CC_ODBC_SKIP_AFTERSQL_ON_FAILURE to insure that there
  is no change in behavior for any of the jobs designed this
  behavior of executing After SQL on job failure
  
  The environment variable (CC_ODBC_SKIP_AFTERSQL_ON_FAILURE)
  needs to be set to 1 in the job / project environment
  

Temporary fix

• There is no known 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

• R850 PSY

     UP

• R870 PSY

     UP

• R910 PSY

     UP