This message is issued when a primary active log data set, and a secondary active log data set, if dual logging has been configured for active log data sets) has been found that has been assigned the desired starting RBA, but no active log data set that DOES have that starting RBA is usable. An active log data set that has been assigned this starting RBA is needed because the active log data set or data sets that contained the previous RBA range have become full. The starting RBA that was being looked for is included in the text of the message. Possibly the initialization of the active log data set failed when the PowerExchange Logger was trying to switch to it, in which case message 172642 will have been issued to document the error that occurred.
Or, the active log data set may have become unusable during some previous execution of the PowerExchange Logger, in which case it will have had the status “STOP” when the PowerExchange Logger was started. The status of the active logs can be seen using the PowerExchange Logger DISPLAY command.
The Logger ends abnormally.
Investigate the reason for the failure in the active log data set, using any other messages that may have been issued, along with appropriate operating system documentation, if necessary. You can also issue the PowerExchange Logger DISPLAY command in batch mode to determine the status of all the active log data sets that are defined. See member #DISPLOG in the SAMPLIB data set for sample JCL to do this. It may be possible to delete the active log data set that has been assigned the specified starting RBA, and the corresponding secondary active log data set, if applicable, using the DELETE_LOG command in a batch invocation of the PowerExchange Logger, similar to SAMPLIB member #DISPLOG, in which case the PowerExchange Logger might be able to be restarted. If you cannot correct the problem, contact Informatica Corporation Product Support.
