Logger detected an insufficient number of active logs defined in ERDS.
The PowerExchange Logger for z/OS detected that not enough active log data sets are defined in the emergency restart data set (ERDS) to start logging captured change data. This condition usually exists for one of the following reasons:
Fewer than two data sets are defined for one of the active log copy sets.
The EDMUPARM options module specifies ACTIVE_LOG_MODE=DUAL for dual logging. However, data sets for two copies of the active log are not defined in the ERDS.
Fewer than two data sets are available for one of the active log copy sets. Available data sets are those not flagged as STOPPED.
PowerExchange Logger startup processing ends abnormally.
Use the PowerExchange Logger batch change utility to make the number of active log data sets defined in the ERDS consistent with the ACTIVE_LOG_MODE parameter in teh EDMUPARM module. You might need to recover log data sets that have a status of STOPPED. The PowerExchange Logger does not reuse STOPPED log data sets. To recover these data sets, either redefine them or recover them from the other copy of the log. Also delete the log data sets and add them to the ERDS with the appropriate RBA addresses. To delete and add log data sets to ERDSs, use the Logger batch change utility. When finished, restart the PowerExchange Logger.
