422

Explanation
This abend is a general use abend code.  It provides
an abend that will be treated similarly to a 222 abend generated by
a CANCEL. This abend will not be delivered to the target task if the
task is already in recovery processing.
This abend may be retryable
or nonretryable depending on the reason code.
The 422 abend
reason codes are in the format: xxxxyyzz
The parts of the reason
code are: xxxx
The first halfword will be left to the component to set.  Some
components use these two bytes for internal identification.
yy
The 3rd byte will contain a component identifier.  This will allow
the 422 abend to be shared by multiple products and components. The
following yy values indicate which component or
product generated the abend: 01
z/OS® UNIX System Services
02
JES2
03
BCP console services
04
TCP/IP Reason Codes
05
JES3

zz
The last byte is used by the component to create unique reason
codes.

z/OS UNIX System Services
Reason Codes (yy= 01): Code
Explanation
xxxx01zz
Where zz is between the values of X'01' and X'7F' and
represents the signal that caused the task to end. An error occurred
in an application program that uses z/OS UNIX System Services.
xxxx0109
The ending address space is the target of a signal.  A signal
is program-generated and causes the job step task in the target user
process to be ended with an abend that cannot be retried.
xxxx0181
This abend is the result of the BPX1EXC (exec) or BPX1EXM (execMVS)
service being issued in a process with multiple threads.  All dubbed
threads in the process are terminated with the abend.
xxxx0182
This abend is the result of the BPX1EXI (_exit) service being
issued in a process with multiple threads.  The initial pthread_create
task (IPT), if not already exited, is abended with this reason, if
the thread calling BPX1EXI is created by pthread create.
xxxx0183
BPXPRMPC was requested to terminate and clean up a process.  This
required the Assembler termination macro CALLRTM of the initial pthread
task.
xxxx0184
The task is being ended because it is in a wait state controlled
by the kernel address space, which is being ended.  To prevent leaving
the task in a never-ending wait, the task is abended.  If a recovery
routine exists in the task, the routine can retry for this abend.
xxxx0185
A system error occurred during thread creation. The process was
terminated.
xxxx0186
A system error occurred during the processing of a local process
exec.  The jobstep is terminated.
xxxx0187
A system error occurred during fork processing. Fork is in the
APPC Receive and Wait window trying to create the child address space.
Fork maybe hung waiting for ASCH initiators.
xxxx0189
The kernel has, at the request of the user, terminated a thread
that was in a ENQ wait.
xxxx018A
A system error occurred creating the child process during fork
processing.  The child process address space is terminated.
xxxx018B
A system error occurred during server_init processing for a server
manager address space.  The calling task is terminated.
xxxx01A0
This abend is the result of the kernel terminating a thread. The
thread and its associated task are terminated.
xxxx01A2
This retryable abend will drive the BPXOINIT process to clean
up a suspected growth of zombie processes.  This growth of zombies
could have been due to a cross memory post failure that prevented
BPXOINIT from waking up sooner to clean up the zombies.
xxxx01A3
This abend is the result of a request to shutdown z/OS UNIX System Services. The thread
and its associated task are terminated.
xxxx01A4
The current owner of a mutex (mutual exclusion lock) or condition
variable abended thereby making unusable the mutex or condition variable
held at that time. The system terminates the thread and any task(s)
waiting for the mutex or condition.
xxxx01A5
The system has terminated a user task that has held a z/OS UNIX System Services latch for
an excessively long time.
xxxx01A6
The system has terminated a user task that was waiting on an internal z/OS UNIX System Services event. The
poster committed to the post but was unable to complete the post.
xxxx01A7
 No z/OS UNIX recovery stacks are available. The address
space is terminated. Reduce concurrent z/OS UNIX workload on the system. Use z/OS UNIX Health
Check, USS_KERNEL_STACKS_THRESHOLD, to receive warnings when available z/OS UNIX stacks
are low.

System action
The unit of work is ended with a nonretryable
error.

System action
The job/TSU/STC is ended with a nonretryable error.
Console
Component Reason Codes (yy=03): Code
Explanation
00010301
A command was cancelled at the operator's request through the
CMDS ABEND command.
00010302
A command was cancelled at the operator's request through the
CMDS FORCE command.

Programmer response
Code
Response
xxxx01zz
The unit of work has terminated for a signal that was either sent
by the user or generated by the system.  Determining the reason for
the signal generally requires an understanding of when signals are
generated by the system.  For a list of signals, refer to z/OS UNIX System Services Programming: Assembler Callable Services Reference. 
xxxx0181
No action is required by the user.
xxxx0182
No action is required by the user.
xxxx0183
No action is required by the user.
xxxx0184
The task was in a wait at the time the kernel terminated.  This
is not an error.
xxxx0185
Retry the operation.  If the error persists, search problem reporting
databases for a fix for the problem. If no fix exists, report the
error to the IBM® Support Center.
xxxx0186
No action is required by the user.
xxxx0187
Review the APPC/ASCH setup relating to OMVS.
xxxx0189
No action is required by the user.
xxxx018A
No action is required by the user.
xxxx018B
No action is required by the user.
xxxx01A0
No action is required by the user.
xxxx01A2
No action is required by the user. This is part of automated clean-up
of  zombie storage that is no longer needed.
xxxx01A3
No action is required by the user.
xxxx01A4
Resubmit those jobs that were terminated when the owner of the
mutex or condition variable terminated.
xxxx01A5
Determine why the owner of the z/OS UNIX System Services latch was
holding it for an excessive period of time. Correct the problem and
resubmit the affected job(s) or restart the affected task(s).
xxxx01A6
No action is required by the user.

  Rerun the job and use a debugger if necessary to
determine why the signal has occurred.
Source:  z/OS UNIX System Services (BPX)
JES2
Reason Codes (yy = 02): Code
Explanation
xxxx0200
xxxx is the identifier of the JES2 processor control element (PCEID)
currently active.  A value of X'02' in the 3rd byte indicates
the JES2 component.  When xxxx=0003, this abend is the result of a
job/TSU/STC being canceled via an $C job or $C job,D command while
it is awaiting conversion or active in conversion.
xxxx0204
The address space was terminated (through CALLRTM TYPE=ABTERM)
during job select processing by a JES2 $C operator command.  A dump
was produced if the DUMP operand was included on the $C command.
xxxx0208
The address space was terminated (through CALLRTM TYPE=MEMTERM)
as the result of a JES2 $C command with the FORCE operand.
00030200
Determine why the job is being canceled.  If you require a dump,
have the operator resubmit the job, and then cancel it with the DUMP
operand.

Source
JES2

Source
Console services
TCP/IP Reason Codes (yy=04): 
See
TCP/IP abend 422 reason codes in z/OS Communications Server: IP and SNA Codes.
JES3
Reason Codes (yy=05): Code
Explanation
00000501
The job was cancelled during job initiation. No dump was requested.
00000502
The job was cancelled with dump during job initiation.
00000503
The job was forced by using the *MODIFY J=nn,FORCE command.