Creating a z/OS system logger log stream
Event Logger requires a z/OS system logger log stream to be defined. You can define one of the following two types of log streams:
Coupling Facility Structure log streams | You must use the Coupling Facility Structure log stream option if more than one BMC application is writing to the log stream on more than one system in a Sysplex. Event Logger merges the log stream data from multiple systems in the Coupling Facility Structure and eventually offloads the data to an offload data set. During the offload processing, in a Coupling Facility Structure log stream, space gets freed up for reuse incrementally. This allows applications to continue writing to the log stream while an offload is progressing. |
DASD-only log streams | DASD-only log streams support multiple applications writing to the log stream simultaneously, provided they are on the same system. In a DASD-only log stream, space occupied by log data does not get freed up until an offload has completed. The Offload process must be complete before Event Logger can use the freed space for new records. |
Recommended log stream parameters and values
BMC recommends that you use the following log stream parameters with the values specified:
Parameter | Description | Recommended value |
|---|---|---|
DASDONLY | Specifies use of a Coupling facility logstream, or DASD only. BMC recommends NO. | NO |
STG_SIZE | Staging data set size. | 150 |
LS_SIZE | Offload data set size. | 150 |
LOWOFFLOAD | Specifies when the logger stops offloading the CF records to the offload data sets. | 0 |
HIGHOFFLOAD | Specifies when the logger starts offloading the CF records to the offload data sets. | 70 |
AUTODELETE | Specifies when the logger can delete physical data sets. | NO BMC recommends this value, as a cleanup job is separately provided. |
RETPD | Retention period, that is, how long to keep the data sets after all the records in the data set have been deleted. | 0 |
Related topic