28.12.2012 Views

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

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

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

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

User Response: Ensure the hardware is operational<br />

<strong>and</strong> the specified device is supported by the system.<br />

Then enter the SALIPL comm<strong>and</strong> again. If the error<br />

persists, contact your system support personnel.<br />

H<strong>CP</strong>400I All {paging|spooling} space is in use.<br />

Explanation: All paging or spooling disk space is in<br />

use.<br />

<strong>System</strong> Action: If both paging <strong>and</strong> spooling spaces<br />

are full, the system issues abend PGT004. If necessary,<br />

spooling space is used to fill paging requests.<br />

Operator Response: Review system usage <strong>and</strong> take<br />

steps to reduce the system load. Review the spool files.<br />

You may start additional printers to reduce print spool<br />

backlog; if a reader backlog exists, request all users to<br />

read in their files. In addition, you may use SPXTAPE to<br />

save selected spool files on tape before purging them.<br />

H<strong>CP</strong>401I 90 percent of all {paging|spooling}<br />

space is in use.<br />

Explanation: Ninety percent of all paging or spooling<br />

space is in use.<br />

<strong>System</strong> Action: Normal system operation continues.<br />

Operator Response: Review system usage <strong>and</strong> take<br />

steps to reduce the system load. Review the spool files.<br />

You may start additional printers to reduce print spool<br />

backlog. If a reader backlog exists, request all users to<br />

read in their files. In addition, you may use SPXTAPE to<br />

save selected spool files on tape before purging them.<br />

H<strong>CP</strong>403I rdev {SCU|CACHE|DASD|MEDIA} sev<br />

ALERT, MT=tttt-mm SER=mmaa-bbbbbbb<br />

REFCODE=cccc-cccc-cccc [ID=id]<br />

[VOLSER=volser] [CCHH=X'cccc hhhh']<br />

[REPEATED]<br />

Explanation: The DASD storage subsystem has<br />

detected an abnormal operational condition within the<br />

DASD subsystem that requires service attention.<br />

In this message, the terms are defined as follows:<br />

rdev The device used to report the condition; this<br />

will be omitted if no I/O activity is directed<br />

toward the affected device resulting in the SIM<br />

being presented on an unrelated device.<br />

sev ACUTE, SERIOUS, MODERATE, or SERVICE<br />

tttt-mm The machine type <strong>and</strong> model or ‘UNKNOWN’ if<br />

they cannot be determined<br />

mmaa-bbbbbbb<br />

The serial number of the failing device<br />

cccc-cccc-cccc<br />

The reference code<br />

id The Service Information Message (SIM)<br />

identifier<br />

H<strong>CP</strong>400I H<strong>CP</strong>406A<br />

volser The DASD volume serial number or ‘/UNKN\’ if<br />

it is unrelated to this SIM<br />

X'cccc hhhh'<br />

The address of the failing track (media SIMs)<br />

REPEATED<br />

For non-media SIMS (DASD hardware) only; it<br />

is shown when the message is a repeat<br />

presentation of a previously reported SIM.<br />

<strong>System</strong> Action: <strong>System</strong> operation continues.<br />

Operator Response: Record all the information<br />

displayed in the message <strong>and</strong> contact your system<br />

support personnel.<br />

Programmer Response: Examine the EREP records<br />

(OBR) for additional details of the failure. Refer to the<br />

hardware <strong>System</strong> Reference Library (SRL) manuals for<br />

sense data formats <strong>and</strong> descriptions. If a hardware<br />

problem is indicated, contact the appropriate hardware<br />

service personnel <strong>and</strong> provide them with the information<br />

displayed in the message.<br />

H<strong>CP</strong>404E Device rdev not detached - device is<br />

being given<br />

Explanation: The user attempted to detach real<br />

device address rdev while the corresponding real device<br />

was being given.<br />

<strong>System</strong> Action: The DETACH comm<strong>and</strong> is ignored,<br />

<strong>and</strong> the GIVE comm<strong>and</strong> continues processing.<br />

User Response: Retry the DETACH comm<strong>and</strong> after<br />

the GIVE comm<strong>and</strong> has completed.<br />

H<strong>CP</strong>405A Mount form operform on {printer|punch}<br />

rdev<br />

Explanation: The output device (rdev) requires that<br />

the form (operform) be mounted.<br />

<strong>System</strong> Action: <strong>CP</strong> suspends printing or punching on<br />

the device until the operator mounts the new form <strong>and</strong><br />

presses the START button, or until the operator enters a<br />

START comm<strong>and</strong> at the console.<br />

Operator Response: Mount the appropriate form on<br />

the device. When the form is mounted, press the<br />

START button or issue the START comm<strong>and</strong>, <strong>and</strong> all<br />

files with the form specified <strong>and</strong> other requirements<br />

matching the START device selection criteria will print or<br />

punch.<br />

H<strong>CP</strong>406A Check forms alignment for form<br />

operform on printer rdev.<br />

Explanation: The printer (rdev) is in SETUP mode.<br />

The form that is active on the device should be checked<br />

for forms alignment.<br />

<strong>System</strong> Action: <strong>CP</strong> suspends printing on the device<br />

until the operator sets up the form <strong>and</strong> presses the<br />

Chapter 3. <strong>System</strong> <strong>Messages</strong> 171

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!