Expected messages

These are the normal messages that you should expect from each component involved in OMEGAMON® Data Provider. If attributes are not arriving at a destination analytics platform, but there are no obvious errors, then use these messages as a checklist to diagnose the problem.

A missing expected message indicates a problem. However, the cause of the problem is not necessarily at the point in processing where the message should occur. The cause might be upstream.

Components and their messages are presented here according to the direction of flow of attributes: from collection tasks, to OMEGAMON Data Broker, and then to OMEGAMON Data Connect. The actual chronological order of some messages can differ from the order presented here.

Tip: Solving a problem upstream can solve multiple problems downstream. Investigate missing messages in the order presented here.

Messages from OMEGAMON Data Provider might be interleaved with messages from other sources, such as the operating system, a related component, or a supporting software framework. For example:

  • The STDOUT file for OMEGAMON Data Connect includes messages from the Spring framework.
  • The SYSPRINT output data set of the Zowe™ cross-memory server includes ZWE-prefix messages from the server that are not specific to the OMEGAMON Data Broker plug-in.

Collection tasks

The RKLVLOG output data set of each monitoring agent job (for example, job names OM*) should contain the following messages.

Message Description
KAYL0005I KPQHSTxx: BROKER NAME = 'value'

Echoes the value of the broker.name key in the RKANPARU(KAYOPEN) configuration member.

If this message is missing, check that your OMNIMON Base component meets the required APAR level for OMEGAMON Data Provider. For details, see Prerequisites for OMEGAMON Data Provider.

KAYL0005I KPQHSTxx: PCODE='product', TABLE='table_name', INTERVAL=interval, DEST={destinations}

Echoes each entry under the collections key in RKANPARU(KAYOPEN).

If this message is missing for a table, check that there is a corresponding entry for the table under the collections key.

KPQH037I KPQHSMGR: TABLE product.table_name HAS BEEN CONNECTED TO PDS

Reports the first instance of a record for each table written to the PDS.

This message is written only for tables that are explicitly specified under the collections key. If RKANPARU(KAYOPEN) does not explicitly specify a table, then the default behavior is to write records from the table to PDS without reporting this message.

If this message is missing for a table, see Attributes not arriving at OMEGAMON Data Broker or PDS.

KPQH038I KPQHSMGR: TABLE product.table_name HAS BEEN CONNECTED TO BROKER

Reports the first instance of a record for each table sent to OMEGAMON Data Broker.

If this message is missing for a table, see Attributes not arriving at OMEGAMON Data Broker or PDS.

OMEGAMON Data Broker

The SYSPRINT output data set of the Zowe cross-memory server job that runs OMEGAMON Data Broker (for example, job name KAYSIS01) should contain the following messages.

Message Description
KAYB0005I CIDB starting, version (APAR apar_number, build_time_stamp)

Reports that OMEGAMON Data Broker is starting. Also reports the OMEGAMON Data Broker version and APAR number.

Some messages use the term CIDB. CIDB is an abbreviation of Common Intercept Data Broker. CIDB is a synonym for OMEGAMON Data Broker.

KAYB0009I Init step 'CIDB anchor initialization' done Normal initialization message.
KAYB0016I No CIDB ID has been provided

Normal initialization message.

OMEGAMON Data Provider users do not need to provide this ID.

KAYB0016I Forwarder subsystem component is on Corresponds to the OMEGAMON Data Broker configuration parameter KAY.CIDB.FWD=ON.
KAYB0009I Init step 'Load CIDB parameters' done
KAYB0009I Init step 'CIDB global area initialization' done
KAYB0009I Init step 'CIDB ID generation' done, ID = 'cidb_id'
KAYB0009I Init step 'CIDB store manager creation' done
KAYB0020I Store 'store_name' has been added
KAYB0009I Init step 'User defined store creation' done
KAYB0009I Init step 'Forwarder subsystem initialization' done
Normal initialization messages.
KAYB0036I Store 'store_name' has connected to sink host:port OMEGAMON Data Broker has connected to OMEGAMON Data Connect.
KAYB0009I Init step 'Forwarder subsystem startup' done
KAYB0006I CIDB successfully started
Normal initialization messages.

OMEGAMON Data Connect

The STDOUT file of OMEGAMON Data Connect should contain the following messages.

General messages, regardless of which outputs are enabled:

Message Description
KAYC0026I Creating JSON mapping provider Normal initialization message
KAYC0023I Starting TCP input service listening on hostname:port OMEGAMON Data Connect has started listening on hostname:port for TCP input from OMEGAMON Data Broker.
KAYC0028I Source hostname:port has connected The instance of OMEGAMON Data Broker that is at hostname:port has connected to OMEGAMON Data Connect.
KAYC0038I Starting console listener OMEGAMON Data Connect has started listening for console commands. For example, z/OS® MVS™ system MODIFY commands.
KAYC0035I Build: build_identifier Reports the OMEGAMON Data Connect build identifier.
KAYC0067I Framework version = connect_framework_version Identifies the version of the OMEGAMON Data Connect framework that was used to build the OMEGAMON Data Connect core JAR file, odp-server-version.jar.
KAYC0068I Extension file jar_file_path found (spec=framework_version, impl=mapping_extension_version) OMEGAMON Data Connect reports this message for each mapping extension JAR file that it finds in the directories that are listed in the OMEGAMON Data Connect runtime option -Dodp.ext.
KAYC0069I class_count mapping classes found in jar_file_path OMEGAMON Data Connect reports the number of mapping classes it finds in each mapping extension JAR file.
KAYC0008I Creating mapping class for table table_name Indicates the first instance of a record received for this table.
KAYC0033I Table table_name received from origin_type origin_name

Indicates the first instance of a record received for this table from this origin.

The origin type depends on the table. Examples: sysplex, CICS region.

KAYC0036I filter_scope filter selected table: table_name, fields: field_list

OMEGAMON Data Connect has been configured to filter records of this table.

If STDOUT output is enabled:

Message Description
KAYC0024I Starting STDOUT output service Normal initialization message.

If TCP output is enabled:

Message Description
KAYC0009I Starting TCP output service Normal initialization message.
KAYC0042I Starting TCP sink: sink_name {host: hostname, port: port}
KAYC0010I Connecting to TCP sink: sink_name {host: hostname, port: port}
KAYC0011I Connected to TCP sink: sink_name {host: hostname, port: port}
Normal initialization messages for each sink.

If HTTP output is enabled:

Message Description
KAYC0076I Starting HTTP output service Normal initialization message.
KAYC0078I Starting output to HTTP endpoint: endpoint_name {url: url}

Normal initialization message for each endpoint.

If Prometheus output is enabled:

Message Description
KAYC0018I Starting metrics service Normal initialization message.
KAYC0037I Registered metric for table: table_name, field: field_name, type: metric_type, labels: [label_list]

Normal initialization message for each metric.

If Kafka output is enabled:

Message Description
KAYC0025I Starting Kafka output service Normal initialization message.

When OMEGAMON Data Connect stops:

Message Description
KAYC0034I Stopping server
KAYC0027I Stopping TCP listener
KAYC0029I Source hostname:port has disconnected
Normal shutdown messages.
KAYC0032I Stopping TCP output service If TCP output was enabled.
KAYC0043I Stopping TCP sink: sink_name {host: hostname, port: port} For each TCP output sink.
KAYC0077I Stopping HTTP output service If HTTP output was enabled.
KAYC0081I Stopping output to HTTP endpoint: endpoint_name {url: url} For each HTTP output endpoint.