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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

H<strong>CP</strong>1152E userid vdev has not been linked<br />

because it would overlap system<br />

{spool|paging|temporary disk} space<br />

Explanation: The specified mini-DASD definition<br />

would overlap one of the following types of system<br />

DASD space:<br />

v Spool<br />

v Page<br />

v Temporary disk.<br />

For minidisk definitions beginning with cylinder 0 of a<br />

system-owned volume, no check is made to determine if<br />

the minidisk definition would overlap system DASD<br />

space.<br />

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

User Response: Inform your system programmer of<br />

the problem; the directory entry for the device you<br />

specified in the LINK comm<strong>and</strong> is incorrect.<br />

H<strong>CP</strong>1153E userid vdev cannot be re-linked<br />

{R/O|R/W} because it is part of a<br />

minidisk-pool <strong>and</strong> was previously<br />

linked {R/W|R/O}.<br />

Explanation: The specified DASD to be relinked<br />

cannot change modes from read-only to write or write to<br />

read-only because it has been specified as part of a<br />

minidisk-pool.<br />

The minidisk remains linked in the original mode.<br />

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

User Response: The minidisk is part of a<br />

minidisk-pool <strong>and</strong> cannot be relinked. It must be<br />

removed from the minidisk pool. This can be<br />

accomplished by detaching the device <strong>and</strong> then linking<br />

it again in the correct mode. Check with the system<br />

programmer or the owner of the user ID before trying to<br />

detach the minidisk.<br />

H<strong>CP</strong>1154I There were no stable links in effect to<br />

the specified minidisk.<br />

Explanation: None of the current links to this minidisk<br />

were made with any of the stable access modes.<br />

<strong>System</strong> Action: The query operation is complete with<br />

the issuance of this message.<br />

User Response: None.<br />

Programmer Response: None.<br />

H<strong>CP</strong>1155E You do not have the proper directory<br />

authorization to LINK a minidisk with<br />

the link mode of mode.<br />

Explanation: The user executing the LINK comm<strong>and</strong><br />

or a default link during logon has attempted to LINK a<br />

minidisk using one of the stable or exclusive link modes.<br />

H<strong>CP</strong>1152E H<strong>CP</strong>1158E<br />

These require authorization through the LNKS or LNKE<br />

options on the OPTION directory control statement in<br />

the user’s directory definition.<br />

<strong>System</strong> Action: The LINK operation is terminated,<br />

<strong>and</strong> this message issued.<br />

User Response: The user should either use another<br />

non-stable or exclusive mode to link the desired disk, or<br />

see the local systems administrator for the authority to<br />

use the desired link mode.<br />

Programmer Response: If use of the stable of<br />

exclusive mode capability is justified, update the user’s<br />

directory definition with the required option.<br />

H<strong>CP</strong>1156I DASD device number forced R/O;<br />

unauthorized for R/W<br />

Explanation: The security label governing your current<br />

session gives you insufficient authority to access the<br />

DASD in read/write mode. However, you are entitled to<br />

read-only access to the DASD.<br />

<strong>System</strong> Action: The system has given you read-only<br />

access to the DASD.<br />

User Response: Either access the DASD in read-only<br />

mode or detach it.<br />

H<strong>CP</strong>1157I DASD vdev was not LINKed because<br />

the MDISK DEVNO parameter requires<br />

the device to be a free volume.<br />

Explanation: The device specified by the comm<strong>and</strong><br />

was not linked. The MDISK definition being processed<br />

contained the DEVNO parameter, defining the minidisk<br />

by its real device number. Such a minidisk definition<br />

requires the real device to be a free volume. Instead,<br />

the device was found to be in use in some other<br />

manner (that is, attached to the system).<br />

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

Operator Response: If the correct device number was<br />

specified, the device must be made free before the<br />

MDISK definition is re-attempted (by logging on again).<br />

H<strong>CP</strong>1158E Stable <strong>and</strong> exclusive links are not<br />

supported. A system that shares this<br />

volume is not at Release <strong>VM</strong>/ESA ®<br />

1.1<br />

or greater.<br />

Explanation: This message is displayed when a user<br />

tries to link a disk that is part of a CSE complex in one<br />

of the new enhanced modes <strong>and</strong> the disk is XLINK<br />

formatted on a system with a release of <strong>VM</strong>/ESA lower<br />

than Version 1 Release 1.1. The enhanced modes are<br />

stable read (SR), stable write (SW), stable multi (SM),<br />

exclusive read (ER). <strong>and</strong> exclusive write (EW).<br />

<strong>System</strong> Action: Nothing happens to the system. The<br />

user is denied the link. The operator is not notified. The<br />

user can link the disk in a valid mode.<br />

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

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

Saved successfully!

Ooh no, something went wrong!