438

Explanation
An error occurred processing an ENQ macro instruction
during processing of global resource serialization.
The control
program found that the parameter list created from the macro instruction
was incorrect.
Register 15 might contain a reason code associated
with this error: Code
Explanation
xxxx0001
The input parameter list was altered during ENQ processing.
xxxx0002
The RESERVE request specified UCB and RNL=NO.
xxxx0003
The storage specified by the input UCB address does not map to
a valid UCB.
xxxx0004
The storage specified by the UCB address specified by an ISGNQXIT
exit routine does not map to a valid UCB.
xxxx0005
The storage passed to ENQ processing could not be accessed in
the caller's key.
xxxx0006
The storage containing the QNAME could not be accessed in the
caller's key.
xxxx0007
The storage containing the RNAME could not be accessed in the
caller's key.
xxxx0008
The storage containing the pointer to the UCB address could not
be accessed in the caller's key.
xxxx0009
The storage containing the UCB address could not be accessed in
the caller's key.
xxxx000A
The local resource count for this request exceeded X'FFFF' resources.
xxxx000B
The global resource count for this request exceeded X'FFFF' resources.
xxxx000C
The format word value specified in the input parameter list prefix
was incorrect.
xxxx000D
The storage specified by the  input TCB was invalid.   
xxxx000E
The storage specified by the input TCB does not map to a  valid
TCB.
xxxx000F
A MASID request incorrectly specified TCB or SMC.
xxxx0010
A MASID request has an rname with an invalid length.
xxxx0011
A MASID request specified invalid RET= value.
xxxx0012
A MASID request has no TCB associated with it.
xxxx0013
Issuing tasks TCB is a subtask of the target TCB, illegal.
xxxx0014
Request attempted to set an obsolete bit in the input parameter
list.
xxxx0015
Request illegally specified TCB with SMC.
xxxx0017
Request specified invalid RET= value.
xxxx0019
The ENQ request illegally attempted a generic request.
xxxx001A
A directed ENQ request was issued with no matching TCB in the
requester's address space.
xxxx001B
Directed ENQ request illegally specified UCB.
xxxx001C
Directed ENQ request illegally specified no ECB with an invalid
RET= value.
xxxx001D
An ECB request but RET does not specify ECB.
xxxx001E
An ECB request illegally specified SMC.
xxxx001F
The storage containing the format word could not be accessed in
the caller's key. 
xxxx0020
The storage containing the format value could not be accessed
in the caller's key.
xxxx0022
The storage containing the PEL Prefix could not be accessed in
the caller's key.
xxxx0023
The RMC=STEP was specified when PASN was not equal to HASN.
xxxx0822
Unable to access the Userdata specified on the request.
xxxx0823
The ALET for the Userdata is bad. 
xxxx0024
The request was made while in SRB mode.
xxxxyyyy
The reason code could also be associated with an ISGENQ Request=Obtain
or Request=Change. Note that the ABEND reason codes for ISGENQ correspond
to the same reason codes listed in the Return and Reason Codes section
of the ISGENQ macro in z/OS MVS Programming: Authorized Assembler Services Reference EDT-IXG.

System action
The system issues an ABEND dump.

System programmer response
If the reason code is X'0004',
check your ISGNQXIT installation exits to ensure that they are coded
to specify a valid UCB address. Otherwise, if the problem persists,
search problem reporting data bases for a fix for the problem. If
no fix exists, contact the IBM® Support
Center. Provide the ABEND dump.

Programmer response
Correct the macro instruction. Recompile
and run the job step again.
If the problem persists, do the
following: Obtain the address of the ENQ parameter list from register 1 in
the UNIQUE-3 column of the SVC 38 entry in the system trace.
Check the parameter list against the SVC 38 mapping. When analyzing
the parameter list, remember that the unit control block (UCB) pointer,
if present, is the address of a field that, in turn, contains the
address of the UCB. If the parameter list contains incorrect data,
continue diagnosis in the program that issued the macro.

Source
Global resource serialization