|
|
Updated:
11 December 1998
|
OpenVMS System Messages: Companion Guide for Help
Message Users
NAMETOOLONG, link name is too long
Facility: LAT, LAT Facility
Explanation: An attempt was made to create or set a
link with a name longer than 16 characters.
User Action: Shorten the link name.
NEGSHBREF, shared memory control block negative refcnt
Facility: BUGCHECK, System Bugcheck
Explanation: The OpenVMS software detected an
irrecoverable, inconsistent condition. After all physical memory is
written to a system dump file, the system automatically reboots if the
BUGREBOOT system parameter is set to 1.
User Action: Use the BACKUP command with the /IGNORE=NOBACKUP qualifier to make a backup save set of the system dump file and the error log file active at the time of the error. Contact a DIGITAL support representative and describe the conditions leading to the error.
NETNOBUF, NETACP - buffer allocation failure
Facility: BUGCHECK, System Bugcheck
Explanation: The OpenVMS software detected an
irrecoverable, inconsistent condition. After all physical memory is
written to a system dump file, the system automatically reboots if the
BUGREBOOT system parameter is set to 1.
User Action: Use the BACKUP command with the /IGNORE=NOBACKUP qualifier to make a backup save set of the system dump file and the error log file active at the time of the error. Contact a DIGITAL support representative and describe the conditions leading to the error.
NETNOSTATE, NETACP - no state transition
Facility: BUGCHECK, System Bugcheck
Explanation: The OpenVMS software detected an
irrecoverable, inconsistent condition. After all physical memory is
written to a system dump file, the system automatically reboots if the
BUGREBOOT system parameter is set to 1.
User Action: Use the BACKUP command with the /IGNORE=NOBACKUP qualifier to make a backup save set of the system dump file and the error log file active at the time of the error. Contact a DIGITAL support representative and describe the conditions leading to the error.
NETRCVPKT, NETACP - no receive I/O packet
Facility: BUGCHECK, System Bugcheck
Explanation: The OpenVMS software detected an
irrecoverable, inconsistent condition. After all physical memory is
written to a system dump file, the system automatically reboots if the
BUGREBOOT system parameter is set to 1.
User Action: Use the BACKUP command with the /IGNORE=NOBACKUP qualifier to make a backup save set of the system dump file and the error log file active at the time of the error. Contact a DIGITAL support representative and describe the conditions leading to the error.
NETSYSSRV, NETACP - unexpected system service failure
Facility: BUGCHECK, System Bugcheck
Explanation: The OpenVMS software detected an
irrecoverable, inconsistent condition. After all physical memory is
written to a system dump file, the system automatically reboots if the
BUGREBOOT system parameter is set to 1.
User Action: Use the BACKUP command with the /IGNORE=NOBACKUP qualifier to make a backup save set of the system dump file and the error log file active at the time of the error. Contact a DIGITAL support representative and describe the conditions leading to the error.
NETTRANCNT, NETACP - transaction count zero
Facility: BUGCHECK, System Bugcheck
Explanation: The OpenVMS software detected an
irrecoverable, inconsistent condition. After all physical memory is
written to a system dump file, the system automatically reboots if the
BUGREBOOT system parameter is set to 1.
User Action: Use the BACKUP command with the /IGNORE=NOBACKUP qualifier to make a backup save set of the system dump file and the error log file active at the time of the error. Contact a DIGITAL support representative and describe the conditions leading to the error.
NETUAFACC, error accessing network authorization file
Facility: LOGIN, Login Procedure
Explanation: LOGIN cannot read the
SYS$SYSTEM:NETPROXY.DAT network user authorization file.
User Action: Determine whether the file
SYS$SYSTEM:NETPROXY.DAT exists and, if it does, make sure it is not
protected against system read access.
NEWLINK, created link 'link-name'
Facility: LAT, LAT Facility
Explanation: The specified link has been created by
LATCP.
User Action: None.
NEWLOGNAME, created logical name 'logical-name' in table 'table-name'
Facility: LAT, LAT Facility
Explanation: The specified logical name has been
created by LATCP in the specified table.
User Action: None.
NEWPORT, created port 'port-name'
Facility: LAT, LAT Facility
Explanation: The specified port has been created by
LATCP.
User Action: None.
NEWSAVSET, now beginning save set 'save set'
Facility: BACKUP, Backup Utility
Explanation: This message indicates the beginning of a
new save set during a wildcard list or restore operation.
User Action: None.
NEWSERVICE, created service 'service-name'
Facility: LAT, LAT Facility
Explanation: The specified service has been created by
LATCP.
User Action: None.
NEWTAPE, place volume 'volume' on device 'device'
Facility: BACKUP, Backup Utility
Explanation: The volume should be placed on the
specified device.
User Action: If you use the /NOASSIST qualifier, you
should place the volume in the drive. Otherwise, you should wait for
the operator to do so.
NEXNOTUBA, nexus is not a UNIBUS adapter
Facility: SYSGEN, System Generation Utility
Explanation: This message is returned from SHOW/UNIBUS
when you specify an adapter other than a UNIBUS adapter.
User Action: Reenter the command, specifying a valid
UNIBUS adapter.
NEXTVOL, volume 'volume' mounted - operation continues
Facility: BACKUP, Backup Utility
Explanation: This message indicates that the next
volume required for the backup operation has been mounted.
User Action: None.
No Path-Block During Virtual Circuit Close - REMOTE PORT 'xxx'
Facility: Cluster Port Driver
Explanation: The port driver attempts to reinitialize
the port; after 50 failed attempts, it marks the device off line.
User Action: Keep the error logs and crash dumps from
the local and remote systems, and contact a DIGITAL support representative.
NOACCMBREX, unable to access all members of existing shadow set
Facility: SHADOW, Volume Shadowing Software
Explanation: A currently mounted shadow set member was
not available to this system during boot time for the number of seconds
specified in the SHADOW_SYS_WAIT system parameter.
User Action: Verify that the shadow set member device
is ready and that the volume is properly loaded.
NOACP, no LATACP to process request
Facility: LAT, LAT Facility
Explanation: Information was requested from the local
LAT software, but LATACP is not currently running on the local node.
User Action: Check to see whether LAT startup has
executed correctly or if LAT shutdown has been performed on the local
node.
NOACPCHAN, failure to assign ACP channel
Facility: BUGCHECK, System Bugcheck
Explanation: The OpenVMS software detected an
irrecoverable, inconsistent condition. After all physical memory is
written to a system dump file, the system automatically reboots if the
BUGREBOOT system parameter is set to 1.
User Action: Use the BACKUP command with the /IGNORE=NOBACKUP qualifier to make a backup save set of the system dump file and the error log file active at the time of the error. Contact a DIGITAL support representative and describe the conditions leading to the error.
NOACPDEV, device named by /PROCESSOR:SAME has no ACP
Facility: MOUNT, Mount Utility
Explanation: The /PROCESSOR qualifier requested that
the ACP currently processing a specified device be used for another
device, but the first device does not have an ACP.
User Action: Reenter the command; select a different
option for the /PROCESSOR qualifier.
NOACPMAIL, failure to create ACP mailbox
Facility: BUGCHECK, System Bugcheck
Explanation: The OpenVMS software detected an
irrecoverable, inconsistent condition. After all physical memory is
written to a system dump file, the system automatically reboots if the
BUGREBOOT system parameter is set to 1.
User Action: Use the BACKUP command with the /IGNORE=NOBACKUP qualifier to make a backup save set of the system dump file and the error log file active at the time of the error. Contact a DIGITAL support representative and describe the conditions leading to the error.
NOADAPTER, no adapter (nexus) number specified
Facility: SYSGEN, System Generation Utility
Explanation: The /ADAPTER qualifier must be specified
in the SYSGEN command CONNECT.
User Action: Correct and reenter the command.
NOALOCLASS, allocation class not allowed with shadowing phase II
virtual unit name
Facility: MOUNT, Mount Utility
Explanation: An allocation class was specified in the
name of the virtual unit. Allocation classes are not allowed in virtual
unit names with volume shadowing phase II (OpenVMS Volume Shadowing).
User Action: Reenter the command without specifying an
allocation class on the virtual unit. The virtual unit must be
specified in the form DSA or DSAnnnn, where nnnn
represents a unique number from 0 to 9999.
NOAPIARGS, callable interface required parameter not specified or
invalid
Facility: BACKUP, Backup Utility
Explanation: Either a required parameter was not
specified or the specified parameter pointed to an invalid set of
options.
User Action: Note the argument passed to the BACKUP
API and examine the set of options for correctness; then specify an
argument that points to a non-zero set of options. (Refer to the BACKUP
documentation and the BACKUP API definitions files for valid option
types and values.)
NOAQBACP, no AQB for ACP
Facility: BUGCHECK, System Bugcheck
Explanation: The OpenVMS software detected an
irrecoverable, inconsistent condition. After all physical memory is
written to a system dump file, the system automatically reboots if the
BUGREBOOT system parameter is set to 1.
User Action: Use the BACKUP command with the /IGNORE=NOBACKUP qualifier to make a backup save set of the system dump file and the error log file active at the time of the error. Contact a DIGITAL support representative and describe the conditions leading to the error.
NOAUTOCNF, autoconfigure all is inhibited
Facility: SYSGEN, System Generation Utility
Explanation: The SYSGEN parameter NOAUTOCONFIG is set
to 1.
User Action: Set NOAUTOCONFIG to 0 and reenter the
command.
NOBACKUP, 'string' data not copied, file marked NOBACKUP
Facility: BACKUP, Backup Utility
Explanation: A save operation was performed on a file
marked NOBACKUP. Therefore, only the file header was saved; no data was
transferred to the save set.
User Action: Either use the /BACKUP qualifier with the
SET FILE command to specify that the file be backed up, or add the
/IGNORE=NOBACKUP qualifier to the BACKUP command line.
NOBADDATA, bad block data not found on 'device-name'
Facility: BACKUP, Backup Utility
Explanation: Software bad block data is not present on
the volume. The volume has been initialized with no bad blocks.
User Action: Execute the Bad Block Locator utility
before using the volume.
NOBITMAP, no valid storage bitmap found on 'device-name'
Facility: BACKUP, Backup Utility
Explanation: The Backup utility encountered an error
during an attempt to search for the storage bitmap file,
[000000]BITMAP.SYS;1, on the specified volume. The volume cannot be
used as a save-set disk.
User Action: Retry the operation using a properly
initialized Files--11 On-Disk Structure Level 2 volume.
NOBUFPCKT, required buffer packet not present
Facility: BUGCHECK, System Bugcheck
Explanation: The OpenVMS software detected an
irrecoverable, inconsistent condition. After all physical memory is
written to a system dump file, the system automatically reboots if the
BUGREBOOT system parameter is set to 1.
User Action: Use the BACKUP command with the /IGNORE=NOBACKUP qualifier to make a backup save set of the system dump file and the error log file active at the time of the error. Contact a DIGITAL support representative and describe the conditions leading to the error.
NOBVPVCB, blocked volume virtual page not found in VCB
Facility: BUGCHECK, System Bugcheck
Explanation: The OpenVMS software detected an
irrecoverable, inconsistent condition. After all physical memory is
written to a system dump file, the system automatically reboots if the
BUGREBOOT system parameter is set to 1.
User Action: Use the BACKUP command with the /IGNORE=NOBACKUP qualifier to make a backup save set of the system dump file and the error log file active at the time of the error. Contact a DIGITAL support representative and describe the conditions leading to the error.
NOCLUDEV, server not loaded, no cluster device
Facility: STACONFIG, Standalone Configure Process
Explanation: No port descriptor table was found on
this node. Either there is no CI or NI adapter on this node, or the
port drivers corresponding to either of the devices has not been loaded.
User Action: Make sure the node you are loading the
server on is configured so that it can participate in an OpenVMS
Cluster environment. If it does not have either an Ethernet or a CI
adapter, the MSCP server cannot be loaded (set MSCP_LOAD to 0). If you
have one of these adapters, make sure the VAXCLUSTER parameter is set
to a nonzero value. If the node participates in a local area OpenVMS
Cluster environment, that NISCS_LOAD is set to 1.
NOCLUSTER, server not loaded, SCS not available
Facility: STACONFIG, Standalone Configure Process
Explanation: The SYSGEN parameters for this system
request that the MSCP server be loaded, but none of the underlying SCS
services are loaded. These SCS services are necessary for the operation
of the MSCP server.
User Action: Make sure the VAXCLUSTER parameter is set
to a nonzero value, or change the MSCP_LOAD parameter to 0, so that the
server is not loaded.
NOCOPYMBR, Boot from copy member not permitted
Facility: SHADOW, Volume Shadowing Software
Explanation: A boot was attempted from a shadow copy
member.
User Action: Reboot the system from a valid shadow set
member.
NODEVADAP, no devices on adapter 'n'
Facility: SYSGEN, System Generation Utility
Explanation: A SHOW/CONFIGURATION operation was tried
on an adapter that has no devices.
User Action: Reenter the command, specifying an
adapter that has devices.
NODEVAVL, device 'device-name' is not available for mounting.
['optional comment']
Facility: MOUNT, Mount Utility
Explanation: Someone else has allocated the device you
requested.
User Action: The operator can either abort the mount
or redirect the mount to a different device. To redirect the mount to a
different device, specify SUBSTITUTE in the reply text, as follows:
REPLY/TO=identification-number "SUBSTITUTE device-name"
|
To cancel the mount, use the /ABORT qualifier:
REPLY/ABORT=identification-number
|
Alternatively, the user can enter Ctrl/Y to abort the mount operation
and then mount a different device.
NODEVICE, no device currently selected
Facility: RBLD, REBUILD Command (Mount Utility)
Explanation: The rebuild operation was supplied with
an invalid device.
User Action: If this error can be reliably reproduced,
contact a Digital support representative.
NOEXTAUTH, external authentication service disabled or unavailable
Facility: LOGIN, Login Procedure
Explanation: A login attempt using external
authentication cannot be completed because the external authentication
service cannot be activated or a network problem prevented the
authentication from completing. Users having the ExtAuth flag set in
their user authorization record are authenticated using an external
authentication service if this service has been enabled on the system.
User Action: The external authentication image must be
installed as a known shareable image by the system manager. Be sure
that the systemwide, executive-mode logical name SYS$ACME_MODULE
correctly describes the location of this image and that the image is
world readable (W:RE). Refer to the OpenVMS Guide to System Security for more information
about configuring external authentication on your system.
NOFILACC, user has no access to magnetic tape file on 'device'
Facility: MOUNT, Mount Utility
Explanation: You do not have access rights for the
specified magnetic tape file on the volume.
User Action: Log in to your account again with the
appropriate access rights, or set the necessary VOLPRO privilege to
access the volume.
NOFILES, no files selected from 'file-spec'
Facility: BACKUP, Backup Utility
Explanation: No files matched the input file selection
criteria.
User Action: Reevaluate the command to ensure that the
obtained results are correct.
NOHDJMT, no Head-JMT in JMT list (journaling)
Facility: BUGCHECK, System Bugcheck
Explanation: The OpenVMS software detected an
irrecoverable, inconsistent condition. After all physical memory is
written to a system dump file, the system automatically reboots if the
BUGREBOOT system parameter is set to 1.
User Action: Use the BACKUP command with the /IGNORE=NOBACKUP qualifier to make a backup save set of the system dump file and the error log file active at the time of the error. Contact a DIGITAL support representative and describe the conditions leading to the error.
NOHOMEBLK, no valid home block found on 'device-name'
Facility: BACKUP, Backup Utility
Explanation: The Backup utility encountered an error
during an attempt to search for the Files--11 home block on the
specified volume. The volume cannot be used as a save set disk.
User Action: Retry the operation using a properly
initialized Files--11 On-Disk Structure Level 2 volume.
NOICBM, failed to find ICBM with prefix 'prefix'
Facility: IOGEN
Explanation: No IOGEN Configuration Building Module
(ICBM) can be found with the specified prefix. The file either does not
exist or is not installed.
User Action: Check if the file exists and ensure that
it is installed as a known image. See the Install utility in the
OpenVMS System Management Utilities Reference Manual for instructions on installing a known image.
NOIDBAVAIL, unable to allocate an IDB
Facility: LAT, LAT Facility
Explanation: LATCP cannot allocate enough virtual
memory for an internal data structure needed to execute a command.
User Action: Take action based on the accompanying message.
NOINDEXF, no valid index file header found on 'device-name'
Facility: BACKUP, Backup Utility
Explanation: The Backup utility encountered an error
during an attempt to search for the index file, [000000]INDEXF.SYS;1,
on the specified volume. The volume cannot be used as a save set disk.
User Action: Retry the operation using a properly
initialized Files--11 On-Disk Structure Level 2 volume.
NOITMLST, unable to allocate virtual memory for command itemlist
Facility: LAT, LAT Facility
Explanation: LATCP cannot allocate enough virtual
memory for a LAT item list needed to execute a command.
User Action: Take action based on the accompanying message.
NOLOCAUTH, not authorized to override external authentication
Facility: LOGIN, Login Procedure
Explanation: An attempt is being made to bypass
external authentication using the /LOCAL_PASSWORD qualifier during
login. This qualifier requires SYSPRV privilege unless local
authentication has been configured on a systemwide basis. Use of this
qualifier is restricted to users who have the ExtAuth flag set in their
user authorization record. Refer to the OpenVMS Guide to System Security for more
information.
User Action: Ensure that anyone using the
/LOCAL_PASSWORD qualifier is marked for external authentication (that
is, the ExtAuth flag is set in their user authorization record) and
that the user is authorized for SYSPRV privilege (unless systemwide
local authentication is enabled).
NOMASTER, no master member found for this virtual unit
Facility: MOUNT, Mount Utility
Explanation: None of the specified shadow set members
is suitable to be a master unit for the shadow set. Accompanying error
messages explain why each of the candidate members cannot be a master.
User Action: Correct the problems reported by the
accompanying messages or locate a suitable master member; then retry
the mount operation.
NOMATCH,
The processor on SCSI bus 'device-name', ID 'slot-number',
is
attached using controller 'device-name'. This condition creates
multiple names for the same device, which can lead to data corruption.
Facility: STACONFIG, Standalone Configure Process
Explanation: The local and remote nodes are attached
to the SCSI bus through unmatched ports.
User Action: Connect the nodes to the SCSI bus through
matching ports on each system.
NOMULTBK, ACP multiple block buffering not supported yet
Facility: BUGCHECK, System Bugcheck
Explanation: The OpenVMS software detected an
irrecoverable, inconsistent condition. After all physical memory is
written to a system dump file, the system automatically reboots if the
BUGREBOOT system parameter is set to 1.
User Action: Use the BACKUP command with the /IGNORE=NOBACKUP qualifier to make a backup save set of the system dump file and the error log file active at the time of the error. Contact a DIGITAL support representative and describe the conditions leading to the error.
NONCONTIG, 'file-name' is not contiguous due to insufficient contiguous
space
Facility: BACKUP, Backup Utility
Explanation: The specified file was originally
allocated contiguous blocks. However, because the output volume lacked
enough space for contiguous blocks, the file has been allocated
noncontiguous blocks.
User Action: If necessary, reorganize the volume to
free a sufficient number of contiguous blocks, and reenter the command.
NONEDEL, no files processed on deletion pass
Facility: BACKUP, Backup Utility
Explanation: The Backup utility did not delete any
files in the deletion pass.
User Action: None.
NONEREC, no files processed on recording pass
Facility: BACKUP, Backup Utility
Explanation: The Backup utility did not update the
backup date on any files in the recording pass.
User Action: None.
NONEXSTACP, Nonexistent ACP process
Facility: BUGCHECK, System Bugcheck
Explanation: The OpenVMS software detected an
irrecoverable, inconsistent condition. After all physical memory is
written to a system dump file, the system automatically reboots if the
BUGREBOOT system parameter is set to 1.
User Action: Use the BACKUP command with the /IGNORE=NOBACKUP qualifier to make a backup save set of the system dump file and the error log file active at the time of the error. Contact a DIGITAL support representative and describe the conditions leading to the error.
NONLOCAL, device is not a local device
Facility: MOUNT, Mount Utility
Explanation: The device name specified in a command or
program request contains a network node name.
User Action: Verify the device name (or logical name,
if a logical name is specified) and reenter the command, specifying a
device on the host system.
NONODE, node name has not been initialized
Facility: LAT, LAT Facility
Explanation: The local LAT node has not been
initialized.
User Action: Use the LATCP command SET NODE to
initialize the local LAT node.
NONPHYSET, nonphysical save set supplied to physical operation
Facility: BACKUP, Backup Utility
Explanation: A save set created without the /PHYSICAL
qualifier is used as input to an operation with the /PHYSICAL qualifier.
User Action: Enter the BACKUP/LIST command to
determine how the save set is created. Reevaluate the operation and
reenter the command.
NONSMPDRV, nonsmpized driver cannot be loaded
Facility: SYSGEN, System Generation Utility
Explanation: SYSGEN cannot load this driver because
the driver has not been modified to support symmetric multiprocessing
(SMP).
User Action: Modify the driver to conform to symmetric
multiprocessing requirements, or turn off SMP.
NONSTDUNI, UNIBUS in nonstandard configuration, device 'device-name'
vector is wrong
Facility: SYSGEN, System Generation Utility
Explanation: The vector on the specified device needs
to be reconfigured.
User Action: Contact a DIGITAL support representative.
NOODS1, Files--11 structure level 1 not supported
Facility: MOUNT, Mount Utility
Explanation: You attempted to mount a Files--11
Structure Level 1 volume on an OpenVMS Alpha system. OpenVMS Alpha does
not support this type of volume.
User Action: Mount the volume on an OpenVMS VAX system.
NOOPER, no operator is available to handle the request
Facility: BACKUP, Backup Utility
Explanation: There are no operator terminals enabled
to handle this request.
User Action: Either service the request yourself, or
abort the request. To ensure that no operator intervention is required
in a backup operation, specify the /NOASSIST qualifier on the command
line.
NOOPR, no operator available to service request
Facility: MOUNT, Mount Utility
Explanation: No operator is present to service the
request.
User Action: Service the request yourself, or abort
the request.
NO_PAGED_ISDS, cannot load paged ISDs in SYSBOOT
Facility: LOADER, Executive Image Loader
Explanation: SYSBOOT failed to load the executive
image because it contains either paged code or paged data sections.
User Action: Correct the link procedure used to build
the executive image; specify the appropriate PSECT_ATTR and COLLECT
statements to eliminate the paged image sections.
NOPARAM, no such parameter
Facility: SYSBOOT, System Bootstrap Facility
Facility: SYSGEN, System Generation Utility
Explanation: The parameter name specified in a SET or
SHOW command is not valid.
User Action: Correct and reenter the command.
NOPATHTBL, invalid or nonexistent path table; built from directories
Facility: SYSTEM, System Services
Explanation: A path table record was not found or it
was illegally formatted according to the ISO 9660 standard. An
in-memory path table is constructed at MOUNT time by walking the entire
directory structure. This operation can take a few minutes.
User Action: Notify the manufacturer of the CD-ROM
media that their product is noncompliant.
NO_POOL, not enough nonpaged pool
Facility: LOADER, Executive Image Loader
Explanation: An attempt was made to load an image
before nonpaged pool has been initialized.
User Action: Contact a DIGITAL support representative.
NOPRIV, user denied privilege to write to volume on 'device-name'
Facility: MOUNT, Mount Utility
Explanation: The user requested initialization of a
volume but does not have the privilege to write to it.
User Action: Mount either a tape that the user has
write privilege to, or a blank tape. Request initialization of this
tape when replying to the next mount request.
NOPROXYDB, cannot find proxy database file NET$PROXY.DAT
Facility: SECSRV, Security Server
Explanation: The security server cannot find the proxy
database file NET$PROXY.DAT.
User Action: If a proxy database exists, make sure
that it is in SYS$SYSTEM or that the logical name NET$PROXY points to
it.
If a proxy database does not exist, create one by using the DCL command
RUN SYS$SYSTEM:CONVERT_PROXY to convert the old NETPROXY.DAT file or by
issuing the CREATE/PROXY command in the Authorize utility to create a
new NET$PROXY.DAT file.
NOPTBLDIR, no path table or directory records found
Facility: SYSTEM, System Services
Explanation: An attempt was made to mount media that
is noncompliant with the ISO 9660 standard. This is a fatal error.
User Action: Notify the manufacturer of the CD-ROM
media that their product is noncompliant.
NORATINGIMAGE, LAT rating image not loaded
Facility: LAT, LAT Facility
Explanation: An attempt was made to start the LAT
ancillary control process (LATACP), but the LAT$RATING image was not
loaded.
User Action: Be sure to start LAT by executing the
LAT$STARTUP command procedure to access the support startup files
supplied by Digital. The LAT$STARTUP command procedure executes other
command procedures, including LAT$CONFIG, which loads the LAT$RATING
image.
NORCP, RCP not active
Facility: BUGCHECK, System Bugcheck
Explanation: The OpenVMS software detected an
irrecoverable, inconsistent condition. After all physical memory is
written to a system dump file, the system automatically reboots if the
BUGREBOOT system parameter is set to 1.
User Action: Use the BACKUP command with the /IGNORE=NOBACKUP qualifier to make a backup save set of the system dump file and the error log file active at the time of the error. Contact a DIGITAL support representative and describe the conditions leading to the error.
NORCVBUF, NETACP - no receive buffer available
Facility: BUGCHECK, System Bugcheck
Explanation: The OpenVMS software detected an
irrecoverable, inconsistent condition. After all physical memory is
written to a system dump file, the system automatically reboots if the
BUGREBOOT system parameter is set to 1.
User Action: Use the BACKUP command with the /IGNORE=NOBACKUP qualifier to make a backup save set of the system dump file and the error log file active at the time of the error. Contact a DIGITAL support representative and describe the conditions leading to the error.
NOSCS, error loading SCS code
Facility: SYSGEN, System Generation Utility
Explanation: SCSLOA.EXE cannot be loaded.
User Action: Do not attempt to load SCSLOA.EXE.
NOSHADLIC, no volume shadowing license available
Facility: MOUNT, Mount Utility
Explanation: Your system does not have a license
enabled for the OpenVMS Volume Shadowing software.
User Action: Obtain and install an OpenVMS Volume
Shadowing license.
NOSHADOW, VMS Volume Shadowing Phase II is not enabled
Facility: MOUNT, Mount Utility
Explanation: The OpenVMS Volume Shadowing software is
not enabled.
User Action: The system manager must reboot the system
with SYSGEN parameter SHADOWING set to 2.
NOSHDWMEM, no eligible shadow set members to mount the shadow set
Facility: MOUNT, Mount Utility
Explanation: No shadow members were specified in the
MOUNT command, and the shadow set is not currently mounted. (If the
shadow set is already mounted on another node in the cluster, MOUNT can
determine the shadow set membership from the other node.)
User Action: Reenter the command, using the /SHADOW
qualifier to specify the names of the shadow set members.
NOSHMGSD, No shared memory global section dsc found for page
Facility: BUGCHECK, System Bugcheck
Explanation: The OpenVMS software detected an
irrecoverable, inconsistent condition. After all physical memory is
written to a system dump file, the system automatically reboots if the
BUGREBOOT system parameter is set to 1.
User Action: Use the BACKUP command with the /IGNORE=NOBACKUP qualifier to make a backup save set of the system dump file and the error log file active at the time of the error. Contact a DIGITAL support representative and describe the conditions leading to the error.
NOSLS, qualifier '/qualifier' is invalid when SLS is not installed
Facility: BACKUP, Backup Utility
Explanation: The command line contains a qualifier
specific to the Storage Library System (SLS), but SLS is not installed
on the system where the BACKUP command was executed.
User Action: Remove the qualifier that is specific to
SLS, or install SLS on the system where the BACKUP command is executed.
NOSUCHFILE, file 'file-name' does not exist.
Facility: STDRV, System Startup Driver
Explanation: A startup component file specified in the
startup database does not exist during system startup.
User Action: Verify that the entry in the startup
database is correct. If it is correct, verify that the component file
is located in the SYS$STARTUP directory.
NO_SUCH_IMAGE, the requested image cannot be located
Facility: LOADER, Executive Image Loader
Explanation: A load request was made for an executive
image that was linked against a shareable image that is not loaded. The
only legal shareable images for executives are SYS$BASE_IMAGE and
SYS$PUBLIC_VECTORS.
User Action: Use /NOSYSSHR or /NOSYSLIB to correct the
link procedure to exclude any shareable images other than
SYS$BASE_IMAGE or SYS$PUBLIC_VECTORS.
NOSUCHMEM, no shared memory found at specified NEXUS
Facility: SYSGEN, System Generation Utility
explanation: The desired shared memory unit number was
not found in a search of the backplane interconnect adapter list.
User Action: Reenter the command, specifying the
correct device unit number.
NOSUCHRVN, /VOLUME = 'number' invalid, volume set contains 'number'
volumes
Facility: BACKUP, Backup Utility
Explanation: The value specified for the /VOLUME
qualifier is larger than the number of volumes in the volume set.
User Action: Reenter the command, using a smaller
value.
NOSUCHSEC, no such (global) section
Facility: SYSTEM, System Services
Explanation: The global section name specified in a
request to map a global section does not exist.
User Action: Verify that the program that creates the
global section successfully created the section, and that the section
has not been deleted. Also, check that the logical name strings
specifying the global section name match.
NOSUCHUSER, no such user
Facility: LOGIN, Login Procedure
Explanation: The specified user name does not exist.
This message is written to the system accounting and security audit
records; the NOTVALID message displays to the user.
User Action: None.
NOSYSDISK, no access to system disk
Facility: BACKUP, Backup Utility
Explanation: The system disk is not accessible.
User Action: Determine why the system disk is
inaccessible. If possible, make the system disk operational and retry
the BACKUP command.
Not enough SPTEs to take selective system dump - switching to complete
memory dump
Facility: BUGCHECK, System Bugcheck
Explanation: When writing a selective dump (SYSGEN
parameter DUMPSTYLE set to 1), the OpenVMS operating system needs to
remap portions of memory for easy access and for efficient writing of
the dump file. The OpenVMS operating system requests 127 system page
table entries (SPTEs) during the bootstrap sequence so that the SPTEs
are ready when needed. If the system is configured so that there are
not sufficient SPTEs to create a selective dump, the system attempts to
write a complete dump.
User Action: When the system comes back up, run
AUTOGEN and reboot with a larger SYSGEN parameter SPTREQ.
NOT1STVOL, 'save-set-spec' is not the start of a save set
Facility: BACKUP, Backup Utility
Explanation: The volume mounted as the first volume of
the specified save set is a continuation volume. This is valid if the
operation is not a restore with the /IMAGE qualifier.
User Action: Reevaluate the operation to ensure that
the correct results are obtained.
NOTACLU, 'device-name' is not a clusterwide device
Facility: MOUNT, Mount Utility
Explanation: An attempt was made to mount a device on
all nodes in the OpenVMS Cluster environment by specifying the /CLUSTER
qualifier; however, the device specified is not available clusterwide,
nor can it be made available clusterwide.
User Action: Reenter the command without the /CLUSTER
qualifier.
NOTANSI, not ANSI volume on 'device-name'
Facility: MOUNT, Mount Utility
Explanation: The volume on the specified device is not
an ANSI-formatted magnetic tape.
User Action: Initialize the tape and reenter the mount
request, or mount the tape foreign.
NOTANSI, tape is not valid ANSI format
Facility: BACKUP, Backup Utility
Explanation: The volume does not have ANSI-standard
labels.
User Action: Locate and mount the correct volume.
NOTASCII, parameter 'name' is not ASCII type
Facility: SYSBOOT, System Bootstrap Facility
Facility: SYSGEN, System Generation Utility
Explanation: An ASCII value is specified in a SET
command for a non-ASCII parameter.
User Action: Reenter the command, specifying a valid
parameter value.
NOTBKBLOCK, invalid subsystem code in save set
Facility: BACKUP, Backup Utility
Explanation: An incorrect value occurred in the
subsystem code field of a save-set block. Data in the save set is
corrupt.
User Action: None. The save-set data is lost.
NOTCOM, BATCH mode can only be used for .COM files
Facility: STDRV, System Startup Driver
Explanation: An entry in the STARTUP component file
specifies a component file to be run with the BATCH command whose file
type is not .COM.
User Action: Use the STARTUP MODIFY FILE command at
the SYSMAN> prompt to correct either the file name or the execution
mode.
NOTDDBDDB, corrupted DDB list
Facility: BUGCHECK, System Bugcheck
Explanation: The OpenVMS software detected an
irrecoverable, inconsistent condition. After all physical memory is
written to a system dump file, the system automatically reboots if the
BUGREBOOT system parameter is set to 1.
User Action: Use the BACKUP command with the /IGNORE=NOBACKUP qualifier to make a backup save set of the system dump file and the error log file active at the time of the error. Contact a DIGITAL support representative and describe the conditions leading to the error.
NOTDISM, unable to dismount 'device-id'
Facility: BACKUP, Backup Utility
Explanation: The Backup utility cannot dismount a tape
drive specified by the command line qualifier /RELEASE_TAPE.
User Action: Take action based on the accompanying message.
NOTFCBFCB, FCB linkage broken
Facility: BUGCHECK, System Bugcheck
Explanation: The OpenVMS software detected an
irrecoverable, inconsistent condition. After all physical memory is
written to a system dump file, the system automatically reboots if the
BUGREBOOT system parameter is set to 1.
User Action: Use the BACKUP command with the /IGNORE=NOBACKUP qualifier to make a backup save set of the system dump file and the error log file active at the time of the error. Contact a DIGITAL support representative and describe the conditions leading to the error.
NOTFCBWCB, Bad FCB pointer in window
Facility: BUGCHECK, System Bugcheck
Explanation: The OpenVMS software detected an
irrecoverable, inconsistent condition. After all physical memory is
written to a system dump file, the system automatically reboots if the
BUGREBOOT system parameter is set to 1.
User Action: Use the BACKUP command with the /IGNORE=NOBACKUP qualifier to make a backup save set of the system dump file and the error log file active at the time of the error. Contact a DIGITAL support representative and describe the conditions leading to the error.
NOTFCPWCB, Not FCP window in IRP
Facility: BUGCHECK, System Bugcheck
Explanation: The OpenVMS software detected an
irrecoverable, inconsistent condition. After all physical memory is
written to a system dump file, the system automatically reboots if the
BUGREBOOT system parameter is set to 1.
User Action: Use the BACKUP command with the /IGNORE=NOBACKUP qualifier to make a backup save set of the system dump file and the error log file active at the time of the error. Contact a DIGITAL support representative and describe the conditions leading to the error.
NOTGENDEV, not a generic device
Facility: MOUNT, Mount Utility
Explanation: An invalid generic device was specified.
User Action: Retry the operation, specifying a valid
generic device.
NOTIRPAQB, Not IRP pointer in AQB
Facility: BUGCHECK, System Bugcheck
Explanation: The OpenVMS software detected an
irrecoverable, inconsistent condition. After all physical memory is
written to a system dump file, the system automatically reboots if the
BUGREBOOT system parameter is set to 1.
User Action: Use the BACKUP command with the /IGNORE=NOBACKUP qualifier to make a backup save set of the system dump file and the error log file active at the time of the error. Contact a DIGITAL support representative and describe the conditions leading to the error.
NOTJOURNAL, 'file-spec' is not a BACKUP journal
Facility: BACKUP, Backup Utility
Explanation: The specified file does not have the
appropriate file attributes; it is not a Backup utility journal file.
User Action: Locate the correct file and reenter the
command.
NOTLABEL, 'volume-label' not on 'device-name'
Facility: MOUNT, Mount Utility
Explanation: The operator responded to a message from
the magnetic tape ACP with a successful completion, but the volume is
not correct. The volume label specified by the original DCL command
MOUNT, or the reply to an operator mount request, does not match the
volume label on the specified device.
User Action: Include the correct label in the next
reply to an operator mount request, or mount the correct volume on the
device. If you do not want to check the label, use the OVERRIDE:ID
qualifier in the original DCL command MOUNT. Verify that the device is
on line.
NOTLKB, Structure is not an LKB
Facility: BUGCHECK, System Bugcheck
Explanation: The OpenVMS software detected an
irrecoverable, inconsistent condition. After all physical memory is
written to a system dump file, the system automatically reboots if the
BUGREBOOT system parameter is set to 1.
User Action: Use the BACKUP command with the /IGNORE=NOBACKUP qualifier to make a backup save set of the system dump file and the error log file active at the time of the error. Contact a DIGITAL support representative and describe the conditions leading to the error.
NOTLOADED, LAT terminal port driver (LTDRIVER) is not loaded
Facility: LAT, LAT Facility
Explanation: An attempt was made to execute LATACP
when LTDRIVER was not loaded.
User Action: Check to see whether the LAT software is
properly configured.
NOTMODEM, VAX/VMS host system modem not wired correctly - contact your
system manager
Facility: LOGIN, Login Procedure
Explanation: The modem connected to the OpenVMS system
is not asserting the proper signal control. The terminal line is set to
/MODEM and TTDRIVER did not detect all the necessary modem signals
within 30 seconds of a login attempt.
User Action: The system manager should ensure that the
following conditions are met:
- The modem cable connecting the modem provides the correct signal.
- The terminal port supports modem use.
- The modem provides the correct signals in the correct order.
For information on how the TTDRIVER identifies a valid modem line,
refer to the section on modem control of terminal drivers in the
OpenVMS I/O User's Reference Manual.
NOTMTLMTL, Corrupted mounted volume list
Facility: BUGCHECK, System Bugcheck
Explanation: The OpenVMS software detected an
irrecoverable, inconsistent condition. After all physical memory is
written to a system dump file, the system automatically reboots if the
BUGREBOOT system parameter is set to 1.
User Action: Use the BACKUP command with the /IGNORE=NOBACKUP qualifier to make a backup save set of the system dump file and the error log file active at the time of the error. Contact a DIGITAL support representative and describe the conditions leading to the error.
NOTNUMBER, parameter 'name' is not numerical type
Facility: SYSBOOT, System Bootstrap Facility
Facility: SYSGEN, System Generation Utility
Explanation: In a SET command, a numeric value is
specified for a nonnumeric parameter.
User Action: Reenter the command, specifying a valid
parameter value.
NOTODS2, shadow members must be Files--11 Structure Level 2
Facility: MOUNT, Mount Utility
Explanation: A specified member of a shadow set is not
Files--11 On-Disk Structure Level 2 (ODS--2). A non-ODS--2 volume can
be added to a shadow set only as a copy target.
User Action: Find or initialize a valid ODS--2 volume
to act as a master for the shadow set.
NOTPARAM, not a parameter file
Facility: SYSGEN, System Generation Utility
Explanation: The file specified in the SYSGEN command
USE is not a valid parameter file.
User Action: Use a valid parameter file that is either
provided by the OpenVMS operating system or created by the SYSGEN
command WRITE in SYSGEN.
NOTPCB, Structure not PCB
Facility: BUGCHECK, System Bugcheck
Explanation: The OpenVMS software detected an
irrecoverable, inconsistent condition. After all physical memory is
written to a system dump file, the system automatically reboots if the
BUGREBOOT system parameter is set to 1.
User Action: Use the BACKUP command with the /IGNORE=NOBACKUP qualifier to make a backup save set of the system dump file and the error log file active at the time of the error. Contact a DIGITAL support representative and describe the conditions leading to the error.
NOTRAN, logical name cannot be translated
Facility: MOUNT, Mount Utility
Explanation: The DCL command MOUNT or INITIALIZE
attempted logical name translation on a device name or logical name and
failed to translate the logical name. Possibly logical names are nested
too deeply or a logical name is assigned to itself.
User Action: Use the DCL command SHOW LOGICAL to
verify the translation of the device name or logical name. If
necessary, reassign the logical name before reentering the MOUNT or
INITIALIZE command.
NOTRELVOL, relative volume 'nnn' not on device
Facility: MOUNT, Mount Utility
Explanation: Each volume in a volume set has a
relative number beginning with 1. The volume mounted on the device is
not the relative volume requested in the previous mount request.
User Action: Mount the correct volume on the device,
or abort the mount request if you do not have the correct volume.
NOTRULUCB, Bad RUL pointer in UCB (journaling)
Facility: BUGCHECK, System Bugcheck
Explanation: The OpenVMS software detected an
irrecoverable, inconsistent condition. After all physical memory is
written to a system dump file, the system automatically reboots if the
BUGREBOOT system parameter is set to 1.
User Action: Use the BACKUP command with the /IGNORE=NOBACKUP qualifier to make a backup save set of the system dump file and the error log file active at the time of the error. Contact a DIGITAL support representative and describe the conditions leading to the error.
NOTRVTVCB, Not RVT pointer in VCB
Facility: BUGCHECK, System Bugcheck
Explanation: The OpenVMS software detected an
irrecoverable, inconsistent condition. After all physical memory is
written to a system dump file, the system automatically reboots if the
BUGREBOOT system parameter is set to 1.
User Action: Use the BACKUP command with the /IGNORE=NOBACKUP qualifier to make a backup save set of the system dump file and the error log file active at the time of the error. Contact a DIGITAL support representative and describe the conditions leading to the error.
NOTSAVESET, 'save-set-spec' is not a BACKUP save set
Facility: BACKUP, Backup Utility
Explanation: The specified file does not have the
appropriate file attributes; it is not a save set.
User Action: Locate the correct file and reenter the
command.
NOTSHDWDEV, not a valid shadow set member
Facility: MOUNT, Mount Utility
Explanation: There are two possible causes for this
error:
- You did not specify an explicit allocation class in the device name
of a shadow set member.
- You specified a device that does not support volume shadowing to be
a shadow set member. Only certain disks, including Digital Storage
Architecture and SCSI disks, support volume shadowing.
User Action: Correct the command syntax or choose a
different device, and enter the command again.
NOTSHDWVU, invalid shadow set virtual unit
Facility: MOUNT, Mount Utility
Explanation: You entered an invalid device name for a
shadow set virtual unit; for example, a device name was specified with
the /SHADOW qualifier.
User Action: Reenter the command, specifying the
shadow set virtual unit as DSAnnn, with no allocation class or
node name.
NOTUCBIRP, not UCB pointer in IRP
Facility: BUGCHECK, System Bugcheck
Explanation: The OpenVMS software detected an
irrecoverable, inconsistent condition. After all physical memory is
written to a system dump file, the system automatically reboots if the
BUGREBOOT system parameter is set to 1.
User Action: Use the BACKUP command with the /IGNORE=NOBACKUP qualifier to make a backup save set of the system dump file and the error log file active at the time of the error. Contact a DIGITAL support representative and describe the conditions leading to the error.
NOTUCBRVT, not UCB pointer in RVT
Facility: BUGCHECK, System Bugcheck
Explanation: The OpenVMS software detected an
irrecoverable, inconsistent condition. After all physical memory is
written to a system dump file, the system automatically reboots if the
BUGREBOOT system parameter is set to 1.
User Action: Use the BACKUP command with the /IGNORE=NOBACKUP qualifier to make a backup save set of the system dump file and the error log file active at the time of the error. Contact a DIGITAL support representative and describe the conditions leading to the error.
NOTUCBUCB, corrupted UCB list
Facility: BUGCHECK, System Bugcheck
Explanation: The OpenVMS software detected an
irrecoverable, inconsistent condition. After all physical memory is
written to a system dump file, the system automatically reboots if the
BUGREBOOT system parameter is set to 1.
User Action: Use the BACKUP command with the /IGNORE=NOBACKUP qualifier to make a backup save set of the system dump file and the error log file active at the time of the error. Contact a DIGITAL support representative and describe the conditions leading to the error.
NOTUCBWCB, bad UCB pointer in window
Facility: BUGCHECK, System Bugcheck
Explanation: The OpenVMS software detected an
irrecoverable, inconsistent condition. After all physical memory is
written to a system dump file, the system automatically reboots if the
BUGREBOOT system parameter is set to 1.
User Action: Use the BACKUP command with the /IGNORE=NOBACKUP qualifier to make a backup save set of the system dump file and the error log file active at the time of the error. Contact a DIGITAL support representative and describe the conditions leading to the error.
NOT_UNL, image is not unloadable or not loaded
Facility: LOADER, Executive Image Loader
Explanation: A call was made to LDR$UNLOAD_IMAGE to
unload an executive image that is not loaded or that was not loaded
with the LDR$V_UNL flag bit set.
User Action: If you want to be able to unload an
executive image, be sure to set the LDR$V_UNL bit in the flags passed
to the LDR$LOAD_IMAGE routine when the image is loaded. The LDR$V_UNL
bit cannot be specified for OpenVMS-supplied executive images or for
images loaded using VMS$SYSTEM_IMAGES.DATA.
NOTVALID, user authorization failure
Facility: LOGIN, Login Procedure
Explanation: An incorrect user name, password, or both
was entered. The USERAUTH message simultaneously displays to the system
manager.
User Action: Repeat the login procedure.
NOTVCBUCB, not VCB pointer in UCB
Facility: BUGCHECK, System Bugcheck
Explanation: The OpenVMS software detected an
irrecoverable, inconsistent condition. After all physical memory is
written to a system dump file, the system automatically reboots if the
BUGREBOOT system parameter is set to 1.
User Action: Use the BACKUP command with the /IGNORE=NOBACKUP qualifier to make a backup save set of the system dump file and the error log file active at the time of the error. Contact a DIGITAL support representative and describe the conditions leading to the error.
NOTVOLSET, volume on 'device-name' not in volume set 'volume-label'
Facility: MOUNT, Mount Utility
Explanation: If the specified device is a disk, a
volume that is not part of a volume set was specified in a list of
volumes to be mounted.
If the specified device is a tape, the volume mounted on the device is
not part of the volume set specified by the file set identifier in the
first file in the volume set.
User Action: For a disk, mount the device by itself
using a separate MOUNT command, or use the /BIND qualifier to include
the device in the volume set.
For a tape, mount the correct volume on the device, or abort the mount
request if you do not have the correct volume.
NOTVVPVCB, not volume virtual page pointer in VCB
Facility: BUGCHECK, System Bugcheck
Explanation: The OpenVMS software detected an
irrecoverable, inconsistent condition. After all physical memory is
written to a system dump file, the system automatically reboots if the
BUGREBOOT system parameter is set to 1.
User Action: Use the BACKUP command with the /IGNORE=NOBACKUP qualifier to make a backup save set of the system dump file and the error log file active at the time of the error. Contact a DIGITAL support representative and describe the conditions leading to the error.
NOTWCBIRP, not WCB Pointer in IRP
Facility: BUGCHECK, System Bugcheck
Explanation: The OpenVMS software detected an
irrecoverable, inconsistent condition. After all physical memory is
written to a system dump file, the system automatically reboots if the
BUGREBOOT system parameter is set to 1.
User Action: Use the BACKUP command with the /IGNORE=NOBACKUP qualifier to make a backup save set of the system dump file and the error log file active at the time of the error. Contact a DIGITAL support representative and describe the conditions leading to the error.
NOTWCBWCB, corrupted WCB list
Facility: BUGCHECK, System Bugcheck
Explanation: The OpenVMS software detected an
irrecoverable, inconsistent condition. After all physical memory is
written to a system dump file, the system automatically reboots if the
BUGREBOOT system parameter is set to 1.
User Action: Use the BACKUP command with the /IGNORE=NOBACKUP qualifier to make a backup save set of the system dump file and the error log file active at the time of the error. Contact a DIGITAL support representative and describe the conditions leading to the error.
NOUNLOAD, driver is not unloadable
Facility: SYSGEN, System Generation Utility
Explanation: Either an attempt is made to reload a
driver that is marked unloadable (DPT$M_NOUNLOAD) in the driver
prologue table, or the unload routine of the driver indicates that the
driver should not be unloaded.
User Action: None.
NOUSRWCS, no user WCS halt restart
Facility: BUGCHECK, System Bugcheck
Explanation: The OpenVMS software detected an
irrecoverable, inconsistent condition. After all physical memory is
written to a system dump file, the system automatically reboots if the
BUGREBOOT system parameter is set to 1.
User Action: Use the BACKUP command with the /IGNORE=NOBACKUP qualifier to make a backup save set of the system dump file and the error log file active at the time of the error. Contact a DIGITAL support representative and describe the conditions leading to the error.
NOVALUE, qualifier 'qualifier' requires value
Facility: BACKUP, Backup Utility
Explanation: No value was given for the specified
qualifier.
User Action: Specify a value for the qualifier and
reenter the BACKUP command.
NOVOLACC, user has no access to magnetic tape volume on 'device'
Facility: MOUNT, Mount Utility
Explanation: The specified tape volume has ANSI VOL1
and HDR1 label accessibility fields that prevent the user from
accessing the volume.
The OpenVMS operating system does not use these fields. The ANSI access
code represents restrictions for file access that are agreed upon by
the originator and the recipient of the volume.
User Action: None.
NOVOLDATA, volume summary data for 'device-name' not found - /IMAGE
cannot be used
Facility: BACKUP, Backup Utility
Explanation: In a restore operation with the /IMAGE
qualifier, no volume initialization data exists. Either the save set is
created without the /IMAGE qualifier, or save-set data has been lost.
User Action: Attempt to recover data without the
/IMAGE qualifier. If this error occurs during a disk-to-disk (copy)
operation, it indicates a software error in the Backup utility; in this
case, contact a DIGITAL support representative.
NOVOLDESC, no CD-ROM volume descriptor found
Facility: SYSTEM, System Services
Explanation: Either an attempt was made to mount media
that is noncompliant with the ISO 9660 standard, or a CD-ROM volume
descriptor with a matching volume name was not found.
User Action: Try to determine the correct volume name
by issuing a MOUNT/OVERRIDE=IDENTIFIER command. If this fails, notify
the manufacturer of the CD-ROM media that their product is noncompliant.
NOVUID, no virtual unit ID found for generic mount
Facility: MOUNT, Mount Utility
Explanation: MOUNT could not find a free generic
virtual unit number for the shadow set. This means that all virtual
unit numbers from 100 to 9999 are in use.
User Action: Specify the MOUNT command using an
explicit shadow set virtual unit number.