JR43684: FAILED JOB COMPILATION REPORTED AS OK. JOB IS NOT RUNNABLE BECAUSE IT DID NOT ACTUALLY COMPILE.

APAR status

• Closed as program error.

Error description

• For certain job compilation failures, the job compilation
  failure messages are lost and the job is wrongly reported as
  compiled OK. The job will show as not compiled on the Director,
  and it cannot be run on the Director or elsewhere.
  
  This specifically affects those compilation failures which are
  not reported as relating to a particular failed stage.
  

Local fix

• The workaround is to determine the reason for compilation
  failure from serverside tracing.
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Users of DataStage job compilation.
  ****************************************************************
  PROBLEM DESCRIPTION:
  Certain cases of failed job compilation are reported as OK,
  because the error messages are lost during the compilation
  process. The job is not runnable because it is not in the
  compiled state.
  ****************************************************************
  RECOMMENDATION:
  Install the patch on the engine tier
  ****************************************************************
  

Problem conclusion

• Fixed a fault in error handling in the engine tier compilation
  helpers
  

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