You were redirected to the closest matching page. If this looks correct, please consider bookmarking it for future reference.

Table of Contents

Search

  1. Preface
  2. DTL0001 to DTL5008
  3. DTL58001 to DTL62569
  4. PWXEDM172000 to PWXEDM173002
  5. PWXEDM175000 to PWXEDM175050
  6. PWXEDM176400 to PWXEDM177699
  7. PWXEDM181200 to PWXEDM181599
  8. PWXEDM261000 to PWXEDM263999
  9. Abend, Return, and Reason Codes in PowerExchange Messages

Message Reference Volume 3

Message Reference Volume 3

PWXEDM 172653 E

PWXEDM
172653
E

Logger log read error DSName=
dsname
, LogRBA=
log_RBA
, RC=
return_code
The PowerExchange Logger offload processor encountered an error while attempting to read the specified active log data set.
If the error occurred during the offload process, the offload processor tries to read the RBA range from a second copy.
  • If a second copy does not exist, the offload processor stops the active log data set.
  • If the second copy also has an error, the processor stops only the original data set that triggered the offload. The archive log data set ends, which leaves a gap in the archived log RBA range. The PowerExchange Logger issues message PWXEDM172654E.
  • If the second copy is satisfactory, the offload processor does not stop the first copy.
If the error occurred during restart, the PowerExchange Logger ends. A restart requires all copies of the active log data set to be available to the PowerExchange Logger.
If the active log data set has been stopped and is no longer used for logging, the data set is not deallocated. The PowerExchange Logger continues to use it for reading.
Check the system messages, such as IEC prefixed messages. Try to resolve the problem by using the recommended actions in those messages.
Alternatively, write a program to archive as much of the stopped active log data set as possible. Then, run the change log inventory utility to notify the emergency restart data set (ERDS) of the new archive log and log RBA range.
When you receive this message, the data set can be stopped or not stopped. In either case, replace any active log data set that gives persistent errors of this type.
Repairing the stopped active log does not solve this problem because the offload processor does not go back to unload the stopped log. You must run the offload process and reestablish a valid active log.

0 COMMENTS

We’d like to hear from you!