PH57914: LAUNCHER TRACE FILE NOT BEING CREATED ITX 11.0 LAUNCHER START WHEN LAUNCHERLOG=EWSC IS ENABLED IN CONFIG.YAML FILE

APAR status

• Closed as program error.

Error description

• Launcher Trace file for the IBM Transformation Extender 11.0.0.0
  Launcher is not created when config.yaml file is edited to
  enable to LauncherLog property by uncommenting the following
  entry:
  
  Commented:
  
  # LauncherLog: "ewsc"
  
  Uncommented:
  
  LauncherLog: "ewsc"
  

Local fix

• ITXCQ - ITX00062175
  PB / PB
  Circumvention: None
  

Problem summary

• Users Affected:
  IBM Transformation Extender users who enable the LauncherLog
  path in config.yaml.
  
  Problem Description:
  Using the new config.yaml interface for ITX 11.0, LauncherLog
  settings were not initialized correctly for the
  CompoundSystem*.txt log file.
  
  Platforms Affected:
  All
  

Problem conclusion

• Fixed the initialization of the LauncherLog.
  
  Applies to:
  11.0.0.0
  
  Fixed in the next service packs and releases.
  
  To obtain the fix for this APAR:
  
  To see if the next service pack or product release is available,
  check the IBM Transformation Extender Release Notes page:
  https://www.ibm.com/support/docview.wss?uid=swg27008337
  
  If the service pack or product release is available, download it
  from Fix Central:
  http://www.ibm.com/support/fixcentral/
  
  If the service pack or product release is not available and you
  require the APAR fix immediately, request a Limited Availability
  Interim Fix (LAIF) by opening a case:
  https://www.ibm.com/mysupport/
  
  Prior to version 9.0.0, IBM Transformation Extender was called
  IBM WebSphere Transformation Extender.
  

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

  ITX

• Fixed component ID

  5724Q2300

Applicable component levels