z/VM: System Messages and Codes Š CP - z/VM - IBM

close is sent to the partner. The lock word should never
be destroyed when the activation block is found. Refer
to z/VM: Diagnosis Guide for information on gathering
the documentation you need to assist IBM in diagnosing
the problem, then contact your IBM support personnel.
AAS001
Explanation: (soft abend) A non-zero condition code
was returned on an IUCV SEVER in the ISFC APPC
mailbox.
User Response: The IUCV SEVER should always
complete with condition code zero. Conversation clean
up will continue. Refer to z/VM: Diagnosis Guide for
information on gathering the documentation you need to
assist IBM in diagnosing the problem, then contact your
IBM support personnel.
AAS002
Explanation: (soft abend) A condition code of zero
was returned on an APPCVM RECEIVE in the ISFC
APPC mailbox.
User Response: At this point in the APPC mailbox
processing, a Message Pending Interrupt has been
received. A condition code of zero (indicating
receive-ahead) should never occur. Processing
continues as if an error occurred on the APPCVM
RECEIVE (condition code 1). Refer to z/VM: Diagnosis
Guide for information on gathering the documentation
you need to assist IBM in diagnosing the problem, then
contact your IBM support personnel.
AAT001
Explanation: (soft abend) A non-zero condition code
was returned on an IUCV SEVER in the ISFC APPC
mailbox.
User Response: The IUCV SEVER should always
complete with condition code zero. Conversation clean
up will continue. Refer to z/VM: Diagnosis Guide for
information on gathering the documentation you need to
assist IBM in diagnosing the problem, then contact your
IBM support personnel.
AAT002
Explanation: (soft abend) During open_complete
processing in the ISFC APPC mailbox, the target side of
the APPC conversation is expecting PIP data on the
connect, but the source side never indicated that it was
sending PIP data.
User Response: This is most likely a timing problem.
The APPC conversation is severed. Refer to z/VM:
Diagnosis Guide for information on gathering the
documentation you need to assist IBM in diagnosing the
problem, then contact your IBM support personnel.
AAU001
Explanation: (soft abend) A non-zero condition code
was received on an IUCV SEVER of the *IDENT path
for an ISFC owned gateway in the ISFC APPC mailbox.
User Response: The IUCV SEVER should always
complete with condition code zero. The cleanup of the
gateway path will continue. Refer to z/VM: Diagnosis
Guide for information on gathering the documentation
you need to assist IBM in diagnosing the problem. Then
contact your IBM support personnel.
ABC001
Explanation: (soft abend) HCPABC received an
unexpected return code when scanning for or opening a
soft abend dump file.
User Response: If message HCPABC9309E preceded
this abend, the return code from an attempt to open a
soft abend dump file is in R3. Otherwise, the return
code is from a scanning operation and is in R15.
Determine what the return code is, then contact your
IBM support personnel.
ABF001
Explanation: An unexpected return code was received
when opening the system dump spool file.
User Response: Contact your IBM support personnel.
ABF002
Explanation: An unexpected return code was received
when reading, writing, or positioning the system dump
spool file.
User Response: Contact your IBM support personnel.
ABF003
Explanation: An unexpected return code was received
when closing the system dump spool file.
User Response: Contact your IBM support personnel.
ABN001
Explanation: An incorrect PSW address was
calculated as the return address in the abending module
when an asynchronous dump was requested.
User Response: Contact your IBM support personnel.
ABN002
AAS001 ABN002
Explanation: Not enough storage was available to
provide the necessary amount of static save areas for
the soft abend process.
User Response: Contact your IBM support personnel.
Chapter 2. System Codes 15