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

SVF003
Explanation: A CP module is attempting to call a
module at location zero. This probably indicates a
missing or misspelled entry point name.
User Response: R13 points to the save area.
SAVER12 or SVGR12 contains the address of the
module making the bad call. SAVER14 or SVGR14
contains the address of the module that received the
bad call. Ensure that all required modules are included
in the CP load list, and then reload the system.
SVF006
Explanation: A supervisor SVC code was used that is
not currently defined.
User Response: Examine the CP trace table and
storage dump for possible causes. CR12 points to the
next available CP trace table entry after the failure.
SVF010
Explanation: (Hard abend) A recursive call has been
made to subroutine MORE. This could occur if MORE
processing eventually called an entry point that required
a new save area.
User Response: Examine the CP trace table and
storage dump for possible causes. If the problem cannot
be determined, contact your IBM support personnel for
assistance.
SVF011
Explanation: (Hard abend) ICLCOUNT in the ICLBK
went negative. ICLCALLS went
negative.
User Response: Contact your IBM support personnel.
SWI001
Explanation: HCPSWIAD was entered using a
VMDBK that was not a base VMDBK.
User Response: R13 points to a save area. Identify
the caller by the return address and base register in the
save area pointed to by R13. The caller did not provide
the VMDBK of the currently dispatched user.
SWI002
Explanation: HCPSWIAD was erroneously entered
when the system VMDBK was the current VMDBK.
User Response: R13 points to a save area. Identify
the caller by the return address and base register in the
save area pointed to by R13. The caller did not provide
the VMDBK of the currently dispatched user.
SWU001
Explanation: HCPSWUMS received a condition code
2 on an IUCV SEND request.
SYN001
Explanation: A processor has requested a spin-lock
that it already owns.
User Response: Examine the dump to determine why
the processor requested the same lock twice without
releasing it.
SYN002
Explanation: A processor tried to release a spin-lock
that it did not own.
User Response: Examine the dump to determine how
the processor got into the function covered by the
spin-lock without first obtaining the spin-lock for that
function.
SZC001
Explanation: An error was detected within the FBA
emulation support. R0 contains a unique checkpoint
code which identifies the origin of the error. Checkpoint
codes are defined in HCPEDEV COPY.
User Response: Contact your IBM support personnel.
SZE001
Explanation: An attempt was made to deallocate an
event which has tasks waiting.
User Response: Contact your IBM support personnel.
SZE002
Explanation: An attempt was made to wait on an
event using latch serialization when a spin lock was
already held on the system.
User Response: Contact your IBM support personnel.
SZE003
Explanation: An attempt was made to wait on an
event using lock serialization when the lock was not
held.
User Response: Contact your IBM support personnel.
SZK001
SVF003 SZK001
Explanation: An attempt was made to deallocate a
lock when the lock was held
User Response: Contact your IBM support personnel.
Chapter 2. System Codes 105