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 172779 W

PWXEDM
172779
W

EDM Logger retrying HSPSERV SREAD of block at RBA
rrrrrrrrrrrr
, found RBA
ffffffffffff
For each Log Reader Process (LRP) task that connects to the PowerExchange Logger, there is an associated Log Reader subtask in the PowerExchange Logger that reads the active and archive log data and passes it to the LRP task. Occasionally, after a Logger switches active log data sets, a user abend U3035 occurs in a Log Reader subtask that is reading data from the new active log data set. The abend can either be with reason code 0033FF05, or with reason code 00D6FF14, if fix 300074 is installed. An abend0C4 after label READ1065 in EDMLLRD0 can also occur. The reason for these abends is that an HSPSERV SREAD operation has returned a page containing all zeros, for a page that had previously been read. This is a problem that is described in IBM APAR OW56713. Because there is no fix currently available for APAR OW56713, logic was added to detect the condition, and to retry the HSPSERV SREAD operation, up to 100 times.
Each time the retry is required, message 172779 is issued. The “found RBA” value
ffffffffffff
will most likely be zero. If the condition persists after 100 retries have been done, the Log Reader subtask of the PowerExchange Logger will abend with user abend U3035 and reason code 00D6FF14. This will cause the PAC jobs containing the associated LRP tasks to terminate. However, the PowerExchange Logger address space will NOT terminate, and the PowerExchange Logger will continue writing data to the active log that it receives from ECCRs.
Restart any terminated PAC jobs.

0 COMMENTS

We’d like to hear from you!