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.
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 are using the DSEXTENT parameter in the LOGR couple data
set system logger issues messages IXG261E and IXG262A indicating that
usage of directory extents is over 85% and 95% respectively.
- If you are using the default number of log data sets allowed for
a log stream (168), system logger issues message IXG257I indicating
that the data set directory for the log stream is over 90% full.
If you have run out of log stream directory space, offloads 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 Parameters for Administrative Data Facility in
z/OS MVS Setting Up a Sysplex for
more information about IXCMIAPU.
- Format another set of LOGR couple data sets with a higher DSEXTENT
value and bringing them into the sysplex as the active primary and
alternate LOGR couple data sets. You must have a LOGR couple data
set to use the DSEXTENT parameter. See Appendix B: Administrative Data Utility in z/OS MVS Setting Up a Sysplex for
the IXCL1DSU utility and the DSEXTENT parameter.
- Free directory extents currently in use in one of the following
ways:
- Use a program that issues the IXGDELET service to delete enough
data from the log stream to free up space in the log stream data set
directory.
Some products provide a program to delete log stream
data. See Deleting Log
Data and Log Data Sets in z/OS MVS Setting Up a Sysplex for information on deletion programs provided for IBM® products.
See the documentation for the product to see if it provides a deletion
program.
- Delete log stream definitions from the LOGR couple data set.
Identify
and delete the definitions for unused or unnecessary log streams.
This will free the directory space associated with the log streams,
which may free up directory extents for use by other log streams.
Note: Deleting DASD log data sets using a non-system
logger method will not work because system logger will still count
the data sets toward the data set directory entry limit. You cannot,
for example:
- Use a TSO/E DELETE command to delete a log data set.
- Use DFHSM to migrate log stream data sets to tape.