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

HCP1839E HCP1842E
v If the disposition is LEAVE or REW, and the tape is
either the only tape or the last active tape, the
command completes with errors and system
operation continues.
User Response: If you have received a response from
SPXTAPE asking you to mount the next tape, and you
have more tapes to process, you can mount the next
tape on this drive or any other drive that is active for
this command. You can also add more drives to the
operation by entering the SPXTAPE LOAD or SCAN
command with an expanded device range that includes
the new devices and all the currently active and
mount-pending devices. Do not specify any additional
file selection criteria. For example, if the original range
on an SPXTAPE LOAD command was 181-182, and
you have device 183 attached that you want to add,
enter:
spxtape load 181-183
After the command completes, you can determine if any
files have been skipped by comparing the volume logs
from this load or scan with the ones that were created
when the files were dumped. Skipped files are not
recoverable.
Some files may have been only partially loaded or
scanned. For a load operation, see the section on
recovering from an I/O error, cancel, reset, or system
failure in the description of the SPXTAPE LOAD
command in the z/VM: CP Commands and Utilities
Reference.
If skipping was not successful, the remaining files in that
tape file are not recoverable. A tape file (ending with
one or more tape marks) contains files dumped by one
logical SPXTAPE DUMP command, which may have
been a single command or multiple commands with the
APPEND disposition. If the tape contains files dumped
by other logical SPXTAPE DUMP commands, you may
still be able to read them. Use the CMS TAPE
command to position the tape to the beginning of the
next tape file, and enter the SPXTAPE LOAD or SCAN
command with the appropriate file selection criteria.
HCP1839E File userid spoolid2 (was spoolid1 on
tape) has been placed in system hold
status because of a tape read I/O error
Explanation: While loading file spoolid1 from tape to
the specified user ID (a new spool ID of spoolid2 was
assigned to the file on the system), the SPXTAPE
LOAD command found part of the file to be unreadable
and placed the file in system hold status.
System Action: Command processing continues.
User Response: Purge the partially loaded file and try
loading the file from another tape drive. If the error
occurs again, you may want to ask the spooling
operator to release the file from system hold status so
you can try reading the part that was loaded. If this is
254 z/VM: System Messages and Codes — CP
unsuccessful, you cannot recover the file from the tape.
HCP1840E File {userid|*IMG|*NLS|*NSS|*UCR}
spoolid has been skipped because
SPXTAPE could not read the control
information. [The file has been placed
in system hold status]
Explanation: While trying to dump the specified file to
tape, the SPXTAPE DUMP command could not read the
information that identified the DASD pages that
contained the file. The file was not dumped. If the file
was a standard spool file, SPXTAPE placed it in system
hold status.
System Action: Command processing continues.
User Response: If the file is a standard spool file, you
may want to ask the spooling operator to release it from
system hold status for additional processing. Otherwise,
purge the file.
HCP1841E Page read error while dumping userid
spoolid fn ft. XAB data has been omitted
on tape
Explanation: While dumping the specified file to tape,
the SPXTAPE DUMP command could not read the
associated extended attribute (XAB) data. The XAB
data was omitted, but the rest of the file was dumped.
The file was flagged to indicate information was
missing.
System Action: Command processing continues.
User Response: None. For future reference,
remember the XAB data is no longer available for this
file. If the file is ever loaded, the flagging results in
message HCP1843E.
HCP1842E Page read error while dumping
{userid|*IMG|*NLS|*NSS|*UCR} spoolid fn
ft; nnnnnnn pages were not dumped to
tape
Explanation: While dumping the specified file to tape,
the SPXTAPE DUMP command could not read a
number of pages and omitted them from the tape. The
rest of the file was dumped and flagged to indicate data
was missing.
This error was caused by one of these conditions:
v I/O errors that occurred while trying to read the data
pages from spool space
v Paging errors that occurred while processing the file
after its control information was read into system
virtual storage.
System Action: Command processing continues.
User Response: Enter the SPXTAPE DUMP
command again. If the error was caused by the second
condition, the file should dump correctly. If the error was