JR31806: DATASTAGE LOGGING CHANGES INTRODUCED AT RELEASE 8.1 CAN IMPACT PERFORMANCE AND CAN ALSO RESULT IN MISSING LOG ENTRIES.

APAR status

• Closed as fixed if next.

Error description

• DataStage logging was changed at release 8.1 to log job run
  detail records into the operational repository, (xmeta) rather
  than the local project level log files, (RT_LOGxxx) that we
  utilized in prior releases for each job. As a result of this
  change we have seen the following issues:
  
  Job run times can increase and Information Server client
  applications may not be as responsive depending on the amount of
  log data that is generated by the jobs.
  
  In some cases no job log entries are written to the log as
  viewed via the DataStage Director client or Web Console, even
  though jobs appear to run and in some cases job log detail
  entries may be missing or do not show up until later.
  
  Job log purge operations may run slowly or fail depending on the
  amount of log entries.
  

Local fix

• These issues can be worked around by reverting to the logging
  mechanism that was in place prior to release 8.1 by implementing
  the following project level changes on the DataStage engine
  server.
  
  Edit the project level DSParams file, typically located in
  /opt/IBM/InformationServer/Server/Projects/%projectName% for
  Linux/UNIX and
  C:\IBM\InformarmationServer\Server\Projects\%projectName% for
  Windows and modify the following 2 lines as shown to revert to
  pre 8.1 logging:
  
  RTLogging=1
  ORLogging=0
  
  Keep in mind that newly created projects inherit their settings
  from the DSParams file that is located in
  /opt/IBM/InformationServer/Server/Template/DSParams for
  Linux/UNIX and C:\IBM\InformationServer\Server\Template\DSParams
  by default and that it should also be modified to ensure that
  new projects use the pre 8.1 logging mechanism.
  
  The old log entries can still be viewed via the Web Console or
  Server Console but will not be accessible using the DataStage
  Director.
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  DataStage logging changes introduced at release 8.1 can impact
  performance and can also result in missing log entries.
  ****************************************************************
  PROBLEM DESCRIPTION:
  DataStage logging was changed at release 8.1 to log job run
  detail records into the operational repository, (xmeta) rather
  than the local project level log files, (RT_LOGxxx) that we
  utilized in prior releases for each job. As a result of this
  change we have seen the following issues:
  
  Job run times can increase and Information Server client
  applications may not be as responsive depending on the amount
  of log data that is generated by the jobs.
  
    In some cases no job log entries are written to the log as
    viewed via the DataStage Director client or Web Console, even
    though jobs appear to run and in some cases job log detail
    entries may be missing or do not show up until later.
  
    Job log purge operations may run slowly or fail depending on
    the amount of log entries.
  
  ****************************************************************
  RECOMMENDATION:
  These issues can be worked around by reverting to the logging
  mechanism that was in place prior to release 8.1.
  
  Refer to this technote for further details on this work-around:
  
  http://www-01.ibm.com/support/docview.wss?rs=14&context=SSZJPZ&d
  c=D600&uid=swg21370048&loc=en_US&cs=utf-8&lang=en
  ****************************************************************
  

Problem conclusion

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

Applicable component levels

• R810 PSN

     UP