VMS Help
DEFRAGMENT, Messages
*Conan The Librarian
|
Look for DFO error messages in the following alphabetical order.
Most messages contain a facility code, a severity indicator, an
identification field and the actual text of the message. Most
messages have $FAO formatting control sequences due to which message
text begins with an ! mark.
failed to abort !AD
Explanation: DFG$DEFRAGMENT returned a failure status when
it attempted to abort the specified script. This message is a
summary message. Associated messages provide more detail.
User Action: Refer to associated messages to determine a course
of action.
no script was aborted
Explanation: DFG$DEFRAGMENT returned a failure status when it
attempted to abort all scripts in the scheduling database. This
message is a summary message. Associated messages provide more
detail.
User Action: Refer to associated messages to determine a course
of action.
abort unsuccessful
Explanation: An ABORT subcommand was unsuccessful. This is a
summary message. This message may or may not indicate an error.
Associated messages provide more detail.
User Action: Refer to associated messages to determine a course
of action.
abort command already issued for !AD
Explanation: An ABORT subcommand had been issued for this script
but it had not yet completed when another ABORT subcommand for
the same script was issued.
User Action: Wait for the command to complete.
access error on file !AD
Explanation: A QIO IO$_ACCESS function could not be performed on
the given file for reasons detailed in associated messages. This
message occurs only in the log file or the /MAIL_NOTIFICATION
messages.
User Action: Refer to associated messages to determine a course
of action.
BUGCHECK - Map pointer copy would run into ACLs
Explanation: The copy made of INDEXF.SYS would run into ACLs.
User Action: Clean up disk and restart program.
channel-assign error for device !AD
Explanation: A channel could not be assigned for the indicated
device. Associated messages provide more detail.
User Action: Refer to associated messages to determine a course
of action.
$CONNECT error on file !AD:[000000]BITMAP.SYS
Explanation: A $CONNECT RMS service was unsuccessful for the
BITMAP.SYS file of the target device. The RMS error is provided
in a subsequent message.
User Action: Determine a course of action based on the RMS error
reported.
$OPEN error on file !AD:[000000]BITMAP.SYS
Explanation: A $OPEN RMS system service could not be performed
on the BITMAP.SYS file of the target device. The RMS error is
provided in a subsequent message.
User Action: Determine a course of action based on the RMS error
reported.
$READ error on file !AD:[000000]BITMAP.SYS
Explanation: A $READ RMS system service failed for the BITMAP.SYS
file of the target device. The RMS error is provided in a
subsequent message.
User Action: Determine a course of action based on the RMS error
reported.
unable to flush extent cache for device !AD
Explanation: An IO$_ACPCONTROL extent cache flush QIO returned a
failure status to the defragmentation process. The root cause is
included in associated messages.
User Action: Refer to associated messages to determine a course
of action.
cancel unsuccessful
Explanation: A CANCEL subcommand was unsuccessful. This is a
summary message. This message may or may not indicate an error.
Associated messages provide more detail.
User Action: Refer to associated messages to determine a course
of action.
failed to cancel !AD
Explanation: DFG$DEFRAGMENT returned a failure status when it
attempted to cancel the specified script. This message is a
summary message. Associated messages provide more detail.
User Action: Refer to associated messages to determine a course
of action.
no script was canceled
Explanation: DFG$DEFRAGMENT returned a failure status when it
attempted to cancel all scripts in the scheduling database. This
message is a summary message. Associated messages provide more
detail.
User Action: Refer to associated messages to determine a course
of action.
Error when copying map pointers for INDEXF.SYS
Explanation: An error occurred when mapping the new INDEXF.SYS
header pointers.
User Action: Submit an SPR.
error closing !AD as input
Explanation: An RMS error was encountered when trying to close an
input file, such as the options file. Associated messages provide
more detail.
User Action: Refer to associated messages to determine a course
of action.
error closing !AD as output
Explanation: An RMS error was encountered when trying to close an
output file. Associated messages provide more detail.
User Action: Refer to associated messages to determine a course
of action.
unknown command; parsing error, please submit an SPR
Explanation: This is an internal error.
User Action: Submit an SPR.
$CONNECT error on log file !AD
Explanation: The RMS $CONNECT service failed for the log file
(occurs in the defragmentation process). Associated messages
provide the root cause.
User Action: Refer to associated messages to determine a course
of action.
free-space consolidation failed for !AD
Explanation: Free-space consolidation failed for the given disk
User Action: None, unless indicated by other messages.
© Copyright 2003 Hewlett-Packard Development Company,L.P.
!SL is an invalid CPU percentage; use 0-100
Explanation: User specified a CPU percent utilization limit that
was not within the 0-100 range.
User Action: Specify valid CPU percentages from 0 to 100,
inclusive.
error creating !AD
Explanation: The $CREATE RMS service failed for the specified
file. Associated messages provide the root cause.
User Action: Refer to associated messages to determine a course
of action.
error creating detached defragmentation process
Explanation: The scheduler could not create the detached
defragmentation process. Associated messages provide more detail.
User Action: Refer to associated messages to determine a course
of action.
error creating global section
Explanation: The global section used for communications could
not be created by the scheduler for reasons given in associated
error messages. This error is caused by a failure status from the
$CRMPSC system service, which could indicate insufficient system
wide global section resources.
User Action: Refer to associated messages to determine a course
of action.
constraint violation in relation !AD (operation !AD)
Explanation: A constraint in the database was violated. The
most common reason is an attempt to enter a duplicate record.
Associated messages provide more detail.
User Action: Refer to associated messages to determine a course
of action.
duplicate record in relation !AD (operation !AD)
Explanation: An attempt was made to enter a duplicate record in
the database. Associated messages provide more detail.
User Action: Refer to associated messages to determine a course
of action.
database-access error; relation !AD, operation !AD, status !SL
Explanation: The database could not be accessed. The cause of
this problem may be an undefined logical, corrupt database, DFG
software error, or RMS software error.
User Action: Verify that all DFG logicals are defined. Refer
to associated messages to determine if additional action is
necessary.
database-access error: !AD transaction
Explanation: The database could not be accessed. The cause of
this problem may be an undefined logical, corrupt database,
DFG software error, or RMS software error. Associated messages
provide more detail.
User Action: Verify that all DFG logicals are defined. Refer
to associated messages to determine if additional action is
necessary.
database-access warning: relation !AD, operation !AD, sqlcode !SL
Explanation: The Rdb software returned a warning status to the
scheduler. The problem may be that the database is corrupt, that
the disk file optimizer software is in error, or that the Rdb
software is in error.
User Action: Try the operation again. If the error persists, re-
create the database. If the error persists after re-creating the
database, submit an SPR.
database-access warning: !AD transaction, sqlcode !SL
Explanation: The Rdb software returned a warning status to the
scheduler. The problem may be that the database is corrupt, that
the disk file optimizer software has is in error, or that the Rdb
software is in error.
User Action: Try the operation again. If the error persists, re-
create the database. If the error persists after re-creating the
database, submit an SPR.
accessing the defragmentation database; please wait
Explanation: Informational message that indicates the DCL
interface is waiting for the database access/update to complete.
User Action: None.
cannot read a needed record from relation !AD
Explanation: The database could not be read. The cause of this
problem may be an undefined logical, corrupt database, DFG
software error, or Rdb software error. This problem can also
be caused if the RMU Monitor process (RDMS_MONITOR) is not
executing. Associated messages provide more detail.
User Action: Verify that all DFG logicals are defined and ensure
that RDMS_MONITOR is running. If RDMS_MONITOR is not running, it
can be started by invoking @SYS$STARTUP:RMONSTART.COM. Refer
to associated messages to determine if additional action is
necessary.
cannot write or update a record in relation !AD
Explanation: The database could not be updated. The cause of
this problem may be an undefined logical, corrupt database,
DFG software error, or Rdb software error. This problem can
also be caused if the RMU Monitor process (RDMS_MONITOR) is not
executing. Associated messages provide more detail.
User Action: Try the command again. If the error persists, re-
create the database. If the error persists after re-creating the
database, submit an SPR.
clearing database
Explanation: A database is being cleared.
User Action: None.
database cleared
Explanation: A database has been cleared.
User Action: None.
creating database
Explanation: A database is being created.
User Action: None.
database created
Explanation: A database has been created.
User Action: None.
invalid translated name
Explanation: This is an internal error.
User Action: Submit an SPR.
no record found in relation !AD (operation !AD)
Explanation: A database record could not be found. This error
can occur if the database is corrupt, the disk file optimizer
software is in error, or the Rdb software is in error.
User Action: Submit an SPR.
database updates rolled back
Explanation: All updates to the database have been rolled back.
User Action: None
database update failed
Explanation: This is a summary message indicating that database
updates were unsuccessful. Associated messages provide more
detail.
User Action: Refer to associated messages to determine a course
of action.
deaccess error on file !AD
Explanation: The specified file could not be deaccessed by the
defragmentation process (using the IO$_DEACCESS QIO). Associated
messages provide more detail.
User Action: Refer to associated messages to determine a course
of action.
cannot delete !AD, notification message
Explanation: An attempt to spawn a subprocess to delete the mail
message sent as a result of the /MAIL_NOTIFICATION qualifier
failed. This error occurs in the scheduler code.
User Action: Refer to associated messages to determine a course
of action.
defragmentation process failed to start
Explanation: This message occurs when a defragmentation process
cannot be started. Associated messages indicate why. This message
does not occur with Defrag PLUS.
User Action: Refer to associated messages to determine a course
of action.
started defragmentation process PID: !XL
Explanation: This message indicates that a defragmentation
process has been started. This message does not occur with Defrag
PLUS.
User Action: None.
defragmentation process timed out on startup
Explanation: The defragmentation process did not map the global
section created by the scheduler within a timeout period.
User Action: Ensure a copy of DFG$ENGINE_MAIN exists in
SYS$SYSTEM and try the command again. If the error persists,
submit an SPR.
!SL is an invalid direct I/O limit, use positive values
Explanation: The user specified a negative number for a direct
I/O limit.
User Action: Specify positive values for the IO_LIMIT keyword
parameter.
directory file !AD is not .DIR;1
Explanation: A file with the directory flag set in its file
header is not version 1 or does not have the extension .DIR
User Action: Rename or delete the file.
failed to disable !AD
Explanation: This is a summary message indicating DFG$DEFRAGMENT
returned a failure status for a DISABLE command. This failure is
related to a specific script supplied in the message. Associated
messages provide the cause of the failure.
User Action: Refer to associated messages to determine a course
of action.
no script was disabled
Explanation: This is a summary message indicating the specified
script was not disabled. Associated messages indicate the reason
the disable operation failed.
User Action: Refer to associated messages to determine a course
of action.
disk !AD too full for defragmentation
Explanation: This error occurs when the defragmentation process
finds that a disk is too full for defragmentation. The process
experiencing the error will terminate (if a single volume or a
stripe set was defragmented) or continue with the next volume in
the volume set.
User Action: None.
duplicate concurrent defragmentation processes for device !AD
Explanation: The defragmentation process detected a currently
running defragmentation process on the target device. Concurrent
defragmentation processes on the same target device are not
allowed; thus, this process exits. This ensures that two
defragmentation processes do not attempt to defragment the same
disk at the same time.
User Action: Ensure that no two defragmentation processes attempt
to defragment the same device at the same time.
duplicate concurrent scheduler on node !AD
Explanation: The scheduler detected another currently running
scheduler on the current node. Concurrent schedulers on the same
node are not allowed.
User Action: Ensure that no two schedulers execute on the same
node at the same time.
duplicate script name: !AD
Explanation: An attempt was made to define two scripts with the
same name.
User Action: Reissue the command using a unique script name for
the /SCRIPT qualifier.
empty defragmentation item list
Explanation: The defragmentation list was empty for a script
definition call to DFG$DEFRAGMENT.
User Action: If the call to DFG$DEFRAGMENT was from HP supplied
software, submit an SPR. Otherwise, correct the calling program.
empty defragmentation and scheduling item lists
Explanation: Both the scheduler list and the defragmentation list
were empty.
User Action: If the call to DFG$DEFRAGMENT was from HP supplied
software, submit an SPR. Otherwise, correct the calling program.
failed to enable !AD
Explanation: This is a summary message indicating the specified
script was not enabled. Associated messages indicate the reason
the enable operation failed.
User Action: Refer to associated messages to determine a course
of action.
no script was enabled
Explanation: This is a summary message indicating that no script
could be enabled (the user specified /ALL on the command line).
Associated messages indicate the reason the enable operation(s)
failed.
User Action: Refer to associated messages to determine a course
of action.
process limit exceeded; increase process limit to run
Explanation: Starting another defragmentation process on
this node would exceed the user-defined maximum number of
defragmentation processes for this node.
User Action: If the limit is acceptable, no action is required.
Otherwise, change the limit using the SET subcommand.
time limit exceeded; defragmentation process stopped
Explanation: A defragmentation process was terminated because its
time limit was exceeded. This is a limit imposed by the user with
the /TIME_LIMIT qualifier.
User Action: None or change the time limit.
error while attempting to queue a process lock for device !AD
Explanation: The defragmentation process received an unexpected
failure status from the $ENQ system service while trying to get
an exclusive lock on the target device. Associated messages
provide more detail. This error does not occur for concurrent
defragmentation processes.
User Action: Refer to associated messages to determine a course
of action.
unable to access extent header(s) for file !AD
Explanation: The defragmentation process could not access the
given file's extent header(s) through the IO$_ACCESS QIO.
User Action: Refer to associated messages to determine a course
of action.
unable to free dynamic memory
Explanation: The defragmentation process called the LIB$FREE_VM
service incorrectly.
User Action: Submit an SPR.
error in getting device information from !AD
Explanation: The defragmentation process received failure status
from the GETDVI system service. Associated messages provide more
detail.
User Action: Refer to associated messages to determine a course
of action.
unable to allocate dynamic memory
Explanation: The defragmentation process received failure status
from the LIB$GET_VM system service. Associated messages provide
more detail.
User Action: If the error is due to insufficient system dynamic
memory, system resources are insufficient to defragment the
volume. If this is not the case, submit an SPR.
unable to map global section
Explanation: The defragmentation process could not map the system
wide global section created by the scheduler. This error is
very unlikely, but could be caused if the scheduler exits after
creating the global section and the defragmentation process,
but before the defragmentation process has a chance to map the
global section. It will also occur if the user tries to run the
DFG$ENGINE_MAIN program directly.
User Action: None.
INDEXF.SYS is completely full. You must delete some files
Explanation: The index file or header is full. The program needs
at least one free file header.
User Action: Delete unneeded file(s).
Your index file is already optimal, no further work needed.
Explanation: The index file is already optimal. No further work
is needed.
User Action: None. The program has completed.
logically inconsistent data in relation !AD
Explanation: The database contains inconsistent data. The root of
the problem may be that the RMS database is corrupt, that the DFG
software has an error.
User Action: Submit an SPR. Include a dump of the scheduling
database contents, if possible.
internal error; invalid supersede flag
Explanation: This is an internal error.
User Action: Submit an SPR.
relation !AD: illegal file or node type (!SL)
Explanation: This is an internal scheduler error.
User Action: Submit an SPR.
illegal function code (!SL) in !AD
Explanation: This is an internal scheduler error.
User Action: Submit an SPR.
internal logic error in !AD
Explanation: This is an internal scheduler error.
User Action: Submit an SPR.
internal memory allocation calculation error; submit an SPR
Explanation: A consistency check found the global section
allocated was not large enough to hold the necessary data. This
is an internal error.
User Action: Submit an SPR.
internal error; inconsistent source !AD
Explanation: This error occurs when the source for one module is
not compatible with the source for another module.
User Action: Submit an SPR.
internal error while verifying node
Explanation: This is an internal error
User Action: Submit an SPR.
all scripts have been !AD
Explanation: Success message for any immediate command (ENABLE,
DISABLE) where /ALL was specified.
User Action: None.
script !AD has been !AD
Explanation: Success message for any immediate command (ENABLE,
DISABLE) where specific scripts were specified.
User Action: None.
internal software error number !UL
Explanation: This is an internal error encountered in the
defragmentation process code.
User Action: Submit an SPR. Include the software error number.
internal error: !AD
Explanation: This is an internal error.
User Action: Submit an SPR. Include the internal error string.
internal error: !AD !XL
Explanation: This is an internal error.
User Action: Submit an SPR. Include the error number and the
associated string supplied in the error message.
device unsuitable for defragmentation
Explanation: Target device not suitable for defragmentation.
User Action: Ensure that the target device for defragmentation is
an ODS-2 volume (or stripe set or volume set). Further, it must
be a local device available from the issuing node.
device not suitable for defragmentation, do you wish to continue
(Y, [N])?
Explanation: The user specified a device for a defragment
operation that is currently unavailable or unsuitable for
defragmentation. However, since the device may become available
by the time the defragmentation operation begins, the user is
allowed the option of continuing or aborting the command.
User Action: If the device specified is correct, but is
currently off line or, for some other reason, is unsuitable for
defragmentation, enter Y in response to the prompt. Otherwise,
enter N or press Return to abort the command.
!AD is an invalid device name
Explanation: The supplied device name was invalid.
User Action: Specify a valid device name.
invalid defragmentation item list
Explanation: The defragmentation list passed to DFG$DEFRAGMENT
was invalid, because of one of the following:
o A call to DFG$DEFRAGMENT using a scheduler list that indicates
the defragmentation list should be empty. For example, DFG$K_
SHOW_SCRIPT must not have a defragmentation item list.
o Something was wrong with the semantics of the defragmentation
item list, or a particular item descriptor was formatted
improperly.
User Action: If the call to DFG$DEFRAGMENT was from HP supplied
software, submit an SPR. Otherwise, correct the calling program.
invalid defragmentation and scheduler item lists
Explanation: Both the scheduler list and the defragmentation list
passed to DFG$DEFRAGMENT were invalid.
User Action: If the call to DFG$DEFRAGMENT was from HP supplied
software, submit an SPR. Otherwise, correct the calling program.
!AD is an invalid file specification
Explanation: An invalid file name was given for either the log
file or the options file. Associated messages describe why the
file name is invalid.
User Action: Based on the associated messages, specify a valid
file name.
invalid combination of DFG$K_INTERVAL and DFG$K_PREDECESSOR
Explanation: The DFG$K_INTERVAL item descriptor is not allowed
with the DFG$K_PREDECESSOR item descriptor in a call to
DFG$DEFRAGMENT.
User Action: If the call to DFG$DEFRAGMENT was from HP supplied
software, submit an SPR. Otherwise, correct the calling program.
invalid item list; item !SL is in error
Explanation: This message indicates the dfg_list or sch_
list parameter to DFG$DEFRAGMENT was incorrectly formatted
or logically invalid. It provides the item number that was
incorrect. Associated messages indicate further errors.
User Action: If the call to DFG$DEFRAGMENT was from HP supplied
software, submit an SPR. Otherwise, correct the calling program.
invalid combination of items in item list
Explanation: This message indicates the dfg_list or sch_list
parameter to DFG$DEFRAGMENT was logically invalid. One of the
lists contained item codes that were not compatible.
User Action: If the call to DFG$DEFRAGMENT was from HP supplied
software, submit an SPR. Otherwise, correct the calling program.
an item list contained an unknown item code
Explanation: This message indicates the dfg_list or sch_list
parameter to DFG$DEFRAGMENT contained an item descriptor with
an unknown item code. It may also indicate a faulty item_list_2
returned from DFG$DEFRAGMENT as part of the SHOW subcommand.
User Action: If the call to DFG$DEFRAGMENT was from HP supplied
software, submit an SPR. Otherwise, correct the calling program.
insufficient license units to run DEFRAGMENT
Explanation: The DFG software is not licensed to run on this
node.
User Action: Install the DFG license.
!AD is an invalid logical name
Explanation: A logical name translation failed because the
logical name was invalid. Associated messages provide more
detail.
User Action: Refer to associated messages to determine a course
of action.
invalid scheduler item list
Explanation: The scheduler list passed to DFG$DEFRAGMENT was
invalid.
User Action: If the call to DFG$DEFRAGMENT was from HP supplied
software, submit an SPR. Otherwise, correct the calling program.
!AD is an invalid script name
Explanation: The user tried to name a script using characters
that are not supported for script names.
User Action: Reenter the script name using valid characters.
script !AD already has a queue entry
Explanation: The user entered a START subcommand for a script
that was already started.
User Action: None.
invalid string descriptor
Explanation: An invalid string descriptor was pointed to from an
item list passed to DFG$DEFRAGMENT.
User Action: If the call to DFG$DEFRAGMENT was from HP supplied
software, submit an SPR. Otherwise, correct the calling program.
invalid string descriptor in item !SL of item list
Explanation: An invalid string descriptor was pointed to from an
item list passed to DFG$DEFRAGMENT. The item number of the item
descriptor containing the offending string descriptor is supplied
by this message.
User Action: If the call to DFG$DEFRAGMENT was from HP supplied
software, submit an SPR. Otherwise, correct the calling program.
log file not specified, but defragmentation level is 5
Explanation: Occurs if /LEVEL=5 is specified without the /LOG
qualifier. Defragmentation statistics are unavailable without the
/LOG qualifier; thus, it is required when /LEVEL=5 is specified.
User Action: Specify /LOG={logfile} when using the /LEVEL=5
qualifier.
!AD limit exceeded
Explanation: A user-specified CPU_LIMIT, IO_LIMIT, or PROCESS_
LIMIT has been exceeded.
User Action: If the limit is correctly set, no action is
required. If the limit is incorrect, set a new limit using the
SET subcommand.
incorrect device name !AD specified on file list
Explanation: A device name was specified with a file on the
frequent, dormant, or exclude lists that does not match the
target device name.
User Action: Correct the device name or remove it altogether.
!SL is an invalid defragmentation level; use 1-5
Explanation: The defragmentation level specified by the user on
the command line was not a number from 1 to 5, inclusive.
User Action: Specify a valid defragmentation level.
the logical name !AD is not defined
Explanation: A required logical name is not defined.
User Action: Define the indicated logical name and try the
command again.
!AD qualifier requires a value in this context
Explanation: A qualifier needed a value, such as a script name,
but the user did not provide one.
User Action: Provide the value requested.
monitor unable to access database for script information
Explanation: This error occurs if the monitor cannot access the
scheduling database. The most likely causes of this error are:
the logical name DFG$DEFRAGMENT is not defined; the database does
not exist.
User Action: If this message persists and the other
defragmentation software is working (scheduler, DCL interface,
defragmentation processes), submit an SPR.
too few columns in display, please resize
Explanation: The display has too few columns to display
meaningful information.
User Action: If your terminal is a DECwindows DECterm, resize the
window as appropriate. If your terminal is a VT100-style device,
submit an SPR.
too few rows in display, please resize
Explanation: The display has too few rows to display meaningful
information.
User Action: If your terminal is a DECwindows DECterm, resize the
window as appropriate. If your terminal is a VT100-style device,
submit an SPR.
!AD is not currently being defragmented
Explanation: An attempt was made to monitor a script that is not
executing.
User Action: Monitor only executing defragmentation processes.
error !SL while reading the monitor interface
Explanation: This error occurs if a process cannot read data
using the interface that exists between the monitor process, the
scheduling process, and the defragmentation process. The process
experiencing the error will continue, though not all data may be
available for the monitor display.
User Action: None.
unexpected error from !AD
Explanation: An error occurred in a call to the Screen Management
facility (SMG). The SMG routine that returned the error is
displayed. A subsequent error message contains the SMG error
code.
User Action: Refer to the subsequent error message to determine a
course of action.
error !SL while writing the monitor interface
Explanation: This error occurs if a process cannot write data
using the interface that exists between the monitor process, the
scheduling process, and the defragmentation process. The process
experiencing the error will continue, though not all data may be
available for the monitor display.
User Action: None.
Relative volume number !UL
Explanation: This is issued to give more information to the
maintainer about a movefile error (either MOVFILQIOERR or
MOVFILSTSERR).
User Action: Submit an SPR.
QIO error on movefile for volume !AD
Explanation: This is an internal error; the movefile QIO was
formatted incorrectly by the defragmentation process.
User Action: Submit an SPR.
status error on movefile for volume !AD
Explanation: The movefile QIO returned an error status to the
defragmentation process. Subsequent messages provide the specific
error encountered.
User Action: Refer to subsequent messages to determine a course
of action.
multiple successors not allowed
Explanation: The script named as predecessor already has a
successor defined.
User Action: Specify a different predecessor or none.
the /NODE qualifier was ignored
Explanation: The /NODE qualifier was specified with show script,
but no CPU, I/O, or process parameter was selected. Any node name
is meaningless when applied to show script only. This message is
informational.
User Action: None.
inherit script !AD not found
Explanation: The script specified in the /INHERIT qualifier could
not be found in the SCRIPTS relation.
User Action: Reissue the command using a defined script name for
the /INHERIT qualifier.
failed attempt to stop a defragmentation process
Explanation: An attempt (by the scheduler) to abort the
defragmentation process failed. Associated messages provide more
detail. It could simply be that the defragmentation process has
completed or is suspended.
User Action: Refer to associated messages to determine a course
of action.
monitor interface not established
Explanation: This error occurs if the defragmentation process
cannot establish the monitor interface. In this case, the error
appears in the defragmentation process log file. The error can
also occur when executing the monitor function if the monitor
interface is not yet established. The error can also appear in
the scheduler log file if the interface is not established.
User Action: If you are trying to run the monitor, try the
command again as the defragmentation process may not yet have
created the interface. If the error occurs in the defragmentation
process or scheduler log files, determine a course of action
based on any associated messages. If the error is due to
insufficient ENQUE limit, increase the ENQUE limit of the user
process running monitor or the scheduler process, whichever is
appropriate.
!AD not found in configuration
Explanation: A node name that was associated with a script was
not present in the configuration. This error can also occur
during scheduler initialization if both the SYSGEN parameter,
SCSNODE, and the logical, SYS$NODE are undefined on the node
where the scheduler is running. In the case of the scheduler, the
node name reported in the message will be blank.
User Action: If the error occurs in the scheduler log file,
define either the logical name SYS$NODE or the SYSGEN parameter
SCSNODE and restart the scheduler. If the error occurs when
entering a command, ensure you have spelled the node name
correctly and that the node exists on the local system.
mail notification of defragmentation process completion failed
Explanation: An attempt to send mail to the mail distribution
list specified in DFG$MAIL_ADDRESS has failed.
User Action: Verify that the logical DFG$MAIL_ADDRESS is defined.
Refer to associated messages to determine if additional action is
necessary.
predecessor script !AD not found
Explanation: The script specified in the /PREDECESSOR qualifier
could not be found in the SCRIPTS relation.
User Action: Check spelling of the script name used with the
/PREDECESSOR qualifier. Use the name of a script that has already
been defined (with the VOLUME subcommand) for the /PREDECESSOR
qualifier.
insufficient privileges; you need BYPASS, CMKRNL, DETACH,
EXQUOTA, NETMBX, SHARE, SYSGBL, SYSLCK, SYSPRV, TMPMBX, and WORLD
Explanation: The user has insufficient privileges to run
DEFRAGMENT.
User Action: Set the BYPASS, CMKRNL, DETACH, EXQUOTA, NETMBX,
SHARE, SYSGBL, SYSLCK, SYSPRV, TMPMBX, and WORLD privileges and
try the command again.
no queue entry for script !AD
Explanation: A queue entry was not found for a script that was
to be canceled, disabled, or enabled. (The database did not have
a record that matched the user-supplied script name for one of
these commands.)
User Action: Check the spelling of the script name. Use
only names that have previously been defined with the VOLUME
subcommand.
scheduling operations may not have completed
Explanation: One or more scheduling operations may not have
completed. This is a summary message. Associated messages provide
more detail.
User Action: Refer to associated messages to determine a course
of action.
script name !AD is not defined in the database
Explanation: The named script is not defined in the database.
User Action: Check the spelling of the script name and try the
command again.
script name !AD not found
Explanation: A script name specified by the user was not in the
scheduling database.
User Action: Check the spelling of the script name and try the
command again.
error retrieving show data from the scheduling database
Explanation: There was an error retrieving show data from the
scheduling database.
User Action: Refer to associated messages to determine a course
of action.
cannot access notification data in !AD
Explanation: This is an internal error. It occurs if one of
the internal user notification routines is called with an
inaccessible parameter.
User Action: Submit an SPR.
invalid data found in !AD
Explanation: This is an internal error. It occurs if one of the
internal user notification routines is called with invalid data.
User Action: Submit an SPR.
error closing temporary notification file
Explanation: An error occurred while closing the temporary
notification file.
User Action: Refer to associated messages to determine a course
of action.
this device is not a disk, recheck the device name
Explanation: The device for which you requested defragmenting is
not a disk.
User Action: Check the device name and try the command again.
script !AD not executing
Explanation: An attempt was made to abort a script that was not
executing.
User Action: None.
error extending the scratch file needed for defragmenting
INDEXF.SYS
Explanation: The temporary scratch file needed to defragment
INDEXF.SYS could not be created. Its creation would have caused a
multi-header entry or there was not enough space on the volume.
User Action: Before defragmenting INDEXF.SYS, be sure to
defragment the volume and consolidate free space. Also, make
sure that the largest free space on the volume is larger than
INDEXF.SYS. To check the largest free space and extents of
INDEXF.SYS, execute the following command:
$ DEFRAGMENT SHOW disk:/VOLUME/LOCATION=[000000]INDEXF.SYS
error writing to temporary notification file
Explanation: The notification message could not be written.
User Action: Refer to associated messages to determine a course
of action.
!AD is not local to !AD
Explanation: The user has specified a target device that is
not local to the node that is trying to run the defragmentation
process.
User Action: Nonlocal devices (such as DFS mounted devices)
cannot be defragmented.
!AD is not an ODS-2 mounted device
Explanation: The user has specified a device for defragmentation
that is not a mounted ODS-2 format volume.
User Action: Specify an ODS-2 format volume.
error translating !AD
Explanation: There was an error translating the supplied logical
name.
User Action: Define the indicated logical using the /EXECUTIVE_
MODE and /SYSTEM qualifiers.
defragmentation process, ID=!XL, was not stopped
Explanation: An attempt to stop a defragmentation process failed.
Associated messages provide more detail. The most likely cause
of this message is that the defragmentation process is no longer
running.
User Action: None.
no volume name specified for VOLUME subcommand
Explanation: DFG$DATABASE received a dfg_list item list that did
not contain a volume name item descriptor.
User Action: If this error occurs with HP supplied software,
submit an SPR. Otherwise, correct the calling program.
a defragmentation process cannot be started for script !AD
Explanation: An attempt to start a defragmentation process
failed. Associated messages provide more detail.
User Action: Refer to associated messages to determine a course
of action.
error opening !AD as input
Explanation: The specified file could not be opened for input.
Associated messages indicate the reason.
User Action: Refer to associated messages to determine a course
of action.
cannot open mail file for /MAIL_NOTIFICATION
Explanation: The mail file cannot be opened by the scheduler
when attempting to notify users by way of the /MAIL_NOTIFICATION
qualifier. Associated messages indicate the reason.
User Action: Refer to associated messages to determine a course
of action.
error opening !AD as output
Explanation: The specified file could not be opened for output.
Associated messages indicate the reason.
User Action: Refer to associated messages to determine a course
of action.
invalid device specified on line !SL, options file !AD
Explanation: A volume was specified with a file name in the
options file and the volume was not the target defragmentation
volume.
User Action: Correct the invalid line in the options file.
Specify no device name, or specify the target device name.
options file error
Explanation: The options file contained errors. This is a summary
message. Associated messages provide more detail.
User Action: Refer to associated messages to determine a course
of action.
file not found on line !SL, options file !AD
Explanation: A file specified as /EXCLUDE, /FREQUENT, or /DORMANT
in the options file was not found.
User Action: No action is necessary. To eliminate this message,
however, you should remove the line in the options file that is
reported in this message. Since the file given on this line is no
longer on the target device, this line has no effect.
invalid qualifier on line !SL, options file !AD
Explanation: A classification for a file was given that was not
one of: /FREQUENT, /DORMANT, /EXCLUDE.
User Action: Check spelling and ensure that only classifications
of /FREQUENT, /DORMANT, or /EXCLUDE are used for files listed in
the options file.
multiple classifications on line !SL, options file !AD
Explanation: A file was classified with multiple classifications
(that is, file.ext/FREQ/DORM). This error prevents the
defragmentation process from being started.
User Action: Specify only one file classification per line in the
options file.
file not classified on line !SL, options file !AD
Explanation: A file was in the options file, but was not
classified as /FREQUENT, /DORMANT, or /EXCLUDE.
User Action: Make sure the file on the line specified in the
options file has one of the above-listed classifications.
RMS error on line !SL, options file !AD
Explanation: An unanticipated error was returned from the $PARSE
or $SEARCH RMS routines.
User Action: Refer to the specified line in the options file.
Also check associated messages for more information.
error parsing !AD
Explanation: The RMS $PARSE service failed for the specified
file.
User Action: Refer to associated messages to determine a course
of action.
!SL is an invalid process limit; specify positive values
Explanation: The process limit was negative.
User Action: Specify only positive values for the PROCESS_LIMIT
keyword parameter to the SET subcommand.
the predecessor for script !AD is not a user-provided name
Explanation: The predecessor for a script was not a user-provided
name. This message can occur during the SHOW subcommand when
the /COMMAND_LINE qualifier is present. Because script names
beginning with DFG$ are reserved for the DEFRAGMENT software,
they are never listed when the /COMMAND_LINE qualifier is used.
This warning message indicates the script whose predecessor was
not listed.
User Action: If the output of the SHOW subcommand was directed
to a file, edit the file and name the script to be used as a
predecessor using the /SCRIPT qualifier. Then, modify the script
listed in this message so the /PREDECESSOR qualifier indicates
the script name used.
defragmentation process aborted
Explanation: The defragmentation process has aborted. It could
be that the total defragmentation time has been exceeded and the
scheduler has stopped the defragmentation software. Thus, this
message does not necessarily indicate failure.
User Action: Refer to associated messages to determine a course
of action.
defragmentation process start
Explanation: This message is generated by the defragmentation
process after it has completed initialization.
User Action: None.
defragmentation process normal completion
Explanation: This message is generated by the defragmentation
process after the process has successfully completed.
User Action: None.
!AD request for all scripts has been successfully queued
Explanation: Any of the queued commands where /ALL was specified
were successful.
User Action: None
!AD request for unnamed script has been successfully queued
Explanation: A defragmentation request was successfully
processed; the user did not supply a script name.
User Action: None
!AD request for script !AD has been successfully queued
Explanation: A defragmentation process was successfully queued
and had a user-specified script name.
User Action: None
failed to remove !AD from the database
Explanation: This is a summary message indicating the specified
script was not removed. Associated messages indicate the reason
the remove operation failed.
User Action: Refer to associated messages to determine a course
of action.
no script was removed from the database
Explanation: This is a summary message indicating that no script
was removed from the scheduling database when the user had
specified the /ALL qualifier.
User Action: Refer to associated messages to determine a course
of action.
remove unsuccessful
Explanation: A REMOVE subcommand was unsuccessful. This is a
summary message. This message may or may not indicate an error.
Associated messages provide more detail.
User Action: Refer to associated messages to determine a course
of action.
remove command for !AD already issued
Explanation: A REMOVE subcommand had been issued for this script,
but it had not yet completed when another REMOVE subcommand for
the same script was issued.
User Action: None.
Map pointer copy would extend into a reserved area
Explanation: The copy of INDEXF.SYS map pointers would run into a
reserved area.
User Action: Submit an SPR.
RMS operation !AD failed (file !AD)
Explanation: The specified RMS operation failed.
User Action: Refer to associated messages to determine a course
of action.
scheduler cannot complete scheduling tasks
Explanation: This is a summary message indicating that the
scheduler did not complete all its scheduling tasks.
User Action: Refer to associated messages to determine a course
of action.
scheduler exited at user request
Explanation: The scheduler exited normally. This occurs if
the user executes the DFG$STOP_SCHEDULER.COM procedure, runs
the SYS$SYSTEM:DFG$STOP_SCHEDULER.EXE image, or executes the
DFG$SHUTDOWN.COM procedure.
User Action: None.
!AD started on !AD !%D
Explanation: A scheduler started. This message appears at the
beginning of every scheduler log.
User Action: None.
script !AD is already disabled
Explanation: An attempt was made to disable a script that was
already disabled.
User Action: None.
script !AD is already enabled
Explanation: An attempt was made to enable a script that was
already enabled.
User Action: None.
loop in $SEARCH: same file returned twice
Explanation: RMS's $SEARCH function did not return files in
alphabetical order. This may be caused by a corrupt directory
file or by an alias that points to a deleted file.
User Action: Investigate the directory structure of the disk.
mail notification failed
Explanation: This is a summary message that occurs when the
scheduler does not send the mail notification message requested
by the user with /MAIL_NOTIFICATION. Associated messages provide
more detail.
User Action: Refer to associated messages to determine a course
of action.
failed to set any specified parameters
Explanation: DFG$DEFRAGMENT returned a failure status for a SET
command.
User Action: Refer to associated messages to determine a course
of action.
a SET subcommand failed for node !AD
Explanation: A DEFRAGMENT SET CPU, I/O, or PROCESS command failed
for the indicated node.
User Action: Refer to associated messages to determine a course
of action.
specified parameters successfully set
Explanation: The database was successfully updated with the new
CPU_LIMIT, IO_LIMIT, and PROCESS_LIMIT values.
User Action: None.
device is a member of a shadow set; specify the shadow set name
Explanation: The user attempted to defragment a member of a
shadow set. Attempting to defragment members of a shadow set
is not supported.
User Action: Defragment the entire shadow set by specifying the
shadow set name (DUSXXX) on the DEFRAGMENT command line.
!AD missing from show data
Explanation: This is an internal error.
User Action: Submit an SPR.
a show script command failed
Explanation: A SHOW SCRIPT command did not complete successfully.
Associated messages provide more detail.
User Action: Refer to associated messages to determine a course
of action.
failed to start !AD
Explanation: DFG$DEFRAGMENT returned a failure status for a
START subcommand. This is a summary message and probably does
not indicate any real error. Most likely, the script was already
started. Associated messages provide more detail.
User Action: Refer to associated messages to determine a course
of action.
start command unsuccessful
Explanation: A START subcommand was unsuccessful. This is a
summary message. This message may or may not indicate an error.
Associated messages provide more detail.
User Action: Refer to associated messages to determine a course
of action.
start command for !AD already issued
Explanation: A START subcommand had been issued for this script
but it had not yet completed when another START subcommand for
the same script was issued.
User Action: None.
call to system service !AD failed
Explanation: A system service call failed.
User Action: Refer to associated messages to determine a course
of action.
invalid time string !AD from !AD
Explanation: The syntax of the time string supplied in the
message was invalid or out of range. The offending routine is
also listed in the message.
User Action: Submit an SPR containing the information in this
message.
unrecoverable error
Explanation: The defragmentation process encountered an
unrecoverable error; no further processing occurred.
User Action: Refer to associated messages to determine a course
of action.
command aborted by user
Explanation: The user decided not to continue after encountering
the INVDEVCONT message. This is a summary message.
User Action: None.
user error
Explanation: The user made an error. Associated messages provide
more detail.
User Action: Refer to associated messages to determine a course
of action.
an ABORT command terminated the defragmentation process
Explanation: Because of a user-issued ABORT command, a
defragmentation process terminated.
User Action: None.
device is a member of a constituent set; specify the set name
Explanation: The user attempted to defragment a virtual member of
a disk set, such as a stripeset member.
User Action: Defragment the entire set by specifying the set name
on the DEFRAGMENT command line.
volume command failed; script !AD was not entered into the
database
Explanation: The specified script was not entered into the
database. Some portion of command validation failed. The exact
nature of the error is provided in associated messages.
User Action: Refer to associated messages to determine a course
of action.
volume command failed; unnamed script was not entered into the
database
Explanation: The command was not entered into the database. Some
portion of command validation failed. The exact nature of the
error is provided in associated messages.
User Action: Refer to associated messages to determine a course
of action.
device is a member of a volume set;specify the volume set name
Explanation: The user attempted to defragment a member of a
volume set. Attempting to defragment members of a volume set
is not supported.
User Action: Defragment the entire volume set by specifying the
volume set name on the DEFRAGMENT command line.
volume lock error for device !AD
Explanation: Error trying to allocation-lock the volume. This
error may only occur in the defragmentation process code. This
prevents file structure changes for a short time while the
defragmentation process reads a fresh copy of BITMAP.SYS.
User Action: Refer to associated messages to determine a course
of action.
volume command unsuccessful
Explanation: A VOLUME subcommand was unsuccessful. This is a
summary message. This message may or may not indicate an error.
Associated messages provide more detail.
User Action: Refer to associated messages to determine a course
of action.
volume unlock error for device !AD
Explanation: The target device could not be allocation-unlocked
by the defragmentation process.
User Action: Refer to associated messages to determine a course
of action.
!SL hotfile records added to the /FREQUENT list.
Explanation: This message indicates the VPA database query has
completed. It also indicates the total number of hotfile records
found that were related to the target device.
User Action: None.