When you delete a log data set, allocation errors may result in an “orphaned” log data set — a log data set that should have been deleted but was not. When a log data set is orphaned, system logger issues message IXG252I. System logger frees up the data set's entry in the directory extent in this case, but the data set still consumes storage. If an allocation error occurs when you delete a log stream or when system logger is deleting a log data set, you will need to manually delete the resulting unnecessary log data sets. The orphaned data sets should be deleted using the IDCAMS delete command. Note that when you delete a log stream by deleting it from the LOGR policy, system logger deletes all the log data sets associated with the log stream that have entries in the logger directory. If a data set was orphaned or simply matches the log stream naming convention but is not in the logger directory, then system logger will NOT attempt to delete the data set when the log stream is deleted.

If you suspect you might have possible orphaned data sets that may have previously been associated with a logs tream, use LIST LOGSTREAM NAME(log_stream_name) DETAIL(YES) on the IXCMIAPU utility for DATA TYPE(LOGR).

If you rename log streams using the UPDATE LOGSTREAM NEWSTREAMNAME keyword, offload data sets from a different log stream instance with the same original name might appear as orphaned data sets when viewing the LIST output. Before taking any action on orphaned data sets, determine if any of them are associated with an existing log stream that had been renamed.

See the topic in the output report entitled "POSSIBLE ORPHANED LOG STREAM DATA SETS:" to find any data sets that match the log stream naming convention but are not part of system logger's data set directory for the log stream. For the LIST parameter of IXCMIAPU, see Administrative data utility.