% Librarian I01-42P&'Ҭpv̫r±<~'5K DEFRAGMENT#ϫr± R_FONSECA DEFRAGMENT bove. Format DEFRAGMENT [ /INTERFACE ] 2 Qualifiers /INTERFACE( /INTERFACE=CHARACTER_CELL(default) /INTERFACE=DECWINDOWS< The /INTERFACE qualifier allows you to start up the; Disk File Optimizer with either the character cell8 terminal interface or the DECwindows interface. 2 ABORTA The ABORT subcommand terminates the execution of the script or) scripts specified in the command line. Format< DEFRAGMENT ABORT { script-name[,...] } [ /QUALIFIERS ] 3 Parameters script-name< The script-name parameter is the name of the script to beC aborted. You can use wildcards in the script-name specification.; Use an asterisk (*) to take action on all scripts on the> VAXcluster system; use a percent sign (%) to match a single. character in the script-name specification. 3 Restrictions< o You cannot use the script-name parameter with the /ALL qual ifier. 3 Qualifiers /AFTER /AFTER={time} /NOAFTER (default)9 The /AFTER qualifier aborts the script after the specified time.; You can specify time as either an absolute time or: as a combination of absolute and delta times. For< complete information on specifying time values, see# the OpenVMS User's Manual. /ALL /ALL /NOALL (default): The /ALL qualifier aborts all curre ntly executing5 scripts across the system. This qualifier is< equivalent to using an asterisk (*) for the script- name parameter. 3 Examples5 The following are examples of the ABORT command:- 1.$ DEFRAGMENT ABORT MY_SCRIPT/AFTER=16:30> This command aborts MY_SCRIPT after 16:30 on the day this command is submitted. 2.$ DEFRAGMENT ABORT/ALLD This command immediately aborts all currently executing scripts in the entire s ystem. 2 ATTACHC The ATTACH subcommand transfers control from the current process4 (which then hibernates) to the specified process. Format8 DEFRAGMENT ATTACH { process-name } [ /QUALIFIERS ] 3 Parameters process-nameD The process-name specifies the name of a process to which control= transfers. The process must already exist, be part of your? current job, and share the same input stream as your currentD process. However, the process cannot be your current process or a1 subprocess created with the /NOWAIT qualifier.B Process names can contain from 1 to 15 alphanumeric characters.D If a connection to the specified process cannot be made, an error message is displayed. 3 Restrictions? o The ATTACH command cannot be used if your terminal has an associated mailbox.8 o You cannot use the process-name parameter with the /IDENTIFICATION qualifier.= o You must supply either a process name or a PID for this command. 3 Qualifiers /IDENTIFICATION /IDENTIFICATION=pid5 /IDENTIFICATION lets you specify the process> identification (PID) of the process to which terminal: control will be transferred. Leading zeros can be omitted. 3 Examples6 The following are examples of the ATTACH command: 1.$ DEFRAGMENT ATTACH JONES_2@ This ATTACH command transfers the terminal's control to the  subprocess named JONES_2.1 2.$ DEFRAGMENT ATTACH /IDENTIFICATION=2A401A1BB This ATTACH command switches control from the current process* to the process whose PID is 2A401A1B. 2 CANCELB The CANCEL subcommand skips the next scheduled execution of the) scripts specified in the command line. Format7 DEFRAGMENT CANCEL { script-name } [ /QUALIFIERS ] 3 Parameters script-name= The script-name parameter is the name of the scripts to beD canceled. You can use wildcards in the script-name specification.; Use an asterisk (*) to take action on all scripts on the> VAXcluster system; use a percent sign (%) to match a single. character in the script-name specification. 3 RestrictionsD o The script-name parameter is not allowed if the /ALL qualifier is used. 3 Qualifiers /ALL /ALL /NOALL (default)6 The /ALL qualifier cancels the next scheduled7 execution of all scripts in the scheduling and parameter database. 3 Examples7 The following is an example of the CANCEL command:/ 1.$ DEFRAGMENT CANCEL MY_SCRIPT, YOUR_SCRIPTC In this example, the next scheduled execution of MY_SCRIPT andD YOUR_SCRIPT are canceled. Afterwards, both scripts resume their normal schedule. 2 DISABLEC The DISABLE subcommand makes the specified script ineligible forC execution. Currently executing scripts are not affected. Use the8 ABORT subcommand to stop currently executing scripts. Format8 DEFRAGMENT DISABLE { script-name } [ /QUALIFIERS ] 3 Parameters script-nameB The script-name parameter specifies the scripts to be disabled.A You can use wildcards in the script-name specification. Use an? asterisk (*) to take action on all scripts on the VAXclusterD system; use a percent sign (%) to match a single character in the script-name specification. 3 RestrictionsD o The script-name parameter is not allowed if the /ALL qualifier is used. 3 Qualifiers /ALL /ALL /NOALL (default)7 The /ALL qualifier disables all scripts in the+ scheduling and parameter database. 3 Examples9 The following example shows how to disable a script:# 1.$ DEFRAGMENT DISABLE MY_SCRIPT, In this example, MY_SCRIPT is disabled. 2 ENABLE; The ENABLE subcommand reactivates scripts that have been disabled. Format7 DEFRAGMENT ENABLE { script-name } [ /QUALIFIERS ] 3 Parameters script-nameC The script-name specifies the name of the scripts to be enabled.A You can use wildcards in the script-name specification. Use an? asterisk (*) to take action on all scripts on the VAXclusterD system; use a percent sign (%) to match a single character in the script-name specification. 3 RestrictionsD o The script-name parameter is not allowed if the /ALL qualifier is used. 3 Qualifiers /ALL /ALL /NOALL (default); The /ALL qualifier enables all disabled scripts in/ the scheduling and parameter database. 3 Examples6 The following are examples of the ENABLE command: 1.$ DEFRAGMENT ENABLE/ALL< In this example, all previously deactivated scripts are: enabled. The enabled script executes according to its previously set schedule.> Enabled predecessor or successor scripts resume executing* according to their link dependencies." 2.$ DEFRAGMENT ENABLE MY_SCRIPT< In this example, MY_SCRIPT is enabled. MY_SCRIPT startsB executing according to the parameters and qualifiers assigned to it. 2 EXITA The EXIT subcommand exits from the Disk File Optimizer utility- and returns the user to the system prompt. Format DEFRAGMENT EXIT 3 Parameters None. 3 Restrictions None. 3 Qualifiers None. 3 Examples5 The following ia an example of the EXIT command: 1.DFO> EXIT $@ This command exits from the Disk File Optimizer utility and( returns the user to the DCL prompt. 2 FILE> The DEFRAGMENT FILE command defragments the files specified? on the command line according to the DEFRAGMENT command line? qualifiers. Use this command to defragment a small number ofC files. To defragment a large number of files, use the DEFRAGMENT VOLUME command. Format9 DEFRAGMENT FILE { file-spec[,...] } [ /QUALIFIERS ] 3 Parameters file-spec[,...]= The file-spec parameter identifies the file or files to beB defragmented. You may use wildcards for the file specification. 3 RestrictionsB o A script that has the /CONTINUOUS qualifier may not be named+ as the predecessor of another script.> o If you specify the /INTERVAL qualifier, the /PREDECESSOR qualifier is not allowed.> o If /LEVEL=5 is selected, the /LOG qualifier is required./ o Do not use /BRIEF and /FULL concurrently. 3 Qualifiers /AFTER /AFTER={time}% /AFTER={current_time} (default) /NOAFTER= The /AFTER qualifier keeps the script from executing( until after the specified time.; You can specify time as either an absolute time or: as a combination of absolute and delta times. For< complete information on specifying time values, see# the OpenVMS User's Manual.9 The /AFTER qualifier has three states. It can be< specified with a valid time, it can be omitted from> the command line, or it can be negated (/NOAFTER). If= /AFTER is specified with a valid time, the script is< scheduled to execute after that time. If the /AFTER; qualifier is omitted, the defragmentation software9 processes the command as if the /AFTER qualifier: were specified with the current time. If /NOAFTER: is specified, no starting time is associated with9 the script being defined. The /NOAFTER qualifier< allows you to define a script without scheduling it> to execute. To subsequently start the script, use the START subcommand. /BRIEF /BRIEF (default) /NOBRIEF8 The /BRIEF qualifier is used only with the /LOG= qualifier. The /BRIEF qualifier requests a brief log= of all actions taken by the defragmentation process.; This log includes beginning and ending file status9 information. The /BRIEF and /FULL qualifiers are; mutually exclusive, and /NOBRIEF produces the same> result as /FULL. The /BRIEF qualifier is the default. /CONSOLIDATE_FREESPACE /CONSOLIDATE_FREESPACE( /NOCONSOLIDATE_FREESPACE (default)<  The /CONSOLIDATE_FREESPACE qualifier tells the Disk; File Optimizer to use its free space consolidation algorithm. /DORMANT /DORMANT=(file-spec[,...]) /NODORMANT (default)5 The /DORMANT qualifier indicates files to be5 considered dormant when final file placement8 decisions are made. In order for the file to be9 placed dormant, it must be the file specified in: the command line. Dormant files are placed at the high end of the volume.7 If a file is indicated in both the DORMANT and< FREQUENT lists, it is considered dormant. If a file< is indicated in both the EXCLUDE and DORMANT lists, it is excluded.) NOTE7 The amount of free space on the volume, the9 number of files currently being accessed, and7 other factors influence file placement. The7 Disk File Optimi zer does not guarantee file< placement, but makes every effort to place files as described. /EPILOGUE /EPILOGUE={file-name} /NOEPILOGUE (default)> The /EPILOGUE qualifier identifies a DCL command file= which DFO executes upon completion of the DEFRAGMENT operation.9 Mounting or dismounting the disks cannot be done, through the Command file specified. /EXCLUDE /EXCLUDE=(file-spec[!,...]) /NOEXCLUDE (default)> The /EXCLUDE qualifier specifies files to be excluded= from processing. The defragmentation process ignores; files matching the listed file specifications. Any9 file indicated in the EXCLUDE list and in either7 the FREQUENT or DORMANT lists is excluded from processing.) NOTE7 The defragmentation process always excludes: system files, open" files, files excluded in an8 options file (/OPTIONS qualifier), and files1 excluded using the /IGNORE qualifier. /FREQUENT! /FREQUENT=(file-spec[,...]) /NOFREQUENT (default)6 The /FREQUENT qualifier indicates files to be7 considered frequently accessed when final file< placement decisions are made. In order for the file= to be placed frequent, it must be the file specified> in the command line. Freque#nt files are placed toward" the center of the volume.8 If a file is indicated in both the FREQUENT and; DORMANT lists, it is considered dormant. If a file= is indicated in both the FREQUENT and EXCLUDE lists, it is excluded.) NOTE7 The amount of free space on the volume, the9 number of files currently being accessed, and7 other factors influence file placement. The7 $ Disk File Optimizer does not guarantee file< placement, but makes every effort to place files as described. /FULL /FULL /NOFULL (default)7 The /FULL qualifier requests a full log of all: actions taken by the defragmentation process. The= /FULL qualifier has no meaning if the /LOG qualifier7 is absent. The /FULL and /BRIEF qualifiers are: mutually exclusive, and /NOFULL provides the same! % functionality as /BRIEF. /HOTFILE_DATABASE /HOTFILE_DATABASE# /NOHOTFILE_DATABASE (default)3 The /HOTFILE_DATABASE qualifier causes the6 defragmenter to query the appropriate hotfile8 database and append the list of hotfiles to the /FREQUENT file list. /IGNORE /IGNORE=(keyword[,...]) /IGNORE=(PLACED) (default) /NOIGNORE0 The /IGNORE qualifier requests that the> defragmentati&on process ignore certain types of files0 as specified by the following keywords:1 o INDEXED-Ignores all RMS indexed files6 o NOINDEXED-May defragment RMS indexed files< o PLACED-Ignores all files with explicit placement& flags set in their headers7 o NOPLACED-May defragment files with explicit placement flags> Files indicated by the /IGNORE qualifier are added to the EXCLUDE list.: The' default value (/IGNORE=PLACED) indicates that8 files with explicit placement control should be6 ignored, and that RMS indexed files should be9 defragmented and placed in appropriate locations on the volume. /INHERIT /INHERIT={script-name} /NOINHERIT (default)9 The purpose of the /INHERIT qualifier is to make: script creation easier. By inheriting most of the: command data from a previously entered script and(< modifying only a few items (such as volume name), a; completely new script can be created. The /INHERIT< qualifier creates a database entry for a new script in the following way:> o Copies all fields from the specified script to the new script.; o Overwrites any qualifier or parameter values in> the new script with those specified on the command line.= o Names the new script as appropri)ate. The user may< specify a script name using the /SCRIPT={script-; name} qualifier. Otherwise, the defragmentation: software creates a unique script name. You can; use wildcards in the script-name specification.= Use an asterisk (*) to take action on all scripts< on the VAXcluster system; use a percent sign (%): to match a single character in the script-name specification. /INTERVAL */INTERVAL={delta-time} /NOINTERVAL (default)5 The /INTERVAL qualifier executes a script at5 regularly scheduled intervals. The /INTERVAL9 qualifier specifies the minimum time between two, consecutive executions of a script.; Specify time as a delta time. Refer to the OpenVMS9 User's Manual for more information on specifying5 times. If you do not specify a time with the9 /INTERVAL qualifier, a default value of 2+4 hours< is used. This value causes the associated script to run every 24 hours.5 If you specify the /AFTER qualifier with the7 /INTERVAL qualifier, the first defragmentation8 operation occurs at or after the time specified; by the /AFTER qualifier; all subsequent operations< execute at intervals set according to the /INTERVAL qualifier. /LEVEL /LEVEL={n} /LEVEL=1 (default)6 The defragm,entation process selects files for> defragmentation (from among those not excluded) based< on the /LEVEL qualifier. Once a file is selected as: a candidate, the defragmentation process attempts; to fully defragment that file (make it 100 percent< contiguous). Specify the level number as an integer" ranging from one to five: o /LEVEL=1; Any file that is not 100 percent contiguous, or< that can be selected usi-ng levels two and three,/ is a candidate for defragmentation. o /LEVEL=2 (default)7 Any file whose extents cannot be completely8 mapped by the mapping window, or that can be: selected using level three, is a candidate for> defragmentation. The default window value is seven4 and can be set for a given volume using:2 $ SET VOLUME {device-spec}/WINDOWS=[n] o /LEVEL=3= Any file. with retrieval pointers in more than one; file header is a candidate for defragmentation. o /LEVEL=46 The defragmentation process for level four> processing performs only free space consolidation.> This level is used with the /CONSOLIDATE_FREESPACE qualifier. o /LEVEL=57 This level requests a volume analysis only;6 no defragmentation occurs. The statistical; results are av/ailable in the log file, which is< required when /LEVEL=5 is selected (see the /LOG< qualifier). If level 5 is selected, the /LEVEL=2; candidate file specifications are listed in the full log file. /LOG /LOG={file-spec} /NOLOG (default)> The /LOG qualifier causes the defragmentation process6 to create a file containing a list of all its; operations. The information in the log file varies= 0 with the presence of the /FULL or /BRIEF qualifiers.< The /FULL qualifier lists all files analyzed by the9 defragmentation process and reports their status. during each phase of defragmentation.: The /BRIEF qualifier lists only the statistics of9 each phase, such as number of files analyzed and& number of files defragmented. /MAIL_NOTIFICATION /MAIL_NOTIFICATION$ /NOMAIL_NOTIFICATION (default)7 The /MAIL_N1OTIFICATION qualifier requests that8 brief status and termination messages regarding3 defragmentation processes be mailed to the9 distribution list provided in the file DFG$MAIL_ ADDRESS. /NODE /NODE=(node-name[,...]) /NONODE (default)4 The /NODE qualifier limits the scope of the7 DEFRAGMENT command to the node or set of nodes4 specified by /NODE=(node-name). By default,9 defragmentation process2es may execute on any LMF% licensed node in the system. /OPCOM_NOTIFICATION# /OPCOM_NOTIFICATION (default) /NOOPCOM_NOTIFICATION8 The /OPCOM_NOTIFICATION qualifier requests that8 brief status and termination messages regarding4 defragmentation processes be sent to OPCOM. /OPTIONS /OPTIONS={file-spec} /NOOPTIONS (default)< The /OPTIONS qualifier provides an alternate method> for associating f3iles with the /DORMANT, /EXCLUDE, or> /FREQUENT qualifiers. If the list of files for any of< these qualifiers is long, you can create a separate> file for this information. Each record in the options< file consists of a file name followed by one of the following keywords:( o /EXCLUDE-File to be excluded6 o /FREQUENT-File to be considered frequently accessed2 o /DORMANT-File to be considered dormant7 4 The following example shows the contents of an5 options file called MYOPTFILE.OPT. This file= specifies that all files on the target device called7 FILE1.EXE are frequent files, all files in the> [ARCHIVE] directory are to be excluded, and all files; in the [OLDSTUFF] directory and its subdirectories are dormant. FILE1.EXE/FREQUENT# [ARCHIVE]*.*;*/EXCLUDE' [OLDSTUFF...]*.*;*/DORMANT9 5 Files indicated by the /EXCLUDE qualifier and by7 either the /DORMANT or /FREQUENT qualifier are< excluded. Files indicated by the /DORMANT qualifier6 and by the /FREQUENT qualifier are considered9 dormant. This rule is applied equally across all9 files specified in the /OPTIONS file, as well as> those associated with these qualifiers on the command line. /PREDECESSOR /PREDECESSOR={script-name} /NOPREDECESSOR (6default)8 The /PREDECESSOR qualifier links scripts. These6 scripts execute in sequence; one successfully. completes before the next one begins.6 The predecessor script name must exist in the: scheduling database or an error status message is; returned. You can use wildcards in the script-name= specification. Use an asterisk (*) to take action on< all scripts on the VAXcluster system; use a percent< sign (%) to mat7ch a single character in the script- name specification. /PRIORITY& /PRIORITY=(DEFAULT=n, MINIMUM=n) /NOPRIORITY (default)= The /PRIORITY qualifier specifies priorities for the< defragment process. The minimum priority setting is: used when the defragmentation process exceeds the; value specified by either /CPU_LIMIT or /IO_LIMIT. /PROLOGUE /PROLOGUE={file-name} /NOPROLOGUE (default)9 The8 /PROLOGUE qualifier identifies a DCL command; file which DFO executes just before the Defragment operation starts.9 Mounting or dismounting the disks cannot be done, through the Command file specified. /RVN /RVN=n /RVN=0 (default)= When you have a bound volume set, use this qualifier< to identify a disk from the volume set or all disks> in the volume set. The default of zero tells the Disk< File 9Optimizer to defragment all disks in the bound; volume set. Specify a relative volume number (RVN)> to defragment a specific disk that belongs to a bound volume set. /SCRIPT /SCRIPT={script-name} /NOSCRIPT (default); The /SCRIPT qualifier assigns a user-supplied name= to a script. If a duplicate script-name is selected,; defragmentation software issues a duplicate script= name error message and does not e:nter the new script: into the database-no defragmentation takes place.; A script name may be up to 64 characters in length9 and may contain any of the following characters:& o Any alphanumeric character o Underscore ( _ ) o Hyphen ( - ) o Dollar sign ( $ ): Observe the following rules when naming a script:8 o You may use any combination of uppercase and lowercase letters.< ; o DO not begin script names using the dollar sign.; However, you can include the dollar sign within= the script name. (The dollar sign is reserved for special use by HP.)= o Do not end a script name with a hyphen, since the5 hyphen is the DCL continuation character. /TIME_LIMIT /TIME_LIMIT={delta-time} /NOTIME_LIMIT (default)8 The /TIME_LIMIT qualifier specifies the maximum9 elapsed time <allowed for a given defragmentation6 operation. If the time limit is exceeded, the, defragmentation process is aborted.; Specify time as a delta time. Refer to the OpenVMS9 User's Manual for more information on specifying times.8 For linked scripts, the time limit of the first5 script applies to the whole set. Time limits8 specified with successor scripts apply to these scripts only.7 If the time lim=it is set unreasonably low, the: defragmentation process may not accomplish useful defragmentation. /WRITE_CHECK /WRITE_CHECK /NOWRITE_CHECK (default)9 The /WRITE_CHECK qualifier requests that a read-; after-write check be performed on all defragmented> or placed files. This qualifier significantly extends9 the execution time of a defragmentation process. 3 ExamplesD The following examples show diffe>rent ways to defragment a file< or group of files and how to use the common qualifiers: 1.$ DEFRAGMENT FILE *.C;*B This command defragments all files with a .C extension in the> user's current default directory. To determine the deviceA and directory in which the files are located, issue the SHOW DEFAULT command. 2.DFO> DEFRAGMENT FILE *.C;*B This command defragments all files with a .C extension on the? user's current default device. The only dif?ference betweenB this command and the previous example is that this command isC entered from within the Disk File Optimizer utility instead of from the DCL prompt.3 3.$ DEFRAGMENT FILE SYS$SYSDEVICE:[000000...]*.C> This command is the same as the previous one, except that; the RMS default string is now explicitly identified as$ SYS$SYSDEVICE:[000000...]*.C;*.< 4.$ DEFRAGMENT FILE SYS$LOGIN:LOGIN.COM;2/EXCLUDE=*.OLD;*D This command defragments the @user's LOGIN.COM file and excludes% all files with a .OLD extension.8 5.$ DEFRAGMENT FILE/INHERIT=OTHER_FILE_SCRIPT.NOAFTER@ This commands creates a file script identical to the OTHER_> FILE_SCRIPT and allows the Disk File Optimizer to name it (DFG$XXX).E 6.$ DEFRAGMENT FILE SYS$SYSTEM:[000000...]*.RDB/INHERIT=X/SCRIPT=Y: This command creates a script called Y . Other scriptA characteristics, such as log file, are inherited from script X. A2 HELPC The HELP subcommand invokes VMS Help for the Disk File Optimizer utility. Format DEFRAGMENT HELP 3 Parameters None. 3 Restrictions None. 3 Qualifiers None. 3 Examples@ The following examples show the various ways you can access. HELP for the Disk File Optimizer utility: 1.$ DEFRAGMENT HELPB This command invokes HELP for the Disk File Optimizer utility directly from DCL. 2.$ HELP DEFRBAGMENTB This command invokes HELP for the Disk File Optimizer utility directly from DCL. 3.DFO> HELPB This command invokes HELP from within the Disk File Optimizer utility. 2 MODIFY< The MODIFY subcommand allows you to change the qualifiers' associated with a particular script. Format7 DEFRAGMENT MODIFY { script-name } [ /QUALIFIERS ] 3 Parameters script-nameA The script-name parameter identifies the script to modiCfy. You= can use wildcards in the script-name specification. Use an? asterisk (*) to take action on all scripts on the VAXclusterD system; use a percent sign (%) to match a single character in the script-name specification. 3 RestrictionsB o A script that has the /CONTINUOUS qualifier may not be named+ as the predecessor of another script.> o If you specify the /INTERVAL qualifier, the /PREDECESSOR qualifier is not allowed.> o If /LEVEL=5 is sDelected, the /LOG qualifier is required./ o Do not use /BRIEF and /FULL concurrently.8 o Do not use /CONTINUOUS and /INTERVAL for a script. 3 Qualifiers /AFTER /AFTER={time}% /AFTER={current_time} (default) /NOAFTER= The /AFTER qualifier keeps the script from executing( until after the specified time.; You can specify time as either an absolute time or: as a combination of absolute and delta times. For< E complete information on specifying time values, see# the OpenVMS User's Manual.9 The /AFTER qualifier has three states. It can be< specified with a valid time, it can be omitted from> the command line, or it can be negated (/NOAFTER). If= /AFTER is specified with a valid time, the script is< scheduled to execute after that time. If the /AFTER; qualifier is omitted, the defragmentation software9 processes the command aFs if the /AFTER qualifier: were specified with the current time. If /NOAFTER: is specified, no starting time is associated with9 the script being defined. The /NOAFTER qualifier< allows you to define a script without scheduling it> to execute. To subsequently start the script, use the START subcommand. /BRIEF /BRIEF (default) /NOBRIEF< The /BRIEF qualifier may only be used when the /LOG8 qualifier is Galso present. The /BRIEF qualifier9 requests a brief log of all actions taken by the= defragmentation process. This log includes beginning9 and ending volume status information. The /BRIEF9 and /FULL qualifiers are mutually exclusive, and8 /NOBRIEF produces the same result as /FULL. The) /BRIEF qualifier is the default. /CONSOLIDATE_FREESPACE /CONSOLIDATE_FREESPACE( /NOCONSOLIDATE_FREESPACE (default)< The /COHNSOLIDATE_FREESPACE qualifier tells the Disk; File Optimizer to use its free space consolidation algorithm. /CONTINUOUS /CONTINUOUS /NOCONTINUOUS (default)4 The /CONTINUOUS qualifier causes the script5 to execute repeatedly. After each successful6 defragmentation operation, the script becomes> eligible for execution again. As long as any PROCESS_: LIMITs (see the SET subcommand) are not violated,> I the script executes repeatedly. If all PROCESS_LIMITs9 have been reached, the script is queued until an< outstanding defragmentation process completes, then* the script is allowed to execute.; By default, the defragmentation process associated7 with a script may execute on any appropriately5 licensed node in a cluster. Thus, successive= defragmentation processes do not necessarily execute on the same node. /DORMANTJ /DORMANT=(file-spec[,...]) /NODORMANT (default)5 The /DORMANT qualifier indicates files to be5 considered dormant when final file placement< decisions are made. Dormant files are placed at the high end of the volume.7 If a file is indicated in both the DORMANT and< FREQUENT lists, it is considered dormant. If a file< is indicated in both the EXCLUDE and DORMANT lists, it is excluded.) K NOTE7 The amount of free space on the volume, the9 number of files currently being accessed, and7 other factors influence file placement. The7 Disk File Optimizer does not guarantee file< placement, but makes every effort to place files as described. /EPILOGUE /EPILOGUE={file-name} /NOEPILOGUE (default)> The /EPILOGUE qualifier identifies a DCL command file= L which DFO executes upon completion of the DEFRAGMENT operation.9 Mounting or dismounting the disks cannot be done, through the Command file specified. /EXCLUDE /EXCLUDE=(file-spec[,...]) /NOEXCLUDE (default)> The /EXCLUDE qualifier specifies files to be excluded= from processing. The defragmentation process ignores; files matching the listed file specifications. Any9 file indicated in the EXCLUDE lisMt and in either7 the FREQUENT or DORMANT lists is excluded from processing.) NOTE7 The defragmentation process always excludes: system files, open files, files excluded in an8 options file (/OPTIONS qualifier), and files1 excluded using the /IGNORE qualifier. /FILES /FILES=(file-spec[,...])> The /FILES qualifier modifies the list of files to be defragmNented. /FREQUENT! /FREQUENT=(file-spec[,...]) /NOFREQUENT (default)6 The /FREQUENT qualifier indicates files to be7 considered frequently accessed when final file9 placement decisions are made. Frequent files are0 placed toward the center of the volume.8 If a file is indicated in both the FREQUENT and; DORMANT lists, it is considered dormant. If a file= is indicated in both the FREQUENT and EXCLUDE lists,O it is excluded.) NOTE7 The amount of free space on the volume, the9 number of files currently being accessed, and7 other factors influence file placement. The7 Disk File Optimizer does not guarantee file< placement, but makes every effort to place files as described. /FULL /FULL /NOFULL (default)7 The /FULL qualifier requests a full lPog of all: actions taken by the defragmentation process. The= /FULL qualifier has no meaning if the /LOG qualifier7 is absent. The /FULL and /BRIEF qualifiers are: mutually exclusive, and /NOFULL provides the same! functionality as /BRIEF. /HOTFILE_DATABASE /HOTFILE_DATABASE# /NOHOTFILE_DATABASE (default)3 The /HOTFILE_DATABASE qualifier causes the6 defragmenter to query the appropriate hotfile8 dQatabase and append the list of hotfiles to the, defragmenter's /FREQUENT file list. /IGNORE /IGNORE=(keyword[,...]) /IGNORE=(PLACED) (default) /NOIGNORE0 The /IGNORE qualifier requests that the> defragmentation process ignore certain types of files0 as specified by the following keywords:1 o INDEXED-Ignores all RMS indexed files6 o NOINDEXED-May defragment RMS indexed files< o PLACED-Ignores aRll files with explicit placement& flags set in their headers7 o NOPLACED-May defragment files with explicit placement flags> Files indicated by the /IGNORE qualifier are added to the EXCLUDE list.: The default value (/IGNORE=PLACED) indicates that8 files with explicit placement control should be6 ignored, and that RMS indexed files should be9 defragmented and placed in appropriate locations on Sthe volume. /INTERVAL /INTERVAL={delta-time} /NOINTERVAL (default): Causes a script to execute at regularly scheduled9 intervals. The /INTERVAL qualifier specifies the= minimum time between two consecutive executions of a script.; Specify time as a delta time. Refer to the OpenVMS9 User's Manual for more information on specifying5 times. If you do not specify a time with the9 /INTERVAL qualifiUer, a default value of 1 day is= used. This value causes the associated script to run every 24 hours.5 If you specify the /AFTER qualifier with the7 /INTERVAL qualifier, the first defragmentation8 operation occurs at or after the time specified; by the /AFTER qualifier; all subsequent operations< execute at intervals set according to the /INTERVAL qualifier. /LEVEL /LEVEL={n} /LEVEL=2 (default)U6 The defragmentation process selects files for> defragmentation (from among those not excluded) based< on the /LEVEL qualifier. Once a file is selected as: a candidate, the defragmentation process attempts; to fully defragment that file (make it 100 percent< contiguous). Specify the level number as an integer" ranging from one to five: o /LEVEL=1; Any file that is not 100 percent contiguous, or< thWat can be selected using levels two and three,/ is a candidate for defragmentation. o /LEVEL=2 (default)7 Any file whose extents cannot be completely8 mapped by the mapping window, or that can be: selected using level three, is a candidate for> defragmentation. The default window value is seven4 and can be set for a given volume using:2 $ SET VOLUME {device-spec}/WINDOWS=[n] o /LEVEL=3W= Any file with retrieval pointers in more than one; file header is a candidate for defragmentation. o /LEVEL=46 The defragmentation process for level four> processing performs only free space consolidation.> This level is used with the /CONSOLIDATE_FREESPACE qualifier. o /LEVEL=57 This level requests a volume analysis only;6 no defragmentation occurs. The statistical; X results are available in the log file, which is< required when /LEVEL=5 is selected (see the /LOG< qualifier). If level 5 is selected, the /LEVEL=2; candidate file specifications are listed in the full log file. /LOG /LOG={file-spec} /NOLOG (default)> The /LOG qualifier causes the defragmentation process6 to create a file containing a list of all its; operations. The information in the log Zfile varies= with the presence of the /FULL or /BRIEF qualifiers.< The /FULL qualifier lists all files analyzed by the> defragmentation process and reports their disposition9 during each phase of defragmentation. The /BRIEF; qualifier lists only the statistics of each phase,> such as number of files analyzed, and number of files defragmented. /MAIL_NOTIFICATION /MAIL_NOTIFICATION$ /NOMAIL_NOTIFICATION (default)Z7 The /MAIL_NOTIFICATION qualifier requests that8 brief status and termination messages regarding8 defragmentation processes be mailed to the mail9 distribution list provided in the file DFG$MAIL_ ADDRESS. /NODE /NODE=(node-name[,...]) /NONODE (default)4 The /NODE qualifier limits the scope of the7 DEFRAGMENT command to the node or set of nodes4 specified by /NODE=(node-name). By default,9 [ defragmentation processes may execute on any LMF% licensed node in the system. /OPCOM_NOTIFICATION# /OPCOM_NOTIFICATION (default) /NOOPCOM_NOTIFICATION8 The /OPCOM_NOTIFICATION qualifier requests that8 brief status and termination messages regarding4 defragmentation processes be sent to OPCOM. /OPTIONS /OPTIONS={file-spec} /NOOPTIONS (default)< The /OPTIONS qualifier provides an alternate method\> for associating files with the /DORMANT, /EXCLUDE, or> /FREQUENT qualifiers. If the list of files for any of< these qualifiers is long, you can create a separate> file for this information. Each record in the options< file consists of a file name followed by one of the following keywords:( o /EXCLUDE-File to be excluded6 o /FREQUENT-File to be considered frequently accessed2 o /DORMANT-File to be ]considered dormant7 The following example shows the contents of an5 options file called MYOPTFILE.OPT. This file= specifies that all files on the target device called7 FILE1.EXE are frequent files, all files in the> [ARCHIVE] directory are to be excluded, and all files; in the [OLDSTUFF] directory and its subdirectories are dormant. FILE1.EXE/FREQUENT [ARCHIVE]*.*;*/EXCLUDE# [OLDSTUFF...]*.*;*/DORM^ANT9 Files indicated by the /EXCLUDE qualifier and by7 either the /DORMANT or /FREQUENT qualifier are< excluded. Files indicated by the /DORMANT qualifier6 and by the /FREQUENT qualifier are considered9 dormant. This rule is applied equally across all9 files specified in the /OPTIONS file, as well as> those associated with these qualifiers on the command line. /PREDECESSOR /PREDECESSOR={script-name} _/NOPREDECESSOR (default): The /PREDECESSOR qualifier identifies the name of> the script that precedes the execution of this script= in a linked set of scripts. These scripts execute in= sequence; one successfully completes before the next one begins.6 The predecessor script name must exist in the: scheduling database or an error status message is; returned. You can use wildcards in the script-name= specification`. Use an asterisk (*) to take action on< all scripts on the VAXcluster system; use a percent< sign (%) to match a single character in the script- name specification. /PRIORITY& /PRIORITY=(DEFAULT=n, MINIMUM=n) /NOPRIORITY (default)= The /PRIORITY qualifier specifies priorities for the< defragment process. The minimum priority setting is: used when the defragmentation process exceeds the; value specified by eiather /CPU_LIMIT or /IO_LIMIT. /PROLOGUE /PROLOGUE={file-name} /NOPROLOGUE (default)9 The /PROLOGUE qualifier identifies a DCL command; file which DFO executes just before the Defragment operation starts.9 Mounting or dismounting the disks cannot be done, through the Command file specified. /RVN /RVN=n /RVN=0 (default)= When you have a bound volume set, use this qualifier< to bidentify a disk from the volume set or all disks> in the volume set. The default of zero tells the Disk< File Optimizer to defragment all disks in the bound; volume set. Specify a relative volume number (RVN)> to defragment a specific disk that belongs to a bound volume set. /SCRIPT /SCRIPT={script-name} /NOSCRIPT (default)6 The /SCRIPT qualifier assigns a new name to a8 script. If a duplicate script-name isc selected,; defragmentation software issues a duplicate script= name error message and does not enter the new script: into the database-no defragmentation takes place.; A script name may be up to 64 characters in length9 and may contain any of the following characters:& o Any alphanumeric character o Underscore ( _ ) o Hyphen ( - ) o Dollar sign ( $ ): Observe the following rules when namidng a script:: o Use any combination of uppercase and lowercase letters.< o Do not begin script names using the dollar sign.; However, you can include the dollar sign within= the script name. (The dollar sign is reserved for special use by HP.)= o Do not end a script name with a hyphen, since the5 hyphen is the DCL continuation character.< The OpenVMS User's Manual contains more informatione on naming conventions. /TIME_LIMIT /TIME_LIMIT={delta-time} /NOTIME_LIMIT (default)8 The /TIME_LIMIT qualifier specifies the maximum9 elapsed time allowed for a given defragmentation6 operation. If the time limit is exceeded, the, defragmentation process is aborted.; Specify time as a delta time. Refer to the OpenVMS9 User's Manual for more information on specifying times.8 For linfked scripts, the time limit of the first5 script applies to the whole set. Time limits8 specified with successor scripts apply to these scripts only.7 If the time limit is set unreasonably low, the: defragmentation process may not accomplish useful defragmentation. /VOLUME /VOLUME={volume-name} /NOVOLUME (default)6 Identifies the volume where the files reside. /WRITE_CHECK /WRITE_CHECKg /NOWRITE_CHECK (default)9 The /WRITE_CHECK qualifier requests that a read-; after-write check be performed on all defragmented> or placed files. This qualifier significantly extends9 the execution time of a defragmentation process. 3 ExamplesB The following examples show how to modify an existing scripts! using the common qualifiers:# 1.$ DEFRAGMENT MODIFY C/SCRIPT=A4 This command changes the name of script C to A.,h 2.$ DEFRAGMENT MODIFY */MAIL_NOTIFICATIONC This command turns on mail notification for all scripts in the database.; 3.$ DEFRAGMENT MODIFY myscript/LOG=new_log/NOPREDECESSOR= This command causes subsequent executions of myscript toB generate a log file called NEW_LOG.LOG, located in the user'sA default directory. The NOPREDECESSOR qualifier disassociatesA myscript from its predecessor. However, any script for whichC myscript is a predecessor remainsi dependent upon the execution of myscript.% 4.$ DEFRAGMENT MODIFY *C/SCRIPT=*DC This command changes the name of each script that ends in C to4 end in D. For instance, DAILYC becomes DAILYCD. 2 MONITORA The MONITOR subcommand displays the the progress of an ongoing+ defragmentation processes on a terminal. FormatD DEFRAGMENT MONITOR { script-name|volume-name } [ /QUALIFIERS ] 3 Parameters script-name|volume-nameC The paramjeter for the MONITOR subcommand is either a script nameA or a volume name for Defrag PLUS. You can use wildcards in theC script-name specification. Use an asterisk (*) to take action onB all scripts on the VAXcluster system; use a percent sign (%) to= match a single character in the script-name specification.> If a volume name is supplied, then you must use the /VOLUME@ qualifier to tell Defrag PLUS the parameter is a volume name, rather than a script name. 3 Restrkictions= o If a volume name is entered as a parameter, the /VOLUME qualifier must be used. 3 Qualifiers /CONTINUOUS /CONTINUOUS (default) /NOCONTINUOUS7 The /CONTINUOUS qualifier invokes a continuous: monitor display. Entering Ctrl/C, Ctrl/Y, or Ctrl$ /Z terminates this display.< Using /NOCONTINUOUS provides a snapshot display and( then returns to the DCL prompt. /VOLUME /VOLUME (dlefault) /NOVOLUME; The /VOLUME qualifier indicates that a volume name; instead of a script name is present on the command8 line. The /VOLUME qualifier must be used when a> volume name is provided as a parameter to the MONITOR subcommand. 3 Examples8 The following are examples of invoking the monitor:, 1.$ DEFRAGMENT MONITOR MY_SCRIPT/NOVOLUMED In this example, the monitor function displays ongoing run-timeC m statistics for the defragmentation process associated with MY_B SCRIPT. It also displays an approximate free-space map of theB target volume. The display continues until interrupted with aC Ctrl/C, Ctrl/Y, or Ctrl/Z because the /CONTINUOUS qualifier is present by default./ 2.$ DEFRAGMENT MONITOR DISK$ONE/NOCONTINUOUSC In this example, the defragmentation process executing againstA DISK$ONE is monitored. Since the /NOCONTINUOUS qualifier was@ specified, nthe monitor function samples the defragmentation? process statistics and the free space on DISK$ONE one time& before exiting to the DCL prompt. 2 OFFLINE_VOLUMEC The DEFRAGMENT OFFLINE_VOLUME command defragments the INDEXF.SYSA file on the offline volume given as a parameter to the command< line according to the defragment command line qualifiers. Format? DEFRAGMENT OFFLINE_VOLUME { volume-name } [ /QUALIFIERS ]0 [ /QUALIoFIERS ]) 3 Parameters volume-name; The volume-name is the name of the volume containing the& INDEXF.SYS file to be defragmented. 3 Restrictions= o This command is only valid on a disk device that is not@ mounted. If the device is mounted, an error occurs and the@ process will abort. This command cannot work on the system( disk because it is always mounted.C o For a bound volume set, this utility only works on the "ROOT" volume.pD o For disk volumes in a shadow set (single member or otherwise),' the following restrictions apply:@ o Do not specify the virtual unit name to defragment (for example: DSAnnnn:).< o Specify only one physical device name (for example: $1$DUAnnnn:).B o Use the following procedure to defragment INDEXF.SYS in a shadow set:4 1. Dismount both members of the shadow set.7 2. Mount one of the physical disk volumes witqhB /OVERRIDE=SHADOW and then dismount it before doing theD defragmentation. If you do not do this, you will receive the following error:/ %SYSTEM-F-WRITLCK, write lock error9 3. Defragment the INDEXF.SYS on the disk volume.6 4. Mount the disk volume into the shadow set.B 5. Add the disk volume that was not defragmented into theD shadow set. Mounting this disk volume causes a full copy operatrion.5 o If you experience a power failure during the> defragmentation of INDEXF.SYS, you may need to do the following:D - Repair alternate index file header and index file bitmap+ by doing a ANALYZE/DISK/REPAIR.6 - Delete disk:[000000]DFG$DEFRAG_INDEXF.DAT. 3 Qualifiers /AFTER /AFTER={time}% /AFTER={current_time} (default) /NOAFTER= The /AFTER qualifier keeps the script from executinsg( until after the specified time.; You can specify time as either an absolute time or: as a combination of absolute and delta times. For< complete information on specifying time values, see# the OpenVMS User's Manual.9 The /AFTER qualifier has three states. It can be< specified with a valid time, it can be omitted from> the command line, or it can be negated (/NOAFTER). If= /AFTER is specified with a valid time, tthe script is< scheduled to execute after that time. If the /AFTER; qualifier is omitted, the defragmentation software9 processes the command as if the /AFTER qualifier: were specified with the current time. If /NOAFTER: is specified, no starting time is associated with9 the script being defined. The /NOAFTER qualifier< allows you to define a script without scheduling it> to execute. To subsequently start the script, use theu START subcommand. /EPILOGUE /EPILOGUE={file-name} /NOEPILOGUE (default)> The /EPILOGUE qualifier identifies a DCL command file= which DFO executes upon completion of the DEFRAGMENT operation.9 Mounting or dismounting the disks cannot be done, through the Command file specified. /INTERVAL /INTERVAL={delta-time} /NOINTERVAL (default)5 The /INTERVAL qualifier executes a script avt5 regularly scheduled intervals. The /INTERVAL9 qualifier specifies the minimum time between two, consecutive executions of a script.; Specify time as a delta time. Refer to the OpenVMS9 User's Manual for more information on specifying5 times. If you do not specify a time with the9 /INTERVAL qualifier, a default value of 1 day is= used. This value causes the associated script to run every 24 hours.5 w If you specify the /AFTER qualifier with the7 /INTERVAL qualifier, the first defragmentation8 operation occurs at or after the time specified; by the /AFTER qualifier; all subsequent operations< execute at intervals set according to the /INTERVAL qualifier. /LOG /LOG={file-spec} /NOLOG (default)6 The /LOG qualifier causes the defragmentation: process to create a file containing a list of all its oxperations. /MAIL_NOTIFICATION /MAIL_NOTIFICATION$ /NOMAIL_NOTIFICATION (default)7 The /MAIL_NOTIFICATION qualifier requests that8 brief status and termination messages regarding8 defragmentation processes be mailed to the mail9 distribution list provided in the file DFG$MAIL_ ADDRESS. /NODE /NODE=(node-name[,...]) /NONODE (default)4 The /NODE qualifier limits the scope of the7 DEFyRAGMENT command to the node or set of nodes4 specified by /NODE=(node-name). By default,9 defragmentation processes may execute on any LMF% licensed node in the system. /OPCOM_NOTIFICATION# /OPCOM_NOTIFICATION (default) /NOOPCOM_NOTIFICATION8 The /OPCOM_NOTIFICATION qualifier requests that8 brief status and termination messages regarding4 defragmentation processes be sent to OPCOM. /PROLOGUE /PROLOGUzE={file-name} /NOPROLOGUE (default)9 The /PROLOGUE qualifier identifies a DCL command; file which DFO executes just before the Defragment operation starts.9 Mounting or dismounting the disks cannot be done, through the Command file specified. /SCRIPT /SCRIPT={script-name} /NOSCRIPT (default); The /SCRIPT qualifier assigns a user-supplied name= to a script. If a duplicate script-name is sele{cted,; defragmentation software issues a duplicate script= name error message and does not enter the new script: into the database-no defragmentation takes place.; A script name may be up to 64 characters in length9 and may contain any of the following characters:& o Any alphanumeric character o Underscore ( _ ) o Hyphen ( - ) o Dollar sign ( $ ): Observe the following rules when naming a| script:8 o You may use any combination of uppercase and lowercase letters.: o You cannot begin script names using the dollar< sign, but you can include the dollar sign within= the script name. (The dollar sign is reserved for special use by HP.); o You should not end a script name with a hyphen,4 since the hyphen is the DCL continuation character. 3 ExamplesD The following} examples illustrate how to use the OFFLINE_VOLUME# subcommand and its qualifiers., 1.$ DEFRAGMENT OFFLINE_VOLUME $1$DKB100:-& /SCRIPT=DEFRAG_OFFLINE_USER1- /NOAFTER" $ DISMOUNT/CLUSTER $1$DKB100: $ MOUNT/OVER=ID $1$DKB100:( $ ANALYZE/DISK_STRUCTURE $1$DKB100: $ DISMOUNT $1$DKB100:, $ DEFRAGMENT START DEFRAG_OFFLINE_USER1 $ MOUNT/OVER=ID $1$DKB100:( $ ANALYZE/DISK_STRUCTURE $1$DKB100: $ DISMOUNT $1$DKB100:% $ MOUNT/CLUST~ER $1$DKB100: USER11 In this example, the following is performed:8 1. Create script to defragment INDEXF.SYS on volume( 2. Dismount volume from the cluster8 3. Mount volume privately to analyze disk structure= 4. Check volume for readability and validity of Files-11 structure information0 5. Dismount volume to defragment INDEXF.SYS# 6. Start OFFLINE_VOLUME script8 7. Mount volume privately to analyze disk structure= 8. Check volume for readability and validity of Files-11 structure information 9. Dismount volume% 10. Mount volume into the cluster 2 REMOVEB The REMOVE subcommand deletes the specified script or node from9 the defragmentation scheduling and parameter database. Format? DEFRAGMENT REMOVE { script-name[,...] | node-name[,...] }' [ /QUALIFIERS ] 3 Parameters script-nameD The script-name parameter specifies the script to remove from theA defragmentation database. You can use wildcards in the script-@ name specification. Use an asterisk (*) to take action on allD scripts on the VAXcluster system; use a percent sign (%) to match7 a single character in the script-name specification.? This parameter is not allowed if the /ALL qualifier is used. node-name@ The node-name parameter specifies the node to remove from the defragmentation database. 3 RestrictionsC o If the /ALL qualifier is used, then the script-name parameter cannot be used.4 o If the node is a script, it cannot be removed.< o If the node has a scheduler or defragmentation process$ running, it cannot be removed. 3 Qualifiers /AFTER /AFTER=time /NOAFTER (default)8 The /AFTER qualifier does not delete the script: until after the specified time. Specify time as a< VMS absolute time or combination absolute and delta: time. Refer to the OpenVMS User's Manual for more, information on how to specify time. /ALL /ALL /NOALL (default): The /ALL qualifier indicates that all scripts are8 to be removed from the scheduling and parameter database.: If /ALL is used, the script-name parameter is not allowed. /NODE /NODE< The /NODE qualifier removes the specified node name4 from the scheduling and parameter database. 3 Examples? The following example shows how to remove a script after a specified time:. 1.$ DEFRAGMENT REMOVE MY_SCRIPT/AFTER=16:30C In this example, MY_SCRIPT is removed from the database. It is< removed after 16:30 on the day this command is entered.$ 2.$ DEFRAGMENT REMOVE MYNODE/NODE: In this example, MYNODE is removed from the database. 2 SET9 The SET subcommand defines or changes the value of the" defragmentation process limits. Format@ DEFRAGMENT SET { (parameter=value[,...]) } [ /QUALIFIERS ] 3 Parameters keywords:> o CPU_LIMIT specifies the percent of CPU usage for any one@ defragmentation process. The CPU percent is the percent of a single CPU.D o IO_LIMIT specifies the maximum direct I/O rate (per second) of& any one defragmentation process.C o PROCESS_LIMIT specifies the maximum number of defragmentation processes per node. 3 Restrictions o None. 3 Qualifiers /NODE /NODE=(node-name[,...]) /NONODE (default)8 The /NODE qualifier limits the scope of the SET9 subcommand. By default, a given parameter is set= identically on all nodes in the scheduling database.= To limit parameters to fewer nodes, specify the node( names with the /NODE qualifier. 3 Examples@ The following examples show how to set limits using the SET# subcommand and its qualifiers:> 1.$ DEFRAGMENT SET PROCESS_LIMIT=3, IO_LIMIT=14/NODE=NODE_1; In this example, the maximum number of defragmentationD processes that can occur on NODE_1 is 3. Further, a restriction> of 14 direct I/Os per second is placed on each of these 3 defragmentation processes." 2.$ DEFRAGMENT SET CPU_LIMIT=50@ In this example, the maximum CPU resources allocated to anyA defragmentation process is set to 50 percent on all nodes inA the system. If a defragmentation process exceeds this limit,B its priority is decremented each minute (approximately) until6 it reaches the SYSGEN parameter, DEFPRI, minus 1. 2 SHOWC The SHOW subcommand displays information about the fragmentation@ state of the given volume and information from the scheduling database. FormatA DEFRAGMENT SHOW { script-name|volume-name } [ /QUALIFIERS ] 3 Parameters script-name|volume-name@ The parameter for the SHOW subcommand is either a script name? or a volume name. Names can be omitted if the /ALL qualifier> is used. If a script name is supplied or if the /PARAMETERSB qualifier is specified, the SHOW command queries the schedulingC database and displays this information. You can use wildcards inD the script-name specification. Use an asterisk (*) to take actionB on all scripts on the VAXcluster system; use a percent sign (%)@ to match a single character in the script-name specification.< If a volume name is supplied (/VOLUME required), the SHOW@ command displays information about the fragmentation state ofA the specified volume. A list of names can be provided, but the4 list cannot contain both script and volume names. 3 RestrictionsB o If showing a script or volume, do not use the /ALL qualifierB o If showing a volume, then you must use the /VOLUME qualifier 3 Qualifiers /ALL /ALL /NOALL (default)< The /ALL qualifier is used to show information from9 the scheduling database. It displays information; about all scripts and parameters in the scheduling= database. If /ALL is used, the script-name parameter is not allowed. /COMMAND_LINE /COMMAND_LINE /NOCOMMAND_LINE (default)4 The /COMMAND_LINE qualifier is used to show5 information from the scheduling database. It= formats the output of the SHOW subcommand as a valid; DEFRAGMENT command line. Thus, all the data in the; scheduling database can be extracted into a file (, /ALL/COMMAND_LINE/OUTPUT=file.ext). /DEVICE, /DEVICE=(device_spec[,device_spec])...= The /DEVICE qualifier selects only the named scripts" on the specified devices. /FILE_LIST /FILE_LIST=(min_extents)/ /FILE_LIST=(VOL_MAP_WINDOW + 1) (default)5 The /FILE_LIST qualifier is used to show the< fragmentation state of a volume. It lists all files< on the volume that have min_extents or more extents; (fragments). By default, the number of file window8 mapping pointers set for the volume (INITIALIZE> {volume}/WINDOW=n) plus one is used. This value lists; all files that require at least one window turn to completely map. /FREE_LIST /FREE_LIST /NOFREE_LIST (default)5 The /FREE_LIST qualifier is used to show the8 fragmentation state of the volume. It lists the: location and size of all of the freespace extents on the volume. /HISTOGRAM /HISTOGRAM /NOHISTOGRAM (default)5 The /HISTOGRAM qualifier is used to show the: fragmentation state of a volume. It generates two8 histograms. The first plots the number of files< against the number of extents per file and provides< information about how many files are fragmented and< how badly they are fragmented. The second histogram> plots the number of freespace extents (holes) against9 the size of these freespace extents. It provides< information about how many freespace extents are on$ the volume and their sizes. /LOCATION! /LOCATION=(file-spec[,...]) /NOLOCATION4 The /LOCATION qualifier is used to show the9 fragmentation state of the volume. It prints the: extents (fragments) associated with all specified8 files. If no files are specified, the /LOCATION< qualifier appends location information to all files; listed with the /FILE_LIST qualifier. The supplied8 file-spec may contain wildcards in place of the< directory, file name, extension, or version fields. /NAMES /NAMES: The /NAMES qualifier lists only the first line of< the usual show output. The first line of the script< includes the name of the script, whether the script> is enabled or disabled, and the target device for the script. /NODE /NODE=(node-name[,...]) /NONODE (default); The /NODE qualifier selects only those scripts and; node names that are specified on the command line.< When used with the /PARAMETERS qualifier, the /NODE= qualifier displays CPU_LIMIT, IO_LIMIT, and PROCESS_7 LIMIT information for specified nodes only. If9 the /NODE qualifier is not used, the /PARAMETERS= qualifier displays this information for all nodes in! the scheduling database. /OUTPUT /OUTPUT={file-spec}" /OUTPUT=SYS$OUTPUT (default)= The /OUTPUT qualifier may be used to show the volume< fragmentation state or to show information from the: scheduling database. It directs the output of the9 SHOW subcommand to a file. By default, output is directed to SYS$OUTPUT. /PARAMETERS /PARAMETERS /NOPARAMETERS (default)> The /PARAMETERS qualifier is used to show information; from the scheduling database. It displays the CPU_< LIMIT, IO_LIMIT, and PROCESS_LIMIT settings for all: nodes in the scheduling database (unless specific; nodes are designated with the /NODE qualifier). By/ default, these settings are not shown. /RUNNING /RUNNING6 The /RUNNING qualifier shows scripts that are currently running. /STATISTICS /STATISTICS (default) /NOSTATISTICS= The /STATISTICS qualifier is used to show the volume: fragmentation state. It provides a summary of the: file and free space fragmentation for the volume. /VOLUME /VOLUME /NOVOLUME (default)7 The /VOLUME qualifier must be used to show the; fragmentation state of a volume. It indicates that8 any parameter supplied on the command line is a: volume name instead of a script name. The /VOLUME= qualifier is incompatible with any of the qualifiers= used to show database information except the /OUTPUT qualifier. 3 Examples> The following are examples of the SHOW subcommand and its qualifiers:! 1.$ DEFRAGMENT SHOW/PARAMETERS? In this example, the current values of CPU_LIMIT, IO_LIMITC and PROCESS_LIMIT for all nodes in the scheduling database are shown.2 2.$ DEFRAGMENT SHOW MY_SCRIPT/OUTPUT=OUTPUT.TXT> In this example, information associated with MY_SCRIPT is@ displayed. No parameter information is displayed. Output is* directed to a file called OUTPUT.TXT.& NOTE@ If output is directed to a filename without extension, the0 file is given a default extension of .lis.= 3. $ DEFRAGMENT SHOW MY_SCRIPT/COMMAND_LINE/PARAMETERS> In this example, information associated with MY_SCRIPT is= displayed. The current values of CPU_LIMIT, IO_LIMIT andD PROCESS_LIMIT for all nodes in the scheduling database are also@ shown. The format for the information is a valid DEFRAGMENT> command line. Output is directed to the user's SYS$OUTPUTC device. If output is directed to a filename without extension,3 the file is given a default extension of .lis.2 4.$ DEFRAGMENT SHOW MY_VOLUME/OUTPUT=OUTPUT.TXT> In this example, information associated with MY_VOLUME is? displayed. Output is directed to a file called OUTPUT.TXT.0 5.$ DEFRAGMENT SHOW DISK$ONE/VOLUME/HISTOGRAMB In this example, the volume fragmentation report includes theC summary statistics (/STATISTICS is default) and histograms forD both file fragmentation and freespace fragmentation. The report& is sent to the SYS$OUTPUT device. 2 SPAWND The Disk File Optimizer SPAWN subcommand creates a subprocess andB executes a DCL command in the subprocess, or transfers terminal7 control to the subprocess if no command is supplied. Format" DEFRAGMENT SPAWN [ command ] 3 Parameters command@ This is a DCL command string of less than 132 characters that> is to be executed in the context of the created subprocess.? After the command is executed, the subprocess terminates andC control returns to the parent process. A command is optional. If1 no command is supplied, control passes to DCL. 3 Restrictions None. 3 Qualifiers None. 3 Examples5 The following are examples of the SPAWN command: 1.$ DEFRAGMENT DFO> SPAWN $B The SPAWN command creates a subprocess and transfers terminal' control to the created subprocess. 2. DFO> SPAWN SHOW DEFAULT DISK$1:[JONES] DFO>@ The SPAWN command creates a subprocess and executes the DCLA command SHOW DEFAULT in the created subprocess. Control then7 returns to the Disk File Optimizer parent process. 2 START4 The START subcommand starts the specified script. Format< DEFRAGMENT START { script-name[,...] } [ /QUALIFIERS ] 3 Parameters script-name? The script-name parameter is the name of the script(s) to beC started. You can use wildcards in the script-name specification.; Use an asterisk (*) to take action on all scripts on the> VAXcluster system; use a percent sign (%) to match a single. character in the script-name specification. 3 Restrictions None. 3 Qualifiers /AFTER /AFTER=time /NOAFTER (default)< The /AFTER qualifier keeps the script from starting( until after the specified time.; You can specify time as either an absolute time or: as a combination of absolute and delta times. For< complete information on specifying time values, see# the OpenVMS User's Manual. 3 Examples7 The following example shows how to start a script:- 1.$ DEFRAGMENT START MY_SCRIPT/AFTER=16:30@ In this example, MY_SCRIPT is started. The /AFTER qualifier> stipulates that MY_SCRIPT should start after 16:30 of theB day this command is submitted. If the script is periodic, the period is unchanged. 2 VOLUME@ The DEFRAGMENT VOLUME subcommand defragments the volume named? on the command line according to the defragment command line qualifiers. Format8 DEFRAGMENT VOLUME { volume-name } [ /QUALIFIERS ] 3 Parameters volume-name< The volume-name parameter is the name of the volume to be defragmented. 3 RestrictionsB o A script that has the /CONTINUOUS qualifier may not be named+ as the predecessor of another script.> o If you specify the /INTERVAL qualifier, the /PREDECESSOR qualifier is not allowed.> o If /LEVEL=5 is selected, the /LOG qualifier is required./ o Do not use /BRIEF and /FULL concurrently.8 o Do not use /CONTINUOUS and /INTERVAL for a script. 3 Qualifiers /AFTER /AFTER={time}% /AFTER={current_time} (default) /NOAFTER= The /AFTER qualifier keeps the script from executing( until after the specified time.; You can specify time as either an absolute time or: as a combination of absolute and delta times. For< complete information on specifying time values, see# the OpenVMS User's Manual.9 The /AFTER qualifier has three states. It can be< specified with a valid time, it can be omitted from> the command line, or it can be negated (/NOAFTER). If= /AFTER is specified with a valid time, the script is< scheduled to execute after that time. If the /AFTER; qualifier is omitted, the defragmentation software9 processes the command as if the /AFTER qualifier: were specified with the current time. If /NOAFTER: is specified, no starting time is associated with9 the script being defined. The /NOAFTER qualifier< allows you to define a script without scheduling it> to execute. To subsequently start the script, use the START subcommand. /BRIEF /BRIEF (default) /NOBRIEF< The /BRIEF qualifier has meaning only when the /LOG8 qualifier is also present. The /BRIEF qualifier9 requests a brief log of all actions taken by the= defragmentation process. This log includes beginning9 and ending volume status information. The /BRIEF9 and /FULL qualifiers are mutually exclusive, and8 /NOBRIEF produces the same result as /FULL. The) /BRIEF qualifier is the default. /CONSOLIDATE_FREESPACE& /CONSOLIDATE_FREESPACE (default) /NOCONSOLIDATE_FREESPACE< The /CONSOLIDATE_FREESPACE qualifier tells the Disk; File Optimizer to use its free space consolidation algorithm. /CONTINUOUS /CONTINUOUS /NOCONTINUOUS (default)4 The /CONTINUOUS qualifier causes the script5 to execute repeatedly. After each successful6 defragmentation operation, the script becomes> eligible for execution again. As long as any PROCESS_: LIMITs (see the SET subcommand) are not violated,> the script executes repeatedly. If all PROCESS_LIMITs9 have been reached, the script is queued until an< outstanding defragmentation process completes, then* the script is allowed to execute.; By default, the defragmentation process associated7 with a script may execute on any appropriately5 licensed node in a cluster. Thus, successive= defragmentation processes do not necessarily execute on the same node. /DORMANT /DORMANT=(file-spec[,...]) /NODORMANT (default)5 The /DORMANT qualifier indicates files to be5 considered dormant when final file placement< decisions are made. Dormant files are placed at the high end of the volume.7 If a file is indicated in both the DORMANT and< FREQUENT lists, it is considered dormant. If a file< is indicated in both the EXCLUDE and DORMANT lists, it is excluded.) NOTE7 The amount of free space on the volume, the9 number of files currently being accessed, and7 other factors influence file placement. The7 Disk File Optimizer does not guarantee file< placement, but makes every effort to place files as described. /EPILOGUE /EPILOGUE={file-name} /NOEPILOGUE (default)> The /EPILOGUE qualifier identifies a DCL command file= which DFO executes upon completion of the DEFRAGMENT operation.9 Mounting or dismounting the disks cannot be done, through the Command file specified. /EXCLUDE /EXCLUDE=(file-spec[,...]) /NOEXCLUDE (default)> The /EXCLUDE qualifier specifies files to be excluded= from processing. The defragmentation process ignores; files matching the listed file specifications. Any9 file indicated in the EXCLUDE list and in either7 the FREQUENT or DORMANT lists is excluded from processing.) NOTE7 The defragmentation process always excludes: system files, open files, files excluded in an8 options file (/OPTIONS qualifier), and files1 excluded using the /IGNORE qualifier. /FREQUENT! /FREQUENT=(file-spec[,...]) /NOFREQUENT (default)6 The /FREQUENT qualifier indicates files to be7 considered frequently accessed when final file9 placement decisions are made. Frequent files are) placed to optimize access speed.8 If a file is indicated in both the FREQUENT and; DORMANT lists, it is considered dormant. If a file= is indicated in both the FREQUENT and EXCLUDE lists, it is excluded.) NOTE7 The amount of free space on the volume, the9 number of files currently being accessed, and7 other factors influence file placement. The7 Disk File Optimizer does not guarantee file< placement, but makes every effort to place files as described. /FULL /FULL /NOFULL (default)7 The /FULL qualifier requests a full log of all: actions taken by the defragmentation process. The= /FULL qualifier has no meaning if the /LOG qualifier7 is absent. The /FULL and /BRIEF qualifiers are: mutually exclusive, and /NOFULL provides the same! functionality as /BRIEF. /HOTFILE_DATABASE /HOTFILE_DATABASE# /NOHOTFILE_DATABASE (default)3 The /HOTFILE_DATABASE qualifier causes the6 defragmenter to query the appropriate hotfile8 database and append the list of hotfiles to the, defragmenter's /FREQUENT file list. /IGNORE /IGNORE=(keyword[,...]) /IGNORE=(PLACED) (default) /NOIGNORE0 The /IGNORE qualifier requests that the> defragmentation process ignore certain types of files0 as specified by the following keywords:1 o INDEXED-Ignores all RMS indexed files6 o NOINDEXED-May defragment RMS indexed files< o PLACED-Ignores all files with explicit placement& flags set in their headers7 o NOPLACED-May defragment files with explicit placement flags> Files indicated by the /IGNORE qualifier are added to the EXCLUDE list.: The default value (/IGNORE=PLACED) indicates that8 files with explicit placement control should be6 ignored, and that RMS indexed files should be9 defragmented and placed in appropriate locations on the volume. /INHERIT /INHERIT={script-name} /NOINHERIT (default)9 The purpose of the /INHERIT qualifier is to make: script creation easier. By inheriting most of the: command data from a previously entered script and< modifying only a few items (such as volume name), a; completely new script can be created. The /INHERIT< qualifier creates a database entry for a new script in the following way:> o Copies all fields from the specified script to the new script.; o Overwrites any qualifier or parameter values in> the new script with those specified on the command line.= o Names the new script as appropriate. The user may< specify a script name using the /SCRIPT={script-; name} qualifier. Otherwise, the defragmentation: software creates a unique script name. You can; use wildcards in the script-name specification.= Use an asterisk (*) to take action on all scripts< on the VAXcluster system; use a percent sign (%): to match a single character in the script-name specification. /INTERVAL /INTERVAL={delta-time} /NOINTERVAL (default)7 The /NOINTERVAL qualifier executes a script at5 regularly scheduled intervals. The /INTERVAL5 qualifier specifies the minimum time between, consecutive executions of a script.; Specify time as a delta time. Refer to the OpenVMS9 User's Manual for more information on specifying5 times. If you do not specify a time with the; /INTERVAL qualifier, the default value of 24 hours is used.5 If you specify the /AFTER qualifier with the7 /INTERVAL qualifier, the first defragmentation8 operation occurs at or after the time specified; by the /AFTER qualifier; all subsequent operations4 execute at intervals set with the /INTERVAL qualifier. /LEVEL /LEVEL={n} /LEVEL=2 (default)6 The defragmentation process selects files for> defragmentation (from among those not excluded) based< on the /LEVEL qualifier. Once a file is selected as: a candidate, the defragmentation process attempts; to fully defragment that file (make it 100 percent< contiguous). Specify the level number as an integer" ranging from one to five: o /LEVEL=1; Any file that is not 100 percent contiguous, or< that can be selected using levels two and three,/ is a candidate for defragmentation. o /LEVEL=2 (default)7 Any file whose extents cannot be completely8 mapped by the mapping window, or that can be: selected using level three, is a candidate for> defragmentation. The default window value is seven4 and can be set for a given volume using:2 $ SET VOLUME {device-spec}/WINDOWS=[n] o /LEVEL=3= Any file with retrieval pointers in more than one; file header is a candidate for defragmentation. o /LEVEL=46 The defragmentation process for level four> processing performs only free space consolidation.> This level is used with the /CONSOLIDATE_FREESPACE qualifier. o /LEVEL=57 This level requests a volume analysis only;6 no defragmentation occurs. The statistical; results are available in the log file, which is< required when /LEVEL=5 is selected (see the /LOG< qualifier). If level 5 is selected, the /LEVEL=2; candidate file specifications are listed in the full log file. /LOG /LOG={file-spec} /NOLOG (default)> The /LOG qualifier causes the defragmentation process6 to create a file containing a list of all its; operations. The information in the log file varies= with the presence of the /FULL or /BRIEF qualifiers.< The /FULL qualifier lists all files analyzed by the> defragmentation process and reports their disposition9 during each phase of defragmentation. The /BRIEF; qualifier lists only the statistics of each phase,> such as number of files analyzed, and number of files defragmented. /MAIL_NOTIFICATION /MAIL_NOTIFICATION$ /NOMAIL_NOTIFICATION (default)7 The /MAIL_NOTIFICATION qualifier requests that8 brief status and termination messages regarding8 defragmentation processes be mailed to the mail9 distribution list provided in the file DFG$MAIL_ ADDRESS. /NODE /NODE=(node-name[,...]) /NONODE (default)4 The /NODE qualifier limits the scope of the7 DEFRAGMENT command to the node or set of nodes4 specified by /NODE=(node-name). By default,9 defragmentation processes may execute on any LMF% licensed node in the system. /OPCOM_NOTIFICATION# /OPCOM_NOTIFICATION (default) /NOOPCOM_NOTIFICATION8 The /OPCOM_NOTIFICATION qualifier requests that8 brief status and termination messages regarding4 defragmentation processes be sent to OPCOM. /OPTIONS /OPTIONS={file-spec} /NOOPTIONS (default)< The /OPTIONS qualifier provides an alternate method> for associating files with the /DORMANT, /EXCLUDE, or> /FREQUENT qualifiers. If the list of files for any of< these qualifiers is long, you can create a separate> file for this information. Each record in the options< file consists of a file name followed by one of the following keywords:( o /EXCLUDE-File to be excluded6 o /FREQUENT-File to be considered frequently accessed2 o /DORMANT-File to be considered dormant7 The following example shows the contents of an5 options file called MYOPTFILE.OPT. This file= specifies that all files on the target device called7 FILE1.EXE are frequent files, all files in the> [ARCHIVE] directory are to be excluded, and all files; in the [OLDSTUFF] directory and its subdirectories are dormant. FILE1.EXE/FREQUENT# [ARCHIVE]*.*;*/EXCLUDE' [OLDSTUFF...]*.*;*/DORMANT9 Files indicated by the /EXCLUDE qualifier and by7 either the /DORMANT or /FREQUENT qualifier are< excluded. Files indicated by the /DORMANT qualifier6 and by the /FREQUENT qualifier are considered9 dormant. This rule is applied equally across all8 files specified in the /OPTIONS file and on the command line. /PREDECESSOR /PREDECESSOR={script-name} /NOPREDECESSOR (default)8 The /PREDECESSOR qualifier links scripts. These6 scripts execute in sequence; one successfully. completes before the next one begins.6 The predecessor script name must exist in the: scheduling database or an error status message is; returned. You can use wildcards in the script-name= specification. Use an asterisk (*) to take action on< all scripts on the VAXcluster system; use a percent< sign (%) to match a single character in the script- name specification. /PRIORITY& /PRIORITY=(DEFAULT=n, MINIMUM=n) /NOPRIORITY (default)= The /PRIORITY qualifier specifies priorities for the< defragment process. The minimum priority setting is: used when the defragmentation process exceeds the; value specified by either /CPU_LIMIT or /IO_LIMIT. /PROLOGUE /PROLOGUE={file-name} /NOPROLOGUE (default)9 The /PROLOGUE qualifier identifies a DCL command; file which DFO executes just before the Defragment operation starts.9 Mounting or dismounting the disks cannot be done, through the Command file specified. /RVN /RVN=n /RVN=0 (default)= When you have a bound volume set, use this qualifier< to identify a disk from the volume set or all disks> in the volume set. The default of zero tells the Disk< File Optimizer to defragment all disks in the bound; volume set. Specify a relative volume number (RVN)> to defragment a specific disk that belongs to a bound volume set. /SCRIPT /SCRIPT={script-name} /NOSCRIPT (default); The /SCRIPT qualifier assigns a user-supplied name= to a script. If a duplicate script-name is selected,= defragmentation software issues an error message and; does not enter the new script into the database-no% defragmentation takes place.; A script name may be up to 64 characters in length9 and may contain any of the following characters:& o Any alphanumeric character o Underscore ( _ ) o Hyphen ( - ) o Dollar sign ( $ ): Observe the following rules when naming a script:: o Use any combination of uppercase and lowercase letters.< o Do not begin script names using the dollar sign,: however you can include the dollar sign within= the script name. (The dollar sign is reserved for special use by HP.)= o Do not end a script name with a hyphen, since the5 hyphen is the DCL continuation character.= If you do not supply a script name using the /SCRIPT: qualifier, the defragmentation software generates8 a unique script name. This internally generated: name has the format DFG$SCRIPTX[X...], where X is9 a hexadecimal number that keeps the script names; unique. Names beginning with DFG$ are reserved for- use by the defragmentation software. /TIME_LIMIT /TIME_LIMIT={delta-time} /NOTIME_LIMIT (default)8 The /TIME_LIMIT qualifier specifies the maximum9 elapsed time allowed for a given defragmentation6 operation. If the time limit is exceeded, the, defragmentation process is aborted.; Specify time as a delta time. Refer to the OpenVMS9 User's Manual for more information on specifying times.8 For linked scripts, the time limit of the first5 script applies to the whole set. Time limits8 specified with successor scripts apply to these scripts only.7 If the time limit is set unreasonably low, the: defragmentation process may not accomplish useful defragmentation. /WRITE_CHECK /WRITE_CHECK /NOWRITE_CHECK (default)9 The /WRITE_CHECK qualifier requests that a read-; after-write check be performed on all defragmented> or placed files. This qualifier significantly extends9 the execution time of a defragmentation process. 3 ExamplesA The following are examples of the DEFRAGMENT VOLUME command:$ 1.$ DEFRAGMENT VOLUME DISK$USER_1C This command defragments DISK$USER_1 using default qualifiers.D The defragmentation process executes only once. In a VAXclusterB system, the defragment operation begins on a node selected atD random from among those nodes in the scheduling database having@ fewer executing processes than the limit imposed by the SETA PROCESS_LIMIT={value} subcommand. If all nodes are busy withB a maximum number of defragment processes, the script does notD execute until one of the outstanding defragmentation operations concludes.C After the defragmentation process stops, the script is removed" from the scheduling database.K 2.$ DEFRAGMENT VOLUME DISK$ONE/SCRIPT=MY_SCRIPT/IGNORE=(INDEXED,PLACED)-R /INTERVAL=2-00:00/FREQUENT=*.EXE/LOG=MYLOG.LOG/FULL/DORMANT=*.ARCHIVE- /NODE=(N1, N2)% This command does the following: o Defragments DISK$ONE.# o Names the script MY_SCRIPT.? o Instructs the defragmentation process to ignore all RMS? indexed files and files with explicit placement controlC information in their headers. (These files are added to the EXCLUDE list.)@ o Instructs the scheduler to execute this script every two days.D o Instructs the defragmentation process that all .EXE files onB the entire volume should be considered frequently accessed5 when final file placement decisions are made.> o Requests a log file, MYLOG.LOG, which is placed in the6 directory from which this command was entered." o Requests a /FULL log file.? o Instructs the defragmentation process that all .ARCHIVE? files on the entire volume should be considered dormantA (rarely accessed) when final file placement decisions are made.B o Limits the nodes available for the defragmentation process to nodes N1 and N2.G 3.$ DEFRAGMENT VOLUME DISK$TWO/INHERIT=MY_SCRIPT/SCRIPT=FIRST_SCRIPT= This command inherits the script defined in the previous? example. Thus, it creates a new script that is the same as5 MY_SCRIPT, except for the following differences:= o The script name is FIRST_SCRIPT instead of MY_SCRIPT.: o The target volume is DISK$TWO instead of DISK$ONE.A In this case, MYLOG.LOG is also inherited. Thus, one version@ of the log file contains data from MY_SCRIPT, and the otherA version contains data from FIRST_SCRIPT. To prevent log file- inheritance, specify the /LOG qualifier.7 4.$ DEFRAGMENT VOLUME DISK$ONE/SCRIPT=SECOND_SCRIPT-% /PREDECESSOR=FIRST_SCRIPT@ This commands links SECOND_SCRIPT to FIRST_SCRIPT using theA /PREDECESSOR qualifier. SECOND_SCRIPT does not execute untilD FIRST_SCRIPT completes successfully. SECOND_SCRIPT uses defaultB parameters. Note that this example uses the DEFRAGMENT VOLUME9 command from within the Disk File Optimizer utility.D 5.$ DEFRAGMENT VOLUME DISK$ONE/SCRIPT=AFTER_SCRIPT/AFTER="+00:05"D This command creates the script AFTER_SCRIPT, and it will start executing in 5 minutes. 2 RELEASE_NOTESB You can find the release notes for the defragmentation softwareB in SYS$HELP:DFGvvu.RELEASE_NOTES, where vv is the major version& number, and u is the update number.< To list all the DEFRAGMENT release notes available, type:3 $ DIRECTORY SYS$HELP:DFG*.RELEASE_NOTES. 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 distribution 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? only 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? indicate 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 system 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 error.+ 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$_ACCESS 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 course 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 failed 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 action. 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. This 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 User 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 accessed. 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 Rdb 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 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 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 database could not be read. The cause of this= problem may be an undefined logical, corrupt database, DFG? software error, or Rdb software error. This problem can also= be caused if the RMU Monitor process (RDMS_MONITOR) is 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> 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 again. 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 database 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: Submit 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 Explanation: 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.B 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: This 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 the 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 defragmentation 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 to 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; Explanation: 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 with 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 associated 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: Submit 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 messages 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 global 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 index 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" database 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 IESCHIMPOSS 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 when 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 Explanation: 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 internal 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 be 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 device 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$DEFRAGMENT0 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 an 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 logA 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 no t 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, submit 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. Associ ated 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. 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 supplied C software, submit an SPR. Otherwise, correct the calling program. 3 INVITMUKN. an item list contained an unknown item code? Explanation: This message indicates the dfg_list or sch_list@ parameter to DFG$DEFRAGMENT contained an item descriptor 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 this 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 o f action. 3 INVSCHLST invalid scheduler item list? Explanation: The scheduler list passed to DFG$DEFRAGMENT was invalid.B User Action: If the call to 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. 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 DFG$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 qualifier; 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_LOGICAL& 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 Explanation: 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 columns 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, submit 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 processC 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 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 information 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 defragmentation 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,D 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 defragmentation 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 interface. 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 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 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 exists 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 m essages to determine if additional action is necessary. 3 NOPRED# predecessor script !AD not foundB Explanation: The script specified in the /PREDECESSOR qualifier. could not be found in the SCRIPTS relation.? User Action: Check spelling of the script name used with 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; yo!u need BYPASS, CMKRNL, DETACH,D EXQUOTA, NETMBX, SHARE, SYSGBL, SYSLCK, SYSPRV, TMPMBX, and WORLD; Explanation: The user has insufficient privileges to run DEFRAGMENT.@ User Action: Set the BYPASS, CMKRNL, DETACH, EXQUOTA, NETMBX,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 enab"led. (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 name. 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 is 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 the 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 paramete%r. 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 notification 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 Action: 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 the volume.; User Action: Before defragmenting INDEXF.SYS, be sure to? defragment the volume and consolidate free space. Also, make@ sure that the largest free space on the volume is larger than= INDEXF.SYS. To check the largest free space and extents of- INDEXF.SYS, execute the following command:A ( $ DEFRAGMENT SHOW disk:/VOLUME/LOCATION=[000000]INDEXF.SYS 3 NOTFILWRERR/ error writing to temporary notification file> Explanation: The notification message could 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: Nonloc)al 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 device 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 Associated 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 con+tain 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 NULLENGINE= 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 input,A Explanation: The specified file could not be opened for input.+ Associated messages indicate the reason.B User Action: Refer to associated messages to determine a 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 associate-d messages to determine a course of action. 3 OPENOUT error opening !AD as outputB Explanation: The specified file could not be opened for output.+ Associated 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 defragme.ntation volume.= User Action: Correct the invalid line in the options file.= Specify no device name, or specify the target device name. 3 OPTFILERR options 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 spe/cified 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 remove 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: /0FREQUENT, /DORMANT, /EXCLUDE.C User Action: Check spelling and ensure that only classificationsC of /FREQUENT, /DORMANT, or /EXCLUDE are used for files listed in the 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 classifica1tion 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 $SEA2RCH RMS routines.@ User Action: Refer to the specified line in the options file.7 Also check associated messages for more information. 3 PARSEFAIL error parsing !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: Sp3ecify 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 qu4alifier 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 5has 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. 63 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: 7 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 re8moved. 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 REMOVENOT9DONE 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 sched;uling 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 procedur<e. 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 alr=eady 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 n?ode !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> Explana@tion: 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 Anot 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 tBo 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 Cnot 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 listDed 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 Eis 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 aF 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 exactG: 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 H 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. ThisIA 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 mJore 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.wwLpv̫r± 1 DEFRAGMENT= Invokes the Disk File Optimizer. This utility is a layered@ product that restores file contiguity while the target volume: remains on line and accessible. The Disk File Optimizer; is compatible with any Files-11 structure levels 2 or 5 = (ODS-2, ODS-5) formatted volume including single volumes, 1 bound volume sets, stripe sets or shadow sets. Format DEFRAGMENT [ /INTERFACE ] 2 Qualifiers /INTERFACE( /INTMERFACE=CHARACTER_CELL(default) /INTERFACE=DECWINDOWS< The /INTERFACE qualifier allows you to start up the6 Disk File Optimizer with either the character= cell terminal interface or the DECwindows interface. 2 ABORTA The ABORT subcommand terminates the execution of the script or) scripts specified in the command line. Format< DEFRAGMENT ABORT { script-name[,...] } [ /QUALIFIERS ] 3 Parameters script-name< The sNcript-name parameter is the name of the script to beC aborted. You can use wildcards in the script-name specification.; Use an asterisk (*) to take action on all scripts on the> VMScluster system. Use a percent sign (%) to match a single. character in the script-name specification. 3 Restrictions< o You cannot use the script-name parameter with the /ALL qualifier. 3 Qualifiers /AFTER /AFTER={time} /NOAFTER (default)9 TheO /AFTER qualifier keeps the script from being0 aborted until after the specified time.; You can specify time as either an absolute time or: as a combination of absolute and delta times. For< complete information on specifying time values, see% the VMS DCL Concepts Manual. /ALL /ALL /NOALL (default): The /ALL qualifier aborts all currently executing5 scripts across the system. This qualifier is9 funPctionally equivalent to using an asterisk (*)' for the script-name parameter. 3 Examples? The following examples show how the ABORT command functions. 1.+ $ DEFRAGMENT ABORT MY_SCRIPT/AFTER=16:30D This command aborts MY_SCRIPT after 16:30 on the day this command is submitted. 2. $ DEFRAGMENT ABORT/ALLB This command immediately aborts all currently executing scripts in the entire system. 2 ATTACHD The ATTACH subcommand traQnsfers control from your current process4 (which then hibernates) to the specified process. Format8 DEFRAGMENT ATTACH { process-name } [ /QUALIFIERS ] 3 Parameters process-name< The process-name specifies the name of a process to whichB control passes. The process must already exist, be part of your? current job, and share the same input stream as your currentD process. However, the process cannot be your current process or a1 subprocess created withR the /NOWAIT qualifier.B Process names can contain from 1 to 15 alphanumeric characters.D If a connection to the specified process cannot be made, an error message is displayed. 3 Restrictions? o The ATTACH command cannot be used if your terminal has an associated mailbox.8 o You cannot use the process-name parameter with the /IDENTIFICATION qualifier.= o You must supply either a process name or a PID for this command. 3 QualifierSs /IDENTIFICATION /IDENTIFICATION=pid5 /IDENTIFICATION lets you specify the process> identification (PID) of the process to which terminal: control will be transferred. Leading zeros can be omitted. 3 ExamplesB The following examples show how you can use the ATTACH command. 1. $ DEFRAGMENT ATTACH JONES_2> This ATTACH command transfers the terminal's control to the subprocess named JONES_2. 2./ $T DEFRAGMENT ATTACH /IDENTIFICATION=2A401A1BC This ATTACH command switches control from the current process to% the process whose PID is 2A401A1B. 2 CANCELB The CANCEL subcommand skips the next scheduled execution of the) scripts specified in the command line. Format7 DEFRAGMENT CANCEL { script-name } [ /QUALIFIERS ] 3 Parameters script-name= The script-name parameter is the name of the scripts to beD canceled. You can use wildcards iUn the script-name specification.; Use an asterisk (*) to take action on all scripts on the> VMScluster system. Use a percent sign (%) to match a single. character in the script-name specification. 3 RestrictionsD o The script-name parameter is not allowed if the /ALL qualifier is used. 3 Qualifiers /ALL /ALL /NOALL (default)6 The /ALL qualifier cancels the next scheduled7 execution of all scripts in the scheduling anVd parameter database. 3 Example= The following example shows how to use the CANCEL command. 1.- $ DEFRAGMENT CANCEL MY_SCRIPT, YOUR_SCRIPTA In this example, the next scheduled execution of MY_SCRIPT andB YOUR_SCRIPT are canceled. Afterwards, both scripts resume their normal schedule. 2 DISABLEC The DISABLE subcommand makes the specified script ineligible forC execution. Currently executing scripts are not affected. Use the8 ABORT subWcommand to stop currently executing scripts. Format8 DEFRAGMENT DISABLE { script-name } [ /QUALIFIERS ] 3 Parameters script-nameB The script-name parameter specifies the scripts to be disabled.A You can use wildcards in the script-name specification. Use an? asterisk (*) to take action on all scripts on the VMSclusterD system. Use a percent sign (%) to match a single character in the script-name specification. 3 RestrictionsD o The scXript-name parameter is not allowed if the /ALL qualifier is used. 3 Qualifiers /ALL /ALL /NOALL (default)= The /ALL qualifier indicates that all scripts in the> scheduling and parameter database should be disabled. 3 Example7 The following example shows how to disable a script. 1.! $ DEFRAGMENT DISABLE MY_SCRIPT1 In this example, script MY_SCRIPT is disabled. 2 ENABLE; The ENABLE subcommand reactivYates scripts that have been disabled. Format7 DEFRAGMENT ENABLE { script-name } [ /QUALIFIERS ] 3 Parameters script-nameC The script-name specifies the name of the scripts to be enabled.A You can use wildcards in the script-name specification. Use an? asterisk (*) to take action on all scripts on the VMSclusterD system. Use a percent sign (%) to match a single character in the script-name specification. 3 RestrictionsD o The scZript-name parameter is not allowed if the /ALL qualifier is used. 3 Qualifiers /ALL /ALL /NOALL (default)7 The /ALL qualifier indicates that all disabled9 scripts in the scheduling and parameter database should be enabled. 3 Examples= The following examples show how to use the ENABLE command. 1. $ DEFRAGMENT ENABLE/ALLC In this example, all previously deactivated scripts are enabled.> The enabl[ed script executes according to its previously set schedule.< Enabled predecessor or successor scripts resume executing( according to their link dependencies. 2. $ DEFRAGMENT ENABLE MY_SCRIPTD In this example, MY_SCRIPT is enabled. MY_SCRIPT starts executing= according to the parameters and qualifiers assigned to it. 2 EXIT8 The EXIT subcommand exits the user from the Disk File Optimizer utility. Format DEFRAGMENT EXIT 3 Paramet\ers None. 3 Restrictions None. 3 Qualifiers None. 3 Example; The following example shows how to use the EXIT command. 1. DFO> EXIT $; This command exits the user from the Disk File Optimizer utility and returns to DCL. 2 FILE? The DEFRAGMENT FILE command defragments the files given as aD parameter on the command line according to the DEFRAGMENT commandD line qualifiers. Use this command to defragment a small numbe]r ofC files. To defragment a large number of files, use the DEFRAGMENT VOLUME command. Format9 DEFRAGMENT FILE { file-spec[,...] } [ /QUALIFIERS ] 3 Parameters file-spec[,...]= The file-spec parameter identifies the file or files to beB defragmented. You can use wildcards for the file specification. 3 RestrictionsB o A script that has the /CONTINUOUS qualifier may not be named+ as the predecessor of another script.> o If you^ specify the /INTERVAL qualifier, the /PREDECESSOR qualifier is not allowed.> o If /LEVEL=5 is selected, the /LOG qualifier is required./ o Do not use /BRIEF and /FULL concurrently. 3 Qualifiers /AFTER /AFTER={time}% /AFTER={current_time} (default) /NOAFTER= The /AFTER qualifier keeps the script from executing( until after the specified time.; You can specify time as either an absolute time or: as _a combination of absolute and delta times. For< complete information on specifying time values, see% the VMS DCL Concepts Manual.9 The /AFTER qualifier has three states. It can be< specified with a valid time, it can be omitted from> the command line, or it can be negated (/NOAFTER). If= /AFTER is specified with a valid time, the script is< scheduled to execute after that time. If the /AFTER; qualifier is omitted, the defragm`entation software9 processes the command as if the /AFTER qualifier: were specified with the current time. If /NOAFTER: is specified, no starting time is associated with9 the script being defined. The /NOAFTER qualifier< allows you to define a script without scheduling it> to execute. To subsequently start the script, use the START subcommand. /BRIEF /BRIEF (default) /NOBRIEF< The /BRIEF qualifier haas meaning only when the /LOG8 qualifier is also present. The /BRIEF qualifier9 requests a brief log of all actions taken by the= defragmentation process. This log includes beginning7 and ending file status information. The /BRIEF9 and /FULL qualifiers are mutually exclusive, and8 /NOBRIEF produces the same result as /FULL. The) /BRIEF qualifier is the default. /CONSOLIDATE_FREESPACE /CONSOLIDATE_FREESPACE( /NOCONbSOLIDATE_FREESPACE (default)7 The /CONSOLIDATE_FREESPACE qualifier tells the2 Disk File Optimizer to use its free space! consolidation algorithm. /DORMANT /DORMANT=(file-spec[,...]) /NODORMANT (default)5 The /DORMANT qualifier indicates files to be5 considered dormant when final file placement< decisions are made. Dormant files are placed on the< volume to allow placing other files in optimum disk< c locations. In general, they are placed further away< from the ODS-2 data structures than /FREQUENT files0 and files not classified in any manner.7 If a file is indicated in both the DORMANT and< FREQUENT lists, it is considered dormant. If a file< is indicated in both the EXCLUDE and DORMANT lists, it is excluded.) NOTE7 The amount of free space on the volume, the9 number of dfiles currently being accessed, and9 other factors influence file placement. Thus,6 the Disk File Optimizer does not guarantee; file placement, but makes every effort to place files as described.8 The file-spec field allows wildcard characters.8 You can specify wildcard characters in place of: the directory name, file name, file type, or file< version number field. The default file-spec for all< wildcared operations is DISK:[000000...]*.*;*. Thus,< specifying *.TMP;* selects all *.TMP;* files on the entire volume. /EPILOGUE /EPILOGUE={file-name} /NOEPILOGUE (default)> The /EPILOGUE qualifier identifies a DCL command file= which DFO executes upon completion of the DEFRAGMENT FILE operation. /EXCLUDE /EXCLUDE=(file-spec[,...]) /NOEXCLUDE (default)> The /EXCLUDE qualifier specifies files to f be excluded= from processing. The defragmentation process ignores; files matching the listed file specifications. Any9 file indicated in the EXCLUDE list and in either7 the FREQUENT or DORMANT lists is excluded from processing.8 The file-spec field allows wildcard characters.8 You can specify wildcard characters in place of: the directory name, file name, file type, or file< version number field. The default file-gspec for all< wildcard operations is DISK:[000000...]*.*;*. Thus,< specifying *.TMP;* selects all *.TMP;* files on the entire volume.) NOTE7 The defragmentation process always excludes: system files, open files, files excluded in an8 options file (/OPTIONS qualifier), and files1 excluded using the /IGNORE qualifier. /FREQUENT! /FREQUENT=(file-spec[,...]) /NOFhREQUENT (default)6 The /FREQUENT qualifier indicates files to be7 considered frequently accessed when final file9 placement decisions are made. Frequent files are) placed to optimize access speed.8 If a file is indicated in both the FREQUENT and; DORMANT lists, it is considered dormant. If a file= is indicated in both the FREQUENT and EXCLUDE lists, it is excluded.) NOTE7 i The amount of free space on the volume, the9 number of files currently being accessed, and9 other factors influence file placement. Thus,6 the Disk File Optimizer does not guarantee; file placement, but makes every effort to place files as described.8 The file-spec field allows wildcard characters.8 You can specify wildcard characters in place of: the directory name, file name, file type, or file< j version number field. The default file-spec for all< wildcard operations is DISK:[000000...]*.*;*. Thus,< specifying *.TMP;* selects all *.TMP;* files on the entire volume. /FULL /FULL /NOFULL (default)7 The /FULL qualifier requests a full log of all: actions taken by the defragmentation process. The= /FULL qualifier has no meaning if the /LOG qualifier7 is absent. The /FULL and /BRIEF qualifiers arke: mutually exclusive, and /NOFULL provides the same! functionality as /BRIEF. /HOTFILE_DATABASE /HOTFILE_DATABASE# /NOHOTFILE_DATABASE (default)3 The /HOTFILE_DATABASE qualifier causes the6 defragmenter to query the appropriate hotfile8 database and append the list of hotfiles to the, defragmenter's /FREQUENT file list. /IGNORE /IGNORE=(keyword[,...]) /IGNORE=(PLACED) (default) /NOIGNlORE0 The /IGNORE qualifier requests that the> defragmentation process ignore certain types of files0 as specified by the following keywords:1 o INDEXED-Ignores all RMS indexed files6 o NOINDEXED-May defragment RMS indexed files< o PLACED-Ignores all files with explicit placement& flags set in their headers7 o NOPLACED-May defragment files with explicit placement flags> Files indicatedm by the /IGNORE qualifier are added to the EXCLUDE list.: The default value (/IGNORE=PLACED) indicates that8 files with explicit placement control should be6 ignored, and that RMS indexed files should be9 defragmented and placed in appropriate locations on the volume. /INHERIT /INHERIT={script-name} /NOINHERIT (default)9 The purpose of the /INHERIT qualifier is to make: script creation easier. By ninheriting most of the: command data from a previously entered script and< modifying only a few items (such as volume name), a; completely new script can be created. The /INHERIT< qualifier creates a database entry for a new script in the following way:> o Copies all fields from the specified script to the new script.; o Overwrites any qualifier or parameter values in> the new script with those specified oon the command line.= o Names the new script as appropriate. The user may< specify a script name using the /SCRIPT={script-; name} qualifier. Otherwise, the defragmentation: software creates a unique script name. You can; use wildcards in the script-name specification.= Use an asterisk (*) to take action on all scripts< on the VMScluster system. Use a percent sign (%): to match a single chparacter in the script-name specification. /INTERVAL /INTERVAL={delta-time} /NOINTERVAL (default); The /INTERVAL qualifier causes a script to execute8 at regularly scheduled intervals. The /INTERVAL9 qualifier specifies the minimum time between two, consecutive executions of a script.; Specify time as a delta time. Refer to the VMS DCL; Concepts Manual for more information on specifying5 times q. If you do not specify a time with the; /INTERVAL qualifier, a default value of one day is= used. This value causes the associated script to run every 24 hours.5 If you specify the /AFTER qualifier with the7 /INTERVAL qualifier, the first defragmentation8 operation occurs at or after the time specified; by the /AFTER qualifier; all subsequent operations< execute at intervals set according to the /INTERVAL qualirfier. /LEVEL /LEVEL={n} /LEVEL=1 (default)6 The defragmentation process selects files for> defragmentation (from among those not excluded) based< on the /LEVEL qualifier. Once a file is selected as: a candidate, the defragmentation process attempts; to fully defragment that file (make it 100 percent< contiguous). Specify the level number as an integer" ranging from one to five: o /LEVEL=1 (default)s; Any file that is not 100 percent contiguous, or= can be selected using levels two through four, is, a candidate for defragmentation. o /LEVEL=2> Any file whose extents cannot be completely mapped: by the mapping window, or that can be selected: using levels three or four, is a candidate for> defragmentation. The default window value is seven4 and can be set for a given volume using:2t $ SET VOLUME {device-spec}/WINDOWS=[n] o /LEVEL=3= Any file with retrieval pointers in more than one< file header, or that can be selected using level5 four, is a candidate for defragmentation.  o /LEVEL=4> The defragmentation process for level 4 processing> performs only free space consolidation. This level9 is used in conjunction with the /CONSOLIDATE_ FREESPACE qualifuier. o /LEVEL=57 This level requests a volume analysis only;6 no defragmentation occurs. The statistical8 results are available in the log file, which: is required when /LEVEL=5 is selected (see the; /LOG qualifier). If level five is selected, the= /LEVEL=2 candidate file specifications are listed! in the full log file. /LOG /LOG={file-spec} /NOLOG (default)> The / vLOG qualifier causes the defragmentation process6 to create a file containing a list of all its; operations. The information in the log file varies= with the presence of the /FULL or /BRIEF qualifiers.< The /FULL qualifier lists all files analyzed by the> defragmentation process and reports their disposition. during each phase of defragmentation.: The /BRIEF qualifier lists only the statistics of: each phase, such as number wof files analyzed, and& number of files defragmented. /MAIL_NOTIFICATION /MAIL_NOTIFICATION$ /NOMAIL_NOTIFICATION (default)7 The /MAIL_NOTIFICATION qualifier requests that8 brief status and termination messages regarding8 defragmentation processes be mailed to the mail9 distribution list provided in the file DFG$MAIL_ ADDRESS. /NODE /NODE=(node-name[,...]) /NONODE (default)4 The /xNODE qualifier limits the scope of the7 DEFRAGMENT command to the node or set of nodes4 specified by /NODE=(node-name). By default,9 defragmentation processes may execute on any LMF% licensed node in the system. /OPCOM_NOTIFICATION# /OPCOM_NOTIFICATION (default) /NOOPCOM_NOTIFICATION8 The /OPCOM_NOTIFICATION qualifier requests that8 brief status and termination messages regarding4 defragmentation processes bye sent to OPCOM. /OPTIONS /OPTIONS={file-spec} /NOOPTIONS (default)< The /OPTIONS qualifier provides an alternate method; for associating files with the /DORMANT, /EXCLUDE,> or /FREQUENT qualifiers. If the list of files for any; of these qualifiers is quite large, you can create= a separate file that contains this information. Each; record in the options file consists of a file name3 followed by one of the fozllowing keywords:( o /EXCLUDE-File to be excluded6 o /FREQUENT-File to be considered frequently accessed2 o /DORMANT-File to be considered dormant7 The following example shows the contents of an5 options file called MYOPTFILE.OPT. This file= specifies that all files on the target device called7 FILE1.EXE are frequent files, all files in the> [ARCHIVE] directory are to be excluded, and all files; { in the [OLDSTUFF] directory and its subdirectories are dormant. FILE1.EXE/FREQUENT# [ARCHIVE]*.*;*/EXCLUDE' [OLDSTUFF...]*.*;*/DORMANT9 Files indicated by the /EXCLUDE qualifier and by7 either the /DORMANT or /FREQUENT qualifier are< excluded. Files indicated by the /DORMANT qualifier6 and by the /FREQUENT qualifier are considered9 dormant. This rule is applied equally across all9 fil|es specified in the /OPTIONS file, as well as> those associated with these qualifiers on the command line. /PREDECESSOR /PREDECESSOR={script-name} /NOPREDECESSOR (default)8 The /PREDECESSOR qualifier links scripts. These6 scripts execute in sequence; one successfully. completes before the next one begins.6 The predecessor script name must exist in the: scheduling database or an error status message is; } returned. You can use wildcards in the script-name= specification. Use an asterisk (*) to take action on< all scripts on the VMScluster system. Use a percent< sign (%) to match a single character in the script- name specification. /PRIORITY& /PRIORITY=(DEFAULT=n, MINIMUM=n) /NOPRIORITY (default)= The /PRIORITY qualifier specifies priorities for the% defragment volume operation. /PROLOGUE /PROLOGU~E={file-name} /NOPROLOGUE (default)> The /PROLOGUE qualifier identifies a DCL command file; which DFO executes just before the DEFRAGMENT FILE operation starts. /RVN /RVN=n /RVN=0 (default)= When you have a bound volume set, use this qualifier< to identify a disk from the volume set or all disks9 in the volume set. The default of zero tells the4 Disk File Optimizer to defragment all disks;  in the bound volume set. Specify a relative volume8 number (RVN) to defragment a specific disk that' belongs to a bound volume set. /SCRIPT /SCRIPT={script-name} /NOSCRIPT (default); The /SCRIPT qualifier assigns a user-supplied name= to a script. If a duplicate script-name is selected,; defragmentation software issues a duplicate script= name error message and does not enter the new script: into the database-no defragmentation takes place.; A script name may be up to 64 characters in length9 and may contain any of the following characters:& o Any alphanumeric character o Underscore ( _ ) o Hyphen ( - ) o Dollar sign ( $ ): Observe the following rules when naming a script:8 o You can use any combination of uppercase and lowercase letters.: o You cannot begin script names using the dollar< sign, but you can include the dollar sign within= the script name. (The dollar sign is reserved for: special use by Digital Equipment Corporation.); o You should not end a script name with a hyphen,4 since the hyphen is the DCL continuation character.> The VMS DCL Concepts Manual contains more information on naming conventions. /TIME_LIMIT /TIME_LIMIT={delta-time} /NOTIME_LIMIT (default)8 The /TIME_LIMIT qualifier specifies the maximum9 elapsed time allowed for a given defragmentation6 operation. If the time limit is exceeded, the, defragmentation process is aborted.; Specify time as a delta time. Refer to the VMS DCL; Concepts Manual for more information on specifying times.8 For linked scripts, the time limit of the first5 script applies to the whole set. Time limits8  specified with successor scripts apply to these scripts only.7 If the time limit is set unreasonably low, the: defragmentation process may not accomplish useful defragmentation. /WRITE_CHECK /WRITE_CHECK /NOWRITE_CHECK (default)9 The /WRITE_CHECK qualifier requests that a read-; after-write check be performed on all defragmented> or placed files. This qualifier significantly extends9 the execution time of a defragmentation process. 3 Examples= The following examples show different ways to defragment a> file or group of files and illustrate how to use the common qualifiers. 1. $ DEFRAGMENT FILE *.C@ This command defragments all files with a .C extension on theD user's current default device. That is, the device portion of theD directory specification returned from a DCL SHOW DEFAULT command.. The RMS default string is [000000...]*.*;*. 2. DFO> DEFRAGMENT FILE *.C@ This command defragments all files with a .C extension on theB user's current default device. The only difference between thisC command and the previous example is that this command is entered> from within the Disk File Optimizer utility instead of from the DCL prompt. 3.. $ DEFRAGMENT FILE *.C/VOLUME=SYS$SYSDEVICE:D This command is the same as the previous one, except that the RMS8 default string is now SYS$SYSDEVICE:[000000...]*.C;*. 4.: $ DEFRAGMENT FILE SYS$LOGIN:LOGIN.COM;2/EXCLUDE=*.OLD;*B This command defragments the user's LOGIN.COM file and excludes# all files with a .OLD extension. 5.6 $ DEFRAGMENT FILE/INHERIT=OTHER_FILE_SCRIPT.NOAFTER> This commands creates a file script identical to the OTHER_9 FILE_SCRIPT and allows the Disk File Optimizer to name it (DFG$XXX). 6.$ $ DEFRAGMENT FILE *.RDB/INHERIT=X $_/SCRIPT=Y/VOLUME=SYS$SYSTEMB This command creates a script called Y that defragments all RDBA files on SYS$SYSTEM. Other script characteristics, such as log% file, are inherited from script X. 2 HELP9 The HELP subcommand invokes VMS help for the Disk File Optimizer utility. Format DEFRAGMENT HELP 3 Parameters None. 3 Restrictions None. 3 Qualifiers None. 3 ExamplesC The following examples show the various ways you can access HELP' for the Disk File Optimizer utility. 1. $ DEFRAGMENT HELP8 This command invokes HELP for the Disk File Optimizer utility directly from DCL. 2. $ HELP DEFRAGMENT8 This command invokes HELP for the Disk File Optimizer utility directly from DCL. 3. DFO> HELP6 This command invokes HELP from within the Disk File Optimizer utility. 2 MODIFY< The MODIFY subcommand allows you to change the qualifiers' associated with a particular script. Format7 DEFRAGMENT MODIFY { script-name } [ /QUALIFIERS ] 3 Parameters script-nameA The script-name parameter identifies the script to modify. You= can use wildcards in the script-name specification. Use an? asterisk (*) to take action on all scripts on the VMSclusterD system. Use a percent sign (%) to match a single character in the script-name specification. 3 RestrictionsB o A script that has the /CONTINUOUS qualifier may not be named+ as the predecessor of another script.> o If you specify the /INTERVAL qualifier, the /PREDECESSOR qualifier is not allowed.> o If /LEVEL=5 is selected, the /LOG qualifier is required./ o Do not use /BRIEF and /FULL concurrently.8 o Do not use /CONTINUOUS and /INTERVAL for a script. 3 Qualifiers /AFTER /AFTER={time}% /AFTER={current_time} (default) /NOAFTER= The /AFTER qualifier keeps the script from exec uting( until after the specified time.; You can specify time as either an absolute time or: as a combination of absolute and delta times. For< complete information on specifying time values, see% the VMS DCL Concepts Manual.9 The /AFTER qualifier has three states. It can be< specified with a valid time, it can be omitted from> the command line, or it can be negated (/NOAFTER). If= /AFTER is specified with a valid time, the script is< scheduled to execute after that time. If the /AFTER; qualifier is omitted, the defragmentation software9 processes the command as if the /AFTER qualifier: were specified with the current time. If /NOAFTER: is specified, no starting time is associated with9 the script being defined. The /NOAFTER qualifier< allows you to define a script without scheduling it> to execute. To subsequently start the script, use the START subcommand. /BRIEF /BRIEF (default) /NOBRIEF< The /BRIEF qualifier has meaning only when the /LOG8 qualifier is also present. The /BRIEF qualifier9 requests a brief log of all actions taken by the= defragmentation process. This log includes beginning9 and ending volume status information. The /BRIEF9 and /FULL qualifiers are mutually exclusive, and8 /NOBRIEF produces the same result as /FULL. The) /BRIEF qualifier is the default. /CONSOLIDATE_FREESPACE /CONSOLIDATE_FREESPACE( /NOCONSOLIDATE_FREESPACE (default)7 The /CONSOLIDATE_FREESPACE qualifier tells the2 Disk File Optimizer to use its free space! consolidation algorithm. /CONTINUOUS /CONTINUOUS /NOCONTINUOUS (default)8 The /CONTINUOUS qualifier links the script with< itself. Thus, the script repeatedly executes. After>  each successful defragmentation operation, the script9 becomes eligible for execution again. As long as8 any PROCESS_LIMITs (see the SET subcommand) are9 not violated, the script executes repeatedly. If< all PROCESS_LIMITs have been reached, the script is< queued until an outstanding defragmentation process: completes, then the script is allowed to execute.; By default, the defragmentation process associated7 with a script may execute on any appropriately5 licensed node in a cluster. Thus, successive= defragmentation processes do not necessarily execute on the same node. /DORMANT /DORMANT=(file-spec[,...]) /NODORMANT (default)5 The /DORMANT qualifier indicates files to be5 considered dormant when final file placement< decisions are made. Dormant files are placed on the< volume to allow placing other files in optimum disk< locations. In general, they are placed further away; from the ODS-2 data structures than frequent files0 and files not classified in any manner.7 If a file is indicated in both the DORMANT and< FREQUENT lists, it is considered dormant. If a file< is indicated in both the EXCLUDE and DORMANT lists, it is excluded.) NOTE7 The amount of free space on the volume, the9 number of files currently being accessed, and9 other factors influence file placement. Thus,6 the Disk File Optimizer does not guarantee; file placement, but makes every effort to place files as described.8 The file-spec field allows wildcard characters.8 You can specify wildcard characters in place of: the directory name, file name, file type, or file< version number field. The default file-spec for all<  wildcard operations is DISK:[000000...]*.*;*. Thus,< specifying *.TMP;* selects all *.TMP;* files on the entire volume. /EPILOGUE /EPILOGUE={file-name} /NOEPILOGUE (default)> The /EPILOGUE qualifier identifies a DCL command file= which DFO executes upon completion of the DEFRAGMENT FILE operation. /EXCLUDE /EXCLUDE=(file-spec[,...]) /NOEXCLUDE (default)> The /EXCLUDE qualifier specifie s files to be excluded= from processing. The defragmentation process ignores; files matching the listed file specifications. Any9 file indicated in the EXCLUDE list and in either7 the FREQUENT or DORMANT lists is excluded from processing.8 The file-spec field allows wildcard characters.8 You can specify wildcard characters in place of: the directory name, file name, file type, or file< version number field. The default file-spec for all< wildcard operations is DISK:[000000...]*.*;*. Thus,< specifying *.TMP;* selects all *.TMP;* files on the entire volume.) NOTE7 The defragmentation process always excludes: system files, open files, files excluded in an8 options file (/OPTIONS qualifier), and files1 excluded using the /IGNORE qualifier. /FILES /FILES=(file-spec[,...])>  The /FILES qualifier modifies the list of files to be defragmented. /FREQUENT! /FREQUENT=(file-spec[,...]) /NOFREQUENT (default)6 The /FREQUENT qualifier indicates files to be7 considered frequently accessed when final file9 placement decisions are made. Frequent files are) placed to optimize access speed.8 If a file is indicated in both the FREQUENT and; DORMANT lists, it is considered dormant. If a file= is indicated in both the FREQUENT and EXCLUDE lists, it is excluded.) NOTE7 The amount of free space on the volume, the9 number of files currently being accessed, and9 other factors influence file placement. Thus,6 the Disk File Optimizer does not guarantee; file placement, but makes every effort to place files as described.8 The file-spec field allows wildcard characters.8 You can specify wildcard characters in place of: the directory name, file name, file type, or file< version number field. The default file-spec for all< wildcard operations is DISK:[000000...]*.*;*. Thus,< specifying *.TMP;* selects all *.TMP;* files on the entire volume. /FULL /FULL /NOFULL (default)7 The /FULL qualifier requests a full log of all: actions taken by the defragmentation process. The= /FULL qualifier has no meaning if the /LOG qualifier7 is absent. The /FULL and /BRIEF qualifiers are: mutually exclusive, and /NOFULL provides the same! functionality as /BRIEF. /HOTFILE_DATABASE /HOTFILE_DATABASE# /NOHOTFILE_DATABASE (default)3 The /HOTFILE_DATABASE qualifier causes the6 defragmenter to query the appropriate hotfile8 database and append the list of hotfiles to the, defragmenter's /FREQUENT file list. /IGNORE /IGNORE=(keyword[,...]) /IGNORE=(PLACED) (default) /NOIGNORE0 The /IGNORE qualifier requests that the> defragmentation process ignore certain types of files0 as specified by the following keywords:1 o INDEXED-Ignores all RMS indexed files6 o NOINDEXED-May defragment RMS indexed files< o PLACED-Ignores all files with explicit placement&  flags set in their headers7 o NOPLACED-May defragment files with explicit placement flags> Files indicated by the /IGNORE qualifier are added to the EXCLUDE list.: The default value (/IGNORE=PLACED) indicates that8 files with explicit placement control should be6 ignored, and that RMS indexed files should be9 defragmented and placed in appropriate locations on the volume. /INTERVAL /INTERVAL={delta-time} /NOINTERVAL (default): Causes a script to execute at regularly scheduled9 intervals. The /INTERVAL qualifier specifies the= minimum time between two consecutive executions of a script.; Specify time as a delta time. Refer to the VMS DCL; Concepts Manual for more information on specifying5 times. If you do not specify a time with the9 /INTERVAL qualifier, a default value of 1 day is=  used. This value causes the associated script to run every 24 hours. 5 If you specify the /AFTER qualifier with the7 /INTERVAL qualifier, the first defragmentation8 operation occurs at or after the time specified; by the /AFTER qualifier; all subsequent operations< execute at intervals set according to the /INTERVAL qualifier. /LEVEL /LEVEL={n} /LEVEL=2 (default)6 The defragmentation pro cess selects files for> defragmentation (from among those not excluded) based< on the /LEVEL qualifier. Once a file is selected as: a candidate, the defragmentation process attempts; to fully defragment that file (make it 100 percent< contiguous). Specify the level number as an integer" ranging from one to five: o /LEVEL=1; Any file that is not 100 percent contiguous, or= can be selected using levels two through four, is, a candidate for defragmentation. o /LEVEL=2 (default)> Any file whose extents cannot be completely mapped: by the mapping window, or that can be selected: using levels three or four, is a candidate for> defragmentation. The default window value is seven4 and can be set for a given volume using:3 $ SET VOLUME {device-spec}/WINDOWS=[n] o /LEVEL=3= Any file with retrieval pointers in more than one< file header, or that can be selected using level5 four, is a candidate for defragmentation. o /LEVEL=4> The defragmentation process for level 4 processing> performs only free space consolidation. This level9 is used in conjunction with the /CONSOLIDATE_ FREESPACE qualifier. o /LEVEL=57 This level requests a volume analysis only;6 no defragmentation occurs. The statistical8 results are available in the log file, which: is required when /LEVEL=5 is selected (see the; /LOG qualifier). If level five is selected, the= /LEVEL=2 candidate file specifications are listed! in the full log file. /LOG /LOG={file-spec} /NOLOG (default)> The /LOG qualifier causes the defragmentation process6 to create a file containing a list of all its;  operations. The information in the log file varies= with the presence of the /FULL or /BRIEF qualifiers.< The /FULL qualifier lists all files analyzed by the> defragmentation process and reports their disposition9 during each phase of defragmentation. The /BRIEF; qualifier lists only the statistics of each phase,> such as number of files analyzed, and number of files defragmented. /MAIL_NOTIFICATION /MAIL_NOTIFICATION$ /NOMAIL_NOTIFICATION (default)7 The /MAIL_NOTIFICATION qualifier requests that8 brief status and termination messages regarding8 defragmentation processes be mailed to the mail9 distribution list provided in the file DFG$MAIL_ ADDRESS. /NODE /NODE=(node-name[,...]) /NONODE (default)4 The /NODE qualifier limits the scope of the7 DEFRAGMENT command to the node or set of nodes4 specified by /NODE=(node-name). By default,9 defragmentation processes may execute on any LMF% licensed node in the system. /OPCOM_NOTIFICATION# /OPCOM_NOTIFICATION (default) /NOOPCOM_NOTIFICATION8 The /OPCOM_NOTIFICATION qualifier requests that8 brief status and termination messages regarding4 defragmentation processes be sent to OPCOM. /OPTIONS /OPTIONS={file-spec} /NOOPTIONS (default)< The  /OPTIONS qualifier provides an alternate method; for associating files with the /DORMANT, /EXCLUDE,> or /FREQUENT qualifiers. If the list of files for any; of these qualifiers is quite large, you can create= a separate file that contains this information. Each; record in the options file consists of a file name3 followed by one of the following keywords:( o /EXCLUDE-File to be excluded6 o /FREQUENT-File to be considered frequently accessed2 o /DORMANT-File to be considered dormant 7 The following example shows the contents of an5 options file called MYOPTFILE.OPT. This file= specifies that all files on the target device called7 FILE1.EXE are frequent files, all files in the> [ARCHIVE] directory are to be excluded, and all files; in the [OLDSTUFF] directory and its subdirectories are dormant. FILE1.EXE /FREQUENT# [ARCHIVE]*.*;*/EXCLUDE' [OLDSTUFF...]*.*;*/DORMANT9 Files indicated by the /EXCLUDE qualifier and by7 either the /DORMANT or /FREQUENT qualifier are< excluded. Files indicated by the /DORMANT qualifier6 and by the /FREQUENT qualifier are considered9 dormant. This rule is applied equally across all9 files specified in the /OPTIONS file, as well as> those associated with these qualifiers on the command line. /PREDECESSOR /PREDECESSOR={script-name} /NOPREDECESSOR (default): The /PREDECESSOR qualifier identifies the name of> the script that precedes the execution of this script= in a linked set of scripts. These scripts execute in= sequence; one successfully completes before the next one begins.6 The predecessor script name must exist in the: scheduling database or an error status message is; returned. You can use wildcards in the script-name= specification. Use an asterisk (*) to take action on< all scripts on the VMScluster system. Use a percent< sign (%) to match a single character in the script- name specification. /PRIORITY& /PRIORITY=(DEFAULT=n, MINIMUM=n) /NOPRIORITY (default)= The /PRIORITY qualifier specifies priorities for the% defragment volume operation. /PROLOGUE /PROLOGUE={file-name} /NOPROLOGUE (default)> The /PROLOGUE qualifier identifies a DCL command file> which DFO executes just before the DEFRAGMENT FILE or, DEFRAGMENT VOLUME operation starts. /RVN /RVN=n /RVN=0 (default)= When you have a bound volume set, use this qualifier< to identify a disk from the volume set or all disks9 in the volume set. The default of zero tells the4 Disk File Optimizer to defragment all disks; in the bound volume set. Specify a relative volume8 number (RVN) to defragment a specific disk that' belongs to a bound volume set. /SCRIPT /SCRIPT={script-name} /NOSCRIPT (default)6 The /SCRIPT qualifier assigns a new name to a8 script. If a duplicate script-name is selected,; defragmentation software issues a duplicate script= name error message and does not enter the new script:  into the database-no defragmentation takes place.; A script name may be up to 64 characters in length9 and may contain any of the following characters:& o Any alphanumeric character o Underscore ( _ ) o Hyphen ( - ) o Dollar sign ( $ ): Observe the following rules when naming a script:: o Use any combination of uppercase and lowercase letters.< o Do not begin script names using the dollar sign.; However, you can include the dollar sign within= the script name. (The dollar sign is reserved for: special use by Digital Equipment Corporation.)= o Do not end a script name with a hyphen, since the5 hyphen is the DCL continuation character.> The VMS DCL Concepts Manual contains more information on naming conventions. /TIME_LIMIT /TIME_LIMIT={delta-time} /NOTIME_LIMIT (default)8 The /TIME_LIMIT qualifier specifies the maximum9 elapsed time allowed for a given defragmentation6 operation. If the time limit is exceeded, the, defragmentation process is aborted.; Specify time as a delta time. Refer to the VMS DCL; Concepts Manual for more information on specifying times. 8 For linked scripts, the time limit of the first5 script applies to the whole set. Time limits8  specified with successor scripts apply to these scripts only.7 If the time limit is set unreasonably low, the: defragmentation process may not accomplish useful defragmentation. /VOLUME /VOLUME={volume-name} /NOVOLUME (default)6 Identifies the volume where the files reside. /WRITE_CHECK /WRITE_CHECK /NOWRITE_CHECK (default)9 The /WRITE_CHECK qualifier requests that a read-; after-write check be performed on all defragmented> or placed files. This qualifier significantly extends9 the execution time of a defragmentation process. 3 ExamplesD The following examples show how you can modify an existing script using the common qualifiers. 1.! $ DEFRAGMENT MODIFY C/SCRIPT=A2 This command changes the name of script C to A. 2.* $ DEFRAGMENT MODIFY */MAIL_NOTIFICATIONA This command turns on mail notification for all scripts in the database. 3.9 $ DEFRAGMENT MODIFY myscript/LOG=new_log/NOPREDECESSORD This command causes subsequent executions of myscript to generate? a log file called NEW_LOG.LOG, located in the user's default@ directory. The NOPREDECESSOR qualifier disassociates myscriptD from its predecessor. However, any script for which myscript is a@ predecessor remains dependent upon the execution of myscript. 4.! $ DEFRAGMENT MODIFY */SCRIPT=*2 This command renames all scripts to themselves. 5.# $ DEFRAGMENT MODIFY *C/SCRIPT=*DA This command changes the name of each script that ends in C to2 end in D. For instance, DAILYC becomes DAILYCD. 6.+ $ DEFRAGMENT MODIFY *C/SCRIPT=*D/PRED=*X@ This command shows the potential pitfalls with using multiple% wildcards in a DEFRAGMENT command.A Consider the following scenario: Suppose you have four scripts> (ABC, ATLASX, ABCX, and DAILYC) and you enter this command.> The Disk File Optimizer first finds all scripts whose names@ end in C (ABC and DAILYC). Then, according to what is writtenC on the command line, we would expect it to change their names toA end in D. Thus, ABC would become ABCD, and DAILYC would become DAILYCD.B After renaming the files, we would expect the script ABCD to beB modified such that it has a predecessor of ABCX, and DAILYCD toC have a predecessor of DAILYCX. However, since there is no script4 named DAILYCX in the database, the command fails.D Since this was entered on one command line, none of these changes actually occur. 2 MONITORD The MONITOR subcommand invokes the monitor function to illustrate5 the progress of ongoing defragmentation processes. FormatD DEFRAGMENT MONITOR { script-name|volume-name } [ /QUALIFIERS ] 3 Parameters script-name|volume-nameC The parameter for the MONITOR subcommand is either a script nameA or a volume name for Defrag PLUS. You can use wildcards in theC script-name specification. Use an asterisk (*) to take action onB all scripts on the VMScluster system. Use a percent sign (%) to= match a single character in the script-name specification.> If a volume name is supplied, then you must use the /VOLUME@ qualifier to tell Defrag PLUS the parameter is a volume name, rather than a script name. 3 Restrictions= o If a volume name is entered as a parameter, the /VOLUME qualifier must be used. 3 Qualifiers /CONTINUOUS /CONTINUOUS (default) NOCONTINUOUS7 The /CONTINUOUS qualifier invokes a continuous: monitor display. Entering Ctrl/C, Ctrl/Y, or Ctrl$ /Z terminates this display.: Using /NOCONTINUOUS indicates the monitor process; should provide a snapshot display and then exit to the DCL prompt. /VOLUME /VOLUME (default) /NOVOLUME; The /VOLUME qualifier indicates that a volume name; instead of a script name is present on the command8 line. The /VOLUME qualifier must be used when a> volume name is provided as a parameter to the MONITOR subcommand. 3 Examples9 The following examples show how to invoke the monitor. 1.* $ DEFRAGMENT MONITOR MY_SCRIPT/NOVOLUMEB In this example, the monitor function displays ongoing run-timeA statistics for the defragmentation process associated with MY_@ SCRIPT. It also displays an approximate free-space map of the@ target volume. The display continues until interrupted with aA Ctrl/C, Ctrl/Y, or Ctrl/Z because the /CONTINUOUS qualifier is present by default. 2.- $ DEFRAGMENT MONITOR DISK$ONE/NOCONTINUOUSA In this example, the defragmentation process executing against? DISK$ONE is monitored. Since the /NOCONTINUOUS qualifier was> specified, the monitor function samples the defragmentationD process statistics and the free space on DISK$ONE one time before exiting to the DCL prompt. 2 OFFLINE_VOLUMEC The DEFRAGMENT OFFLINE_VOLUME command defragments the INDEXF.SYSA file on the offline volume given as a parameter to the command< line according to the defragment command line qualifiers. Format? DEFRAGMENT OFFLINE_VOLUME { volume-name } [ /QUALIFIERS ]0 [ /QUALIFIERS ]) 3 Parameters volume-name@ The volume-name is the name of the volume that is to have the INDEXF.SYS file defragmented. 3 Restrictions= o This command is only valid on a disk device that is not? mounted. If the device is mounted an error will occur and the process will abort.C o For a bound volume set, this utility only works on the "ROOT" volume. 3 Qualifiers /AFTER /AFTER={time}% /AFTER={current_time} (default) /NOAFTER= The /AFTER qualifier keeps the script from executing( until after the specified time.; You can specify time as either an absolute time or: as a combination of absolute and delta times. For< complete information on specifying time values, see% the VMS DCL Concepts Manual.9 The /AFTER qualifier has three states. It can be< specified with a valid time, it can be omitted from> the command line, or it can  be negated (/NOAFTER). If= /AFTER is specified with a valid time, the script is< scheduled to execute after that time. If the /AFTER; qualifier is omitted, the defragmentation software9 processes the command as if the /AFTER qualifier: were specified with the current time. If /NOAFTER: is specified, no starting time is associated with9 the script being defined. The /NOAFTER qualifier< allows you to define a script without scheduling it> to execute. To subsequently start the script, use the START subcommand. /EPILOGUE /EPILOGUE={file-name} /NOEPILOGUE (default)> The /EPILOGUE qualifier identifies a DCL command file= which DFO executes upon completion of the DEFRAGMENT VOLUME operation. /INTERVAL /INTERVAL={delta-time} /NOINTERVAL (default): Causes a script to execute at regularly scheduled9 intervals . The /INTERVAL qualifier specifies the= minimum time between two consecutive executions of a script.; Specify time as a delta time. Refer to the VMS DCL; Concepts Manual for more information on specifying5 times. If you do not specify a time with the9 /INTERVAL qualifier, a default value of 1 day is= used. This value causes the associated script to run every 24 hours.5 If you specify the /AFTER qualifier with the7 /INTERVAL qualifier, the first defragmentation8 operation occurs at or after the time specified; by the /AFTER qualifier; all subsequent operations< execute at intervals set according to the /INTERVAL qualifier. /LOG /LOG={file-spec} /NOLOG (default)> The /LOG qualifier causes the defragmentation process6 to create a file containing a list of all its; operations. The information in the log file varies= with the presence of the /FULL or /BRIEF qualifiers.< The /FULL qualifier lists all files analyzed by the> defragmentation process and reports their disposition9 during each phase of defragmentation. The /BRIEF; qualifier lists only the statistics of each phase,> such as number of files analyzed, and number of files defragmented. /MAIL_NOTIFICATION /MAIL_NOTIFICATION$ /NOMAIL_NOTIFICATION (default)7 The /MAIL_NOTIFICATION qualifier requests that8 brief status and termination messages regarding8 defragmentation processes be mailed to the mail9 distribution list provided in the file DFG$MAIL_ ADDRESS. /NODE /NODE=(node-name[,...]) /NONODE (default)4 The /NODE qualifier limits the scope of the7 DEFRAGMENT command to the node or set of nodes4 specified by /NODE=(node-name). By default,9  defragmentation processes may execute on any LMF% licensed node in the system. /OPCOM_NOTIFICATION# /OPCOM_NOTIFICATION (default) /NOOPCOM_NOTIFICATION8 The /OPCOM_NOTIFICATION qualifier requests that8 brief status and termination messages regarding4 defragmentation processes be sent to OPCOM. /PROLOGUE /PROLOGUE={file-name} /NOPROLOGUE (default)> The /PROLOGUE qualifier identifies a DCL command file; which DFO executes just before the DEFRAGMENT FILE operation starts. /SCRIPT /SCRIPT={script-name} /NOSCRIPT (default); The /SCRIPT qualifier assigns a user-supplied name= to a script. If a duplicate script-name is selected,; defragmentation software issues a duplicate script= name error message and does not enter the new script: into the database-no defragmentation takes place.; A script name may be up to 64 characters in length9 and may contain any of the following characters:& o Any alphanumeric character o Underscore ( _ ) o Hyphen ( - ) o Dollar sign ( $ ): Observe the following rules when naming a script:8 o You can use any combination of uppercase and lowercase letters.: o You cannot begin script names using the dollar< sign, but you can include the dollar sign within= the script name. (The dollar sign is reserved for: special use by Digital Equipment Corporation.); o You should not end a script name with a hyphen,4 since the hyphen is the DCL continuation character.> The VMS DCL Concepts Manual contains more information on naming conventions. 2 REMOVE> The REMOVE subcommand deletes the specified script from the5 defragmentation scheduling and parameter database. Format= DEFRAGMENT REMOVE { script-name[,...] } [ /QUALIFIERS ] 3 Parameters script-nameD The script-name parameter specifies the script to remove from theA defragmentation database. You can use wildcards in the script-@ name specification. Use an asterisk (*) to take action on allD scripts on the VMScluster system. Use a percent sign (%) to match7 a single character in the script-name specification.? This parameter is not allowed if the /ALL qualifier is used. 3 RestrictionsC o If the /ALL qualifier is used, then the script-name parameter cannot be used. 3 Qualifiers /AFTER /AFTER=time /NOAFTER (default)8 The /AFTER qualifier does not delete the script: until after the specified time. Specify time as a< VMS absolute time or combination absolute and delta< time. Refer to the VMS DCL Concepts Manual for more, information on how to specify time. /ALL /ALL /NOALL (default): The /ALL qualifier indicates that all scripts are8 to be removed from the scheduling and parameter database.: If /ALL is used, the script-name parameter is not allowed. 3 Example= The following example shows how to remove a script after a specified time. 1., $ DEFRAGMENT REMOVE MY_SCRIPT/AFTER=16:30A In this example, MY_SCRIPT is removed from the database. It is: removed after 16:30 on the day this command is entered. 2 SET9 The SET subcommand defines or changes the value of the" defragmentation process limits. Format@ DEFRAGMENT SET { (parameter=value[,...]) } [ /QUALIFIERS ] 3 Parameters keywords:? o CPU_LIMIT: specifies the percent of CPU usage for any oneB defragmentation process. The CPU percent is the percent of a single CPU.B o IO_LIMIT: specifies the maximum direct I/O rate (per second)) of any one defragmentation process.D o PROCESS_LIMIT: specifies the maximum number of defragmentation processes per node. 3 Restrictions o None. 3 Qualifiers /NODE /NODE=(node-name[,...]) /NONODE (default)8 The /NODE qualifier limits the scope of the SET9 subcommand. By default, a given parameter is set= identically on all nodes in the scheduling database.= To limit parameters to fewer nodes, specify the node( names with the /NODE qualifier. 3 Examples> The following examples show how to set limits using the SET! subcommand and its qualifiers. 1.< $ DEFRAGMENT SET PROCESS_LIMIT=3, IO_LIMIT=14/NODE=NODE_1C In this example, the maximum number of defragmentation processes< that can occur on NODE_1 is three. Further, a restriction@ of 14 direct I/Os per second is placed on each of these three defragmentation processes. 2. $ DEFRAGMENT SET CPU_LIMIT=50? In this example, the maximum CPU percentage allocated to any? defragmentation process is set to 50 percent on all nodes in? the system. If a defragmentation process exceeds this limit,C its priority is decremented each minute (approximately) until it? reaches that specified by the /PRIORITY qualifier or three.. 2 SHOWC The SHOW subcommand displays information about the fragmentation@ state of the given volume and information from the scheduling database. FormatA DEFRAGMENT SHOW { script-name|volume-name } [ /QUALIFIERS ] 3 Parameters script-name|volume-name@ The parameter for the SHOW subcommand is either a script name? or a volume name, or it can be omitted if the /ALL qualifier> is used. If a script name is supplied or if the /PARAMETERSB qualifier is specified, the SHOW command queries the schedulingC database and displays this info rmation. You can use wildcards inD the script-name specification. Use an asterisk (*) to take actionB on all scripts on the VMScluster system. Use a percent sign (%)@ to match a single character in the script-name specification.< If a volume name is supplied (/VOLUME required), the SHOW@ command displays information about the fragmentation state ofA the specified volume. If a list of names is provided, the list/ cannot contain both script and volume names. 3 RestrictionsB o If showing a script or volume, do not use the /ALL qualifier@ o If it is a volume, then you must use the /VOLUME qualifier 3 Qualifiers /ALL /ALL /NOALL (default)< The /ALL qualifier is used when showing information> from the scheduling database. It displays information; about all scripts and parameters in the scheduling= database. If /ALL is used, the script-name parameter is not allowed. /COMMAND_LINE /COMMAND_LINE /NOCOMMAND_LINE (default)9 The /COMMAND_LINE qualifier is used when showing5 information from the scheduling database. It= formats the output of the SHOW subcommand as a valid; DEFRAGMENT command line. Thus, all the data in the; scheduling database can be extracted into a file (, /ALL/COMMAND_LINE/OUTPUT=file.ext). /DEVICE, /DEVICE=(device_spec[,device_spec])...9  The /DEVICE qualifier selects only those scripts; that match the script name provided on the command9 line and that target any devices named with this qualifier. /FILE_LIST /FILE_LIST=(min_extents)/ /FILE_LIST=(VOL_MAP_WINDOW + 1) (default): The /FILE_LIST qualifier is used when showing the< fragmentation state of a volume. It lists all files< on the volume that have min_extents or more extents; (fragments). By default, the number of file window8 mapping pointers set for the volume (INITIALIZE> {volume}/WINDOW=n) plus one is used. This value lists; all files that require at least one window turn to completely map. /FREE_LIST /FREE_LIST /NOFREE_LIST (default): The /FREE_LIST qualifier is used when showing the8 fragmentation state of the volume. It lists the: location and size of all of the freespace extents on the volume. /HISTOGRAM /HISTOGRAM /NOHISTOGRAM (default): The /HISTOGRAM qualifier is used when showing the: fragmentation state of a volume. It generates two8 histograms. The first plots the number of files< against the number of extents per file and provides< information about how many files are fragmented and< how badly they are fragmented. The second histogram> plots the number of freespace extents (holes) against9 the size of these freespace extents. It provides< information about how many freespace extents are on$ the volume and their sizes. /LOCATION! /LOCATION=[file-spec[,...]] /NOLOCATION9 The /LOCATION qualifier is used when showing the9 fragmentation state of the volume. It prints the: extents (fragments) associated with all specified8 files. If no files are specified, the /LOCATION<  qualifier appends location information to all files; listed with the /FILE_LIST qualifier. The supplied8 file-spec may contain wildcards in place of the< directory, file name, extension, or version fields. /NAMES /NAMES: The /NAMES qualifier lists only the first line of< the usual show output. The first line of the script< includes the name of the script, whether the script> is enabled or disabled, and the target device for the script. /NODE /NODE=(node-name[,...]) /NONODE (default)7 The /NODE qualifier selects only those scripts; that match the script name provided on the command; line and that match any of the node specifications& provided with this qualifier.< When used with the /PARAMETERS qualifier, the /NODE= qualifier displays CPU_LIMIT, IO_LIMIT, and PROCESS_7 LIMIT information for specified nodes only. If9 the /NODE qualifier is not used, the /PARAMETERS= qualifier displays this information for all nodes in! the scheduling database. /OUTPUT /OUTPUT={file-spec}" /OUTPUT=SYS$OUTPUT (default)7 The /OUTPUT qualifier may be used when showing7 the volume fragmentation state or when showing= information from the scheduling database. It directs8 the output of the SHOW subcommand to a file. By3 default, output is directed to SYS$OUTPUT. /PARAMETERS /PARAMETERS /NOPARAMETERS (default)7 The /PARAMETERS qualifier is used when showing5 information from the scheduling database. It; displays the CPU_LIMIT, IO_LIMIT and PROCESS_LIMIT: settings for all nodes in the scheduling database= (unless specific nodes are designated with the /NODE> qualifier). By default, these settings are not shown. /RUNNING /RUNNING6 The /RUNNING qualifier shows scripts that are currently running. /STATISTICS /STATISTICS /NOSTATISTICS (default); The /STATISTICS qualifier is used when showing the= volume fragmentation state. It provides a summary of> the file and free space fragmentation for the volume. /VOLUME /VOLUME /NOVOLUME (default)7 The /VOLUME qualifier must be used to show the; fragmentation state of a volume. It indicates that8 any parameter supplied on the command line is a: volume name instead of a script name. The /VOLUME= qualifier is incompatible with any of the qualifiers= used to show database information except the /OUTPUT qualifier. 3 Examples@ The following examples show how to SHOW limits using the SHOW! subcommand and its qualifiers. 1. $ DEFRAGMENT SHOW/PARAMETERSA In this example, the current values of CPU_LIMIT, IO_LIMIT andD PROCESS_LIMIT for all nodes in the scheduling database are shown. 2.0 $ DEFRAGMENT SHOW MY_SCRIPT/OUTPUT=OUTPUT.TXT< In this example, information associated with MY_SCRIPT is> displayed. No parameter information is displayed. Output is( directed to a file called OUTPUT.TXT. 3.6 $ DEFRAGMENT SHOW MY_SCRIPT/COMMAND_LINE/PARAMETERS< In this example, information associated with MY_SCRIPT isD  displayed. The current values of CPU_LIMIT, IO_LIMIT and PROCESS_A LIMIT for all nodes in the scheduling database are also shown.? The format for the information is a valid DEFRAGMENT command< line. Output is directed to the user's SYS$OUTPUT device. 4.. $ DEFRAGMENT SHOW DISK$ONE/VOLUME/HISTOGRAM@ In this example, the volume fragmentation report includes theA summary statistics (/STATISTICS is default) and histograms forB both file fragmentation and freespace fragmentation. The report$ is sent to the SYS$OUTPUT device. 2 SPAWN= The Disk File Optimizer SPAWN command creates a subprocess= and executes a DCL command in the subprocess, or transfers@ terminal control to the subprocess if no command is supplied. Format" DEFRAGMENT SPAWN [ command ] 3 Parameters command@ This is a DCL command string of less than 132 characters thatC is to be executed in the context of the created subprocess. WhenA the command completes execution, the subprocess terminates andC control returns to the parent process. A command is optional. If1 no command is supplied, control passes to DCL. 3 Restrictions None. 3 Qualifiers None. 3 ExamplesA The following examples show how to SPAWN processes from within# the Disk File Optimizer utility. 1. DFO> SPAWN $@ The SPAWN command creates a subprocess and transfers terminal% control to the created subprocess. 2. DFO> SPAWN SHOW DEFAULT DISK$1:[JONES] DFO>> The SPAWN command creates a subprocess and executes the DCL? command SHOW DEFAULT in the created subprocess. Control then5 returns to the Disk File Optimizer parent process. 2 START4 The START subcommand starts the specified script. Format< DEFRAGMENT START { script-name[,...] } [ /QUALIFIERS ] 3 Parameters script-name= The script-name parameter is the name of the scripts to beC started. You can use wildcards in the script-name specification.; Use an asterisk (*) to take action on all scripts on the> VMScluster system. Use a percent sign (%) to match a single. character in the script-name specification. 3 Restrictions None. 3 Qualifiers /AFTER /AFTER=time /NOAFTER (default)< The /AFTER qualifier keeps the script from starting( until after the specified time.; You can specify time as either an absolute time or: as a combination of absolute and delta times. For< complete information on specifying time values, see% the VMS DCL Concepts Manual. 3 Example5 The following example shows how to start a script. 1.+ $ DEFRAGMENT START MY_SCRIPT/AFTER=16:30> In this example, MY_SCRIPT is started. The /AFTER qualifier@ stipulates that MY_SCRIPT should start after 16:30 of the dayC this command is submitted. If the script is periodic, the period is unchanged. 2 VOLUMEB The DEFRAGMENT VOLUME command defragments the volume given as aD parameter on the command line according to the defragment command line qualifiers. Format8 DEFRAGMENT VOLUME { volume-name } [ /QUALIFIERS ] 3 Parameters volume-name< The volume-name parameter is the name of the volume to be defragmented. 3 RestrictionsB o A script that has the /CONTINUOUS qualifier may not be named+ as the predecessor of another script.> o If you specify the /INTERVAL qualifier, the /PREDECESSOR qualifier is not allowed.> o If /LEVEL=5 is selected, the /LOG qualifier is required./ o Do not use /BRIEF and /FULL concurrently.8 o Do not use /CONTINUOUS and /INTERVAL for a script. 3 Qualifiers /AFTER /AFTER={time}% /AFTER={current_time} (default) /NOAFTER= The /AFTER qualifier keeps the script from executing( until after the specified time.; You can specify time as either an absolute time or: as a combination of absolute and delta times. For< complete information on specifying time values, see% the VMS DCL Concepts Manual.9 The /AFTER qualifier has three states. It can be< specified with a valid time, it can be omitted from> the command line, or it can be negated (/NOAFTER). If= /AFTER is specifi ed with a valid time, the script is< scheduled to execute after that time. If the /AFTER; qualifier is omitted, the defragmentation software9 processes the command as if the /AFTER qualifier: were specified with the current time. If /NOAFTER: is specified, no starting time is associated with9 the script being defined. The /NOAFTER qualifier< allows you to define a script without scheduling it> to execute. To subsequently start the script, use the START subcommand. /BRIEF /BRIEF (default) /NOBRIEF< The /BRIEF qualifier has meaning only when the /LOG8 qualifier is also present. The /BRIEF qualifier9 requests a brief log of all actions taken by the= defragmentation process. This log includes beginning9 and ending volume status information. The /BRIEF9 and /FULL qualifiers are mutually exclusive, and8 /NOBRIEF produces the same result as /FULL. The) /BRIEF qualifier is the default. /CONSOLIDATE_FREESPACE& /CONSOLIDATE_FREESPACE (default) /NOCONSOLIDATE_FREESPACE7 The /CONSOLIDATE_FREESPACE qualifier tells the2 Disk File Optimizer to use its free space! consolidation algorithm. /CONTINUOUS /CONTINUOUS /NOCONTINUOUS (default)8 The /CONTINUOUS qualifier links the script with< itself. Thus, the script repeatedly e xecutes. After> each successful defragmentation operation, the script9 becomes eligible for execution again. As long as8 any PROCESS_LIMITs (see the SET subcommand) are9 not violated, the script executes repeatedly. If< all PROCESS_LIMITs have been reached, the script is< queued until an outstanding defragmentation process: completes, then the script is allowed to execute.; By default, the defragmentation process associated7 with a script may execute on any appropriately5 licensed node in a cluster. Thus, successive= defragmentation processes do not necessarily execute on the same node. /DORMANT /DORMANT=(file-spec[,...]) /NODORMANT (default)5 The /DORMANT qualifier indicates files to be5 considered dormant when final file placement< decisions are made. Dormant files are placed on the< volume to allow placing other fil es in optimum disk< locations. In general, they are placed further away< from the ODS-2 data structures than /FREQUENT files0 and files not classified in any manner.7 If a file is indicated in both the DORMANT and< FREQUENT lists, it is considered dormant. If a file< is indicated in both the EXCLUDE and DORMANT lists, it is excluded.) NOTE7 The amount of free space on the volume, th e9 number of files currently being accessed, and9 other factors influence file placement. Thus,6 the Disk File Optimizer does not guarantee; file placement, but makes every effort to place files as described.8 The file-spec field allows wildcard characters.8 You can specify wildcard characters in place of: the directory name, file name, file type, or file< version number field. The default file-spec for all< wildcard operations is DISK:[000000...]*.*;*. Thus,< specifying *.TMP;* selects all *.TMP;* files on the entire volume. /EPILOGUE /EPILOGUE={file-name} /NOEPILOGUE (default)> The /EPILOGUE qualifier identifies a DCL command file= which DFO executes upon completion of the DEFRAGMENT VOLUME operation. /EXCLUDE /EXCLUDE=(file-spec[,...]) /NOEXCLUDE (default)> The /EXCLUDE qualifier specifies files to be excluded= from processing. The defragmentation process ignores; files matching the listed file specifications. Any9 file indicated in the EXCLUDE list and in either7 the FREQUENT or DORMANT lists is excluded from processing.8 The file-spec field allows wildcard characters.8 You can specify wildcard characters in place of: the directory name, file name, file type, or file< version number field. The default file-spec for all< wildcard operations is DISK:[000000...]*.*;*. Thus,< specifying *.TMP;* selects all *.TMP;* files on the entire volume.) NOTE7 The defragmentation process always excludes: system files, open files, files excluded in an8 options file (/OPTIONS qualifier), and files1 excluded using the /IGNORE qualifier. /FREQUENT! /FREQUENT=(file-spec[,...]) /NOFREQUENT (default)6 The /FREQUENT qualifier indicates files to be7 considered frequently accessed when final file9 placement decisions are made. Frequent files are) placed to optimize access speed.8 If a file is indicated in both the FREQUENT and; DORMANT lists, it is considered dormant. If a file= is indicated in both the FREQUENT and EXCLUDE lists, it is excluded.)  NOTE7 The amount of free space on the volume, the9 number of files currently being accessed, and9 other factors influence file placement. Thus,6 the Disk File Optimizer does not guarantee; file placement, but makes every effort to place files as described. 8 The file-spec field allows wildcard characters.8 You can specify wildcard characters in place of: the directory name, file name, file type, or file< version number field. The default file-spec for all< wildcard operations is DISK:[000000...]*.*;*. Thus,< specifying *.TMP;* selects all *.TMP;* files on the entire volume. /FULL /FULL /NOFULL (default)7 The /FULL qualifier requests a full log of all: actions taken by the defragmentation process. The= /FULL qualifier has no meaning if the /LOG qualifier7 is absent. The /FULL and /BRIEF qualifiers are: mutually exclusive, and /NOFULL provides the same! functionality as /BRIEF. /HOTFILE_DATABASE /HOTFILE_DATABASE# /NOHOTFILE_DATABASE (default)3 The /HOTFILE_DATABASE qualifier causes the6 defragmenter to query the appropriate hotfile8 database and append the list of hotfiles to the, defragmenter's /FREQUENT file list. /IGNORE /IGNORE=(keyword[,...]) /IGNORE=(PLACED) (default) /NOIGNORE0 The /IGNORE qualifier requests that the> defragmentation process ignore certain types of files0 as specified by the following keywords:1 o INDEXED-Ignores all RMS indexed files6 o NOINDEXED-May defragment RMS indexed files< o PLACED-Ignores all files with explicit placement& flags set in their headers7 o NOPLACED-May defragment files with explicit placement flags> Files indicated by the /IGNORE qualifier are added to the EXCLUDE list.: The default value (/IGNORE=PLACED) indicates that8 files with explicit placement control should be6 ignored, and that RMS indexed files should be9 defragmented and placed in appropriate locations on the volume. /INHERIT /INHERIT={script-name} /NOINHERIT (default)9 The purpose of the /INHERIT qualifier is to make:  script creation easier. By inheriting most of the: command data from a previously entered script and< modifying only a few items (such as volume name), a; completely new script can be created. The /INHERIT< qualifier creates a database entry for a new script in the following way:> o Copies all fields from the specified script to the new script.; o Overwrites any qualifier or parameter values in> the new script with those specified on the command line.= o Names the new script as appropriate. The user may< specify a script name using the /SCRIPT={script-; name} qualifier. Otherwise, the defragmentation: software creates a unique script name. You can; use wildcards in the script-name specification.= Use an asterisk (*) to take action on all scripts< on the VMScluster system. Use a percent sign (%): to match a single character in the script-name specification. /INTERVAL /INTERVAL={delta-time} /NOINTERVAL (default): Causes a script to execute at regularly scheduled9 intervals. The /INTERVAL qualifier specifies the= minimum time between two consecutive executions of a script.; Specify time as a delta time. Refer to the VMS DCL; Concepts Manual for more information on specifying5  times. If you do not specify a time with the9 /INTERVAL qualifier, a default value of 1 day is= used. This value causes the associated script to run every 24 hours.5 If you specify the /AFTER qualifier with the7 /INTERVAL qualifier, the first defragmentation8 operation occurs at or after the time specified; by the /AFTER qualifier; all subsequent operations< execute at intervals set according to the /INTERVAL  qualifier. /LEVEL /LEVEL={n} /LEVEL=2 (default)6 The defragmentation process selects files for> defragmentation (from among those not excluded) based< on the /LEVEL qualifier. Once a file is selected as: a candidate, the defragmentation process attempts; to fully defragment that file (make it 100 percent< contiguous). Specify the level number as an integer ranging from 1 to 5: o /LEVEL=1;  Any file that is not 100 percent contiguous, or< can be selected using levels 2-4, is a candidate for defragmentation. o /LEVEL=2 (default)7 Any file whose extents cannot be completely8 mapped by the mapping window, or that can be< selected using levels 3 or 4, is a candidate for> defragmentation. The default window value is 7 and0 can be set for a given volume using:3 $ SET VOLUME {device-spec}/WINDOWS=[n] o /LEVEL=3= Any file with retrieval pointers in more than one< file header, or that can be selected using level2 4, is a candidate for defragmentation. o /LEVEL=4> The defragmentation process for level 4 processing> performs only free space consolidation. This level9 is used in conjunction with the /CONSOLIDATE_ FREESPACE qualifier. o /LEVEL=57 This level requests a volume analysis only;6 no defragmentation occurs. The statistical; results are available in the log file, which is< required when /LEVEL=5 is selected (see the /LOG< qualifier). If level 5 is selected, the /LEVEL=2; candidate file specifications are listed in the full log file. /LOG /LOG={file-spec} /NOLOG (default)> The /LOG qualifier causes the defragm entation process6 to create a file containing a list of all its; operations. The information in the log file varies= with the presence of the /FULL or /BRIEF qualifiers.< The /FULL qualifier lists all files analyzed by the> defragmentation process and reports their disposition9 during each phase of defragmentation. The /BRIEF; qualifier lists only the statistics of each phase,> such as number of files analyzed, and number of files defragmented. /MAIL_NOTIFICATION /MAIL_NOTIFICATION$ /NOMAIL_NOTIFICATION (default)7 The /MAIL_NOTIFICATION qualifier requests that8 brief status and termination messages regarding8 defragmentation processes be mailed to the mail9 distribution list provided in the file DFG$MAIL_ ADDRESS. /NODE /NODE=(node-name[,...]) /NONODE (default)4 The /NODE qualifier limits the scope of the7 DEFRAGMENT command to the node or set of nodes4 specified by /NODE=(node-name). By default,9 defragmentation processes may execute on any LMF% licensed node in the system. /OPCOM_NOTIFICATION# /OPCOM_NOTIFICATION (default) /NOOPCOM_NOTIFICATION8 The /OPCOM_NOTIFICATION qualifier requests that8 brief status and termination messages regarding4 defragmentation processes be sent to OPCOM. /OPTIONS /OPTIONS={file-spec} /NOOPTIONS (default)< The /OPTIONS qualifier provides an alternate method; for associating files with the /DORMANT, /EXCLUDE,> or /FREQUENT qualifiers. If the list of files for any; of these qualifiers is quite large, you can create= a separate file that contains this information. Each; record in the options file consists of a file name3 followed by one of the following keywords:( o /EXCLUDE-File to be excluded6 o /FREQUENT-File to be considered frequently accessed2 o /DORMANT-File to be considered dormant7 The following example shows the contents of an5 options file called MYOPTFILE.OPT. This file= specifies that all files on the target device called7 FILE1.EXE are frequent files, all files in the> [ARCHIVE] directory are to be excluded, and all files; in the [OLDSTUFF] directory and  its subdirectories are dormant. FILE1.EXE/FREQUENT# [ARCHIVE]*.*;*/EXCLUDE' [OLDSTUFF...]*.*;*/DORMANT9 Files indicated by the /EXCLUDE qualifier and by7 either the /DORMANT or /FREQUENT qualifier are< excluded. Files indicated by the /DORMANT qualifier6 and by the /FREQUENT qualifier are considered9 dormant. This rule is applied equally across all9 files specified in the /OPTIONS file, as well as> those associated with these qualifiers on the command line. /PREDECESSOR /PREDECESSOR={script-name} /NOPREDECESSOR (default)8 The /PREDECESSOR qualifier links scripts. These6 scripts execute in sequence; one successfully. completes before the next one begins.6 The predecessor script name must exist in the: scheduling database or an error status message is; returned. You can use wildcards in the script-name= specification. Use an asterisk (*) to take action on< all scripts on the VMScluster system. Use a percent< sign (%) to match a single character in the script- name specification. /PRIORITY& /PRIORITY=(DEFAULT=n, MINIMUM=n) /NOPRIORITY (default)= The /PRIORITY qualifier specifies priorities for the% defragment volume operation. /PROLOGUE /PROLOGUE={file-name} /NOPROLOGUE (default)> The /PROLOGUE qualifier identifies a DCL command file= which DFO executes just before the DEFRAGMENT VOLUME operation starts. /RVN /RVN=n /RVN=0 (default)= When you have a bound volume set, use this qualifier< to identify a disk from the volume set or all disks9 in the volume set. The default of zero tells the4 Disk File Optimizer to defragment all disks; in the bound volume set. Specify a relative volume8 number (RVN) to defragment a specific disk that' belongs to a bound volume set. /SCRIPT /SCRIPT={script-name} /NOSCRIPT (default); The /SCRIPT qualifier assigns a user-supplied name= to a script. If a duplicate script-name is selected,; defragmentation software issues a duplicate script= name error message and does not enter the new script: into the database-no defragmentation takes place.; A script name may be up to 64 characters in length9 and may contain any of the following characters:& o Any alphanumeric character o Underscore ( _ )  o Hyphen ( - ) o Dollar sign ( $ ): Observe the following rules when naming a script:8 o You can use any combination of uppercase and lowercase letters.: o You cannot begin script names using the dollar< sign , but you can include the dollar sign within= the script name. (The dollar sign is reserved for: special use by Digital Equipment Corporation.); o You should not end a script name with a hyphen,4 since the hyphen is the DCL continuation character.> The VMS DCL Concepts Manual contains more information on naming conventions.= If you do not supply a script name using the /SCRIPT: qualifier, the defr agmentation software generates8 a unique script name. This internally generated: name has the format DFG$SCRIPTX[X...], where X is9 a hexadecimal number that keeps the script names; unique. Names beginning with DFG$ are reserved for- use by the defragmentation software. /TIME_LIMIT /TIME_LIMIT={delta-time} /NOTIME_LIMIT (default)8 The /TIME_LIMIT qualifier specifies the maximum9 elapsed time allowed for a gi ven defragmentation6 operation. If the time limit is exceeded, the, defragmentation process is aborted.; Specify time as a delta time. Refer to the VMS DCL; Concepts Manual for more information on specifying times.8 For linked scripts, the time limit of the first5 script applies to the whole set. Time limits8 specified with successor scripts apply to these scripts only.7 If the time limit is set unre asonably low, the: defragmentation process may not accomplish useful defragmentation. /WRITE_CHECK /WRITE_CHECK /NOWRITE_CHECK (default)9 The /WRITE_CHECK qualifier requests that a read-; after-write check be performed on all defragmented> or placed files. This qualifier significantly extends9 the execution time of a defragmentation process. 3 ExamplesD The following examples show different ways to defra gment a volume3 and illustrate how to use the common qualifiers. 1." $ DEFRAGMENT VOLUME DISK$USER_1A This command defragments DISK$USER_1 using default qualifiers.A The defragmentation process executes once and does not repeat.? In a VMScluster system, the defragment operation begins on aC node selected at random from among those nodes in the schedulingC database having fewer executing processes than the limit imposed@ by the SET PROCESS_LIMIT={value} subcomma nd. If all nodes areA busy with a maximum number of defragment processes, the script@ does not execute until one of the outstanding defragmentation operations concludes.A After the defragmentation process stops, the script is removed from the scheduling database. 2.1 $ DEFRAGMENT VOLUME DISK$ONE/SCRIPT=MY_SCRIPT-? $ _/IGNORE=(INDEXED,PLACED)/INTERVAL=2-00:00/FREQUENT=*.EXE-9 $ _/LOG=MYLOG.LOG/FULL/DORMANT=*.ARCHIVE/NODE=(N1, N2)# This command does the following: o Defragments DISK$ONE o Names the script MY_SCRIPT= o Instructs the defragmentation process to ignore all RMS= indexed files and files with explicit placement controlA information in their headers. (These files are added to the EXCLUDE list.)C o Instructs the scheduler to execute this script every two daysB o Instructs the defragmentation process that all .EXE files on@ the entire volume should be considered frequently accessed2  when final file placement decisions are made< o Requests a log file, MYLOG.LOG, which is placed in the3 directory from which this command was entered o Requests a /FULL log fileC o Instructs the defragmentation process that all .ARCHIVE files? on the entire volume should be considered dormant (rarely< accessed) when final file placement decisions are madeC o Limits the nodes available for the defragmentation process to nodes N1 and N2 3.1 $ DEFRAGMENT VOLUME DISK$TWO/INHERIT=MY_SCRIPT $_/SCRIPT=FIRST_SCRIPTA This command inherits the script definition made in example 2.? Thus, it creates a new script that is the same as MY_SCRIPT,( except for the following differences:; o The script name is FIRST_SCRIPT instead of MY_SCRIPT.8 o The target volume is DISK$TWO instead of DISK$ONE.B In this case, MYLOG.LOG is also inherited. Thus, one version ofC the log file contains data from MY_SCRIPT, and the other versionD contains data from FIRST_SCRIPT. To prevent log file inheritance, specify the /LOG qualifier. 4.8 DFO> DEFRAGMENT VOLUME DISK$ONE /SCRIPT=SECOND_SCRIPT" DFO>_ /PREDECESSOR=FIRST_SCRIPT: This commands links SECOND_SCRIPT to FIRST_SCRIPT usingB the PREDECESSOR qualifier. SECOND_SCRIPT does not execute untilB FIRST_SCRIPT completes successfully. SECOND_SCRIPT uses defaultD parameters. Note that this command supplies the DEFRAGMENT VOLUME7 optio ns from within the Disk File Optimizer utility. 2 RELEASE_NOTESB You can find the release notes for the defragmentation softwareB in SYS$HELP:DFGvvu.RELEASE_NOTES, where vv is the major version& number, and u is the update number.< To list all the DEFRAGMENT release notes available, type:3 $ DIRECTORY SYS$HELP:DFG*.RELEASE_NOTES.ww