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 172681 E

PWXEDM
172681
E

Logger RESOLVE_INDOUBT {COMMIT|ABORT} for UOW
uow_ID
failed at
date
time
(
error_type
)
A PowerExchange Logger for z/OS RESOLVE_INDOUBT COMMIT or ABORT command failed at the specified data and time. In this message, the
error_type
is one of the following values:
  • UOW not found
    . The PowerExchange Logger did not find the specified UOW.
  • ECCR=
    eccr_name
    . The PowerExchange Logger found the specified UOW, but the name of the ECCR that is associated with the UOW is incorrect.
  • Gbl Queue error
    . An error occurred while PowerExchange was attempting to write a command notification to the PowerExchange Logger input queue.
  • Pkt Queue error
    . The UOW information could not be added to the PowerExchange Logger internal queue.
  • EDMLLLG0 error
    . An error occurred while the EDMLLG0 module was processing the command.
The RESOLVE_INDOUBT command fails, but PowerExchange Logger processing continues.
If the UOW was not found, verify that the UOW ID specified in the RESOLVE_INDOUBT command matches the UOW ID shown in the DISPLAY OBJ=CONN,TYPE=UOW command output. If the ECCR name was incorrect, verify that the correct ECCR name is specified in the RESOLVE_INDOUBT command. After you correct either error, run the RESOLVE_INDOUBT UOW command again. If the problem persists, contact Informatica Global Customer Support.
If another error type caused the failure, contact Informatica Global Customer Support.

0 COMMENTS

We’d like to hear from you!