Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
When DASD log data set space fills z/OS MVS Setting Up a Sysplex SA23-1399-00 |
|
This step applies to both coupling facility and DASD-only log streams. The number of DASD log data sets available for log streams in a sysplex depends on whether you use the default (168 per log stream) or have provided additional directory extents in the LOGR couple data set. See Increasing the space available for DASD log data sets for more information. System logger monitors usage of the available log stream directory
space, notifying you as follows if you start to run out of space:
If you have run out of log stream directory space, off-loads may fail. When this occurs, system logger issues message IXG301I. Offload processing for the log stream cannot complete until more log stream directory space or directory extents are made available. If the last disconnect to a log stream occurs and the offload cannot complete successfully, the log stream is in a failed state. In this case, the log stream is considered 'in use' and there may be a failed-persistent connection to a structure associated with the log stream. You can make more directory space available for a log stream in
one of the ways below. Use the IXCMIAPU utility to run a report of
the log stream definitions in the LOGR couple data set to help you
with this step. The LIST LOGSTREAM NAME(*) DETAIL(YES) statement outputs
information showing which log streams might be using large numbers
of data sets and directory extents. See LOGR keywords and parameters for the administrative data utility for
more information about IXCMIAPU.
|
Copyright IBM Corporation 1990, 2014
|