Document revision date: 19 July 1999
|
|
|
|
OpenVMS System Messages: Companion Guide for Help
Message Users
ODS2SAVE, save set disk on 'device-name' must be structure level 2
Facility: BACKUP, Backup Utility
Explanation: The specified volume is not a Files--11
On-Disk Structure Level 2 volume. The volume cannot be used as a
save-set disk.
User Action: Retry the operation using a properly
initialized structure level 2 volume.
OFFLINE, 'device-name' off line
Facility: MOUNT, Mount Utility
Explanation: The specified device is off line. The
requested action cannot be completed.
User Action: Place the device on line and reenter the
command.
ONEF11DEV, both input and output must not be save sets
Facility: BACKUP, Backup Utility
Explanation: When the BACKUP command was executed, you
specified that both input and output files reference a save set. Either
the input or the output specification, not both, can reference a save
set.
User Action: Correct and reenter the command.
ONEF11OUT, file-structured output must not be a list
Facility: BACKUP, Backup Utility
Explanation: The output specification for a copy,
restore, or compare operation without the /IMAGE qualifier is a list of
file specifications. (The Backup utility does not accept this.)
User Action: Modify your output specification and
reenter the command.
ONEIMGDEV, /IMAGE input specification must not be a list
Facility: BACKUP, Backup Utility
Explanation: The specification for an input volume set
to be processed with the /IMAGE qualifier is a list of file
specifications. (The Backup utility does not accept this.)
User Action: Modify your input specification and
reenter the command.
ONEPHYDEV, /PHYSICAL specification must not be a list
Facility: BACKUP, Backup Utility
Explanation: The specification for a physical volume
is a list of file specifications. (The Backup utility does not accept
this.)
User Action: Modify your specification and reenter the
command.
OPENDIR, error opening directory 'directory-name'
Facility: BACKUP, Backup Utility
Explanation: An error was encountered during an
attempt to open the specified directory file. The Backup utility cannot
process files in this directory or its subdirectories.
User Action: Take action based on the accompanying message.
OPENFAIL, failure opening component file 'file-number', 'file-name'
Facility: STDRV, System Startup Driver
Explanation: The startup driver failed to open one of
the system files that describes the tasks that need to be performed at
startup. The startup operation attempts to continue, but may not
properly perform all startup tasks.
User Action: Make sure that the named file is
available and can be read.
OPENIN, error opening 'file-name' as input
Facility: LOGIN, Login Procedure
Explanation: A file to be read by LOGINOUT (for
example, a file containing the announcement message) cannot be opened.
User Action: Ensure that the file exists and that it
has read access.
OPENIN, error opening 'file-name' as input
Facility: BACKUP, Backup Utility
Explanation: The Backup utility cannot open the
specified input file.
User Action: Determine why the file cannot be opened
and repeat the backup operation.
OPENOUT, error opening 'file-name' as output
Facility: BACKUP, Backup Utility
Explanation: The Backup utility cannot open the
specified output file.
User Action: Determine why the file cannot be opened
and repeat the backup operation.
OPERABORT, operator has aborted request, reply is 'reply'
Facility: BACKUP, Backup Utility
Explanation: This informational message displays the
operator's response to a query from the Backup utility after the
operator aborted or canceled a request.
User Action: None.
OPERASSIST, operator assistance has been requested
Facility: BACKUP, Backup Utility
Explanation: This message notifies you that operator
assistance has been requested.
User Action: None.
OPERFAIL, error requesting operator service
Facility: BACKUP, Backup Utility
Explanation: The Backup utility encountered an error
during an attempt to interact with the operator. The error may be
caused because the operator replied to the request with REPLY/ABORT.
User Action: Take action based on the accompanying message.
OPERSPEC, specify option ('options')
Facility: BACKUP, Backup Utility
Explanation: This message is returned to the operator.
It indicates that the Backup utility encountered a recoverable error.
User Action: The operator must select one of the
options listed in the message. The options listed depend upon the
recoverable error that was encountered. Possible options are: QUIT,
CONTINUE, RESTART, NEW, OVERWRITE and USE. If the QUIT option is
selected, the Backup utility will terminate. If the CONTINUE option is
selected, the Backup utility will ignore the error and continue
processing. If the RESTART option is selected, the Backup utility will
restart the operation at the beginning of the current volume. If the
NEW option is selected, the Backup utility will dismount the current
tape volume and request that a new tape volume be mounted. If the
OVERWRITE option is selected, the Backup utility will overwrite the
currently loaded volume label. If the USE option is selected, the
Backup utility will use the currently loaded volume label.
OPRABORT, mount aborted by operator
Facility: MOUNT, Mount Utility
Explanation: This is the final message in a series of
messages issued from MOUNT to the operator. The operator has refused
your request.
User Action: None.
OPRABORT, operator has aborted backup request
Facility: BACKUP, Backup Utility
Explanation: The operator selected the ABORT option
when prompted for input.
User Action: The backup operation has been aborted.
You might want to restart the backup operation, because all data has
not been saved.
OPREPLY, 'reply'
Facility: MOUNT, Mount Utility
Explanation: This is the operator's response to the
DCL command REQUEST.
User Action: Take action based on the reply.
OPREPLY, operator reply is 'reply'
Facility: BACKUP, Backup Utility
Explanation: This message contains the operator's
reply to a request.
User Action: Take action based on the reply.
OPRQST, 'request'
Facility: MOUNT, Mount Utility
Explanation: This message contains a request from
MOUNT to the operator.
User Action: Take action based on the request or wait
for the operator to service the request.
OPRQSTCAN, operator request canceled
Facility: MOUNT, Mount Utility
Explanation: An operator request was canceled because
the mount failed or was aborted with a Ctrl/Y.
User Action: None.
OPRSNDERR, error sending request to operator
Facility: MOUNT, Mount Utility
Explanation: MOUNT failed in an attempt to send a
message to the operator.
User Action: Take action based on the accompanying message.
OPSPECLBL, the label was not specified; specify label (up to 6
characters)
Facility: BACKUP, Backup Utility
Explanation: Exact label checking is in effect, but
the command line did not specify enough labels to cover the current
volume.
User Action: You must specify a volume label to be
used in exact volume order checking.
OUTCOMTERMINATED, security server's outgoing message mechanism failed
and is exiting
Facility: SECSRV, Security Server
Explanation: An error occurred in the security
server's communication system and the server is shutting down.
User Action: Issue the DCL command SET SERVER
SECURITY/START to restart the security server. If this condition
persists, contact a Digital support representative.
OUTOFRANGE, value specified is not within the legal range for this
qualifier
Facility: LAT, LAT Facility
Explanation: A value was specified that is out of
range for a LATCP qualifier.
User Action: Specify a value within the legal range
(see the OpenVMS System Management Utilities Reference Manual).
OUTPUTERR, error opening primary output file SYS$OUTPUT
Facility: LOGIN, Login Procedure
Explanation: The system cannot open the current output
device and cannot perform the login. This message is usually
accompanied by an RMS file system message indicating the reason for the
failure.
User Action: Take action based on the accompanying message.
OUT_RANGE, number cannot be less than 1 or larger than 127
Facility: SYSGEN, System Generation Utility
Explanation: The SYSGEN command CONFIGURE specifies a
number that is either too small or too large.
User Action: Reenter the command, specifying a number
within the range of 1 to 127.
OUTSWPERR, outswap 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.
OVERFLOW, overflow in floating addresses, illegal configuration
Facility: SYSGEN, System Generation Utility
Explanation: The SYSGEN command CONFIGURE computed an
illegal floating address for a CSR or vector.
User Action: Reenter the command with the correct
number of controllers.
OVERWRITE, relative volume 'volume-name' on device 'device-name' will
be overwritten
Facility: BACKUP, Backup Utility
Explanation: This message notifies you that the volume
header of the indicated volume will be overwritten with the information
requested by the BACKUP command.
User Action: None.
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.