Table of Contents

Search

  1. Preface
  2. PWX-00000 to PWX-00099
  3. PWX-00100 to PWX-00999
  4. PWX-01000 to PWX-01999
  5. PWX-02000 to PWX-04999
  6. PWX-05000 to PWX-06999
  7. PWX-07000 to PWX-09999
  8. Abend, Return, and Reason Codes in PowerExchange Messages

Message Reference Volume 1

Message Reference Volume 1

Reason Codes 001 to 255 - PowerExchange Agent

Reason Codes 001 to 255 - PowerExchange Agent

The PowerExchange Agent issues the following types of reason codes:
  • Messages that display the abend code U0001 also display a related reason code to help you determine the cause of the abend.
  • Other messages display the second type of reason code to help you determine the cause of the error related to that message.
    The following table describes this type of reason code:
    Decimal Reason Code
    Hexadecimal Reason Code
    Explanation
    001
    01
    A private STORAGE OBTAIN failed.
    002
    02
    A private STORAGE OBTAIN for less than 16M bytes failed.
    003
    03
    A common STORAGE OBTAIN failed.
    004
    04
    A common STORAGE OBTAIN for less than 16M bytes failed.
    005
    05
    MVS is not at the required SP level.
    006
    06
    A RACROUTE AUTH call failed.
    007
    07
    An AUTH call, which is not a RACROUTE AUTH call, failed.
    008
    08
    An internal logic error occurred in the module that is calling the PowerExchange Agent. It did not send the correct password key.
    009
    09
    The required PowerExchange subsystem data space does not exist.
    010
    0A
    The PowerExchange subsystem could not be found.
    011
    0B
    A subsystem was found, but it is not an PowerExchange subsystem.
    012
    0C
    An attempt to load the EDMSDIR module failed.
    013
    0D
    The EDMXCIRQ circular queue returned an error.
    014
    0E
    The global queue does not exist.
    015
    0F
    The calling module did not pass an PowerExchange queue handle.
    016
    10
    The calling module passed a queue handle, but the handle has an incorrect version number or format.
    017
    11
    The calling module did not pass an PowerExchange handle.
    018
    12
    The calling module passed an PowerExchange handle, but the PowerExchange handle has an incorrect version number or format.
    019
    13
    The PowerExchange subsystem initialization (EDMSINIT) has not been performed.
    020
    14
    An PowerExchange subsystem initialization (EDMSINIT) was attempted; however, it is already initialized.
    021
    15
    An EDMSCTRL pointer is missing or invalid.
    022
    16
    The address space creation macro (ASCRE) failed.
    023
    17
    The address space creation macro (ASCRE) failed because another component sent the PowerExchange Agent an invalid address space name.
    024
    18
    The address space creation macro (ASCRE) failed because the requested resource is not available. The requesting component needs to request the resource later. If the requesting component times out before the resource is available, you may need to run the job again.
    025
    19
    The PowerExchange Agent attempted to create the global queue; however, it already exists.
    026
    1A
    The PowerExchange Agent is processing a DRAIN command.
    027
    1B
    The PowerExchange Agent completed processing for a DRAIN command.
    028
    1C
    The EDMSASIN module terminated the address space creation macro (ASCRE).
    029
    1D
    The PowerExchange Agent received a SHUTDOWN COMPLETELY command and was completely shut down.
    030
    1E
    A dynamic allocation (DYNALLOC) for the subsystem DD failed.
    031
    1F
    The global queue received a request from a program with an invalid ASID.
    032
    20
    There was a mismatch with the global queue sequence number.
    035
    23
    The PowerExchange Agent attempted to access the PowerExchange repository and found the PowerExchange repository was not open or found the PowerExchange repository command was invalid.
    036
    24
    The PowerExchange Agent received an invalid repository command.
    037
    25
    An error occurred with an RIOM call.
    040
    28
    The PowerExchange Agent found that data was truncated.
    045
    2D
    The module currently holds or has obtained the lock.
    046
    2E
    The module does not currently hold the lock.
    047
    2F
    The requested lock was unavailable.
    048
    30
    The lock is not held and cannot be obtained because of hierarchy rules.
    060
    3C
    The SIOW area could not obtain storage.
    061
    3D
    The resource manager could not obtain storage.
    062
    3E
    The task work area could not obtain storage.
    063
    3F
    The global queue handler could not obtain storage.
    070
    46
    A bad STOKEN occurred during an EDMSRMGR call.
    071
    47
    A bad TCB occurred during an EDMSRMGR call.
    072
    48
    The EDMSRMGR TCB is not in the home ASID.
    230
    E6
    The PowerExchange Agent does not allow SRB mode callers.
    231
    E7
    An internal request or response included a count mismatch, which indicates a timeout probably occurred.
    232
    E8
    An internal request or response included a count mismatch, which indicates a timeout probably occurred.
    233
    E9
    An internal control block error occurred during a CLOSE operation on a subsystem dataset.
    234
    EA
    An unexpected format of the linkage stack was detected.
    237
    ED
    No more subsystem dataset entries (GCQNTs) exist.
    238
    EE
    No more entries (TAFFs, Task AFFinity entries) are available for tasks to connect to the PowerExchange Agent.
    239
    EF
    A request timed out.
    240
    F0
    An illogical function request occurred.
    241
    F1
    A required subsystem or subtask is not active.
    242
    F2
    An OPEN command failed.
    243
    F3
    A CLOSE command failed.
    244
    F4
    The PowerExchange Agent encountered and invalid data set name.
    245
    F5
    A module LOAD failed.
    246
    F6
    The IBM timing macro (STIMERM) failed.
    247
    F7
    The PowerExchange Agent encountered a command with the incorrect number of operands.
    248
    F8
    Another component requested a function that is not available.
    249
    F9
    The PowerExchange Agent could not add data to a buffer or file, because the buffer or file was full.
    250
    FA
    Another component sent a request to the PowerExchange Agent to find something, but the PowerExchange Agent could not find it.
    251
    FB
    The PowerExchange Agent found a duplicate request or duplicate record.
    252
    FC
    One module passed an incorrect operand to another module.
    253
    FD
    An invalid function was requested or the function request had an incorrect number of errors.
    255
    FF
    An abnormal termination (abend) occurred.

0 COMMENTS

We’d like to hear from you!
Hi, I'm Bolo!
What would you like to know?
Please to access Bolo.