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

PWXEDM
172642
E

EDM Log allocation error dsname=
dsname
, error status=
reason
The PowerExchange physical logger encountered an error while attempting to allocate the active or archive log data set specified by
dsname
. The status shows the error reason code that the MVS dynamic allocation returns. The log manager actions vary depending on the type of data set involved. The following actions apply to active log data sets:
If the error is encountered during log manager initialization, PowerExchange startup ends.
If two copies of the active log data set are defined, this message appears only once.
For archive log data sets, two copies of the archive log data sets are defined and processing continues on the remaining archive log data set.
Your response varies depending on the type of data set involved and the type of error that occurred.
If you were allocating active log data sets and if the problem occurred during initialization, you can resolve the problem by doing one of the following:
  • Resolve the error associated with the active log data set as indicated by the reason code.
  • Provide another copy of the active log using IDCAMS.
  • Update the restart data set (ERDS) with the PowerExchange Logger batch utility.
  • Restart the PowerExchange Logger.
    For archive log data sets
  • If the problem occurred during allocation with the intent to write the data set, no immediate action is required. However, failure to resolve the SVC99 error (indicated by the reason code) may eventually cause the available space in the active log to be exhausted (DSNJ111E), which may cause all future off-loads to fail due to the same error.
  • If the problem occurred during allocation with the intent to read the data set, the problems are likely MVS dynamic allocation errors. Therefore, perform the following tasks:
    • Determine the cause of the problem using the appropriate MVS system messages and codes, and correct those problems.
    • Use the batch command DELETE_LOG to delete the archive log data set from the restart data set archive log inventory.
    • Use the DEFINE_LOG function to add the data set back into the archive log inventory, pointing to the correct volume and device.

0 COMMENTS

We’d like to hear from you!