IMS Connect Extensions feed fields

Categories are descriptive only

The Category column in the previous table groups fields according to the nature of the information they contain about a transaction. These categories exist for documentation purposes only, to help you select fields that are of interest to you.

Field output order

The previous table does not reflect the order of fields in the feed JSON Lines output.

Each line of the feed JSON Lines output contains fields in the following order:

1. time
2. type
3. Remaining field names in alphabetical order

The time and type fields are always included

Each line of the feed JSON Lines output always begins with a time field followed by a type field:

{"time":"2018-11-01T15:25:03.123456Z","type":"ims-ca20",… }

Do not specify time or type in the FIELDS parameter.

Field names

In general, the feed field names match IMS Connect transaction index field names, with the following variations and exceptions:

• The field names in the feed JSON Lines output are all lowercase.
• The time field in the feed corresponds to the starttime field in an IMS Connect transaction index.
• The type field has no corresponding field in an IMS Connect transaction index.
• The fields that you can specify in the FIELDS parameter are a subset of the IMS Connect transaction index fields.

Some feed fields match form fields in IBM® IMS Performance Analyzer for z/OS®. For more detailed descriptions of these fields, see the IMS Performance Analyzer documentation.

Fields with parent fields

Fields in the previous table with a Parent field are either flag bits or flag byte values. In the feed JSON Lines output, these fields have the boolean value true or false.

The Parent field column makes it easier to find these child fields when browsing IMS Connect transaction index records in IBM Transaction Analysis Workbench for z/OS or IBM IMS Problem Investigator for z/OS. You browse a record, and then select a parent field to browse its child field values.

Elapsed time values

Elapsed time field values are represented as a number of seconds to microsecond precision; six decimal places.

Fields with hexadecimal values

Some fields, such as computer-generated identifiers or correlation tokens, are represented as a string of hexadecimal digits. Each pair of digits represents a byte. For example, the 4-character string value "10FF" represents a sequence of two bytes, decimal values 16 and 255.

Elapsed time fields that cannot be calculated are omitted

Elapsed times are typically calculated from the difference between event time stamps. If an event that is required to calculate an elapsed time did not occur or was not collected, then the elapsed time cannot be calculated. Rather than including a bogus value, such as 0.0, which might skew statistics for the field, the feed omits the field. The line of JSON for that transaction does not include a property for that field.

Empty string fields are omitted

If a string field value is empty (), the feed omits the field. The line of JSON for that transaction does not include a property for that field.

Collection level can determine whether a field has a value

The LEVEL configuration parameter of the feed job specifies the IMS Connect Extensions collection level. The collection level controls which events the feed collects.

Some fields, such as some elapsed time fields, rely on events that are only collected at a certain minimum collection level. For details, see Events recorded by IMS Connect Extensions.