The sections that follow describe the steps you should take to gather and submit information to IBM Support.

• AIX
  Modify the ics_manager file so that the Java executable command line reads as follows:
  
  exec $JAVA_ICS -verbose:gc -classpath "${CWCLASSES}"...
  
  Verify that verbose:gc messages are logged to the ics_manager.log file.

• Windows
  Modify the start_server.bat file so that the Java executable command line reads as follows:
  
  NaV -verbose:gc -Djava.....%2 %3 %4 %5 2>verbosegc.log
  
  In this example, garbage-collection output is redirected to the verbosegc.log file that is written to in the NaV\jre\ directory.

• AIX
  Enable heap dumps by adding the following environment variables:




 
•  
• Set 1:
  
  export IBM_HEAP_DUMP=true
  export IBM_HEAPDUMP=true
  export IBM_HEAPDUMP_OUTOFMEMORY=true
  export IBM_JAVADUMP_OUTOFMEMORY=true
  export IBM_JAVA_HEAPDUMP_TEXT=true
  
  You can also set the JAVA_DUMP_OPTS variable to explicitly trigger dumps. You can use this variable for any signal or for a specific condition, such as out of memory. Set up the JAVA_DUMP_OPTS variable as follows:
  
  export JAVA_DUMP_OPTS="ONANYSIGNAL(JAVADUMP[n],HEAPDUMP[n])"
  
  where n is the maximum number of heap dumps or Java dumps that can be generated. For example, if n=5 then a maximum of 5 javacores and heap dumps are generated. After that, for any signal, no more dumps are generated. This variable is particularly useful for generating dumps explicitly when an out-of-memory condition is not encountered.
  
  Refer to the Java Diagnostics Guide for more options for using this variable for out-of-memory conditions.
  
  You can enable dumps using variables in Set 1 or using the JAVA_DUMP_OPTS variable. When you use multiple variables, depending on the service refresh versions, the order of processing varies. Refer to the Java Diagnostics Guide for detailed information.
  
  (Optional) To specify the location of the dumps, you can set the variables as follows:
  
  export IBM_HEAPDUMPDIR=alternate_directory
  export IBM_JAVACOREDIR=alternate_directory
  
  You can add the variables to the ics_manager script or to the profile. Restart InterChange Server
  to activate the heap dumps. Check that heap dumps have been activated by running the command kill -3 Interchange_Server_process_ID while InterChange Server is running. The WebSphere InterChange Server process is momentarily interrupted to write the heap dump, but the process is not stopped. A message is logged to the ics_manager.log file that indicates the location of the heap dump.




 
•  
• Windows
  Enable heap dumps by adding the following environment variables:
  
  Set 1:
  
  set IBM_HEAP_DUMP=true
  set IBM_HEAPDUMP=true
  set IBM_HEAPDUMP_OUTOFMEMORY=true
  set IBM_JAVADUMP_OUTOFMEMORY=true
  set IBM_JAVA_HEAPDUMP_TEXT=true
  
  You can also set the JAVA_DUMP_OPTS variable to explicitly trigger dumps. You can use this variable for any signal or for a specific condition, such as out of memory. Set up the JAVA_DUMP_OPTS variable as follows:
  
  export JAVA_DUMP_OPTS="ONANYSIGNAL(JAVADUMP[n],HEAPDUMP[n])"
  
  where n is the maximum number of heap dumps or Java dumps that can be generated. For example, if n=5 then a maximum of 5 javacores and heap dumps are generated. After that, for any signal, no more dumps are generated. This variable is particularly useful for generating dumps explicitly when an out-of-memory condition is not encountered.
  
  Refer the Java Diagnostics Guide for more options for using this variable for out-of-memory conditions.
  
  You can enable dumps using variables in Set 1 or using the JAVA_DUMP_OPTS variable. JAVA_DUMP_OPTS works for all service refreshes of JDK 1.4.2. When you use multiple variables, depending on the service refresh versions, the order of processing varies. Refer to the Java Diagnostics Guide for detailed information.
  
  As an option, you can specify the location of the dumps, as follows:
  
  set IBM_HEAPDUMPDIR=another_directory
  set IBM_JAVACOREDIR=another_directory
  
  You can add the variables to the start_server.bat script or to the Windows environment. Restart InterChange Server to activate the heap dumps. Check that heap dumps have been activated by sending a Ctrl-Break signal in the InterChange Server console window. The WebSphere InterChange Server process is momentarily interrupted to write the heap dump, but the process is not stopped. A message is logged indicating the exact location of the heap dump file.