To initiate ARTIMPP/ARTIBMP/ARTIGW transaction/application performance data and analysis, do the following:

• Enable performance tracing

  Add the UBBCONFIG file -V option for ARTIMPP/ARTIBMP/ARTIGW to enable performance tracing for the server, or use the IMS_PERF_ENABLE environment variable as a global switch for performance tracing.

  If IMS_PERF_ENABLE is set,it takes precedence over UBBCONFIG file setting.

  Note:

  If performance and debug tracing are set at the same time, debug tracing is automatically disabled.
• Performance trace data location

  If IMS_TRACE_PATH is defined, the performance trace is located at $IMS_TRACE_PATH. If IMS_TRACE_PATH is not defined, the performance trace is located at $APPDIR/log.

  The performance trace names are defined as follows:

  • perf.mpp.trace.$pid: for MPP
  • perf.bmp.trace.$pid: for BMP
  • perf.gw.trace.$pid: for GW

  Tip:

  Clear all previously generated performance trace files before initiating performance tracing.

  The File system will cache data for a while before writing to the trace file. For large amounts of data, if you want to get the complete trace, you must wait and then shutdown the Oracle Tuxedo domain (or just the IMS server), so the file system can flush data to the trace file.

• Using analysis tool

  Use the imsperf tool (located at IMS_RT/bin to get transaction/application performance reports as follows:

  imsperf [-d path]

  path is where the performance trace is located.

  Its output is the performance analysis results (tranname.csv, appname.csv), which can be opened directly in CSV format.