IO07031: IF THE LOG4J LOG MANAGER IS SET IN CMBLOGCONFIG.PROPERTIES, THENTHERE IS NO LOGGING OF ENVIRONMENT INFO AT APPLICATIN STARTUP.

APAR status

• Closed as program error.

Error description

• This problem involves the behaviour of DB2 Information
  Integrator for Content logging when the log4j log manager is
  used versus when the Default log manager is used.
  
  If, in cmblogconfig.properties, the log manager is set
  to the Default log manager
  (that is, DKLogManagerFactory
  = com.ibm.mm.sdk.logtool.DKLogManagerFactory_default
  )
  then when Information Integrator for Content logging is
  started for an application that uses the APIs of Information
  Integrator for Content, environment information *is* logged,
  
  However, if, in cmblogconfig.properties, the Log
  Manager is set to Log4J
  (that is,
  DKLogManagerFactory =
  com.ibm.mm.sdk.logtool.DKLogManagerFactory_Log4J
  )
  
  then when Information Integrator for Content logging is
  started for an application that uses the APIs of Information
  Integrator for Content, environment information is *not* logged,
  
  The behaviour should be that when either log manager is used
  (the Default log manager or the log4J log manager), when
  Information Integrator for Content logging is started for an
  application that uses the APIs of Information Integrator for
  Content, environment information is logged.
  

Local fix

• Use the Default Log Manager
  

Problem summary

• If the LOG4J Log manager is set in cmblogconfig.properties, then
  there is no
  logging of environment information at application startup.
  

Problem conclusion

• Log environment information at application startup.
  

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

  CM CONNECT V8

• Fixed component ID

  5724B43A1

Applicable component levels