Table of Contents

Search

  1. Preface
  2. DTL0001 to DTL3004
  3. DTL58001 to DTL62591
  4. PWXEDM172000 to PWXEDM173002
  5. PWXEDM175000 to PWXEDM175648
  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

EDM Logger log read error dsname=
dsname
, logrba=
logrba
, return code is
rc
The PowerExchange Logger off‑load processor encountered an error while attempting to read the active log specified by
dsname
.
The system action depends on when the error occurs:
If the error occurs during the off‑load process, the off‑load processor tries to read the RBA range from a second copy.
  • If a second copy does not exist, the off‑load 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 off‑load. 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 off‑load processor does not stop the first copy.
  • If the error occurs during restart, the PowerExchange Logger ends. During restart, all copies of the active log data set must be available to the PowerExchange Logger.
  • If the active log data set has been stopped, it is no longer used for logging. However, the data set is not deallocated. The PowerExchange Logger continues to use it for reading.
Check any system messages, such as IEC prefixed messages, and attempt to resolve the problem using the recommended actions given in those messages.
Alternatively, you can 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 restart data set (ERDS) of the new archive log and log RBA range.
When you receive this message, the data set may or may not be stopped. In either case, you should replace an active log data set that gives persistent errors of this type.
! Repairing the stopped active log does not solve this problem because the off‑load processor does not go back to unload the stopped log. You must perform the off‑load process and reestablish a valid active log.

0 COMMENTS

We’d like to hear from you!