Preparing the Data Collector to collect data in stream mode

Before you configure the Data Collector to collect different data types in stream mode, you must first complete the required setup for the data type. This prepares the Data Collector to collect data in stream mode.

About this task

To prepare the Data Collector to collect data in stream mode, complete the required setup in accordance with the data type as illustrated in Table 1.

Table 1. Prerequisites for configuring the Data Collector in stream mode

Data source type	Prerequisites
SYSLOG	If you configure a z/OS® SYSLOG data stream for gathering z/OS SYSLOG data from a user exit, you must install either the HBOSYSG or HBOMDBG user exit. For more information, see Installing the user exit for collecting z/OS SYSLOG data. If you configure only a z/OS SYSLOG from OPERLOG data stream for gathering z/OS SYSLOG data, the installation of a user exit is not necessary.
SMF	If you are collecting SMF data from an in-memory resource or log stream, see Requirements for collecting SMF data. If you are collecting SMF data from the SMF user exit, see Installing the SMF user exit.
RMF Monitor III report	Requirements for collecting RMF Monitor III report data
IBM Z® NetView® messages	Configuring the z/OS NetView message provider for collecting NetView messages

To send data to Apache Kafka, the Data Collector automatically creates a header topic IBM-CDP-CSV-HEADER to store the headers from the following sources:

• z/OS Resource Measurement Facility (RMF) Monitor III report
• Job log, which is the output that is written to a data definition (DD) by a running job
• z/OS UNIX log file, including the UNIX System Services system log (syslogd)
• Entry-sequenced Virtual Storage Access Method (VSAM)
• z/OS sequential data set
• IBM Z NetView messages
• IBM® WebSphere® Application Server for z/OS High Performance Extensible Logging (HPEL) log