|
|
Updated:
11 December 1998
|
OpenVMS System Messages: Companion Guide for Help
Message Users
PAGECRIT, page file nearly full; system trying to continue
Facility: SYSTEM, System Services
Explanation: The system is running out of page file
space. This message is more critical than the PAGEFRAG message.
User Action: Create a new page file with more space.
See the OpenVMS System Manager's Manual.
PAGED_GST_TOBIG, paged global symbol fixup data exceeds table size
Facility: LOADER, Executive Image Loader
Explanation: An executive image has more global
symbols in the fixup data than can fit in the loader's internal tables.
User Action: Contact a DIGITAL support representative.
PAGEFRAG, page file filling up; please create more space
Facility: SYSTEM, System Services
Explanation: The system is running out of page file
space.
User Action: Create a new page file with more space.
See the OpenVMS System Manager's Manual.
PAGEREDERR, page read error
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.
PAGEWRTERR, page write error
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.
PAGNTRNVAL, page not in transition or valid
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.
Parallel Path is Closing Virtual Circuit - REMOTE PORT 'xxx'
Facility: Cluster Port Driver
Explanation: The port driver switched communications
from a low-performance communication link to a high-performance
communication link. This event is a normal virtual circuit shutdown.
User Action: None.
PARSE, error opening 'file-spec'
Facility: BACKUP, Backup Utility
Explanation: The Backup utility encountered an error
during an attempt to access the specified file.
User Action: Take action based on the accompanying message.
Path #n. Has become working but CROSSED to Path #n. -
REMOTE PORT 'xxx'
Facility: Cluster Port Driver
Explanation: The specified path is working, but the
cables appear to be crossed.
User Action: Check for crossed-cable pairs and correct
the problem.
Path #n. Has gone from BAD to GOOD - REMOTE PORT 'xxx'
Facility: Cluster Port Driver
Explanation: A hardware error condition has been
cleared on the specified path.
User Action: None.
Path #n. Has gone from GOOD to BAD - REMOTE PORT 'xxx'
Facility: Cluster Port Driver
Explanation: A hardware error has occurred on the
specified path.
User Action: Check cables on the specified path for
breaks or improper connections and correct the problem.
Path #n. Loopback has gone from BAD to GOOD
Facility: Cluster Port Driver
Explanation: A loopback error has been cleared on the
specified path.
User Action: None.
Path #n. Loopback has gone from GOOD to BAD
Facility: Cluster Port Driver
Explanation: A loopback error has occurred on the
specified path.
User Action: Check for crossed-cable pairs or faulty
CI hardware and correct the problem.
PFNLISTCNT, inconsistent PFN list count
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.
PFNREFNZRO, PFN reference count nonzero
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.
PGFGBLBAD, pagefault, global page table entry bad format
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.
PGFIPLHI, pagefault with IPL too high
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.
PGFLOCBAD, pagefault, location field has bad value
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.
PHYDEVGEO, device type of 'device-name' does not match input
Facility: BACKUP, Backup Utility
Explanation: In an operation with the /PHYSICAL
qualifier, the output device must be the same type as the input device.
User Action: Reevaluate the operation; another mode of
operation, such as using the /IMAGE qualifier, may be appropriate. Or,
retry the operation, specifying the same type of device.
PHYFILSPE, /PHYSICAL specification must have only device name
Facility: BACKUP, Backup Utility
Explanation: When the /PHYSICAL command qualifier was
used, more than a device name was specified as an input-specifier or
output-specifier. The file specification for a volume to be processed
with the /PHYSICAL qualifier must contain only a device name.
User Action: Refer to the OpenVMS System Management Utilities Reference Manual for
information on the /PHYSICAL command qualifier and reenter the command.
PHYSET, physical save set supplied to nonphysical operation
Facility: BACKUP, Backup Utility
Explanation: A save set created with the /PHYSICAL
qualifier cannot be used as input to an operation without specifying
the /PHYSICAL qualifier.
User Action: Use the DCL command BACKUP/LIST to
determine how the save set is created. Reevaluate the operation, and
reenter the command.
Port Error Bit(s) Set - CNF/PMC/PSR 'xxxxxxxx/xxxxxxxx/xxxxxxxx'
Facility: Cluster Port Driver
Explanation: The port driver attempts to reinitialize
the port; after 50 attempts, it marks the device off line.
User Action: Check the error logs for a sanity
timeout. This sanity timeout is indicated by bit 6 of the PSR (PSR =
'xxxxxx4x'). The error logs describe the sanity timeout bit as a
"Maintenance Timer Expiration." If sanity timeouts occur,
check the console log to see if the operator has halted and continued
the system for any reason. If the console log does not show operator
intervention, increase the PASTIMOUT SYSGEN parameter until the
timeouts no longer occur. For nontimeout errors, contact a DIGITAL support representative
to check the port hardware.
Port Error Bit(s) Set - NODESTS/CASR(H)/(L) 'xxxxxxxx/xxxxxxxx/xxxxxxxx'
Facility: Cluster Port Driver
Explanation: The adapter is reporting an internal
error. The port driver attempts to reinitialize the adapter; after 50
failed attempts it marks the device off line.
User Action: Contact a DIGITAL support representative to check the port
hardware.
Port has Closed Virtual Circuit - REMOTE PORT 'xxx'
Facility: Cluster Port Driver
Explanation: The port driver has closed the virtual
circuit that the local port opened to the remote port.
User Action: Check the PP$DB_STATUS field of the error
log entry to see why the virtual circuit is closed. This error is
normal if the remote system crashed or is shut down.
Port is going Offline
Facility: Cluster Port Driver
Explanation: The port is offline after failing to
reinitialize following a port failure.
User Action: Check the error log for errors from this
port and call a DIGITAL support representative.
Port is Reinitializing. Check the Error Log
Facility: Cluster Port Driver
Explanation: The port is reinitializing after a port
failure. The port attempts to recover from all failures.
User Action: Check the error log for errors from this
port and call a DIGITAL support representative.
Port is Reinitializing ('number' Retries Left). Check the Error Log
Facility: Cluster Port Driver
Explanation: The port is reinitializing after a port
failure. The port attempts to recover from a failure, and if the retry
count is exhausted, the port is set offline.
User Action: Check the error log for errors from this
port and call a DIGITAL support representative.
Port Power Down
Facility: Cluster Port Driver
Explanation: The port driver detected a power down
interrupt from the port.
User Action: Contact a DIGITAL support representative to check the port
power supply.
Port Power Up
Facility: Cluster Port Driver
Explanation: A system-wide power failure was detected
and is being recovered. In the case of a CI 750 adapter, the expansion
box may have lost power and power is now being restored.
User Action: None.
Port Transition Failure - CNF/PMC/PSR 'xxxxxxxx/xxxxxxxx/xxxxxxxx'
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: Contact a DIGITAL support representative to check the port
hardware.
Port Transition Failure - NODESTS/CASR(H)/(L)
'xxxxxxxx/xxxxxxxx/xxxxxxxx'
Facility: Cluster Port Driver
Explanation: The adapter is reporting an internal
error during initialization or restart. The port driver attempts to
reinitialize the adapter; after 50 failed attempts it marks the device
off line.
User Action: Contact a DIGITAL support representative to check the port
hardware.
Port ucode not at current rev level. PROM/RAM rev is 'xxxx/xxxx'
Facility: Cluster Port Driver
Explanation: The port driver continues port operation.
User Action: Check the console storage device for the
latest microcode version. For ports with on-board microcode, contact
a DIGITAL support representative to upgrade the port microcode. Prolonged operation of
the port with obsolete microcode is not supported by Digital.
Port ucode not at required rev level. PROM/RAM rev is 'xxxx/xxxx'
Facility: Cluster Port Driver
Explanation: The adapter microcode must be updated to
ensure correct operation. Most likely a major defect exists in the
microcode revision currently in the adapter.
User Action: Load the latest microcode for that
adapter from the console load media, or contact a DIGITAL support representative to check
the hardware and load the latest microcode.
POSERROR, error positioning 'file-spec'
Facility: BACKUP, Backup Utility
Explanation: The Backup utility encountered an error
during an attempt to reposition the specified file.
User Action: Take action based on the accompanying message.
POSITERR, error positioning 'save-set-spec'
Facility: BACKUP, Backup Utility
Explanation: The Backup utility encountered an error
during an attempt to reposition the specified save-set volume.
User Action: Take action based on the accompanying message.
PREFIX, searching for ICBM with prefix 'prefix'
Facility: IOGEN
Explanation: This message is displayed while IO
AUTOCONFIGURE searches through IOGEN Configuration Building Modules
(ICBMs), configures devices, and loads drivers.
User Action: None.
PROCDONE, operation completed. Processing finished at 'date-time'
Facility: BACKUP, Backup Utility
Explanation: Standalone backup processing has
completed.
User Action: None.
PROCGONE, Process not in system
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.
PROCINDEX, error processing index file on 'device,' RVN 'n'
Facility: BACKUP, Backup Utility
Explanation: The Backup utility encountered an error
during an attempt to process the index file, [000000]INDEXF.SYS;1, on
the specified relative volume of the specified device.
User Action: Take action based on the accompanying message.
PROXYCONVERT, old-format proxy database needs to be converted
Facility: SYSTEM, System Services
Explanation: The security server startup command
procedure detected an existing NETPROXY.DAT file with no corresponding
NET$PROXY.DAT file. This error occurs when the old-format NETPROXY.DAT
database file has not yet been converted to a new NET$PROXY.DAT
database following a system upgrade.
User Action: Run the conversion utility
(CONVERT_PROXY) to convert NETPROXY.DAT. (See the installation
documentation for details.)
PROXYMISSING, old-format proxy database file is missing
Facility: SYSTEM, System Services
Explanation: The security server startup command
procedure detected a new format proxy database (NET$PROXY.DAT) with no
corresponding old format proxy database (NETPROXY.DAT). Probably the
CONVERT_PROXY utility was run to create the new database, and then the
old format database was deleted. The old database is required on the
system by DECnet Phase IV and many layered products.
User Action: Restore NETPROXY.DAT from backup files.
PROXYNOTOPEN, cannot open proxy database
Facility: SECSRV, Security Server
Explanation: The proxy database NET$PROXY.DAT exists,
but it cannot be opened for the reason stated in an accompanying
message.
User Action: Take action based on the accompanying
message.
PROXYSHUTDOWN, proxy processing is shutting down
Facility: SECSRV, Security Server
Explanation: As requested, proxy processing is
shutting down.
User Action: None.
PROXYSTARTINGUP, proxy processing now starting up
Facility: SECSRV, Security Server
Explanation: As requested, proxy processing is
starting up.
User Action: None.
PROXYTERMINATED, an error caused proxy processing to terminate
Facility: SECSRV, Security Server
Explanation: An error occurred in the proxy processing
component of the security server.
User Action: Contact a DIGITAL support representative.
PRTEXT, file only partly extended. Volume may be too fragmented.
Facility: SYSGEN, System Generation Utility
Explanation: The SYSGEN command CREATE failed due to
insufficient disk space.
User Action: Clean up your disk space, or specify a
smaller /SIZE qualifier.
PSB_FIXUPS, image contains LPPSB fixups, link NATIVE_ONLY
Facility: LOADER, Executive Image Loader
Explanation: A load request was made for an executive
image that contains LPPSB fixup data because it was linked
/NONATIVE_ONLY. Executive images must be linked /NATIVE_ONLY.
User Action: Relink the image using /NATIVE_ONLY.
PTELENVIOL, unexpected page table length violation
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.
PTRCNT, ACP block count exceeds retrieval pointer size
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.
PURGWSSCN, purge working set scan error
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.
PWDEXPIR, your password has expired - contact your system manager
Facility: LOGIN, Login Procedure
Explanation: The password is valid for a specific
length of time as determined by your system manager. When a password
reaches the end of its specified time period, it expires and can no
longer be used to gain access to the system. This is a system security
feature that forces users to change their passwords on a regular basis.
You should have been receiving advance messages notifying you when your
password would expire.
User Action: Ask your system manager for a new
password.