JR33919: LOCAL MESSAGE HANDLER REMOVED FROM THE JOB WHEN FORCE COMPILE US ED

APAR status

• Closed as program error.

Error description

• Using force compile on the Designer or the Multiple Job Compiler
  causes the local message handler for the job to be deleted.
  

Local fix

• Note that this option is the default on Multiple Job Compile. As
  a workaround, it can be unchecked if not required.
  
  This fix is included in 8.0.1 fixpack 3
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Potentially affects users in all environments
  ****************************************************************
  PROBLEM DESCRIPTION:
  Use of force compile option on the DeataStage Designer or the
  Multiple Job Compiler will cause the job's local message
  handlerto be deleted.
  ****************************************************************
  RECOMMENDATION:
  Customers should apply this patch if they use local message
  handlers and require the "force compile" job compilation
   option.
  This fix is included in 8.1 FP1.
  ****************************************************************
  

Problem conclusion

• Resolution was to fix the uncompile helper option on the server
  so that it preserved the message handler contents, if a message
  handler is found.
  

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:

Modules/Macros

• SERVER
  

Fix information

• Fixed component name

  WIS DATASTAGE

• Fixed component ID

  5724Q36DS

Applicable component levels

• R801 PSY

     UP

• R810 PSY

     UP