IBM Support

Binary map trace files in Transformation Extender, V9.0.0.2

Product Documentation


Abstract

With Transformation Extender version 9.0.0.2, you can create map trace files in binary or text format. Binary trace files reduce the trace file size and the time it takes for the trace to run. ASSERT messages in the binary trace file indicate which data type (from the type tree) Transformation Extender is validating.

Content


The new Format option in the Map Designer map settings (Map Settings > MapTrace > Format) creates a map trace file in text or binary format. The new Unique file name option (Map Settings > MapLocation > FileName) creates a unique name for a map trace file in either text or binary format. Unique trace file names have the format:

    Mer_mapname_processKey_mapCounter_hostname.mtr

The dtxmaptrace utility converts a map trace file from binary format to text format. On a non-z/OS system, use the dtxmaptrace –toascii option to convert a binary trace file that was created on a z/OS system. When the z/OS trace file is converted to text, the –toascii option changes the character encoding from EBCDIC to ASCII, so that the file is readable on the non-z/OS system.

The B and U options of the MapTrace (-T) execution command create a binary trace file or a trace file with a unique name.

The map object properties of the TX Programming Interface support unique trace file names and binary trace files.

[{"Product":{"code":"SSVSD8","label":"IBM Transformation Extender"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"Not Applicable","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"},{"code":"PF035","label":"z\/OS"}],"Version":"9.0.0.2","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
08 August 2018

UID

swg27049845