% Librarian I01-42绬) 绬h  5$^ About File_Menu Inherit_List: IntroductionMonitor_a_Script_or_Volume Node_List Optimize_Menu~ Options_Menu`Predecessor_ListReport_on_the_State_of_a_VolumeRVN` Script_List< Script_MenuSelect_Many_FilesSelect_One_File Volume_ListvVolume_List_Report 绬1 AboutD The Disk File Optimizer (DFO) software reduces file fragmentation: on a device while that device remains on line to users.B This software is compatible with any Files-11 structure level 2B (ODS-2) formatted volume including single volumes, bound volume> sets, stripe sets, and shadow sets.The file defragmentationD utility is also compatible with ODS-5 formatted device on OpenVMS Alpha 7.2-1 and above.@ Operating OpenVMS VAX (Version V6.0, V6.1, V6.2, V7.0,( V7.1, V7.2 and V7.3)B System and OpenVMS AXP (Version V6.1, V6.2, V7.0, V7.1-2,: V7.2-1, V7.3, V7.3-1, V7.3-2 and V8.2) Version, Software Disk File Optimizer V2.9 Version 2 Copyright4 Hewlett-Packard Development Company, L.P. 2005.C Confidential computer software. Valid license from hp and/or its9 subsidiaries required for possession, use, or copying.= Consistent with FAR  12.211 and 12.212, Commercial Computer@ Software, Computer Software Documentation, and Technical DataA for Commercial Items are licensed to the U.S. Government under vendors commercial license.= Neither hp nor any of its subsidiaries shall be liable forB technical or editorial errors or omissions contained herein.The; information in this document is provided "as is" withoutD warranty of any kind and is subject to change without notice. TheB warranties for hp products are set forth in the express limitedA warranty statements accompanying such products. Nothing herein> should be construed as constituting an additional warranty. ww绬1 Inherit_ListA Select the script you want to inherit the characteristics of a2 previously create script. Press OK to continue. ww绬1 Script_List: Select the script you want work on and then press OK to continue. ww绬1 RVN? Select the relative volume number you want optimize and then press OK to continue. ww绬1 Predecessor_ListD Select the script you want this script to be a predecessor of and then press OK to continue. ww绬1 Volume_List> Select the volume you want to optimize and then press OK to continue. ww绬1 Volume_List_Report? Select the volume you want to report on and then press OK to continue. ww绬 1 Node_List@ Select the node/s you want to execute this script on and then press OK to continue. ww绬1 Select_One_File1 Select the file and then press OK to continue. ww绬1 Select_Many_Files3 Select the file/s and then press OK to continue.? In addition to the DCL command line interface, the Disk FileA Optimizer (DFO) software includes a DECwindows interface. ThisB interface gives a visual reference for tasks built into the DFO software. ww绬1 Introduction@ The DFO DECwindows interface allows you to initiate, control,? and stop defragmentation operations. To start the DECwindows! interface, enter this command:$ $ DEFRAGMENT/INTERFACE=DECWINDOWS2 The Disk File Optimizer initial window appears. = The interface allows you to perform the following actions:) o File-exit the DECwindows interface.D o Optimize-create a script to optimize a volume, selected files,# or a disks volume index file.> o Script-create, modify, remove, show, schedule, and abort# scripts for files or volumes.@ o Monitor-monitor the defragmentation process by selecting a" script or volume to monitor.A o Report-review the current state of a volume to determine if defragmentation is needed.9 o Options-set or show the Disk File Optimizer process parameters. 2 Logicals3DFO Logical names are recognized by the prefix DFG$ Table 1 Logical Names Installation Logical& Name Variant Purpose: DFG$DATABASE Defrag Equates to the device:[dir]? PLUS specification where the database< resides. Also located in this> directory are the scheduler log@ files, which have a name of DFG$_B xxxx. LOG, where xxxx is the name ofA the node on which the scheduler is' running.D DFG$DISK All Provided to the EPILOGUE and PROLOGUE> command files. It translates to@ the name of the disk on which DFO2 currently operates.@ DFG$MAIL_ Defrag Equates to a file name containing@ ADDRESS PLUS a mail dist ribution list of thoseC who should receive notification whenB defragmentation processes complete.) DFG$MESSAGE All Equates toA SYS$MESSAGE:DFG$MESSAGE.EXE, which@ is the shareable image containing? all the defragmentation-specific= messages. This logical is used? onl y if you install the callable) interface.D DFG$SCRIPT All Provided to the EPILOGUE and PROLOGUEB command files. It translates to theA name of the script associated with/ the DFO process.D DFG$STATE All Provided to the EPILOGUE and PROLOGUE? command files. As appropriate to? ind icate the state of DFO to theB command procedure, it translates to6 either of these strings* PROLOGUE* EPILOGUED DFG$STATUS All Provided to the EPILOGUE and PROLOGUEB command files. It translates to theA current status of the DFO process.B For the EPILOGUE command file, thisD status is the final status of the DFO' process.C DFG$ASTLM All These logicals affect the associated? DFG$BIOLM process quota of any DFO process> DFG$BYTLM running on the associated node. DFG$DIOLM DFG$ENQLM DFG$FILLM DFG$JTQUOTA DFG$PGFLQUOTA DFG$PRCLM DFG$TQELM DFG$WSDEFAULT DFG$WSEXTENT DFG$WSQUOTAC DFG$TRANSFERSIZE All The logical, DFG$TRANSFERSIZE, helps@ you tune the Disk File Optimizer.D The definition of this logical allows? you to change the amount of dataB that is transferred at one time. OnA a volume that has files with large? extents, you could wait up to 20A minutes while the s ystem transfersC these large extents before you could@ access the file. By defining thisB logical, you could access this fileB in less than a minute. This logicalD changes the impact that the Disk FileA Optimizer has on applications thatD are simultaneously accessing the same%  files.C This logical is set to 10,000 blocks? by default. You can change it byB editing SYS$STARTUP:DFG$STARTUP.COM= and then executing the command) procedure.. 2 Messages@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. MostDmessages have $FAO formatting control sequences due to which messagetext begins with an ! mark. 3 ABOFAIL1 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.B User Action: Refer to associated messages to determine a course of action. 3 ABOFAIL2 no script was aborted@ Explanation: DFG$DEFRAGMENT returned a failure status when itB attempted to abort all scripts in the scheduling database. ThisA message is a summary message. Associated messages provide more detail.B User Action: Refer to associated messages to determine a course of action. 3 ABORTNOTDONE abort unsuccessful? Explanation: An ABORT subcommand was unsuccessful. This is aB summary message. This message may or may not indicate an er ror.+ Associated messages provide more detail.B User Action: Refer to associated messages to determine a course of action. 3 ABOSEEN' abort command already issued for !ADC Explanation: An ABORT subcommand had been issued for this scriptA but it had not yet completed when another ABORT subcommand for the same script was issued.1 User Action: Wait for the command to complete. 3 ACCESSERR access error on file !ADC Explanation: A QIO IO$_ACCE!SS function could not be performed onC the given file for reasons detailed in associated messages. This@ message occurs only in the log file or the /MAIL_NOTIFICATION messages.B User Action: Refer to associated messages to determine a course of action. 3 ACLERR2 BUGCHECK - Map pointer copy would run into ACLs@ Explanation: The copy made of INDEXF.SYS would run into ACLs.2 User Action: Clean up disk and restart program. 3 ASSIGNERR& channel-assign "error for device !ADA Explanation: A channel could not be assigned for the indicated3 device. Associated messages provide more detail.B User Action: Refer to associated messages to determine a course of action. 3 BITMAPCONERR0 $CONNECT error on file !AD:[000000]BITMAP.SYS? Explanation: A $CONNECT RMS service was unsuccessful for theB BITMAP.SYS file of the target device. The RMS error is provided in a subsequent message.C User Action: Determine a cour#se of action based on the RMS error reported. 3 BITMAPOPENERR- $OPEN error on file !AD:[000000]BITMAP.SYSA 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.C User Action: Determine a course of action based on the RMS error reported. 3 BITMAPREADERR- $READ error on file !AD:[000000]BITMAP.SYSD Explanation: A $READ RMS system service faile$d for the BITMAP.SYS< file of the target device. The RMS error is provided in a subsequent message.C User Action: Determine a course of action based on the RMS error reported. 3 CACHEFLUSHERR. unable to flush extent cache for device !ADC Explanation: An IO$_ACPCONTROL extent cache flush QIO returned aC failure status to the defragmentation process. The root cause is# included in associated messages.B User Action: Refer to associated messages to determine %a course of action. 3 CANCELNOTDONE cancel unsuccessful? Explanation: A CANCEL subcommand was unsuccessful. This is aB summary message. This message may or may not indicate an error.+ Associated messages provide more detail.B User Action: Refer to associated messages to determine a course of action. 3 CANFAIL1 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.B User Action: Refer to associated messages to determine a course of action. 3 CANFAIL2 no script was canceled@ Explanation: DFG$DEFRAGMENT returned a failure status when itC attempted to cancel all scripts in the scheduling database. ThisA message is a summary message. Associated messages provide more detail.B User Action: Refer to associated messages to determine a course of ac'tion. 3 CHECKSUMERR1 Error when copying map pointers for INDEXF.SYSA Explanation: An error occurred when mapping the new INDEXF.SYS header pointers. User Action: Submit an SPR. 3 CLOSEIN error closing !AD as inputD Explanation: An RMS error was encountered when trying to close anD input file, such as the options file. Associated messages provide more detail.B User Action: Refer to associated messages to determine a course of action. ( 3 CLOSEOUT error closing !AD as outputD Explanation: An RMS error was encountered when trying to close an8 output file. Associated messages provide more detail.B User Action: Refer to associated messages to determine a course of action. 3 CMDUNKNOWN7 unknown command; parsing error, please submit an SPR* Explanation: This is an internal error. User Action: Submit an SPR. 3 CONNECTERR! $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.B User Action: Refer to associated messages to determine a course of action. 3 CONSFAIL* free-space consolidation failed for !ADB Explanation: Free-space consolidation failed for the given disk9 User Action: None, unless indicated by other messages. 3 COPYRIGHT< Copyright 2003 Hewlett-Packard Development Company,L.P. * 3 CPUOUTRNG. !SL is an invalid CPU percentage; use 0-100C 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. 3 CREATEERR error creating !AD@ Explanation: The $CREATE RMS service failed for the specified4 file. Associated messages provide the root cause.B User Action: Refer to associated messages to determine a course of action.+ 3 CREPRCFAIL2 error creating detached defragmentation process; Explanation: The scheduler could not create the detachedD defragmentation process. Associated messages provide more detail.B User Action: Refer to associated messages to determine a course of action. 3 CRESECFAIL error creating global section@ Explanation: The global section used for communications couldB not be created by the scheduler for reasons given in associatedD error messages. T,his error is caused by a failure status from theC $CRMPSC system service, which could indicate insufficient system! wide global section resources.B User Action: Refer to associated messages to determine a course of action. 3 DBACCCONSTR7 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.B U-ser Action: Refer to associated messages to determine a course of action. 3 DBACCDUP3 duplicate record in relation !AD (operation !AD)B Explanation: An attempt was made to enter a duplicate record in9 the database. Associated messages provide more detail.B User Action: Refer to associated messages to determine a course of action. 3 DBACCERRA database-access error; relation !AD, operation !AD, status !SL@ Explanation: The database could not be acce.ssed. The cause ofB 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. 3 DBACCERR2) database-access error: !AD transaction@ Explanation: The database could not be accessed. The cause of> this problem may be an undefined logical, corrupt database,A 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. 3 DBACCWD database-access warning: relation !AD, operation !AD, sqlcode !SLA Explanation: The Rdb software returned a warning status to theC scheduler. The problem may be that the database is corrupt, that@ the disk file optimizer software is in error, or that the Rdb0 software is in error.C User Action: Try the operation again. If the error persists, re-C create the database. If the error persists after re-creating the database, submit an SPR. 3 DBACCW28 database-access warning: !AD transaction, sqlcode !SLA Explanation: The Rdb software returned a warning status to theC scheduler. The problem may be that the database is corrupt, thatD the disk file optimizer software has is in error, or that the Rdb software is in erro1r.C User Action: Try the operation again. If the error persists, re-C create the database. If the error persists after re-creating the database, submit an SPR. 3 DBBUSY6 accessing the defragmentation database; please wait< Explanation: Informational message that indicates the DCLC interface is waiting for the database access/update to complete. User Action: None. 3 DBCANTREAD0 cannot read a needed record from relation !ADA Explanation: The da 2tabase 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 not6 executing. Associated messages provide more detail.C User Action: Verify that all DFG logicals are defined and ensureC that RDMS_MONITOR is running. If RDMS_MONITOR is not running, it? can be started by invoking @SYS$STARTUP:RMONSTART.COM. Refer> 3 to associated messages to determine if additional action is necessary. 3 DBCANTWRITE2 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 canB also be caused if the RMU Monitor process (RDMS_MONITOR) is not6 executing. Associated messages provide more detail.A User Action: Try the command 4again. If the error persists, re-C create the database. If the error persists after re-creating the database, submit an SPR. 3 DBCLEAR clearing database, Explanation: A database is being cleared. User Action: None. 3 DBCLEARED database cleared, Explanation: A database has been cleared. User Action: None. 3 DBCREATE creating database, Explanation: A database is being created. User Action: None. 3 DBCREATED d5atabase created, Explanation: A database has been created. User Action: None. 3 DBINVXLNAM invalid translated name* Explanation: This is an internal error. User Action: Submit an SPR. 3 DBNOREC2 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 optimizer9 software is in error, or the Rdb software is in error. User Action: Su6bmit an SPR. 3 DBROLLBACK database updates rolled backB Explanation: All updates to the database have been rolled back. User Action: None 3 DBUPDATERR database update failedB Explanation: This is a summary message indicating that database> updates were unsuccessful. Associated messages provide more detail.B User Action: Refer to associated messages to determine a course of action. 3 DEACCESSERR deaccess error on file !ADA E7xplanation: The specified file could not be deaccessed by theC defragmentation process (using the IO$_DEACCESS QIO). Associated messages provide more detail.B User Action: Refer to associated messages to determine a course of action. 3 DELERR* cannot delete !AD, notification messageC Explanation: An attempt to spawn a subprocess to delete the mail? message sent as a result of the /MAIL_NOTIFICATION qualifier3 failed. This error occurs in the scheduler code.8B User Action: Refer to associated messages to determine a course of action. 3 DFGNOSTART* defragmentation process failed to startB Explanation: This message occurs when a defragmentation processD cannot be started. Associated messages indicate why. This message# does not occur with Defrag PLUS.B User Action: Refer to associated messages to determine a course of action. 3 DFGSTART+ started defragmentation process PID: !XL= Explanation: This9 message indicates that a defragmentationD process has been started. This message does not occur with Defrag PLUS. User Action: None. 3 DFGTMO/ defragmentation process timed out on startupB 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. 3 : DIOOUTRNG: !SL is an invalid direct I/O limit, use positive valuesA Explanation: The user specified a negative number for a direct I/O limit.@ User Action: Specify positive values for the IO_LIMIT keyword parameter. 3 DIRVERERR# 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. 3 DISFAIL1 failed ;to disable !ADC Explanation: This is a summary message indicating DFG$DEFRAGMENTC returned a failure status for a DISABLE command. This failure isC related to a specific script supplied in the message. Associated- messages provide the cause of the failure.B User Action: Refer to associated messages to determine a course of action. 3 DISFAIL2 no script was disabledB Explanation: This is a summary message indicating the specifiedC script was not disabled<. Associated messages indicate the reason the disable operation failed.B User Action: Refer to associated messages to determine a course of action. 3 DISKFULL( disk !AD too full for defragmentationB Explanation: This error occurs when the defragmentation processA finds that a disk is too full for defragmentation. The processA experiencing the error will terminate (if a single volume or aC stripe set was defragmented) or continue with the next volume in t=he volume set. User Action: None. 3 DUPDEFRAGER@ duplicate concurrent defragmentation processes for device !AD@ Explanation: The defragmentation process detected a currentlyC 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 twoB defragmentation processes do not attempt to defragment the same disk at the same time.D User Action>: Ensure that no two defragmentation processes attempt2 to defragment the same device at the same time. 3 DUPSCHED- duplicate concurrent scheduler on node !AD@ Explanation: The scheduler detected another currently runningC scheduler on the current node. Concurrent schedulers on the same node are not allowed.A User Action: Ensure that no two schedulers execute on the same node at the same time. 3 DUPSCRPT duplicate script name: !ADB Explanation?: An attempt was made to define two scripts with the same name.B User Action: Reissue the command using a unique script name for the /SCRIPT qualifier. 3 EMPDFG" empty defragmentation item list? Explanation: The defragmentation list was empty for a script% definition call to DFG$DEFRAGMENT.B User Action: If the call to DFG$DEFRAGMENT was from HP suppliedC software, submit an SPR. Otherwise, correct the calling program. 3 EMPDFGSCH2 empty defragm@entation and scheduling item listsD Explanation: Both the scheduler list and the defragmentation list were empty.B User Action: If the call to DFG$DEFRAGMENT was from HP suppliedC software, submit an SPR. Otherwise, correct the calling program. 3 ENAFAIL1 failed to enable !ADB Explanation: This is a summary message indicating the specifiedB script was not enabled. Associated messages indicate the reason the enable operation failed.B User Action: Refer Ato associated messages to determine a course of action. 3 ENAFAIL2 no script was enabledC Explanation: This is a summary message indicating that no scriptB could be enabled (the user specified /ALL on the command line).B Associated messages indicate the reason the enable operation(s) failed.B User Action: Refer to associated messages to determine a course of action. 3 ENGLIMEXC8 process limit exceeded; increase process limit to run; ExplanatiBon: Starting another defragmentation process on< this node would exceed the user-defined maximum number of+ defragmentation processes for this node.B User Action: If the limit is acceptable, no action is required.8 Otherwise, change the limit using the SET subcommand. 3 ENGMAXTIM7 time limit exceeded; defragmentation process stoppedD Explanation: A defragmentation process was terminated because itsD time limit was exceeded. This is a limit imposed by the user withC the /TIME_LIMIT qualifier.. User Action: None or change the time limit. 3 ENQLOCKERR@ error while attempting to queue a process lock for device !ADB Explanation: The defragmentation process received an unexpectedB 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.B User Action: Refer to associateDd messages to determine a course of action. 3 EXTHDRERR1 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.B User Action: Refer to associated messages to determine a course of action. 3 FREEVMERR unable to free dynamic memoryB Explanation: The defragmentation process called the LIB$FREE_VM service incorrectly. User Action: ESubmit an SPR. 3 GETDVIERR/ error in getting device information from !ADC Explanation: The defragmentation process received failure statusC from the GETDVI system service. Associated messages provide more detail.B User Action: Refer to associated messages to determine a course of action. 3 GETVMERR$ unable to allocate dynamic memoryC Explanation: The defragmentation process received failure statusB from the LIB$GET_VM system service. Associated Fmessages provide more detail.B User Action: If the error is due to insufficient system dynamic> memory, system resources are insufficient to defragment the2 volume. If this is not the case, submit an SPR. 3 GLBSECMAPERR unable to map global sectionD Explanation: The defragmentation process could not map the system> wide global section created by the scheduler. This error isB very unlikely, but could be caused if the scheduler exits after? creating the globalG section and the defragmentation process,A but before the defragmentation process has a chance to map theB global section. It will also occur if the user tries to run the$ DFG$ENGINE_MAIN program directly. User Action: None. 3 IDXFILEFULL< INDEXF.SYS is completely full. You must delete some filesC Explanation: The index file or header is full. The program needs! at least one free file header.( User Action: Delete unneeded file(s). 3 IDXOPT> Your Hindex file is already optimal, no further work needed.B Explanation: The index file is already optimal. No further work is needed.0 User Action: None. The program has completed. 3 IEDBDATA. logically inconsistent data in relation !ADD Explanation: The database contains inconsistent data. The root ofD 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" datIabase contents, if possible. 3 IELOGNAM1) internal error; invalid supersede flag* Explanation: This is an internal error. User Action: Submit an SPR. 3 IESCHFILNODTYP0 relation !AD: illegal file or node type (!SL)4 Explanation: This is an internal scheduler error. User Action: Submit an SPR. 3 IESCHFUNC% illegal function code (!SL) in !AD4 Explanation: This is an internal scheduler error. User Action: Submit an SPR. 3 IESCHIMJPOSS internal logic error in !AD4 Explanation: This is an internal scheduler error. User Action: Submit an SPR. 3 IESE1> internal memory allocation calculation error; submit an SPR< Explanation: A consistency check found the global sectionB allocated was not large enough to hold the necessary data. This is an internal error. User Action: Submit an SPR. 3 IESRCINCONSIS* internal error; inconsistent source !ADC Explanation: This error occurs whKen the source for one module is5 not compatible with the source for another module. User Action: Submit an SPR. 3 IEVERNOD1& internal error while verifying node) Explanation: This is an internal error User Action: Submit an SPR. 3 IMEDALL all scripts have been !ADB Explanation: Success message for any immediate command (ENABLE,% DISABLE) where /ALL was specified. User Action: None. 3 IMEDSUCC script !AD has been !ADB ExplaLnation: Success message for any immediate command (ENABLE,2 DISABLE) where specific scripts were specified. User Action: None. 3 INTERNALERR% internal software error number !UL< Explanation: This is an internal error encountered in the defragmentation process code.A User Action: Submit an SPR. Include the software error number. 3 INTERR internal error: !AD* Explanation: This is an internal error.A User Action: Submit an SPR. Include the interMnal error string. 3 INTERR2 internal error: !AD !XL* Explanation: This is an internal error.? User Action: Submit an SPR. Include the error number and the3 associated string supplied in the error message. 3 INVDEV( device unsuitable for defragmentation? Explanation: Target device not suitable for defragmentation.D User Action: Ensure that the target device for defragmentation isB an ODS-2 volume (or stripe set or volume set). Further, it must5 bNe a local device available from the issuing node. 3 INVDEVCONTC 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 forB 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 dOevice specified is correct, but isB currently off line or, for some other reason, is unsuitable forA defragmentation, enter Y in response to the prompt. Otherwise,0 enter N or press Return to abort the command. 3 INVDEVNAM !AD is an invalid device name5 Explanation: The supplied device name was invalid., User Action: Specify a valid device name. 3 INVDFGLST$ invalid defragmentation item listA Explanation: The defragmentation list passed to DFG$DEFRAGMEN PT0 was invalid, because of one of the following:D o A call to DFG$DEFRAGMENT using a scheduler list that indicatesC the defragmentation list should be empty. For example, DFG$K_< SHOW_SCRIPT must not have a defragmentation item list.C o Something was wrong with the semantics of the defragmentation> item list, or a particular item descriptor was formatted improperly.B User Action: If the call to DFG$DEFRAGMENT was from HP suppliedC software, submit anQ SPR. Otherwise, correct the calling program. 3 INVDSLST3 invalid defragmentation and scheduler item listsD Explanation: Both the scheduler list and the defragmentation list) passed to DFG$DEFRAGMENT were invalid.B User Action: If the call to DFG$DEFRAGMENT was from HP suppliedC software, submit an SPR. Otherwise, correct the calling program. 3 INVFILNAM' !AD is an invalid file specificationA Explanation: An invalid file name was given for either the loRgA file or the options file. Associated messages describe why the file name is invalid.A User Action: Based on the associated messages, specify a valid file name. 3 INVITEMCOMB> invalid combination of DFG$K_INTERVAL and DFG$K_PREDECESSORA Explanation: The DFG$K_INTERVAL item descriptor is not allowed: with the DFG$K_PREDECESSOR item descriptor in a call to DFG$DEFRAGMENT.B User Action: If the call to DFG$DEFRAGMENT was from HP suppliedC software, sub Smit an SPR. Otherwise, correct the calling program. 3 INVITM* 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.B User Action: If the call to DFG$DEFRAGMENT was from HP suppliedC software, submit an SPR. Otherwise, correct the calling program.T 3 INVITMLST, 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 the7 lists contained item codes that were not compatible.B User Action: If the call to DFG$DEFRAGMENT was from HP suppliedC software, submit an SPR. Otherwise, correct the calling program. 3 INVITMUKN. an item list contained an unknown item code? Explanation: This message indicat Ues the dfg_list or sch_list@ parameter to DFG$DEFRAGMENT contained an item descriptor withB an unknown item code. It may also indicate a faulty item_list_2? returned from DFG$DEFRAGMENT as part of the SHOW subcommand.B User Action: If the call to DFG$DEFRAGMENT was from HP suppliedC software, submit an SPR. Otherwise, correct the calling program. 3 INVLMFLIC/ insufficient license units to run DEFRAGMENT? Explanation: The DFG software is not licensed to run on thisV node.( User Action: Install the DFG license. 3 INVLOGNAM! !AD is an invalid logical name= Explanation: A logical name translation failed because the= logical name was invalid. Associated messages provide more detail.B User Action: Refer to associated messages to determine a course of action. 3 INVSCHLST invalid scheduler item list? Explanation: The scheduler list passed to DFG$DEFRAGMENT was invalid.B User Action: If the call toW DFG$DEFRAGMENT was from HP suppliedC software, submit an SPR. Otherwise, correct the calling program. 3 INVSCRNAM !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. 3 INVSTARTCMD' script !AD already has a queue entry@ Explanation: The user entered a START subcommand for a script that was already started.X User Action: None. 3 INVSTRDSC invalid string descriptorC Explanation: An invalid string descriptor was pointed to from an& item list passed to DFG$DEFRAGMENT.B User Action: If the call to DFG$DEFRAGMENT was from HP suppliedC software, submit an SPR. Otherwise, correct the calling program. 3 INVSTRDSCNBR5 invalid string descriptor in item !SL of item listC Explanation: An invalid string descriptor was pointed to from anB item list passed to DFGY$DEFRAGMENT. The item number of the itemD descriptor containing the offending string descriptor is supplied by this message.B User Action: If the call to DFG$DEFRAGMENT was from HP suppliedC software, submit an SPR. Otherwise, correct the calling program. 3 L5NOLOG9 log file not specified, but defragmentation level is 5@ Explanation: Occurs if /LEVEL=5 is specified without the /LOGD qualifier. Defragmentation statistics are unavailable without theC /LOG qualifieZr; thus, it is required when /LEVEL=5 is specified.> User Action: Specify /LOG={logfile} when using the /LEVEL=5 qualifier. 3 LIMEXC !AD limit exceededA Explanation: A user-specified CPU_LIMIT, IO_LIMIT, or PROCESS_ LIMIT has been exceeded.; User Action: If the limit is correctly set, no action isA required. If the limit is incorrect, set a new limit using the SET subcommand. 3 LSTBADVOL3 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. 3 LVLOUTRNG3 !SL is an invalid defragmentation level; use 1-5B Explanation: The defragmentation level specified by the user on< the command line was not a number from 1 to 5, inclusive.6 User Action: Specify a valid defragmentation level. 3 MISSING_LOGIC\AL& the logical name !AD is not defined7 Explanation: A required logical name is not defined.= User Action: Define the indicated logical name and try the command again. 3 MISSNGVAL1 !AD qualifier requires a value in this contextB Explanation: A qualifier needed a value, such as a script name,$ but the user did not provide one., User Action: Provide the value requested. 3 MONBRKNDB; monitor unable to access database for script informationB E]xplanation: This error occurs if the monitor cannot access theA scheduling database. The most likely causes of this error are:D the logical name DFG$DEFRAGMENT is not defined; the database does not exist.6 User Action: If this message persists and the otherA defragmentation software is working (scheduler, DCL interface,- defragmentation processes), submit an SPR. 3 MONINVCOL, too few columns in display, please resize: Explanation: The display has too few column^s to display meaningful information.D User Action: If your terminal is a DECwindows DECterm, resize theC window as appropriate. If your terminal is a VT100-style device, submit an SPR. 3 MONINVROW) too few rows in display, please resizeB Explanation: The display has too few rows to display meaningful information.D User Action: If your terminal is a DECwindows DECterm, resize theC window as appropriate. If your terminal is a VT100-style device, submi_t an SPR. 3 MONNOVOL* !AD is not currently being defragmentedC Explanation: An attempt was made to monitor a script that is not executing.A User Action: Monitor only executing defragmentation processes. 3 MONRDERR0 error !SL while reading the monitor interface? Explanation: This error occurs if a process cannot read dataC using the interface that exists between the monitor process, theC scheduling process, and the defragmentation process. The proc`essC experiencing the error will continue, though not all data may be% available for the monitor display. User Action: None. 3 MONUNEXP unexpected error from !ADD 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.D User Action: Refer to the subsequent error message to determine a course of action. 3 a MONWRERR0 error !SL while writing the monitor interface@ Explanation: This error occurs if a process cannot write dataC using the interface that exists between the monitor process, theC scheduling process, and the defragmentation process. The processC experiencing the error will continue, though not all data may be% available for the monitor display. User Action: None. 3 MOVFILINFO1 Relative volume number !UL> Explanation: This is issued to give more binformation to the< maintainer about a movefile error (either MOVFILQIOERR or MOVFILSTSERR). User Action: Submit an SPR. 3 MOVFILQIOERR' QIO error on movefile for volume !AD? Explanation: This is an internal error; the movefile QIO was8 formatted incorrectly by the defragmentation process. User Action: Submit an SPR. 3 MOVFILSTSERR* status error on movefile for volume !AD@ Explanation: The movefile QIO returned an error status to theD defracgmentation process. Subsequent messages provide the specific error encountered.B User Action: Refer to subsequent messages to determine a course of action. 3 MULTSUCC" multiple successors not allowed= Explanation: The script named as predecessor already has a successor defined.8 User Action: Specify a different predecessor or none. 3 NODEIGNOR" the /NODE qualifier was ignoredC Explanation: The /NODE qualifier was specified with show script,Dd but no CPU, I/O, or process parameter was selected. Any node nameC is meaningless when applied to show script only. This message is informational. User Action: None. 3 NOINHER inherit script !AD not foundD Explanation: The script specified in the /INHERIT qualifier could( not be found in the SCRIPTS relation.C User Action: Reissue the command using a defined script name for the /INHERIT qualifier. 3 NOKILL3 failed attempt to stop a defragmeentation process: Explanation: An attempt (by the scheduler) to abort theC defragmentation process failed. Associated messages provide moreB detail. It could simply be that the defragmentation process has completed or is suspended.B User Action: Refer to associated messages to determine a course of action. 3 NOMEINTERFACE$ monitor interface not established@ Explanation: This error occurs if the defragmentation processB cannot establish the monitor interfac fe. In this case, the errorA appears in the defragmentation process log file. The error can@ also occur when executing the monitor function if the monitorA 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 haveD created the interface. If the error occurs in the defragmentation? process g or scheduler log files, determine a course of action; based on any associated messages. If the error is due toA insufficient ENQUE limit, increase the ENQUE limit of the userA process running monitor or the scheduler process, whichever is appropriate. 3 NONODE! !AD not found in configurationA 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 h SYSGEN parameter,? SCSNODE, and the logical, SYS$NODE are undefined on the nodeD where the scheduler is running. In the case of the scheduler, the3 node name reported in the message will be blank.> User Action: If the error occurs in the scheduler log file,B 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 existis on the local system. 3 NONOTIFYA mail notification of defragmentation process completion failed@ Explanation: An attempt to send mail to the mail distribution1 list specified in DFG$MAIL_ADDRESS has failed.D User Action: Verify that the logical DFG$MAIL_ADDRESS is defined.D Refer to associated messages to determine if additional action is necessary. 3 NOPRED# predecessor script !AD not foundB Explanation: The script specified in the /PREDECESSOR qjualifier. could not be found in the SCRIPTS relation.? User Action: Check spelling of the script name used with theD /PREDECESSOR qualifier. Use the name of a script that has alreadyA been defined (with the VOLUME subcommand) for the /PREDECESSOR qualifier. 3 NOPRIV< insufficient privileges; you need BYPASS, CMKRNL, DETACH,D EXQUOTA, NETMBX, SHARE, SYSGBL, SYSLCK, SYSPRV, TMPMBX, and WORLD; Explanation: The user has insufficient privileges to run DEFRAGMENkT.@ User Action: Set the BYPASS, CMKRNL, DETACH, EXQUOTA, NETMBX,B SHARE, SYSGBL, SYSLCK, SYSPRV, TMPMBX, and WORLD privileges and try the command again. 3 NOQENTRY no queue entry for script !ADA Explanation: A queue entry was not found for a script that wasC to be canceled, disabled, or enabled. (The database did not haveA a record that matched the user-supplied script name for one of these commands.): User Action: Check the spelling of the script namle. Use? only names that have previously been defined with the VOLUME subcommand. 3 NOSCHED/ scheduling operations may not have completed> Explanation: One or more scheduling operations may not haveD completed. This is a summary message. Associated messages provide more detail.B User Action: Refer to associated messages to determine a course of action. 3 NOSCRIPT1 script name !AD is not defined in the database@ Explanation: The named script ims not defined in the database.A User Action: Check the spelling of the script name and try the command again. 3 NOSCRNAM script name !AD not foundB Explanation: A script name specified by the user was not in the scheduling database.A User Action: Check the spelling of the script name and try the command again. 3 NOSHODAT: error retrieving show data from the scheduling database@ Explanation: There was an error retrieving show data from then scheduling database.B User Action: Refer to associated messages to determine a course of action. 3 NOTACCVIO) 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. 3 NOTBADDATA invalid data found in !ADB Explanation: This is an internal error. It occurs if one of theC internal user nootification routines is called with invalid data. User Action: Submit an SPR. 3 NOTCLOSERR, error closing temporary notification file= Explanation: An error occurred while closing the temporary notification file.B User Action: Refer to associated messages to determine a course of action. 3 NOTDISK5 this device is not a disk, recheck the device nameC Explanation: The device for which you requested defragmenting is not a disk.@ User Actipon: Check the device name and try the command again. 3 NOTEXEC script !AD not executingB Explanation: An attempt was made to abort a script that was not executing. User Action: None. 3 NOTEXTEND< error extending the scratch file needed for defragmenting INDEXF.SYS? Explanation: The temporary scratch file needed to defragmentD INDEXF.SYS could not be created. Its creation would have caused aB multi-header entry or there was not enough space on tqhe 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:A $ DEFRAGMENT SHOW disk:/VOLUME/LOCATION=[000000]INDEXF.SYS 3 NOTFILWRERR/ error writing to temporary notification file> Explanation: The notification message crould not be written.B User Action: Refer to associated messages to determine a course of action. 3 NOTLOCDEV !AD is not local to !AD> Explanation: The user has specified a target device that isB 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. 3 NOTODSDEV% !AD is not an ODS-2 mounted deviceC Explanation: The user has specified a devicse for defragmentation- that is not a mounted ODS-2 format volume./ User Action: Specify an ODS-2 format volume. 3 NOTRAN error translating !ADC Explanation: There was an error translating the supplied logical name.B User Action: Define the indicated logical using the /EXECUTIVE_ MODE and /SYSTEM qualifiers. 3 NOTSTOPPED3 defragmentation process, ID=!XL, was not stoppedD Explanation: An attempt to stop a defragmentation process failed.A Atssociated messages provide more detail. The most likely causeC of this message is that the defragmentation process is no longer running. User Action: None. 3 NOVOLUME1 no volume name specified for VOLUME subcommandC 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,9 submit an SPR. Otherwise, correct the calling program. 3 NULuLENGINE= a defragmentation process cannot be started for script !AD= Explanation: An attempt to start a defragmentation process3 failed. Associated messages provide more detail.B User Action: Refer to associated messages to determine a course of action. 3 OPENIN error opening !AD as inputA Explanation: The specified file could not be opened for input.+ Associated messages indicate the reason.B User Action: Refer to associated messages to determine va course of action. 3 OPENMAILERR/ cannot open mail file for /MAIL_NOTIFICATION? Explanation: The mail file cannot be opened by the schedulerC when attempting to notify users by way of the /MAIL_NOTIFICATION6 qualifier. Associated messages indicate the reason.B User Action: Refer to associated messages to determine a course of action. 3 OPENOUT error opening !AD as outputB Explanation: The specified file could not be opened for output.+ Assocwiated messages indicate the reason.B User Action: Refer to associated messages to determine a course of action. 3 OPTBADVOL9 invalid device specified on line !SL, options file !AD> Explanation: A volume was specified with a file name in theA 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. 3 OPTFILERR optxions file errorD Explanation: The options file contained errors. This is a summary4 message. Associated messages provide more detail.B User Action: Refer to associated messages to determine a course of action. 3 OPTHASFNF/ file not found on line !SL, options file !ADD Explanation: A file specified as /EXCLUDE, /FREQUENT, or /DORMANT% in the options file was not found.B User Action: No action is necessary. To eliminate this message,B however, you should ryemove the line in the options file that isD reported in this message. Since the file given on this line is no8 longer on the target device, this line has no effect. 3 OPTINVQUAL2 invalid qualifier on line !SL, options file !ADB Explanation: A classification for a file was given that was not) one of: /FREQUENT, /DORMANT, /EXCLUDE.C User Action: Check spelling and ensure that only classificationsC of /FREQUENT, /DORMANT, or /EXCLUDE are used for files listed in tzhe options file. 3 OPTMULCLA9 multiple classifications on line !SL, options file !ADC Explanation: A file was classified with multiple classifications9 (that is, file.ext/FREQ/DORM). This error prevents the. defragmentation process from being started.D User Action: Specify only one file classification per line in the options file. 3 OPTNOTCLA4 file not classified on line !SL, options file !AD; Explanation: A file was in the options file, but was not2{ 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. 3 OPTRMSERR* RMS error on line !SL, options file !ADC Explanation: An unanticipated error was returned from the $PARSE or $SEARCH RMS routines.@ User Action: Refer to the specified line in the options file.7 Also check associated messages for more information. 3 PARSEFAIL error par|sing !AD? Explanation: The RMS $PARSE service failed for the specified file.B User Action: Refer to associated messages to determine a course of action. 3 PRCOUTRNG; !SL is an invalid process limit; specify positive values/ Explanation: The process limit was negative.B User Action: Specify only positive values for the PROCESS_LIMIT+ keyword parameter to the SET subcommand. 3 PREDNOTUSRNAME= the predecessor for script !AD is not a user-provided } nameD 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,B they are never listed when the /COMMAND_LINE qualifier is used.B This warning message indicates the script whose predecessor was not listed.A 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 aC predecessor using the /SCRIPT qualifier. Then, modify the scriptA listed in this message so the /PREDECESSOR qualifier indicates the script name used. 3 PROCABORTED" defragmentation process abortedA Explanation: The defragmentation process has aborted. It couldC be that the total defragmentation time has been exceeded and theA scheduler has stopped the defragmentation software. Thus, this1 message does not necessarily indicate failure.B User Action: Refer to associated messages to determine a course of action. 3 PROCESS_START defragmentation process start@ Explanation: This message is generated by the defragmentation1 process after it has completed initialization. User Action: None. 3 PROCESS_STOP, defragmentation process normal completion@ Explanation: This message is generated by the defragmentation8 process after the process has successfully completed. User Action: None. 3 QUEDALL; !AD request for all scripts has been successfully queuedC Explanation: Any of the queued commands where /ALL was specified were successful. User Action: None 3 QUEDNONAM> !AD request for unnamed script has been successfully queued: Explanation: A defragmentation request was successfully4 processed; the user did not supply a script name. User Action: None 3 QUEDSUCC: !AD request for script !AD has been successfully queuedA Explanation: A defragmentation process was successfully queued( and had a user-specified script name. User Action: None 3 REMFAIL1) failed to remove !AD from the databaseB Explanation: This is a summary message indicating the specifiedB script was not removed. Associated messages indicate the reason the remove operation failed.B User Action: Refer to associated messages to determine a course of action. 3 REMFAIL2* no script was removed from the databaseC Explanation: This is a summary message indicating that no script= was removed from the scheduling database when the user had specified the /ALL qualifier.B User Action: Refer to associated messages to determine a course of action. 3 REMOVENOTDONE remove unsuccessful? Explanation: A REMOVE subcommand was unsuccessful. This is aB summary message. This message may or may not indicate an error.+ Associated messages provide more detail.B User Action: Refer to associated messages to determine a course of action. 3 REMOVSEEN( remove command for !AD already issuedD Explanation: A REMOVE subcommand had been issued for this script,B but it had not yet completed when another REMOVE subcommand for the same script was issued. User Action: None. 3 RESAREA5 Map pointer copy would extend into a reserved areaD Explanation: The copy of INDEXF.SYS map pointers would run into a reserved area. User Action: Submit an SPR. 3 RMSERR& RMS operation !AD failed (file !AD)3 Explanation: The specified RMS operation failed.B User Action: Refer to associated messages to determine a course of action. 3 SCHEDERR- scheduler cannot complete scheduling tasks= Explanation: This is a summary message indicating that the7 scheduler did not complete all its scheduling tasks.B User Action: Refer to associated messages to determine a course of action. 3 SCHEXIT# 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. 3 SCHSTART !AD started on !AD !%D@ Explanation: A scheduler started. This message appears at the$ beginning of every scheduler log. User Action: None. 3 SCRDIS! script !AD is already disabled@ Explanation: An attempt was made to disable a script that was already disabled. User Action: None. 3 SCRENA script !AD is already enabled? Explanation: An attempt was made to enable a script that was already enabled. User Action: None. 3 SEARCHLOOP, 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 directory5 file or by an alias that points to a deleted file.@ User Action: Investigate the directory structure of the disk. 3 SENDMAILERR mail notification failed> Explanation: This is a summary message that occurs when theB scheduler does not send the mail notification message requestedC by the user with /MAIL_NOTIFICATION. Associated messages provide more detail.B User Action: Refer to associated messages to determine a course of action. 3 SETFAIL) failed to set any specified parametersB Explanation: DFG$DEFRAGMENT returned a failure status for a SET command.B User Action: Refer to associated messages to determine a course of action. 3 SETNODFAIL' a SET subcommand failed for node !ADD Explanation: A DEFRAGMENT SET CPU, I/O, or PROCESS command failed for the indicated node.B User Action: Refer to associated messages to determine a course of action. 3 SETSUCC( specified parameters successfully setB Explanation: The database was successfully updated with the new1 CPU_LIMIT, IO_LIMIT, and PROCESS_LIMIT values. User Action: None. 3 SHDWSETERRB 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.B User Action: Defragment the entire shadow set by specifying the; shadow set name (DUSXXX) on the DEFRAGMENT command line. 3 SHODATMIS !AD missing from show data* Explanation: This is an internal error. User Action: Submit an SPR. 3 SHOSCRFAIL a show script command failedD Explanation: A SHOW SCRIPT command did not complete successfully.+ Associated messages provide more detail.B User Action: Refer to associated messages to determine a course of action. 3 STAFAIL failed to start !AD> Explanation: DFG$DEFRAGMENT returned a failure status for a@ START subcommand. This is a summary message and probably doesC not indicate any real error. Most likely, the script was already4 started. Associated messages provide more detail.B User Action: Refer to associated messages to determine a course of action. 3 STARTNOTDONE start command unsuccessful> Explanation: A START subcommand was unsuccessful. This is aB summary message. This message may or may not indicate an error.+ Associated messages provide more detail.B User Action: Refer to associated messages to determine a course of action. 3 STARTSEEN' start command for !AD already issuedB Explanation: A START subcommand had been issued for this scriptA but it had not yet completed when another START subcommand for the same script was issued. User Action: None. 3 SYSSRVERR$ call to system service !AD failed- Explanation: A system service call failed.B User Action: Refer to associated messages to determine a course of action. 3 TIMEINV# 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. 3 UNRECOVERR unrecoverable error: Explanation: The defragmentation process encountered an7 unrecoverable error; no further processing occurred.B User Action: Refer to associated messages to determine a course of action. 3 USERABORT command aborted by userC Explanation: The user decided not to continue after encountering5 the INVDEVCONT message. This is a summary message. User Action: None. 3 USER_ERR user errorC Explanation: The user made an error. Associated messages provide more detail.B User Action: Refer to associated messages to determine a course of action. 3 USRKILLENG: an ABORT command terminated the defragmentation process9 Explanation: Because of a user-issued ABORT command, a& defragmentation process terminated. User Action: None. 3 VIRMEMERR@ device is a member of a constituent set; specify the set nameD Explanation: The user attempted to defragment a virtual member of* a disk set, such as a stripeset member.D User Action: Defragment the entire set by specifying the set name" on the DEFRAGMENT command line. 3 VOLFAIL1= volume command failed; script !AD was not entered into the database= Explanation: The specified script was not entered into theA database. Some portion of command validation failed. The exact: nature of the error is provided in associated messages.B User Action: Refer to associated messages to determine a course of action. 3 VOLFAIL2A volume command failed; unnamed script was not entered into the databaseC 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.B User Action: Refer to associated messages to determine a course of action. 3 VOLSETERRA 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.B User Action: Defragment the entire volume set by specifying the2 volume set name on the DEFRAGMENT command line. 3 VOLUMELOCKERR# volume lock error for device !AD@ Explanation: Error trying to allocation-lock the volume. ThisA 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.B User Action: Refer to associated messages to determine a course of action. 3 VOLUMENOTDONE volume command unsuccessful? Explanation: A VOLUME subcommand was unsuccessful. This is aB summary message. This message may or may not indicate an error.+ Associated messages provide more detail.B User Action: Refer to associated messages to determine a course of action. 3 VOLUNLOCKERR% volume unlock error for device !ADB Explanation: The target device could not be allocation-unlocked" by the defragmentation process.B User Action: Refer to associated messages to determine a course of action. 3 VPAEND3 !SL hotfile records added to the /FREQUENT list.A Explanation: This message indicates the VPA database query hasC completed. It also indicates the total number of hotfile records0 found that were related to the target device. User Action: None. wwf绬 1 File_MenuD The File menu serves only one purpose. It allows you to exit thisB instance of Disk File Optimizer application. To do so, click onB the File menu for the Exit option. Click on 'Exit' to close and exit this application. wwf绬1 Optimize_Menu% The Optimize menu has options for:C o Optimizing specific targets - a volume, file or an index file# o aborting the optimize processA Note that while you use the 'Optimize' option, you will create> a script to optimize the 'target'. This step is the same as- creating a script from the 'Scripts' menu.> Use the following procedure to optimize a volume or a file.# 1. Pull down the Optimize menu .- 2. Select the target you wish to optimize: o a volume o selected files> o a volume index file The 'Create Script to optimize a Volume' appears as inA 3. To specify a script name type the script name in the script@ field box. I f you don't enter a script name, this instanceB of the Disk File Optimizer application will assign a defaultB script name for you that resembles DFG$SCRIPTxxx, where x isA any hexidecimal character between 0 through F. This default> script will be deleted upon successful completion of the defragmentation process.A o Click on 'Reset' to restore the content of all fields to their defaults.B o Click on 'Inherit' to browse a script list and sele ct the4 script you wish to inherit properties from.< 4. Choose a Volume, Selected Files, or Volume Index File.A o If you choose the Volume option, enter a specific VolumeC name on the Volume insert line or click on the volume list8 button to get a list of volumes to select from.B o If you choose the Selected Files option, enter a specificD file name on the file insert line or click on the file list3 button for a list of files to sel ect from.< o If you choose the Volume Index File option, enter a? specific disk name or names on the Disk insert line orD click on the disk list button for a list of disks to select from.A 5. Fill out the rest of the Define dialog box according to the@ field description information in Define Dialog Box Fields.> 6. Click on the Restrict button in this dialog box and fill? in the information fields according to the information in( Restrict Special Files Dialog Box.> 7. Click on the Schedule button in this dialog box and fill@ in the schedule script information fields according to the0 procedure in Schedule a Script Dialog Box.. 8. To complete the script creation process:B o click on 'OK' to complete the script and close the dialog box.A o click on 'Cancel' to close this dialog box and return to the previous screen.A o click on 'Apply' to save the script and kee p the present dialog box open. wwf绬1 Script_Menu! The Script menu allows you to: o create o modify o remove o show o schedule and o abort scripts for files or volumes. 2 Create_ScriptsA Use the following procedure to create a script for a volume or file. 1. Pull down the Script menu.B 2. Select the create script option and designate the target youA wish to create a script for: a Volume, Selected Files, or a Volume Index File.) NOTE= Note that you must define a script using the 'Script; Define' buttons in the respective dialog box - seeA 3. To specify a script name type the script name in the script@ field box. If you don't enter a script name, this instanceB of the Disk File Optimizer application will assign a defaultB script name for you that resembles DFG$SCRIPTxxx, where x isA any hexidecimal character between 0 through F. This default> script will be deleted upon successful completion of the defragmentation process.A o Click on 'Reset' to restore the content of all fields to their defaults.B o Click on 'Inherit' to browse a script list and select the4 script you wish to inherit properties from.< 4. Choose a Volume, Selected Files, or Volume Index File.A o If you choose the Volume option, enter a specif ic VolumeC name on the Volume insert line or click on the volume list8 button to get a list of volumes to select from.B o If you choose the Selected Files option, enter a specificD file name on the file insert line or click on the file list3 button for a list of files to select from.< o If you choose the Volume Index File option, enter a? specific disk name or names on the Disk insert line orD click on the disk list button for a list of disks to select from.A 5. Fill out the rest of the Define dialog box according to the@ field description information in Define Dialog Box Fields.> 6. Click on the Restrict button in this dialog box and fill? in the information fields according to the information in( Restrict Special Files Dialog Box.> 7. Click on the Schedule button in this dialog box and fill@ in the schedule script information fields according to the0 procedure in Schedule a Script Dialog Box.. 8. To complete the script creation process:B o click on 'OK' to complete the script and close the dialog box.A o click on 'Cancel' to close this dialog box and return to the previous screen.A o click on 'Apply' to save the script and keep the present dialog box open. 3 Define_a_ScriptC Before you can create a script or optimize a volume or file, you@ have to define a script using one of the Script Define dialog: boxes for Volume, Selected Files, or Volume Index File.9 In the Script Define dialog box for a volume, you can: o Select a volume name.. o Select to enable or disable write check.8 o Select the relative volume number of a volume set.B o Select whether to defragment files and what kind of files to defragment.5 o Select whether to consolidate freespace or not.4 o Select whether or not to do a volume analysis.@ o Select whether to notify you by log file, console message,$ mail message, or by all three.7 o Select whether to report brief or full log files.A o Select whether to inherit the properties of another script.A Refer to the Define Dialog Box Fields for a description of the information fields.D In the Script Define dialog box for a volume index file, you can: o Select a disk.C o Select whether to notify you by log file, console message, or$ mail message, or by all three.7 o Select whether to report brief or full log files.A o Select whether to inherit the properties of another script.# Table 2 Define Dialog Box Fields Field Description& Script A name for the script. Name> If you give a duplicate script-name, Disk File@ Optimizer issues the duplicate script name errorB message and does not enter the new script into the8 database-no defragmentation takes place.B A script name can be up to 64 characters in length@ and can contain any of the following characters:- o Any alphanumeric character# o Underscore ( _ ) o Hyphen ( - )$ o Dollar sign ( $ )A Observe the following rules when naming a script:A o Use any combination of uppercase and lowercase letters.C o Do not begin script names using the dollar sign,B however, you can include the dollar sign withinD the script name. (The dollar sign is reserved for& special use by HP.)A o Do not end a script name with a hyphen because@ the hyphen is the DCL continuation character.8 o If you don't enter a script name, the@ defragmentation process will assign a default; script name, DFG$SCRIPTxxx, where x is a> hexidecimal character between 0 and F. This; default script name will be deleted upon? successful completion of the defragmentation process.A Volume Defragments the volume named in the volume field.@ This has the same effect as using the DEFRAGMENT# VOLUME DCL command.@ Selected Defragments the file or files na med in the files< Files field. This has the same effect as using the, DEFRAGMENT FILE DCL command.C Volume Defragments the INDEXF.SYS of the disk named in theA Index Files disk field. This has the same effect as using the6 DEFRAGMENT OFFLINE_VOLUME DCL command.D Volume... The Volume... button only appears when the Volume orB Volume Index File buttons are depressed. Enter theC volume name or use the Volum e... button to bring up+ a list of volumes or disks.B Files... The Files... button only appears when the SelectedB Files button is depressed. Push the File... button1 file to bring up a list of files.B Write Check The Write Check option requests that a read-after-? write check be performed on all defragmented orB placed files. This qualifier significantly extends@ the execution time of a defragmentation process.@ This has the same effect as the /WRITE_CHECK DCL qualifier.B Relative Allows you to select the relative volume number ofC Volume a volume set. This has the same effect as the /RVN= Number DCL qualifier.; Operations You may elect to defragment specific files,? consolidate disk space, or do an analysis checkB only. File defragmentation and space consolidation% can be done together.B Defragment Files: Allows you to select which filesB to defragment. Use the three-position sliding bar:= o LEFT - Files that are not 100% contiguous.C o MIDDLE - Files whose extent cannot be completely mapped.C o RIGHT - Files with retrieval points in more than# one file header.B Consolidated Freespace: Consolidate the free space  on the volume.@ Volume analysis only: Requests a volume analysis@ only, no defragmentation occurs. The results are* available in the log file.> Log File The Log File option causes the defragmentationA process to create a file containing a list of all? its operations. The information in the log fileD varies with the presence of the Full or Brief option selectio ns:@ o The Brief option lists only the statistics ofC each phase, such as number of files analyzed and0 number of files defragmented.> o The Full option lists all files analyzed by@ the defragmentation process and reports theirD disposition during each phase of defragmentation.A This has the same effect as the /LOG=log_file and. /FULL or /BRIEF DCL qual ifier.> Console The console message option requests that brief9 Message status and termination messages regarding@ defragmentation processes be sent to OPCOM. ThisB has the same effect as the /OPCOM_NOTIFICATION DCL qualifier.> Mail The Mail option requests that brief status and> Message termination messages regarding defragmentation< processes be mailed to the distribution list? provided in the DFG$MAIL_ADDRESS file. This has; the same effect as the /MAIL DCL qualifier. $3 Restrict_Special_Files_Dialog_BoxA The Restrict Special Files dialog box allows you to include or@ exclude any special files during the defragmentation process.> Restrict File of Dialog Box Fields decribes the information fields.! You can exclude files such as: o Files placed by the User o RMS Indexed Files o Excluded Files; You can also exclude the following types of Place Files:# o Files in the hotfile database o Dormant files o Frequent files- Table 3 Restrict File of Dialog Box Fields Field Description2 Script Identifies the name of the script. Name:C Files Select this button if you wish to ignore explicitly= Placed placed files. This has the same effect at the/ by User /IGNORE=(PLACED) DCL qualifier.D RMS Indexed Select this button i f you wish to ignore RMS indexed Files files.> Excluded The Exclude Files option specifies files to be> Files excluded from processing. You may enter a fileB name in the file field or use the file list button? to bring up a list of files to select from. The> defragmentation process ignores files matchingB the listed file specifications. Any file indicatedA in the EXCLUDE list and in either th e FREQUENT or: DORMANT lists is excluded from processing.? The file-spec field allows wildcard characters.? You can specify wildcard characters in place ofA the directory name, file name, file type, or file? version number field. The default file-spec forA all wildcard operations is DISK:[000000...]*.*;*.C Specifying *.TMP;* selects all *.TMP;* files on the entire v olume.A The defragmentation process always excludes files? marked NOMOVE, open files, files excluded in anA options file, and files excluded using the Ignore option.@ Files in This option causes the defragmenter to query theC Hotfile appropriate hotfile database and append the list ofB Database hotfiles to the defragmenter's frequent file list.> Dormant The Dormant Files option indicates files to be< Files considered dormant when final file placement? decisions are made. You may enter the file nameA or use the file list button to bring up a list ofD files to chose from. Dormant files are placed on theC volume to allow placing other files in optimum diskC locations. In general, they are placed further awayB from the ODS-2 data structures than Frequent files7 and files no t classified in any manner.> If a file is indicated in both the DORMANT and9 FREQUENT lists, it is considered dormant.> If a file is indicated in both the EXCLUDE and. DORMANT lists, it is excluded.. NOTEA The amount of free space on the volume, the? number of files currently being accessed,A and other factors influence file placement.@ The Disk File Optimizer does not guarantee? file placement, but makes every effort to/ place files as described.? The file-spec field allows wildcard characters.? You can specify wildcard characters in place ofA the directory name, file name, file type, or file? version number field. The default file-spec forA all wildcard operation s is DISK:[000000...]*.*;*.C Specifying *.TMP;* selects all *.TMP;* files on the entire volume.? Frequent The Frequent Files option indicates files to be> Files considered frequently accessed when final file? placement decisions are made. You may enter theA file name or use the file list button to bring upA a list of files to chose from. Frequent files are0 placed to optimize access speed.? If a file is indicated in both the FREQUENT and8 DORMANT lists, it is considered dormant.? If a file is indicated in both the FREQUENT and. EXCLUDE lists, it is excluded.. NOTEA The amount of free space on the volume, the? number of files currently being accessed,A and other factors influence file placement.@ The Disk File Optimizer does not guarantee? file placement, but makes every effort to/ place files as described.? The file-spec field allows wildcard characters.? You can specify wildcard characters in place ofA the directory name, file name, file type, or file? version number field. The default file-spec forA all wildcard operations is DISK:[000000. ..]*.*;*.C Specifying *.TMP;* selects all *.TMP;* files on the entire volume.D In Options The Options File option provides an alternate methodD File for associating files with the Dormant File, ExcludeA File, or Frequent File options. You may enter theA file name or use the file list button to bring upC a list of files to chose from. If the list of filesB for any of these options is long, you can create a3 separate file for this information.B Each record of the options file consists of a file7 name followed by one of these keywords:/ o /EXCLUDE-File to be excluded= o /FREQUENT-File to be considered frequently accessed9 o /DORMANT-File to be considered dormant> The following example shows the contents of an< options file called MYOPTFILE.OPT. This file= specifies that all files on the target device> called FILE1.EXE are frequent files, all files> in the [ARCHIVE] directory are to be excluded,A and all files in the [OLDSTUFF] directory and its+ subdirectories are dormant.& FILE1.EXE/FREQUENT* [ARCHIVE]*.*;*/EXCLUDE. [OLDSTUFF...]*.*;*/DORMANT 3 Schedule_a_Script_Dialog_Box< The Schedule Definition dialog box allows you choose many; different script or defragmentation schedule parameters.A The Schedule Definition Dialog Box Fields describes the dialog box information fields.( The parameters in the dialog box are: o Start after this time o Wait for start time o Don't reschedule! o Reschedule at this interval o Reschedule continuously! o Reschedule to follow script o Schedule on nodes: o Time limit? o Execute a prologue command file before running the script? o Execute an epilogue command file after running the script0 Table 4 Schedule Definition Dialog Box Fields Field DescriptionB Script Name Identifies the name of the script to be scheduled.B Start After Starts execution of the script after the specifiedC This Time time. This has the same effect as the DCL qualifier /AFTER=.? Wait for Keeps the spec ified script from executing untilD Start started by the Schedule Scripts option in the ScriptB Command pulldown menu. This has the same effect as the DCL# qualifier /NOAFTER.D Priority This is the priority that the OpenVMS scheduler uses@ for the defragment volume operation. The defaultA priority is set at 4. The minimum priority is setC at 3. This has the same effect as the DCL qualifier1 /PRIORITY=(DEFAULT=n, MINIMUM=n).< Time Limit Specifies the delta time allowed for a givenC defragmentation operation. This has the same effect2 as the DCL qualifier /TIME_LIMIT=.A Don't The DFO schedule will not reschedule this script. RescheduleA At This Specifies the delta time of the interval at which> Interval the script will be executed. This has the same7 effect as the DCL qualifier /INTERVAL=.; Con tinuously Causes the script to run continuously. When= selected, the defragmentation script used for? the process must be aborted or canceled when noB longer needed. This has the same effect as the DCL' qualifier /CONTINOUSLY.A To Follow Names the script that will run before the current@ Script: script is executed. The script must exist in theD database. Enter a script name or click on the scriptC list button for the list of scripts to choose from.= This has the same effect as the DCL qualifier /PREDECESSOR=.> Schedule on Limits the defragmentation to only those nodesD Nodes: listed. Enter a node, or nodes, or click on the nodeD list button for a list of nodes to choose from. This@ has the same effect as the DCL qualifier /NODE=.A Epilogue The Epilogue File option identifies a DCL command= File file that DFO executes upon completion of theC defragmentation operation. This has the same effect0 as the /EPILOGUE= DCL qualifier.9 Prologue The Prologue File option identifies a DCL> File command file that DFO executes just before theC defragmentation operation starts. This has the same7 effect as the /PROLOGUE= DCL qualifier. 2 Modify_a_Script9 This section describes how to modify existing scripts.2 Use the following procedure to modify a script: 1. Pull down the Script menu.A 2. Select the Modify Script option and a Script List selection box appears.9 3. Select a script from the script list selection box.> 4. Select either the Apply or the OK button to bring up the Modify Script dialog box.B 5. From this point on, follow the same procedure as if you wereA creating a script. These procedures are found in the DefineA a Script, Restrict Special Files Dialog Box, and Schedule a Script Dialog Box. 2 Remove_a_Script> This option allows you to remove scripts from the database.2 Use the following procedure to remove a script:C 1. Select the Remove Script option of the Script pull-down menu.. 2. Select the scripts from the Script List.@ Point to and click on the script names in the list to mark# that you wish to remove them.( 3. To complete the remove, click on :@  o OK to remove the selected script(s) and exit the Remove Script option.D o Cancel to leave the Remove Script option without taking any action.A o Apply to remove the selected script(s) and remain in the Remove Script option. 2 Show_a_ScriptA The Show dialog box provides three ways of sorting the scripts you would like to show:A o Scripts that apply to specific nodes, either exclusively or shared by other nodes1 o Scripts that apply to specific disk volumes! o All scripts in the databaseC You also have the option of creating an output file for selected scripts./ Use the following procedure to show scripts:8 1. Select the Show Scripts option of the Script menu.A 2. Click twice on a script name in the 'Scripts' box to select it.A 3. Choose the kind of output you wish for the selected script:? IF you keep the Output File option, enter the name of the% output file you want to create.B IF you do not select the output file option, the script file. is visible only while using this option.@ 4. If you want to show scripts sorted by volume, proceed with: Step 4, otherwise, continue to show scripts by node.> To 'limit' the scripts display to those belonging to the@ selected node leave the 'Limited' option selected (this is the default).D IF you select the Limited option, you limit the candidate li st? of scripts to those that apply only to the selected node.B IF you do not wish to use the 'Limited' option, click on theC option box to deselect it. The candidate list of scripts will7 then include every script that runs on all nodes.D Select a script in the Node box, and note that the script name* gets highlighted in the Scripts box. Proceed with Step 6.D 5. To show the scripts that apply to a volume, select the volume.@ Scripts that app ly to the volume are listed in the Scripts box.C Select a script that applies to a Volume, and note the script/ name gets highlighted in the Scripts box.= 6. To see a script, double click on the script name in theB Scripts field or press Return, or click on the Apply button.D The contents of the script appear in the area below the script name.D This feature allows you to see more than one script at a time.4 To see additional scripts, select their names.6 7. Finish the show script operation by clicking on:? o OK to produce the output file named in the Output File fieldA o Apply to leave the Show Script dialog box and optionally? produce the output file named in the Output File field: o Cancel to quit and not produce any further output 2 Schedule_a_ScriptC This section describes how to schedule a defragmentation script.D Use the following procedure to schedule scripts and manage script schedules:' 1. Select the Script pull-down menu.D 2. Select the Schedule Script option of the Script pull-down menu for the script list box.A 3. Select all the scripts you want for scheduling actions from= the Script list and click on either the OK or the ApplyA button. This will bring up the Schedule Scripts dialog box.> 4. Take any of the actions on the script outlined in Script Scheduling Actions./ 5. To finish the scheduling action click on:B o OK button to apply the modifications and leave the dialog box.B o Cancel button to quit and not take any scheduling actions on the named script.C o Apply button to apply the scheduling options selected. YouB may take action on another script by entering the name of- the script in the Script Name field.$ Table 5 Script Scheduling Actions Option Description3 Script Name of script for scheduling action. NameC Cancel Cancels the next scheduled execution of the specified; script. Normal scheduling resumes thereafter.= Disable This option disables the script from execution.D Enable This option enables a previously disabled script. Once4 enabled, the script operates normally.8 Start Starts execution of the script identified.? Start Starts execution of the script when the specifiedD /After time is reached. Enter the time in the field below the option. 2 Abort_a_Script@ Use this option to stop a script that is currently executing.A Use the following procedure to abort an active defragmentation script:' 1. Select the Script pull-down menu. 2. Select the Abort option.> 3. Select the script to abort from the Script List box. UseA caution because a double click on a script entry will abort that script.C Point to any one or more of the scripts listed, clicking once$ on each one you want to abort.+ 4. Finish the abort action by selecting:C o OK to abort the selected scripts and exit the Abort Script optionD o Apply to abort the selected scripts and remain in the Abort Script optionC o Cancel to leave the Abort Script option without taking any action ww绬1 Monitor_a_Script_or_Volume? The Monitor menu allows you to se lect a script or volume for? monitoring the defragmentation process. You can view how theD space is allocated on the full volume or on a partial volume in a sliding window.? When selecting the Monitor option, DFO displays two windows:A o A process statistics window showing process information forC the defragmentation process. Refer to Defragmentation Process$ Statistics Window Description.D o A monitor map window showing free space and allocated space on  the volume.D This procedure describes how to monitor allocated space on a disk volume.( 1. Select the Monitor pull-down menu.= 2. Select the means by which you want to monitor allocated@ space. Select the Script, Volume, or Full Volume option of! the Monitor pull-down menu.? o IF you want to identify the volume by a script, select@ the Script option, then select the script name from the> Script List. If you choose to monitor the volume by aA script, a Defragmentation Process Statistic Window and aB Defragmentation Full Volume Map Window will appear. ReferB to Defragmentation Process Statistics Window Description.? o IF you want to identify the volume by name, select theB Volume or Full Volume option, then select the volume name from the Volume List.> The volume options allows you to view different partsA of the entire volume map, use the arrows and scroll b arsD around the map on the defragmentation volume map window. IfD you choose to monitor the Volume, a Defragmentation ProcessB Statistic Window and a Defragmentation Partial Volume Map@ Window will appear. Refer to Defragmentation Volume Map Window Description.@ To view the full volume, select the Full Volume option,= then select the volume name from the Volume List. IfA you choose to monitor the Full Volume, a Defragmentatio nC Process Statistic Window and a Defragmentation Full VolumeA Map Window will appear. Refer to Defragmentation Process' Statistics Window Description.A 3. To view more detailed information about the allocated spaceA shown on the Defragmentation Volume Map, press mouse button@ 1 and drag the cursor over the area of the map you want toC examine. A pop-up window identifies the files taking space on that area of the volume. ,2 Defragmentation_Process_Statistics_WindowB The Defragmentation Process Statistics Window shows the process; information and statistics on how files and space on the? volume are allocated during defragmentation. DefragmentationA Process Statistics Window Description describes the date field information.@ Table 6 Defragmentation Process Statistics Window Description% Field Description@ Process Id: The defragmentation process ID number.; Process: The defragmentation process name.4 Date: The current date and time.A Script Name: The name of the script being monitored.? (The field applies to the Defrag PLUS( variant only.)? Operating On: The node on which the defragmentation/ process is operating.D Current Status: The status of the defragmentation process.D Phase: The current defragmentation process phase.A Elapsed Time: The elapsed time since the start of the2 defragmentation process.@ Buffered I/O The buffered I/O count and rate of the2 Count: defragmentation process. and Rate:> Direct I/O The direct I/O count and rate of the2 Count: defragmentation process. and Rate:A CPU Utilization The CPU utilization (time and usage) of6 Time: the defragmentation process. and Usage:> Page Fault The page fault count and rate of the2 Count: defragmentation process. and Rate:4 Files Evaluated: Number of files evaluated.2 Dormant Count: Number of dormant files.7 Candidate Count: Number of candidate files for* defragmentation.3 Exclude Count: Number of excluded files.1 Placed Files:  Number of placed files.3 Frequent Count: Number of frequent files.2 Indexed Files: Number of indexed files.> Files Partly Number of files partly defragmented. Defragmented:9 Dormant Files Placed: Number of dormant files placed.7 Files Defragmented: Number of files defragmented.: Frequent Files Number of frequent files placed. Placed:4 Files Processed: Number of files processed.C Free Space Extent  Number of extents to be consolidated into% Count: free space.C Free Space Extent Number of extents left to be consolidated* Countdown: into free space.7 Current File: Current file being evaluated. 2 Full_Volume_Window; The defragmentation full volume map window allows you to> see how the storage space and free space on the full volume? are allocated. Defragmentation Volume Map Window Description6 describes the window contents and how it functions.8 Table 7 Defragmentation Volume Map Window Description Field Description@ Start LBN The starting LBN at the upper left corner of the of Window viewport.A Phase The current phase of the defragmentation process.B Volume The name of the volume that is being defragmented.> Allocated Shows the color of allocated space on the disk Space volume.A Free Space Shows the color of free space on t he disk volume.D Mix of Shows the color of space that is partially allocated> Allocated and free space. This entry is only on the full and Free volume map. Space> File The file locator button on the Full or PartialC Locator Volume Map windows is normally selected by default,D resulting in the file locator pop-up menu appearing.C If you deselect the file locator button, the pop-upA menu will go away. T he File Locator pop-up window: displays the following list of file types: Directories Dormant Exclude Frequent GeneralB Select the General file category whenever you wantB to enter a specific file. By selecting the GeneralB category and then pressing the OK button, you willB get a General File Locator pop-up window where youD can enter the specific file name you want to locate.C Push the OK button to highlight the space allocated to that file.? End LBN of The ending LBN at the lower right corner of the Window viewport.= Free Blocks The number of free blocks on the disk volume.C Blocks/Grid The number of blocks in each grid on the view port.? Current The current file the defragmentation process isA File working on. This entry is only on the full volume map. 2 Partial_Volume_WindowA The partial volume map window provides a closeup detailed view@ of how the storage space is allocated on a smaller segment ofB the whole volume. Defragmentation Volume Map Window Description6 describes the window contents and how it functions.> When a Defragmentation Full or Partial Volume Map Window isA displayed on the screen, the File Type color bar at the bottomC of the dialog helps you identify the different file types on the volume map.@ The file type color bar shows the different file types on the= volume map in different colors if you have used these file@ categories in the defragmentation process. The following list: shows the color categories for the various files types. Directories GREEN Dormant Files YELLOW Exclude Files ORANGE Frequent Files BLUE General Files BLACK ww 绬 "1 Report_on_the_State_of_a_Volume@ The report menu allows you to review the current state of theB volumes to determine if defragmentation is needed. Click on theA Report menu for the two options it supports. You can opt for a8 graphic or a text report of the state of the volumes. 2 Graphics_Format< Use the following procedure for a graphics display of the selected volume(s).: 1. Click on the Graph... suboption of the Report-VolumeD Fragmentation menu. The Report - Select Volume dialog appears.A 2. Note that the first entry in the list is marked selected byA default. You can select any other volume for the respectiveD report. To select another volume, move mouse pointer to it and click. 3. Click on OK.D A graphical report of the state of the selected volume(s) appears= in the dialog. Click on Cancel to close this image dialog.  AThis dialog is nothing but a color coded window of how the volume>is shared by its files and directories. The first line in thisAdialog shows the Start LBN and Volume id - both of which are self explanatory.) The following may require explanation:B o The multicolored grid below the first line is actually a map of the volume's contents.> o Three gray levels mark different extents. Darkest gray -A allocated space, Lightest gray - free space and medium gray( - mix of allocated and free space.C o Blocks/grid, End LBN of Window and F ree Block, are again self explanatory.7 o The colored boxes that follow serve as the key toA understanding the volume-map. The colors green, cyan, blue,B magenta and red represent directories, indexed files, placed6 files, nomove files and open files respectively.@ o Click on a directory (green) or an open file (red) for the= Volume Map File Information dialog see - It has details@ concerning the selected entity with respect to its volume.' o Click on OK to close that dialog.& NOTE< Click on Apply in the Graphic - Full volume Map dialog> to find out if the selected volume is being defragmented currently. 2 Text_FormatA Use the following procedure for a text display of the selected volume(s).9 1. Click on the Text... suboption of the Report-Volume@ Fragmentation menu. for the Report - Select Volume dialog.= Use the following procedure to show volume information:* 1. Select the Report pull-down menu.? 2. Click on the Volume fragmentation option of the Report= pull-down menu for the report type list - Graph/Text? report. Click on 'Text' to select it. You will see the) 'Report - Select Volume' dialog.A 3. Select a volume from the list in the Show Volume options dialog box.B 4. Select any of the options for showing volume information.B Report Volume Option and Fiel d Descriptions describes the options.B o IF you keep the Statistics option(default), and double? click on the volume or click on 'OK' you will see a= scrollable page of a Fragmentation Report showing< fragmentation index, Freespace Summary, and FileA Fragmentation Summary, plus more information that you can scroll down.A o IF you select the Histogram option, you will see thatC portion of the Fragmentation Report that shows the File@ Fragmentation Histogram for the number of files with? a given number of extents and the Volume Free Space> Histogram which shows the free space size in LBNs.> 5. Finish the Report Volume Defragmentation operation by selecting:B o OK to show the volume report and optionally create the? output file you named in the Output File field. The" dialog box disappears.A  o Apply to show the volume report and optionally createC the output file you named in the Output File field. The dialog box remains.. o Cancel to leave the Report option.6 Table 8 Report Volume Option and Field Descriptions Field DescriptionD Free List The Free List option is used to show the fragmentationD state of the volume. It lists the location and size of7 all the free space extents on the volume. D Histogram The Histogram option is used to show the fragmentationA state of a volume. It generates two histograms. The@ first plots the number of files against the number@ of extents per file and provides information aboutB how many files are fragmented and how badly they areB fragmented. The second histogram plots the number ofB free space extents (holes) against the size of theseC free space exten ts. It provides information about howA many free space extents are on the volume and their sizes.> Statistics The Statistics option is used to show the volume? fragmentation state. It provides a summary of the? file and free space fragmentation for the volume.D File List The File List option is used to show the fragmentationA state of a volume. It lists all files on the volumeC that have min_extents or more extents (fragments). ByA default, the number of file window mapping pointersD set for the volume (INITIALIZE {volume}/WINDOW=n) plusB one is used. This value lists all files that require9 at least one window turn to completely map.C Use the field to specify the files for which you want) to show the window mapping.? Location The Location option shows the extents (fragments)> associated with all files specified in the fieldA next to this option. If no files are specified, theA Location option appends location information to allD files listed with File List option. The supplied file-C spec may contain wildcards in place of the directory,6 file name, extension, or version fields.? Output The Output File option is used to show the volumeA File fragmentation state or to show information from theD scheduling database. It directs the output of the SHOW# subcommand to a file. ww) 绬1 Options_MenuC This pull-down menu option allows you to set and show these Disk% File Optimizer process parameters: o CPU usage o I/O limit o Process limit 2 Setting_Process_LimitsC This option allows you to set the defragmentation process limits@ for the defragmentation processes on the nodes in your systemC and allows you to remove unwanted nodes from the database. TheseA process limits define how much of your computing resources you3 want to dedicate to the defragmentation process.D Set Parameters Dialog Box describes the fields and buttons of the Set Parameters dialog box.$ Table 9 Set Parameters Dialog Box Field DescriptionA CPU: Enter into this field the percentage of CPU usageD for any one defragmentation process. The CPU percent9 is the percent of a single CPU resources.A IO: Enter into this field the maximum direct I/O rate@ (per second) of any one defragmentation process.; MAX PROC: Enter into this field the maximum number of3 defragmentation processes per node.C Include in Use the All Nodes button to select all nodes on the list: VMScluster.@ Use the 'Only those in DB' button to select only< nodes which have process parameter settings.> Node list This list presents all nodes in the VMScluster< system from which you select nodes to change3 defragmentation process parameters. #3 The_Set_Process_Limits_ProcedureA Use the following procedure to set Defrag PLUS process limits:@ 1. Select the Options pull-down menu, then select Set Process Limits.@ 2. Select the node on which the defragmentation process to be changed runs.: IF you are setting process parameters for a node not? previously addressed, use the All Nodes option to include nodes on the list.= IF you are setting process parameters for a node in theA database, you can use either option to include nodes on the list.# 3. Enter the process parameters: o CPU o IO o MAX PROC@ 4. Exit the Set Process Limits option by selecting the Cancel button. 3 Procedure_for_Removing_NodesC Before removing nodes, no scripts must have this node in it. UseC the following procedure to remove a node from the scheduling and parameter database:? 1. Select the Options pull-down menu option, then select Set Process Limits.A 2. Set the list to include only those nodes in the database by, selecting the Only those in DB option.? 3. Select the node which is to be removed from the database. 4. Select Remove button.@ 5. Exit the Set Process Limits option by selecting the Cancel button. 32 Showing_Defragmentation_Process_Limits_ProcedureD This option allows you to show the defragmentation process limits@ in effect on all nodes in the VMScluster system. You may also= produce an output file to report this information. Use theB following procedure to show defragmentation process parameters:( 1. Select the Options pull-down menu.@ 2. Select the Show Process Limits option and the Show Process"  Limits dialogue box appears.' 3. Select to produce an output file.= IF you do not want an output file, proceed with Step 4.D IF you want an output file, select the Output File option, and enter the file name.9 4. Finish the Show Process Limits option by selecting:< o OK to leave the Show Process Limits dialog box, and, optionally produce the output file.D o Apply to produce and output file. The dialog box remains so1 you can produce additional output files.8 o Cancel to leave the Show Process Limits option.ww