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

PWXEDM
172642
E

Log allocation error DSName=
dsname
, error status=
reason_code
The PowerExchange physical logger encountered an error while attempting to allocate the active or archive log data set with the specified data set name. The
status
value is the error reason code that the MVS dynamic allocation returns. The log manager response to the error depends on the type of data set involved.
For active log data sets, the following results can occur:
  • 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.
The user response depends on the type of data set involved and the type of error that occurred.
If you were allocating active log data sets and the problem occurred during initialization, resolve the problem by performing one of the following actions:
  • Resolve the error associated with the active log data set as indicated by the reason code.
  • Provide another copy of the active log by using IDCAMS.
  • Update the emergency restart data set (ERDS) with the PowerExchange Logger batch utility.
  • Restart the PowerExchange Logger.
If you were allocating archive log data sets, respond as follows:
  • 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) might eventually cause the available space in the active log to be exhausted (DSNJ111E). IF the active log becomes full, all future off-loads fail because of 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. In this case, perform the following tasks:
    • Determine the cause of the problem by using the appropriate MVS system messages and codes. Then correct those problems.
    • Use the batch command DELETE_LOG to delete the archive log data set from the ERDS 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!