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

PWXEDM
177535
W

Persistent outstanding UOW
urid
.
data_sharing_member_id
found at
rba_or_lrsn
.
data_sharing_member_id
.
sequence_number
During statistics processing, the DB2 ECCR produces a list of outstanding UOWs in the same format as in the URID command output. The ECCR examines each outstanding UOW to determine how long it has been outstanding. If any UOW has been outstanding for the entire statistics interval, as specified at ECCR startup in the STAT command, the ECCR issues this message to warn that the UOW has been outstanding a long time. This situation might occur if the ECCR missed the completion of the UOW. This message includes the DB2 URID for the outstanding UOW.
Processing continues.
If the outstanding UOW persists, examine the output from the DB2 ECCR and DB2 subsystem to determine why the UOW has not completed. You can run the DB2 DSN1LOGP utility, or equivalent, to determine if the UOW is really outstanding. If you cannot determine the reason why the UOW is outstanding, contact Informatica Global Customer Support.

0 COMMENTS

We’d like to hear from you!