OpenVMS Version 7.1 New Features Manual
Previous
| Contents
In the second case, you must delete a file before you can create
another file on the media.
FILESEQCHK, file identification sequence number check
Facility: SYSTEM, System Services
Explanation: This message can occur under either of
the following conditions:
- The file sequence number in the file header is not the expected
one. The directory entry points to a file that was deleted.
- An attempt was made to store more than 9999 file sections in a
file on a tape. This error might typically occur when using a large
capacity tape for backups.
User Action: In the first case cited above, remove the
directory entry using the following command:
DELETE file-spec
In the second case, you must delete a file section before you can add
another file section to that file.
FORMAT, device name is not specified in the format ddcu
Facility: PPPD, Point-to-Point Protocol Utility
Explanation: The device name is not specified in the
standard device name format (_ddcu).
User Action: Trace all logical names pointing to the
physical device to ensure that the final definition conforms to the
standard device name format (_ddcu).
ILLEGALACCM, illegal transmit ACCM bits are specified in value 'value'
Facility: PPPD, Point-to-Point Protocol Utility
Explanation: The PPPD command SET/TRANSMIT_ACCM
[ddcu:] specified a bit value that cannot be set.
User Action: Specify a new mask value in the range of
0X0 to 0XFFFFFFFF. Check the TCP/IP Networking on OpenVMS Systems manual for additional
restrictions on Asynchronous Control Character Map (ACCM) bit settings
for PPPD.
INCREDSYN, incomplete redirection syntax; supply missing file parameter
Facility: CLI, Command Language Interpreter (DCL)
Explanation: The redirection syntax is missing the
redirection file parameter.
User Action: Add the missing file parameter to the
redirection syntax.
INUSE, cannot connect; device is in use
Facility: PPPD, Point-to-Point Protocol Utility
Explanation: An attempt was made to connect to a
device that is in use.
User Action: Retry the connection when the device
becomes available.
INVALID_HW_ID, invalid hardware identifier
Facility: LICENSE, License Management Utility
Explanation: The hardware identifier required by this
licensed product is not on the available licenses.
User Action: Contact the software vendor for the
correct license.
INVALID_TOKEN, invalid product token
Facility: LICENSE, License Management Utility
Explanation: The product token required by this
licensed product is not on the available licenses.
User Action: Contact the software vendor for the
correct license.
INVASNCODE, invalid ASN item code of 'value'
Facility: PPPD, Point-to-Point Protocol Utility
Explanation: The specified ASN item code is not valid.
User Action: Contact a Digital support representative.
INVCONCHAR, invalid continuation character; a command sequence cannot
be terminated by a continuation character
Facility: CLI, Command Language Interpreter (DCL)
Explanation: A DCL continuation character was detected
in a DCL PIPE command sequence, where it is meaningless. The command
line continuation function is legal only in the context of the whole
PIPE command.
User Action: Remove the continuation character that
terminates the command sequence.
INVDIALSTS, invalid DIALOUT_MAIN return status of 'value'
Facility: PPPD, Point-to-Point Protocol Utility
Explanation: The specified I/O status returned by the
PPPD command DIAL_OUT [ddcu:] is not valid.
User Action: Contact a Digital support representative.
INVEUSRLEN, invalid external username length
Facility: SET, SET PASSWORD Command
Explanation: The external user name entered at the
prompt exceeds the maximum number of characters allowed.
User Action: Enter a user name that does not exceed
the maximum number of characters permitted by the authentication
modules on your system.
INVFLOWCTRL, cannot set hardware flow control on a serial port set to
both NOMODEM and NOCOMMSYNC
Facility: PPPD, Point-to-Point Protocol Utility
Explanation: The flow control setting for the current
serial port is not valid.
User Action: Use the XON_XOFF flow control setting or
have your system manager reset the communications port to MODEM and
COMMSYNC.
INVHANGASTINIT, invalid P1 passed in, P1 and io_port_block = 'value1'
'value2'
Facility: PPPD, Point-to-Point Protocol Utility
Explanation: An unexpected parameter was passed to the
hangup AST during the current DIAL_OUT operation.
User Action: Contact a Digital support representative.
INVHANGASTP1, unexpected condition in hangup AST, P1 is default
Facility: PPPD, Point-to-Point Protocol Utility
Explanation: The parameter that was passed to the
hangup AST was not set to SS$_HANGUP as expected during the current
DIAL_OUT operation.
User Action: Contact a Digital support representative.
INVNULLCMD, null command sequence found; please specify the missing
command sequence
Facility: CLI, Command Language Interpreter (DCL)
Explanation: An expected command sequence was not
found.
User Action: Either add the missing command sequence
or remove the extraneous command sequence separators.
INVPERMCONN, cannot establish a permanent point-to-point connection
with an incoming login session
Facility: PPPD, Point-to-Point Protocol Utility
Explanation: An invalid connection was attempted
through the current login session. PPPD supports only temporary
(transient) connections through incoming sessions.
User Action: Establish a transient session using the
PPPD command CONNECT [ddcu:].
INVPERMFLOW, cannot open a permanent point-to-point connection on a
serial port set to MODEM or COMMSYNC
Facility: PPPD, Point-to-Point Protocol Utility
Explanation: An invalid connection was attempted
through the current serial port. PPPD supports only temporary
(transient) connections through a serial port set to MODEM or COMMSYNC.
User Action: Establish a transient session using the
PPPD command CONNECT [ddcu:] or have your system manager reset the
communications port to NOMODEM and NOCOMMSYNC.
INVPPPCODE, invalid PPPD item code of 'value'
Facility: PPPD, Point-to-Point Protocol Utility
Explanation: The specified PPPD item code is not valid.
User Action: Contact a Digital support representative.
INVRANGE, value specified for '/qualifier' ('value') is not within the
valid range
Facility: PPPD, Point-to-Point Protocol Utility
Explanation: A qualifier specified a value that is
outside the legal range.
User Action: Check the TCP/IP Networking on OpenVMS Systems manual for the
valid values for this PPPD qualifier. Specify a value within the legal
range.
INVREDSYN, invalid redirection type specified in a pipe segment
Facility: CLI, Command Language Interpreter (DCL)
Explanation: The redirection type specified in the
pipe segment command in a pipeline is invalid.
User Action: Observe the following restrictions and
correct the invalid redirection syntax:
- SYS$OUTPUT redirection can be specified only in the last pipe
segment command of a pipeline.
- SYS$INPUT redirection can be specified only in the first pipe
segment command of a pipeline.
INVUIC, invalid UIC
Facility: SYSMAN, System Management Utility
Explanation: An invalid UIC was entered. Typical
errors include the following:
- The UIC format is incorrect.
- An alphanumeric UIC does not have a numeric equivalent.
- The user-supplied value for the /GROUP qualifier is not a valid
UIC group number.
User Action: Enter a valid UIC. (See the OpenVMS System Manager's Manual
for more information about UICs.) If you use the /GROUP qualifier,
specify a value between 0 and 255.
INVUSER, no such user
Facility: SYSTEM, System Services
Explanation: In an attempt to map a user ID, no valid
user name match was found.
User Action: If the user ID for an ExtAuth user exists
in the external authentication domain, ensure that it maps to a valid
OpenVMS account in SYSUAF.DAT and that the ExtAuth flag is set for the
user. For locally authenticated users, ensure that the user name exists
in SYSUAF.DAT.
INVVALUE, value specified for '/qualifier' ('value') is not valid
Facility: PPPD, Point-to-Point Protocol Utility
Explanation: The value given for the specified
qualifier is not valid.
User Action: Check the TCP/IP Networking on OpenVMS Systems manual for the
valid value(s) for this PPPD qualifier. Specify a legal value.
IOSBALLOC, allocated IOSB list is not empty
Facility: PPPD, Point-to-Point Protocol Utility
Explanation: When you tried to switch or disconnect
the line during a DIAL_OUT operation, PPPD encountered I/O status
blocks (IOSBs) from a pending I/O request in the IOSB allocation queue.
User Action: Contact a Digital support representative.
IVGROUP, invalid UIC group: 'number'
Facility: SDP, Set Dump Priority Utility
Explanation: The specified UIC group number is invalid.
User Action: Edit the data file to specify an octal
group number between 1 and 37777; then retry the operation.
IVIDENT, invalid identifier: 'identifier'
Facility: SDP, Set Dump Priority Utility
Explanation: The specified identifier cannot be
translated to a UIC. For example, the identifier does not exist or the
RIGHTSLIST.DAT file is not accessible.
User Action: Edit the data file or otherwise correct
the problem; then retry the operation.
IVMEMBER, invalid UIC member: 'number'
Facility: SDP, Set Dump Priority Utility
Explanation: The specified UIC member number is
invalid.
User Action: Edit the data file to supply an octal
member number between 1 to 177777; then retry the operation.
IVPROCESS, process name too long: 'process-name'
Facility: SDP, Set Dump Priority Utility
Explanation: The specified process name exceeds 15
characters.
User Action: Edit the data file to correct the
problem; then retry the operation.
LBLNOTALLINPIP, labels are not allowed in a PIPE command
Facility: CLI, Command Language Interpreter (DCL)
Explanation: A DCL label was specified in a PIPE
command.
User Action: Remove the offending DCL labels from the
command.
LEN_NOTPAGMULT, specified length is not a multiple of CPU-specific pages
Facility: SYSTEM, System Services
Explanation: The specified length is not an even
multiple of CPU-specific pages. Or, if the specified range of virtual
addresses is within a shared page table region, the specified length is
not an even multiple of CPU-specific page table pages or does not
include the last page in the global section.
User Action: Ensure that the length passed to the
system service is an even multiple of CPU-specific pages. Or, if the
specified range of virtual addresses is within a shared page table
region, ensure that the specified length is an even multiple of
CPU-specific page table pages or includes the last page in the global
section.
LENPWDSYNCH, password could not be synchronized; illegal password length
Facility: SET, SET PASSWORD Command
Explanation: A password maintained by an external
authenticator cannot be set in the UAF because the password length is
illegal. The password is sent to the external authenticator, but no
attempt is made to synchronize the password in the UAF.
User Action: None.
LINKTIMEMISM, link time of 'file-name' ('dd-mmm-yy hh:mm') does not
match link time of image in 'target' ('dd-mmm-yy hh:mm')
Facility: SDA, System Dump Analyzer
Explanation: The copy of SYS$BASE_IMAGE.EXE used by
SDA to build its symbol table is not the same version as that used when
the system being analyzed was booted.
This message is only a warning. SDA continues unless the mismatch
causes an unrecoverable error.
User Action: Ensure that logical name
ALPHA$LOADABLE_IMAGES points to a directory containing the same version
of SYS$BASE_IMAGE.EXE that was used when the system being analyzed was
booted.
LISTIGNORED, combination set for 'producer' 'product' includes a PAK
without an include or exclude list; other lists ignored
Facility: LICENSE, License Management Utility
Explanation: During the process of combining licenses
prior to loading, the License Management Facility (LMF) detected a PAK
in the set without an include list or exclude list. Under these
conditions, LMF essentially ignores the include lists and/or exclude
lists on the other licenses and always attempts to load the license.
User Action: Issue the LICENSE MODIFY command to
attach an appropriate include list or exclude list on the PAK that is
missing it.
LOGNAME, logical name exceeds maximum length for device name
Facility: PPPD, Point-to-Point Protocol Utility
Explanation: The specified logical name exceeds the
limit for a device name.
User Action: Revise the logical name so it does not
exceed 64 characters.
MEMNOTACC, memory locations not accessible
Facility: SDA, System Dump Analyzer
Explanation: The dump is being examined in override
mode. In this mode, no commands that access the dump using a memory
address can be used (for example, the SHOW SUMMARY command).
User Action: In override mode, use only commands such
as SET OUTPUT and SHOW DUMP.
MISSINGQUALS, needed qualifiers not given
Facility: SDA, System Dump Analyzer
Explanation: Some required qualifiers were omitted
from the command.
User Action: Review the documentation and reissue the
command with all the required qualifiers.
MODEMHANGUP, modem has signaled a hangup on the line; session ended
Facility: PPPD, Point-to-Point Protocol Utility
Explanation: Due to a hardware error, interference
over the serial line, or a timeout event, the modem has initiated a
hangup and ended data transmission over the serial line.
User Action: Try to access a better connection by
repeating the previous DIAL_OUT operation. If the problem persists,
check your serial cable connections, and verify that both the
transmitting and receiving devices are functioning properly.
If the modem continues to initiate a hangup, notify your system manager.
MRES_PFNSMALL, specified length is larger than reserved pre-allocated
memory
Facility: SYSTEM, System Services
Explanation: The amount of preallocated memory in the
Reserved Memory Registry is smaller than the length specified for the
global section.
User Action: Specify a smaller size for the global
section, or free the preallocated memory from the Reserved Memory
Registry and attempt to create the global section with the same length.
NEEDVIRTTERM, point-to-point connections on 'device-name' must be done
on a virtual terminal
Facility: PPPD, Point-to-Point Protocol Utility
Explanation: The specified device does not have an
associated virtual terminal session enabled.
User Action: Contact your system manager and request
that they do one of the following:
- Enable a virtual terminal session on the device that you originally
specified
- Designate another device on which a virtual terminal session is
currently enabled
Reissue the PPPD command CONNECT [ddcu:] and specify the appropriate
device.
NOASNACCESS, error accessing ASN device
Facility: PPPD, Point-to-Point Protocol Utility
Explanation: PPPD failed to access the specified
asynchronous device for the reason described in the accompanying
message.
User Action: Take action based on the accompanying
message.
NOCHANGE, value not changed; dump not updated
Facility: SDA, System Dump Analyzer
Explanation: No change resulted from executing a
MODIFY DUMP command because the location already contains the value
specified in the command.
User Action: Check the location and value specified in
the MODIFY command against the contents of the location to be modified;
then correct the command and reissue it.
NOCLOSEBRACKET, no ']' found: 'text'
Facility: SDP, Set Dump Priority Utility
Explanation: A right bracket is missing from a process
description.
User Action: Specify the process using one of the
following formats:
- [ident]process
- [group,member]process
NODELPERMANENT, permanent persona cannot be deleted
Facility: SYSTEM, System Services
Explanation: The $PERSONA_DELETE system service
detected an attempt to delete a permanent persona. Currently the only
permanent persona is the process's login persona (persona ID 1).
User Action: Modify the user code that performs the
$PERSONA_DELETE system service so it does not attempt to delete the
permanent persona.
NODISCPRIV, no privilege to disconnect the specified device
Facility: PPPD, Point-to-Point Protocol Utility
Explanation: You do not have the privileges required
to disconnect the device. Unless you have SYSPRV privileges, you cannot
disconnect a point-to-point connection that you did not make.
User Action: Ask a user with SYSPRV privileges
(usually the system manager) to disconnect the device.
NODUMPHERE, only the error log buffers were written to this file
Facility: SDA, System Dump Analyzer
Explanation: The ANALYZE/CRASH command was run on the
stub file, SYS$ERRLOG.DMP. This file looks like a dump file, but
contains only the header and error log buffers.
User Action: Analyze the correct file, either
SYSDUMP.DMP or PAGEFILE.SYS.
NOEXTAUTH, external authentication is not available
Facility: SYSTEM, System Services
Explanation: External authentication is not available
for authentication of the specified user. Typically, this is caused by
external authentication not being enabled.
User Action: Ensure that external authentication is
enabled through the SYS$SINGLE_SIGNON system logical.
NOMATCH, expected value does not match value in dump; dump not updated
Facility: SDA, System Dump Analyzer
Explanation: A MODIFY DUMP command was issued with the
/CONFIRM qualifier, but the contents of the specified location in the
dump do not match the value specified by /CONFIRM.
User Action: Check the location and value specified in
the MODIFY command against the contents of the location to be modified;
then correct the command and reissue it.
NOMEMRESID, requires rights identifier VMS$MEM_RESIDENT_USER
Facility: SYSTEM, System Services
Explanation: The program attempted to create a
memory-resident global section without having the VMS$MEM_RESIDENT_USER
identifier required for this privileged operation.
User Action: Enable the VMS$MEM_RESIDENT_USER
identifier for the process. If you have been granted the
VMS$MEM_RESIDENT_USER identifier, you can enable the identifier by
issuing the following DCL command:
$ SET RIGHTS_LIST /ENABLE VMS$MEM_RESIDENT_USER
This DCL command fails if you have not been granted the
VMS$MEM_RESIDENT_USER identifier. If your system manager chooses to
grant you this identifier, he or she can do so by entering the
following AUTHORIZE command:
UAF> GRANT/ID/ATTR=DYNAMIC VMS$MEM_RESIDENT_USER username
Once the system manager grants you the identifier, you must log out and
then log back in for your process to have this identifier. For more
information about Authorize utility commands, see the OpenVMS System Management Utilities Reference Manual.
NOMODIFY, conflicting access or protection of dump file prevents
modification
Facility: SDA, System Dump Analyzer
Explanation: SDA could not open the dump file for
write access when invoked with the command ANALYZE/CRASH_DUMP/OVERRIDE.
Typical causes of this failure are file protection preventing write
access, or another process or the system already having the file open
for write access.
User Action: The user action depends upon the cause of
the failure:
- If the problem is caused by file protection, use an account that
has write access to the file.
- If another process already has the file open for write access, end
access to the file from that process for write access, end access to
the file from that process (probably by exiting SDA). Then restart SDA
so that it can open the file for writing.
- If the file is held open by the system (as is the case for
SYS$SYSTEM:SYSDUMP.DMP), you must make a copy of the dump file and
modify the copy. You can use the DCL command COPY if you cannot use SDA
because of the problem with the dump file that necessitated using the
MODIFY DUMP command.
NOOPENBRACKET, no '[' found: 'text'
Facility: SDP, Set Dump Priority Utility
Explanation: A left bracket is missing from a process
description.
User Action: Specify the process using one of the
following formats:
- [ident]process
- [group,member]process
NOPARITY, device must be set to no parity
Facility: PPPD, Point-to-Point Protocol Utility
Explanation: The physical device is set to something
other than no parity.
User Action: Set the physical device to no parity by
executing the following command:
$ SET TERMINAL/NOPARITY device-name
NOPOOLTYPE, no pool type specified for given subtype
Facility: SDA, System Dump Analyzer
Explanation: A SHOW POOL command containing the
qualifier /SUBTYPE=n must also include a /TYPE=type
qualifier specifying a numeric or symbolic pool type.
User Action: Reissue the command, including the
appropriate /TYPE qualifier.
NOPORTACCESS, error accessing 'device-name'
Facility: PPPD, Point-to-Point Protocol Utility
Explanation: PPPD failed to access the specified
device for the reason described in the accompanying message.
User Action: Take action based on the accompanying
message.
NOPPP, network protocol has not registered a PPPD callback routine
Facility: PPPD, Point-to-Point Protocol Utility
Explanation: The network protocol that you are using
does not include Point-to-Point Protocol support.
User Action: Check the manufacturer's specifications
and use a network protocol that includes Point-to-Point Protocol
support.
NOPPPACCESS, error accessing PPP device
Facility: PPPD, Point-to-Point Protocol Utility
Explanation: PPPD failed to access the specified
Point-to-Point Protocol device for the reason given in the accompanying
message.
User Action: Take action based on the accompanying
message.
NOPROCESSES, no processes set
Facility: SDP, Set Dump Priority Utility
Explanation: No valid process names are specified in
the data file.
User Action: No action is required if you
intentionally specified no process names in order to clear a previously
defined process list. If the empty list is an error, edit the data file
to correct the problem; then retry the operation.
NOPWDSYNCH, password could not be set; UAF synchronization is disabled
Facility: SET, SET PASSWORD Command
Explanation: The remote user ID cannot be determined
and password synchronization is disabled. The SYSUAF is not modified if
the password is maintained by an external authenticator.
User Action: None.
NORMRONVAX, no reserved memory registry on VAX nodes
Facility: SMI, System Management Integrator/Server
Explanation: The user issued a RESERVED_MEMORY ADD,
REMOVE, or LIST command in a SYSMAN environment that includes VAX nodes.
User Action: To avoid this message, set the SYSMAN
environment to include only Alpha nodes.
NOSELWGHTMOD, selection weight cannot be modified on an Availability
PAK, 'product'
Facility: LICENSE, License Management Utility
Explanation: You tried to modify the selection weight
of an Availability PAK.
User Action: See the OpenVMS License Management Utility Manual for details about
using selection weights.
NOSHPTS, service cannot accept a shared page table region
Facility: SYSTEM, System Services
Explanation: The specified system service does not
operate on virtual addresses within shared page table regions.
User Action: Do not specify a shared page table region
when calling this system service.
NOSUCHPOOL, no 'pool-type' pool found; look in non-paged pool
Facility: SDA, System Dump Analyzer
Explanation: No pool of the specified type has been
allocated. All requests for the specified type of pool have been
satisfied from nonpaged pool.
User Action: None.
NOTALPHADUMP, dump file does not contain an OpenVMS Alpha system dump
Facility: SDA, System Dump Analyzer
Explanation: The dump file you are trying to analyze
using the OpenVMS Alpha System Dump Analyzer was not written on an
OpenVMS Alpha system.
User Action: Confirm that the dump file you wish to
analyze is from an OpenVMS Alpha system, and that a system dump has
actually been written to the file.
NOTANLMB, specified block is not an LMB header
Facility: SDA, System Dump Analyzer
Explanation: A SHOW DUMP/LMB=n command was
issued where the block specified by "n" in the dump is not a
logical memory block (LMB) header.
User Action: Review the contents of the dump and the
specified SHOW DUMP command; then reissue the command, specifying a
valid LMB header block number.
NOTCONNECT, device has not been set up for a point-to-point connection
Facility: PPPD, Point-to-Point Protocol Utility
Explanation: You tried to disconnect a device that was
not part of a Point-to-Point Protocol (PPP) connection.
User Action: Check the device name and reissue the
PPPD command DISCONNECT [ddcu:].
NOTNUMERIC, value specified for '/qualifier' ('value') must be numeric
Facility: PPPD, Point-to-Point Protocol Utility
Explanation: A nonnumeric value was entered where a
numeric value is required.
User Action: Enter a numeric value.
NOTREG, network protocol has not been registered
Facility: PPPD, Point-to-Point Protocol Utility
Explanation: The protocol specified by the PPPD
command SET/NETWORK_PROTOCOL [ddcu:] does not match the name of the
protocol registered in the network database (using the DCL command SET
NETWORK/NETWORK_TYPE).
User Action: Verify that the protocol name is correct
and reissue the command. If the problem persists, contact your system
manager.
NULLPIPE, null pipe segment found; please specify the missing pipe
segment
Facility: CLI, Command Language Interpreter (DCL)
Explanation: An expected pipe segment command was not
found in a pipeline.
User Action: Either add the missing pipe segment
commands or remove the extraneous pipe segment command separator (|).
OFF_NOTPAGALGN, specified offset is not CPU-specific page aligned
Facility: SYSTEM, System Services
Explanation: The specified page offset is not
CPU-specific page aligned. Or, if the specified virtual address range
is within a shared page table region, the specified offset is not
CPU-specific page table page aligned.
User Action: Ensure that the offset passed to the
system service is CPU-specific page aligned. Or, if the specified
virtual address range is within a shared page table region, ensure that
the offset is CPU-specific page table page aligned.
OPENERR, unable to open file 'file-name'
Facility: SDP, Set Dump Priority Utility
Explanation: The specified data file is not accessible
for the reason specified in an accompanying message.
User Action: Take action based on the accompanying
message; then retry the operation.
OUTPUTERR, error creating output line
Facility: PPPD, Point-to-Point Protocol Utility
Explanation: PPPD cannot display messages or show
communications settings for the reason given in the accompanying
message.
User Action: Take action based on the accompanying
message.
PAUSEINPUT, SYS$COMMAND is not a terminal; /PAUSE ignored
Facility: SYSMAN, System Management Utility
Explanation: A SYSMAN command with the /PAUSE
qualifier was submitted from something other than a terminal device.
User Action: Either execute the SYSMAN command from a
terminal device, or eliminate the /PAUSE qualifier from the SYSMAN
command.
PORTDISC, error disconnecting 'device-name'
Facility: PPPD, Point-to-Point Protocol Utility
Explanation: PPPD cannot disconnect the specified
device for the reason given in the accompanying message.
User Action: Take action based on the accompanying
message.
PORTSETUP, error with 'device-name' device setup
Facility: PPPD, Point-to-Point Protocol Utility
Explanation: PPPD cannot configure the serial port
associated with the specified device for the reason given in the
accompanying message.
User Action: Take action based on the accompanying
message.
PPPCONNECTERR, error connecting to PPP device
Facility: PPPD, Point-to-Point Protocol Utility
Explanation: A point-to-point connection to the
specified device cannot be established for the reason given in the
accompanying message.
User Action: Take action based on the accompanying
message.
PPPCREATEERR, error creating link between PPP device and serial device
Facility: PPPD, Point-to-Point Protocol Utility
Explanation: A point-to-point connection between the
specified devices cannot be established for the reason given in the
accompanying message.
User Action: Take action based on the accompanying
message.
PPPENABLEERR, error starting PPP connection
Facility: PPPD, Point-to-Point Protocol Utility
Explanation: A point-to-point connection was not
enabled for the reason given in the accompanying message.
User Action: Take action based on the accompanying
message.
PPPINFOERR, error obtaining information from PPP device
Facility: PPPD, Point-to-Point Protocol Utility
Explanation: PPPD cannot retrieve information from the
specified device for the reason given in the accompanying message.
User Action: Take action based on the accompanying
message.
PPPLISTOVER, PPP itemlist overrun; tag, items size, items item_length
and len = 'value1' 'value2' 'value3' 'value4'
Facility: PPPD, Point-to-Point Protocol Utility
Explanation: A data encoding error occurred within
PPPD.
User Action: Contact a Digital support representative.
PPPNOTAVAIL, point-to-point driver is not installed
Facility: PPPD, Point-to-Point Protocol Utility
Explanation: PPPD cannot locate the Point-to-Point
Protocol (PPP) device driver; it is not installed on the system.
User Action: Contact your system manager.
PPPSETERR, error setting PPP device
Facility: PPPD, Point-to-Point Protocol Utility
Explanation: While the Point-to-Point Protocol (PPP)
device was being initialized, an error occurred for the reason given in
the accompanying message.
User Action: Take action based on the accompanying
message.
PREVSET, device has already been set up for point-to-point connections
Facility: PPPD, Point-to-Point Protocol Utility
Explanation: The device specified by the PPPD CONNECT
command has already been set up for point-to-point connections by a
previous PPPD CONNECT command.
User Action: To reinstate a failed connection on a
device, execute a PPPD DISCONNECT [ddcu:] command followed by a PPPD
CONNECT [ddcu:] command.
PROCNOTDUMPED, process 'process-name' not dumped; process private
memory not accessible
Facility: SDA, System Dump Analyzer
Explanation: In a selective memory dump, there is not
always enough space to dump all processes. The specified process was
not dumped, so only structures in system space (such as the process
control block and process header) are accessible.
User Action: If processes you need to analyze are
sometimes not included or are incompletely included in system dumps,
consider increasing the size of the system dump file and/or use the
SYS$SET_DUMP_PRIORITY utility to force the process to be written
earlier in the dump.
PROCPARTDUMPED, process 'process-name' not completely dumped; some
process private memory not accessible
Facility: SDA, System Dump Analyzer
Explanation: In a selective memory dump, there is not
always enough space to dump all processes. The specified process was
only partly dumped, so only some locations in the process's address
space are accessible (in addition to structures in system space, such
as the process control block and process header).
User Action: If processes you need to analyze are
sometimes not included or are incompletely included in system dumps,
consider increasing the size of the system dump file and/or use the
SYS$SET_DUMP_PRIORITY utility to force the process to be written
earlier in the dump.
PROGINIT, error in initialization
Facility: PPPD, Point-to-Point Protocol Utility
Explanation: PPPD cannot initialize itself for the
reason given in the accompanying message.
User Action: Take action based on the accompanying
message.
PROTOERR, error initiating network protocol callback routine
Facility: PPPD, Point-to-Point Protocol Utility
Explanation: An error occurred while attempting to
execute the network protocol callback routine.
User Action: Check the manufacturer's specification to
see if the network protocol supports Point-to-Point Protocol. You must
use a network protocol that includes this support. If you get this
message while using a network protocol that supports Point-to-Point
Protocol, contact the manufacturer.
READERR, error reading from 'device-name'
Facility: PPPD, Point-to-Point Protocol Utility
Explanation: During a read operation on the specified
device, an error occurred for the reason described in the accompanying
message.
User Action: Take action based on the accompanying
message.
READERR, unable to read from file 'file-name'
Facility: SDP, Set Dump Priority Utility
Explanation: A record in the specified data file is
unreadable for the reason given in an accompanying message (for
example, the record is too long).
User Action: Edit the data file to correct the
problem; then retry the operation.
REMOTE, physical device specified cannot be a remote terminal
Facility: PPPD, Point-to-Point Protocol Utility
Explanation: The specified physical device is a remote
terminal.
User Action: Specify a physical device that is not a
remote terminal.
RMRDUPINV, name and group already in registry
Facility: SMI, System Management Integrator/Server
Explanation: The user issued a RESERVED_MEMORY ADD
command with values for the name argument and /GROUP qualifier that
match an extant record in the current version of
SYS$SYSTEM:VMS$RESERVED_MEMORY.DATA.
User Action: Specify a different name or UIC group for
the new section.
RMRFILCRE, reserved memory registry file created
Facility: SMI, System Management Integrator/Server
Explanation: The user issued a RESERVED_MEMORY ADD
command for the first time on this node, resulting in the creation of
SYS$SYSTEM:VMS$RESERVED_MEMORY.DATA.
User Action: None.
RMRFREPAG, pages successfully freed from reservation
Facility: SMI, System Management Integrator/Server
Explanation: The user issued a RESERVED_MEMORY FREE
command that completed successfully.
User Action: None.
RMRNOMATCH, no records matched search criteria
Facility: SMI, System Management Integrator/Server
Explanation: The user issued a RESERVED_MEMORY REMOVE
command with values for the name argument and /GROUP qualifier that do
not match any extant records in the current version of
SYS$SYSTEM:VMS$RESERVED_MEMORY.DATA.
User Action: Examine the contents of
SYS$SYSTEM:VMS$RESERVED_MEMORY.DATA to confirm the name and UIC group
of the record to be deleted.
RMRVERMIS, reserved memory registry version mismatch
Facility: SMI, System Management Integrator/Server
Explanation: There is a mismatch between the version
marker in the current incarnation of
SYS$SYSTEM:VMS$RESERVED_MEMORY.DATA and the version expected by the
executing SMISERVER image.
User Action: Rename the existing version of
SYS$SYSTEM:VMS$RESERVED_MEMORY.DATA and use the current version of
SYSMAN to create a new registry file.
SDALINKMISM, link time of SYS$BASE_IMAGE built into SDA$SHARE
('dd-mmm-yy hh:mm') does not match link time of image in 'target'
('dd-mmm-yy hh:mm')
Facility: SDA, System Dump Analyzer
Explanation: The copy of the SDA$SHARE image you are
using was not built for the version of SYS$BASE_IMAGE.EXE that was used
when the system being analyzed was booted.
Previous
| Next
| Contents
| [Home]
| [Comments]
| [Ordering info]
| [Help]
6480P009.HTM
OSSG Documentation
5-DEC-1996 13:51:21.29
Copyright © Digital Equipment Corporation 1996. All Rights Reserved.
Legal