JR45195: A JOB INSTANCE ID MAY BE OMITTED FROM THE DATASTAGE JOB LOG VIEW(CTRL-L) WHEN OPERATIONAL METADATA IS BEING GENERATED

IBM InfoSphere Information Server, Version 9.1.2
Download REST API Rollup Patch for Information Server DataStage

APAR status

• Closed as program error.

Error description

• A Job's instance id may be omitted from the DataStage Designer's
  Job log view (ctrl-L) when operational metadata is being
  generated.
  
  This behavior occurs when a multi-instanced Job in run initially
  without an instance id followed immediately by running it again
  with an instance id. However, viewing the same log through the
  DataStage Director client shows the instance id correctly for
  both runs.
  

Local fix

• Run the Job using Director.
  

Problem summary

• *************************************************************
  USERS AFFECTED:
  Users running multi-instance jobs from the Designer with the
  Log View enabled.
  *************************************************************
  PROBLEM DESCRIPTION:
  User creates and compiles a multi instance job using
  Designer. The user then runs the Job, via Designer, with OMD
  being generated (General tab of run dialog) and specifies an
  invocation id. Once the job has completed and the user views
  the job log it will show that the invocation id is missing.
  Original APAR said that OMD should be used, but the problem
  only occurs if the Log View is used in the Designer, OMD is
  not necessary.
  *************************************************************
  RECOMMENDATION:
  Apply patch JR45195.
  *************************************************************
  

Problem conclusion

• Apply patch JR45195.
  

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