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
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
H<strong>CP</strong>092E H<strong>CP</strong>093E<br />
Explanation: The amount of temporary space<br />
requested cannot be satisfied from the available<br />
space remaining on the system.<br />
If you specified device T2314, T2319, or T3310, the<br />
temporary space requested is not available because<br />
these devices are not supported in z/<strong>VM</strong>.<br />
<strong>System</strong> Action: <strong>System</strong> operation continues. If<br />
temporary space was just released, it may not be<br />
available until it is cleared if the CLEAR_TDISK<br />
option was specified on the FEATURES statement in<br />
the system configuration file or if the SYSCLR = YES<br />
option was specified in H<strong>CP</strong>SYS.<br />
User Response: Enter the DEFINE comm<strong>and</strong>,<br />
requesting fewer cylinders or blocks, <strong>and</strong> requesting<br />
temporary space on devices other than T2314,<br />
T2319, or T3310.<br />
Operator Response: If additional preformatted <strong>CP</strong><br />
packs are available, <strong>and</strong> the packs’ volume serial<br />
numbers are defined in the <strong>CP</strong>-owned volume list.<br />
The following comm<strong>and</strong> can be entered to provide<br />
more <strong>CP</strong> temporary disk space.<br />
ATTach dev [TO] SYSTEM [[AS] volid]<br />
v vdisk space not available<br />
Explanation: A virtual disk in storage cannot be<br />
created without exceeding either the system limit or<br />
the user limit on the amount of storage available for<br />
allocating virtual disks in storage.<br />
– If you receive this message when logging on, a<br />
virtual disk in storage that is defined by an MDISK<br />
statement in your directory, or that is the target of<br />
a LINK statement in your directory, does not<br />
currently exist <strong>and</strong> cannot be created without<br />
exceeding the system limit.<br />
Note: A virtual disk in storage defined by an<br />
MDISK statement may already exist if<br />
another user has a link to it.<br />
– If you receive this message when using the LINK<br />
comm<strong>and</strong>, the target virtual disk in storage does<br />
not currently exist <strong>and</strong> cannot be created without<br />
exceeding the system limit.<br />
– If you receive this message when using the<br />
DEFINE (Virtual Disk in Storage) comm<strong>and</strong>, there<br />
is not enough space to create the virtual disk in<br />
storage without exceeding one of the following<br />
limits:<br />
- The system limit<br />
- The user limit on the amount of space that can<br />
be allocated for virtual disks in storage created<br />
by a single user with the DEFINE comm<strong>and</strong>.<br />
You may have too many virtual disks in storage<br />
already defined, or the virtual disk in storage you<br />
are trying to define may be too large, or all the<br />
system virtual disk in storage space may be in<br />
use.<br />
<strong>System</strong> Action: <strong>System</strong> operation continues.<br />
146 z/<strong>VM</strong>: <strong>System</strong> <strong>Messages</strong> <strong>and</strong> <strong>Codes</strong> — <strong>CP</strong><br />
User Response:<br />
– If you are logging on or using the LINK comm<strong>and</strong>,<br />
contact your system administrator <strong>and</strong> request that<br />
the user or system limit on virtual disk in storage<br />
space be increased.<br />
– If you are using the DEFINE comm<strong>and</strong>, reenter<br />
the comm<strong>and</strong> for a smaller size virtual disk in<br />
storage. You may need to free some space first by<br />
detaching virtual disks in storage created earlier<br />
with the DEFINE comm<strong>and</strong> that you are no longer<br />
using.<br />
Attention: Any virtual disk in storage created<br />
with the DEFINE comm<strong>and</strong> is immediately<br />
destroyed when detached.<br />
If the DEFINE comm<strong>and</strong> still fails, contact your<br />
system administrator <strong>and</strong> request that the user or<br />
system limit on virtual disk in storage space be<br />
increased.<br />
H<strong>CP</strong>092E Device vdev not defined; device vdev<br />
already defined<br />
Explanation: The virtual device specified is already<br />
defined within the virtual machine’s configuration. If the<br />
type is CONSOLE, your console was not defined<br />
because only one virtual CONSOLE is allowed on each<br />
virtual machine configuration.<br />
<strong>System</strong> Action: <strong>System</strong> operation continues.<br />
User Response: Reissue the comm<strong>and</strong>; specify a<br />
virtual device that is not already defined within the<br />
virtual machine configuration, or detach the conflicting<br />
virtual device before reissuing the comm<strong>and</strong>.<br />
If you want to redefine your console to some other<br />
device type, you must first detach your current console<br />
<strong>and</strong> then define the new one.<br />
H<strong>CP</strong>093E Storage size requested (reqsize)<br />
exceeds maximum allowed on this<br />
processor (maxsize). Size set to<br />
maximum allowed.<br />
Explanation: The size requested for the primary<br />
(BASE) address space in your virtual machine is larger<br />
than the real processor permits. The size you requested<br />
(reqsize) has been lowered to the maximum that this<br />
processor supports (maxsize).<br />
<strong>System</strong> Action: The base address space for the<br />
virtual machine is created using the maximum size for<br />
the real processor.<br />
User Response: Ensure that your operating system<br />
<strong>and</strong> applications can execute successfully in a virtual<br />
machine with the lower storage size.