PM31981: Renderer expiry date is null should be moved from the SystemOut.log to Trace.log.

6.1.0.6 Download: WebSphere Portal and WCM V6.1.0 fix pack 6
7.0.0.2 Download: WebSphere Portal and WCM V7.0 fix pack 2
Fixes integrated in WebSphere Portal 7.0.0.1 & 7.0.0.2 Combined Cumulative Fixes

APAR status

• Closed as program error.

Error description

• Problem Summary: Changing from info to trace the statement
  RendererModul
  I RendererModule
  T0103: expiry date is null. Setting the expiration date to:
  
  Problem Description:
  When rendering without expire value in connect tag, info
  statement
  writing to the logs:
  RendererModul I RendererModule T0103: expiry date is null.
  Setting the
  expiration date to:
  
  This is something that is normal behavior, but should be moved
  out to be
  a
  trace statement.
  

Local fix

• N/A
  

Problem summary

• Problem Summary: Changing from info to trace the statement
  RendererModul
  I RendererModule
  T0103: expiry date is null. Setting the expiration date to:
  
  Problem Description:
  When rendering without expire value in connect tag, info
  statement
  writing to the logs:
  RendererModul I RendererModule T0103: expiry date is null.
  Setting the
  expiration date to:
  
  This is something that is normal behavior, but should be moved
  out to be
  a
  trace statement.
  

Problem conclusion

• WCM Changed to log trace statement instead of info statement
  

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

  LOTUS WEB CONT

• Fixed component ID

  5724I2900

Applicable component levels

• R61C PSY

     UP

• R610 PSY

     UP

• R615 PSY

     UP