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

SPY001
Explanation: (soft abend) End-of-volume processing
for a particular tape volume being dumped should be
complete, but the TAPPRGCT counter that monitors
end-of-volume processing is not zero.
User Response: Check the end-of-volume processing
code. End-of-volume processing for all files
(represented by a TKTBK) occurs on a file-by-file basis
with a loss of control between each file. When the
processing is started, TAPPRGCT is incremented. When
end-of-volume processing for all the files on that volume
has completed, TAPPRGCT is decremented. A share of
the TAPBK lock should be held during all of this
end-of-volume processing. The code where the abend
occurred obtains the TAPBK lock exclusive before
checking TAPPRGCT. This field should be zero before
the exclusive lock is obtained. If it is not, there may be
a problem with the locking of the TAPBK in the
end-of-volume processing code.
SPY002
Explanation: (soft abend) More XAB data exists for
the file being dumped than will fit in the first segment
(TKTSEGDU=0). The XAB data in the first segment
should have been dumped in full page increments.
Either this has not occurred, or there is a calculation
error in the loop that is dumping the XAB data.
User Response: R6 points to the TKTBK. Use the
current values of the registers and the appropriate fields
in the TKTBK to determine what is wrong with the loop
in HCPSPY that dumps the XAB data.
SRM004
Explanation: (soft abend) Entry point HCPADJDU
passed an unexpected return code.
User Response: R15 contains an unexpected return
code. The most likely cause is that HCPADJDU was
changed to add a new return code and the caller was
not changed to recognize this return code. Examine the
listings to verify this.
SRM005
Explanation: (soft abend) Entry point HCPAPJUD
passed an unexpected return code.
User Response: R15 contains an unexpected return
code. The most likely cause is that HCPAPJUD was
changed to add a new return code and the caller was
not changed to recognize this return code. Examine the
listings to verify this.
SRN001
Explanation: The available processing unit count
(SRMNCPUA) became negative.
User Response: Examine the dump and trace table
entries to determine what caused the count to become
negative.
SRN002
Explanation: CP determined that the directory entry
for a user ID contains an incorrect share.
User Response: R2 points to the DVMD of the user
ID whose directory entry is incorrect. Examine the
directory space on DASD to determine how the entry
became incorrect.
SRN003
Explanation: (soft abend) One of the totals in the
SRMRTHRU or SRMCTHRU table went negative.
User Response: Examine the logic that computed the
negative value to determine the cause of the failure.
R0: Contains the negative value
R1: Contains an index pointing to the failing
element of the table
R15: Points to the failing code.
SRN004
Explanation: (soft abend) The logical processing unit
identifier mask that was passed to HCPSRNAD is not
valid.
User Response: Determine why the caller of
HCPSRNAD passed a processing unit identifier that
was not valid.
SRN005
Explanation: (soft abend) The logical processing unit
identifier mask passed to HCPSRNDR is not valid.
User Response: Determine why the caller of
HCPSRNDR passed a processing unit identifier that
was not valid.
STK003
SPY001 STK003
Explanation: The interrupt address or the execution
address of a TRQBK, IORBK, or CPEBK is zero. This
probably indicates a missing or misspelled entry point
name.
User Response: Make sure that all required modules
are included in the CP load list and are spelled
correctly. Then reload the system.
Chapter 2. System Codes 101