RMDRIVER

[Mario Abruzzi]

For what component of VMS is the RMDRIVER used?

[Lawrence Czlapinski · Accepted solution]

Mario, AMDS and Availability Manager. You need to DELETE it before installing a new version.
Lawrence

[Mario Abruzzi]

Lawrence,

Could you expand on the "delete it" part of your previous response?

[John Gillings]

Mario,

Because RMDRIVER and AMDS have hooks deep into the operating system, it's recommended to completely remove them from the system before upgrading to a later version.

The following procedure can be used to completely remove DECamds from a system:

1. Log into the SYSTEM account on the system Console. Stop the Console Display processes on the console system (when running). From either the "System verview" or "Event Log" display windows, choose the "File" menu and select "Exit".

2. Stop the RMDRIVER using the following commands:

On a standalone system:

$ @SYS$STARTUP:AMDS$STARTUP STOP

On a system in a VMScluster:

$ MCR SYSMAN
SYSMAN> SET ENVIRONMENT/CLUSTER
SYSMAN> DO @SYS$STARTUP:AMDS$STARTUP STOP
SYSMAN> EXIT

3. Delete the AMDS files using the following commands:

$ DELETE SYS$STARTUP:AMDS*.*;*
$ DELETE AMDS$SYSTEM:AMDS*.*;*
$ DELETE AMDS$HELP:AMDS*.*;*
$ DELETE AMDS$TEST:AMDS*.*;*
$ DELETE SYS$LOADABLE_IMAGES:*RMDRIVER*.*;*

4. Remove AVAIL command verb from DCLTABLES:

$ SET COMMAND /DELETE=AVAIL -
/TABLE=SYS$SHARE:DCLTABLES.EXE -
/OUTPUT=SYS$COMMON:[SYSLIB]DCLTABLES.EXE

NOTE: After issuing the command above, login to the system at this point with a new session, without logging out of your existing session, to verify that the newly created DCLTABLES functions correctly.

5. Reboot the system.

As an alternative to rebooting, replace the DCLTABLES and deassign AMDS logical names by issuing the following:

$ INSTALL
INSTALL> REPLACE SYS$LIBRARY:DCLTABLES.EXE
INSTALL> EXIT

$ SHOW LOGICAL/SYSTEM AMDS*
.
.
.
$ DEASSIGN/SYSTEM/EXECUTIVE
.
.
.

[Ian Miller.]

Is the removal of RMDRIVER recommended due to the problems that earlier kits had in updating SYS$RMDRIVER which are fixed in the latest kits according to Barry's posting here
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=757619

[Lawrence Czlapinski]

Ian, Sometimes RMDRIVER is in a different location than the new version. So on reboot you wind up running the old version. I don't know if the latest version fixes that problem.
Lawrence

[Ian Miller.]

Lawrence, I don't the answer but I expect Barry Kierstein does.

[Barry Kierstein]

Mario, Lawrence, and others,

If you put on the latest kit, it will fix a number of problems in keeping RMDRIVER and related files in synch with the operating system. There are a few things to note, however.
If you had DECamds installed before V7.2, then you might need to clean up some files as the DECamds, Availability Manager and OpenVMS kits now put files in their "new" places. The older DECamds kits put various files into SYS$COMMON:[AMDS] that are now in SYS$SYSTEM, SYS$MANAGER, etc. So, if you had a DECamds installation older than V7.2, then you should look at the DECamds installation notes that deal with the change in file locations ("Starting to Use the Data Provider" section). If you don't do this, then you will get some strange behavior.
Once you get the files in the right place, and get the latest kits on, then the PCSI installation will handle keeping the files current for your system.

Barry