If you are upgrading from Disk File Optimizer V1.0 and want to save the data in your database, you must save the data in a command procedure. Perform the following command to save in a command procedure:

$ DEFRAGMENT SHOW */COMMAND/OUT=LOAD_DB.COM

This command saves the data from your Rdb database and allows you restore it after installation of Disk File Optimizer.

The Disk File Optimizer kit allows for two installation variants:

Table 1.1, “Differences Between Installation Variants” identifies the major differences between Defrag and Defrag PLUS.

Defrag is recommended on any system where the additional features are not desired or where disk space is very limited.

Defrag PLUS is recommended on VMScluster systems and on any single-node system where the additional features of Defrag PLUS are desired.

The Disk File Optimizer free disk storage space requirements are different during installation and after installation. Table 1.2, “Disk Space Requirements” summarizes the storage requirements.

To determine the number of free disk blocks on the current system disk, enter the following command at the DCL prompt:

$ SHOW DEVICE SYS$SYSDEVICE

Disk File Optimizer is supported on OpenVMS VAX 7.3, OpenVMS Alpha 7.3-2 & 8.2 and OpenVMS I64 8.2.

To install the software, you must be logged in to an account that has SETPRV privileges.

This section lists those system parameters whose default values may be insufficient for proper operation of the defragmentation software. Table 1.3, “Minimum System Parameter Values” lists these parameters, recommended minimum settings, and whether the parameters apply to Defrag or Defrag PLUS.

The account you use to install the Disk File Optimizer software must have sufficient quotas to enable you to perform the installation. Table 1.4, “Process Account Quotas for the Installing Account” summarizes the process quotas required for the installing account, regardless of which installation variant you install.

User account quotas are stored in the SYSUAF.DAT file. Use the VMS Authorize utility (AUTHORIZE) to verify and change user account quotas. First set your directory to SYS$SYSTEM, and then run AUTHORIZE:

$ SET DEFAULT SYS$SYSTEM
$ RUN AUTHORIZE
UAF>

At the UAF> prompt, enter the SHOW command with an account name to check a particular account, for example:

UAF> SHOW SMITH

To change a quota, enter the MODIFY command. The following example changes the FILLM quota for the SMITH account, and then exits from the utility:

UAF> MODIFY SMITH /FILLM=50
UAF> EXIT

After you exit from the utility, the system displays messages indicating whether or not changes were made. Once the changes have been made, you must log out and log in for the new quotas to take effect.

For more information on modifying account quotas, see the description of the Authorize utility in the VSI OpenVMS System Management Utilities Reference Manual.

Use the following list of guidelines when installing the Disk File Optimizer on a VMScluster system:

Defrag PLUS requires either SCSNODE (SYSGEN parameter) or SYS$NODE (DECnet logical) be defined on the node that Disk File Optimizer is installed on. If both SCSNODE and SYS$NODE are NOT defined, the Disk File Optimizer scheduler will not start.

If the node is part of a cluster then SCSNODE has to be defined in SYSGEN. You can check if SCSNODE is defined by using the following command:

$ WRITE SYS$OUTPUT F$GETSYI("NODENAME")
SPIELN
$

In this example, SPIELN is the SCSNODE name. If the SYSGEN parameter SCSNODE is not defined then no node name is returned.

Another way of checking SCSNODE is to go into SYSGEN and execute the following command:

$ MCR SYSGEN
SYSGEN> SHOW SCSNODE
Parameter Name   Current   Default   Min.      Max.      Unit   Dynamic
--------------   -------   -------   -------   -------   ----   -------
SCSNODE          "SPIELN"  "     "   "     "   "ZZZZ"    Ascii
SYSGEN> EXIT
$

In this example, SPIELN is the SCSNODE name.

If the node is a standalone node, it does not require that SCSNODE be defined. However, if you wish to, you can define it in SYS$SYSTEM:MODPARAMS.DAT as follows and then do an AUTOGEN:

SCSNODE="SPIELN"
SCSSYSTEMID=9112

If the node is running DECnet, it will have a logical SYS$NODE defined. You can check to see if the logical SYS$NODE is defined using the following command:

$ SHOW LOG SYS$NODE
"SYS$NODE" = "SPIELN::" (LNM$SYSTEM_TABLE)
$

In this example, SPIELN is the SYS$NODE name.

If you are running a previous version of the Disk File Optimizer, then shut down the Scheduler software on all nodes before installing the new version of Defrag or Defrag PLUS software.

Use SYSMAN to shut down the Scheduler software or execute the following command on all nodes:

$ @SYS$MANAGER:DFG$STOP_SCHEDULER.COM

Before you run the Disk File Optimizer, execute SYS$SYSTEM:SETFILENOMOVE.COM against all OpenVMS operating system disks on your cluster. SETFILENOMOVE.COM identifies all system files that must not be moved because they are accessed without the file system. When you run this command file, it sets the NOMOVE bit in the file header for the identified files. If you do not run this command procedure, system files could be moved that would be ‘‘lost’’ to the accessing processes.

This procedure marks certain critical system files with the NOMOVE attribute. This anchors these files to the disk; any attempt to relocate them using the XQP MOVEFILE function fails.

While attempting to execute SETFILENOMOVE.COM, you may receive several errors similar to the following:

%SET-E-READERR, error reading <file name>
-SYSTEM-W-ACCONFLICT, file access conflict

To set the NOMOVE attribute on these files you must boot from another system, such as the distribution CD, and then execute SETFILEMOVE.COM against the disk. However, these files may already have the NOMOVE attribute set. Use the DIRECTORY/FULL command to determine if the NOMOVE attribute was already set.

If the NOMOVE attribute is not set and you cannot boot from another system disk, you should be all right because the file is open when the system is booted. Disk File Optimizer does not defragment or move open files.

To use this SETFILENOMOVE.COM procedure, you must specify the file name as P1 on the command line. For example:

$ @SYS$SYSTEM:SETFILENOMOVE $1$DKB100:

When you are installing Disk File Optimizer software for the first time, you must register the Disk File Optimizer software license.

The following sections describe:

$ LICENSE REGISTER DFG -

_$ /ISSUER=DEC -

_$ /AUTHORIZATION=xxxxxxx -

_$ /PRODUCER=DEC -

_$ /UNITS=nn -

_$ /RELEASE_DATE=dd-mmm-yyyy -

_$ /TERMINATION_DATE=dd-mmm-yyyy -

_$ /AVAILABILITY=x -

_$ /OPTIONS=xxxxxx -

_$ /CHECKSUM=x-xxxx-xxxx-xxxx-xxxx

$ LICENSE LOAD DFG

Before beginning the installation procedure, you may want to read the following questions and answers:

The Disk File Optimizer installation procedure consists of a series of questions and informational messages. See Appendix B for a sample installation. Follow the steps in Table 1.6, “How to Install the Disk File Optimizer Software” to install Disk File Optimizer software.

@SYS$UPDATE:VMSINSTAL saveset-name device-name OPTIONS N

%VMSINSTAL-W-ACTIVE, The following processes are still active
* Do you want to continue anyway [NO]?

* Are you satisfied with the backup of your system disk [Yes]?

Release notes included with this kit are always copied to SYS$HELP.
Additional Release Notes Options:
1. Display release notes
2. Print release notes
3. Both 1 and 2
4. None of the above
* Select option [2]:

* Do you want to continue the installation [NO]?

* Do you want to purge files replaced by this installation [YES]?

* Does this product have an authorization key registered and loaded?

* Do you want to run the IVP after the installation [YES]?

* Has SETFILENOMOVE.COM been executed against all system disks [NO]?

* Do you want to install Defrag or Defrag PLUS [PLUS]?

* Do you want to install the Defrag DECwindows interface [YES]?

* Do you wish to install the DFO callable interface [NO]?

* Device and directory to contain the scheduling database files
[SYS$COMMON:[DFG$DATABASE]]:
You have chosen the following as a location for the
defragmentation scheduling and parameter database:
SYS$COMMON:[DFG$DATABASE]
* Is this device and directory correct [YES]?

The following scheduling/parameter database already exists:
DISK$USER1:[DFG$DATABASE]DFG$DB.DAT;
DISK$USER1:[DFG$DATABASE]DFG$FILE.DAT;
DISK$USER1:[DFG$DATABASE]DFG$GENERAL.DAT;
DISK$USER1:[DFG$DATABASE]DFG$NODE.DAT;
DISK$USER1:[DFG$DATABASE]DFG$QUEUE.DAT;
DISK$USER1:[DFG$DATABASE]DFG$SCRIPT.DAT;
DISK$USER1:[DFG$DATABASE]DFG$VOLUME.DAT;
* Do you wish to use it [YES]?

* Mail distribution file name [SYS$COMMON:[DFG$DATABASE]DFG$MAIL.DIS]:
The mail distribution file for notification messages is
SYS$COMMON:[DFG$DATABASE]DFG$MAIL.DIS;
* Is this the correct file specification [YES]?

By default, the mail distribution file contains only the user name
of the installing account.
* Do you want to override the default contents of {mail.DIS} [NO]?

No more input is required to complete this installation. From this
point it proceeds automatically.

Attempting to convert your RMS database so there is no index key
compression. This requires converting the database. The old
database files will be renamed to:
DFG$DATABASE:DFG$DB_OLD.DAT
DFG$DATABASE:DFG$FILE_OLD.DAT
DFG$DATABASE:DFG$GENERAL_OLD.DAT
DFG$DATABASE:DFG$NODE_OLD.DAT
DFG$DATABASE:DFG$QUEUE_OLD.DAT
DFG$DATABASE:DFG$SCRIPT_OLD.DAT
DFG$DATABASE:DFG$VOLUME_OLD.DAT
After you are satisfied with the installation, you may wish to delete
these files.

%RUN-S-PROC_ID, identification of created process is 0000012B
Defragmentation scheduler, DFG$XXXX started on XXXX
Scheduler log file: DFG$DATABASE:DFG$XXXX.LOG

Beginning the V2.9 installation verification proced

Installation verification for V2.9 has successfully

If errors occur during the installation or when the IVP is running, VMSINSTAL displays failure messages. If the installation fails, the following message is displayed:

%VMSINSTAL-E-INSFAIL, The installation of DFG Version
V2.9
has failed.

If the IVP fails, the following messages are displayed:

The DFG Version V2.9 Installation Verification Procedure failed.
%VMSINSTAL-E-IVPFAIL, The IVP for DFG Version
V2.9 has failed.

Errors can occur during the installation if any of the following conditions exist:

For descriptions of the error messages generated by these conditions, see the VMS documentation about system messages, recovery procedures, and VMS software installation. If you are notified that any of these conditions exist, take the appropriate action as described in the message.

You usually run the Installation Verification Procedure (IVP) during the installation by responding YES to the question:

* Do you want to run the IVP after the installation [YES]?

If you did not run the IVP during the installation, or if you want to run the IVP separately to confirm the integrity of installed files, execute the IVP by entering this command:

$ @SYS$TEST:DFG$IVP.COM

Requirements:

The Disk File Optimizer software must be running on the system where the IVP is executed.

System startup:

You must edit the system startup procedure to ensure automatic startup of the Disk File Optimizer software each time the system boots. Add the following line to

SYS$MANAGER:SYSTARTUP.COM:
$ @SYS$MANAGER:DFG$STARTUP.COM

System shutdown:

You can modify the system shutdown file to provide for an orderly shutdown of the Disk File Optimizer. To do this, add the following line to SYS$MANAGER:SYSHUTDWN.COM:

$ @SYS$MANAGER:DFG$SHUTDOWN.COM

To make the Disk File Optimizer available on all nodes of the cluster, you should ensure that all nodes have the latest version of DCLTABLES.EXE installed. You can do this by using SYSMAN or by logging in to each node in the cluster and entering the following command:

$ INSTALL REPLACE SYS$COMMON:[SYSLIB]DCLTABLES.EXE

If you upgraded the Defrag PLUS variant of Disk File Optimizer, there are seven old files on your disk:

You can delete these files.

If you are upgrading from Disk File Optimizer V1.0 and have saved the data in your database, you must restore it. If you saved your database data as described in Section 1.2.1, “Upgrading From Disk File Optimizer V1.0”, you can load it into your new RMS database using the following command:

$ @LOAD_DB

The following privileges are required to run the Disk File Optimizer software:

tbs