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

If this error message includes “The UCS could not be
loaded or read,” two possible reasons could be:
v The I/O to the printer to determine the Print Band ID
fails.
v The I/O to the printer to determine the Print Band ID
does not fail, but the Print Band ID returned is
X'00000000'. This will occur if the LOADBUF
command was entered on a second level system,
and the printer is really a virtual simulated device.
System Action: The command is not executed.
System operation continues.
User Response: If another printer is available that has
the function requested, enter the command again for
that printer. If a printer is not available with the function,
enter the print request again without specifying that
function.
HCP422E The same option was specified twice.
Explanation: You specified the same option twice in
the same command.
System Action: System operation continues.
User Response: Reissue the command specifying the
option only once.
HCP423E The function requested is incompatible
with a previously specified operand.
Explanation: The function requested by a specified
option is incompatible with a previously specified
operand.
System Action: CP processes the command until it
encounters the error. System operation continues.
User Response: Check the command syntax and
reenter the command, making sure that each operand is
compatible with all previous operands.
HCP424I The requested option(s) would result in
incompatible settings for reader vdev.
The reader has been spooled KEEP to
remove this conflict.
Explanation: The reader was spooled CONT,
RESCAN, HOLD, and NOKEEP.
System Action: The reader is spooled KEEP to
remove the conflict.
User Response: None.
HCP427E type {rdev | vdev | NSS_name |
TRF_filename[.userid]} system spool
space full; file {closed | held | purged}
Explanation: System spooling space on the device
specified, or for the system trace file specified, is full.
The type may be: a reader, printer, punch, console,
tape, NSS, or system trace file.
HCP422E HCP428E
If the message refers to one of the following file types,
CP purges the files: reader, NSS, or tape.
Otherwise, CP closes the file. For a console, printer, or
punch file, CP also puts it in HOLD status.
System Action: When the console spool file closes,
virtual console spooling stops. The virtual machine
continues to execute, but without console spooling.
For virtual devices, an intervention-required unit check
condition is returned to the virtual machine. CP makes
the virtual device not ready, and the system continues
execution when the printer or punch output file closes.
For the DEFSYS or DEFSEG command, CP does not
create the skeleton file. For the SAVESYS or SAVESEG
command, CP purges the system data file.
If the message refers to a system trace file, the open
file is closed. Tracing is ended for the trace name or
user userid generating data for this file.
The related files (spool IDs) already generated are
saved, as if tracing had been terminated by user
commands.
User Response: Inform the system operator that you
received this message. When spool space is available,
issue the SPOOL CONSOLE START command to
resume console spooling, or issue the READY
command to resume printer or punch spooling.
If the message refers to a system trace file, inform the
person who started trace recording so that they can
reissue the command when spool space becomes
available.
Operator Response: Make an attempt to reduce the
spooling load on the system as soon as possible. You
may use SPXTAPE to save selected spool files on tape
before purging them. If the real reader file is purged, try
the read operation again when more space is available.
Programmer Response: For NSS type files, purge
unnecessary system data files or spool files to reclaim
spool space. For system trace files, purge unnecessary
system data files or spool file files and reissue the
TRSOURCE or TRSAVE command.
HCP428E type {rdev|name [ userid]} spool error;
file {held| purged|closed}
Explanation: A paging I/O error occurred while CP
was reading or writing a file for the specified real device
or trace file, or while tracing to a system data file.
System Action: For all non-trace operations, if the file
that was processing at the time the I/O error occurred is
a printer or punch file, CP places the file in system
HOLD status, and system operation continues. If the file
is a reader file, CP purges it.
For system trace files, CP attempts to close the file.
Tracing is ended for the trace name or origin ID userid
Chapter 3. System Messages 173