Explanation
An error occurred when the system was processing
a DOM macro.
Register 15 contains a hexadecimal error code
in the format
xxxxyyyy. The fields in this error
code are the following:
- xxxx
- This halfword is for IBM® internal
use only.
- yyyy
- This halfword is the unique reason code identifier. Only yyyy is
listed below.
The following are the
yyyy values
and their meanings:
- Code
- Explanation
- 0004
- The caller passed an incorrect value in register 0.
- 0008
- Either caller was not a task in the same job step and address
space as the issuer of the WTOR macro that created the message to
be deleted, or the caller was not in key 0-7 or APF authorized.
- 000C
- A program check occurred while the system was verifying that the
caller could access each byte of a multiple DOM parameter list.
- 0010
- An unauthorized caller tried to delete a WTO message that was
not created by the same task in the same address space.
- 0014
- The entry was by a branch, but the caller is not authorized.
- 0018
- An unauthorized caller tried to delete a message that was issued
on another system.
- yy1C
- The system could not obtain needed storage. The return code from
the STORAGE service is found in the yy field.
- yy40
- A recovery environment could not be established. The return code
from the ESTAE macro is found in the yy field.
- 0050
- A DOMCBLK request specified an invalid DOMC length.
- 0051
- A failure occurred when broadcasting the DOM to the sysplex.
- 0052
- A failure occurred when attempting to DOM a message found in the
parking lot.
- yy53
- A failure occurred in the data block create routine. The return
code from the data block create routine is found in the yy field.
- Fyyy
- An internal processing error occurred. The yyy contains
the abend code of the failure.
System action
The system ignores the DOM macro. The DOM parameter
list and the failing message identifier are shown in the dump. The
system ignores any other message identifiers in the parameter list.
System programmer response
For a yy53 reason
code, search problem reporting data bases for a fix for the problem.
If no fix exists, contact the IBM Support
Center with the reason code.
Programmer response
Ensure that the correct message identifier
is being used in the DOM macro. Ensure that the DOM issuer is in
the same job step as the WTOR issuer.
Source