Wednesday 23 September 2009

Simple Volume Shadowing of the System Disk under OpenVMS

I am not an OpenVMS expert. I had to read the manual a couple of times and consult with the Hoff to get the commands sorted to do this, so hopefully it will save you some time.

Volume Shadowing on OpenVMS at it's very simplest can be used to provide RAID-1 mirroring using two or more locally attached hard drives. In my case I have a single hard drive (DKA300:) which acts as my system and data disk. I wanted a complete hot mirror of this drive in case of hardware failure. I have used two identical drives to do this.

If you are an OpenVMS hobbyist you will have the license required for volume shadowing. You can easily check:

$ SHOW LICENSE VOLSHAD
Active licenses on node ORAC:

------- Product ID -------- ---- Rating ----- -- Version --
Product Producer Units Avail Activ Version Release Termination
VOLSHAD DEC 0 0 100 0.0 (none) 16-OCT-2009

You then need to setup the system parameters so that when you reboot OpenVMS your current system disk is included in a shadow set to which another drive (or drives) can then be added. Edit the file SYS$SYSTEM:MODPARAMS.DAT and add the following lines:

ALLOCLASS=100
SHADOWING=2
SHADOW_SYS_DISK=1
SHADOW_SYS_UNIT=0

A sensible value for ALLOCLASS is 100, but it can be anything from 1 to 255. If you have previously added the box to a cluster this parameter may already be defined. SHADOWING must be 2 to enable shadowing. SHADOW_SYS_DISK must be 1 to enable shadowing for the system disk, and SHADOW_SYS_UNIT defines the virtual unit number which is appended to the virtual drive name DUAx:

You then need to run AUTOGEN to save these parameters. I used the following two commands:

$ @SYS$UPDATE:AUTOGEN SAVPARAMS GENPARAMS
$ @SYS$UPDATE:AUTOGEN GENPARAMS REBOOT

The second command may fail on errors, if this is the case and you are happy to proceed add the keyword FEEDBACK to the end.

This will reboot the system and (hopefully) when it's started up you should see the virtual unit when you run the SHOW DEVICE command:

$ show dev d

Device Device Error Volume Free Trans Mnt
Name Status Count Label Blocks Count Cnt
DSA0: Mounted 0 OVMSVAXSYS 16637880 337 1
$100$DKA200: (ORAC) Online wrtlck 0
$100$DKA300: (ORAC) ShadowSetMember 0 (member of DSA0:)

To add a new member to the volume set use the MOUNT command, like this:

MOUNT/CONFIRM/SYSTEM DSA0: /SHADOW=($100$DKA300,$100$DKA400) OVMSVAXSYS

This command specifies the existing system disk $100$DKA300 and the new disk $100$DKA400. You will need to confirm that you want to overwrite the contents of the new drive. The command initiates a copy of the data on the system disk to the new drive. SHOW DEVICE will indicate the copy progress:

$ show dev d

Device Device Error Volume Free Trans Mnt
Name Status Count Label Blocks Count Cnt
DSA0: Mounted 0 OVMSVAXSYS 16637880 337 1
$100$DKA200: (ORAC) Online wrtlck 0
$100$DKA300: (ORAC) ShadowSetMember 0 (member of DSA0:)
$100$DKA400: (ORAC) ShadowCopying 0 (copy trgt DSA0: 43% copied)

After the copy is complete the two shadow set members will contain identical data, so that if one of the drives should fail it can be replaced without losing any data.

I encourage you to consult the Volume Shadowing for OpenVMS manual for more information.

Sunday 6 September 2009

VAX APL LK201 Keyboard

From the VAX APL Users Guide page 1-3 comes an image of the LK201-EC variant with APL keycaps:



With this image as a reference I designed a set of replacement keycaps for an existing LK201 using the Open Office Drawing tool (source file) and the excellent Simpl APL Unicode Font:


These were printed out using a laser printer on the self-adhesive transparency paper provided as part of the Hooleon Keyboard Sticker Label Making Kit. These were then cut out using a scalpel and mounted on backing stickers which are opaque. A final top sticker adds a textured finish and protects the printed label.This is the resulting keyboard:

Left Hand Side:


Right Hand Side:


I've also uploaded a short video to YouTube demonstrating how you interact with VAX APL V4.0 using this keyboard together with a VT320 terminal.