[Info-vax] bound volume set limits

[Baldrick]

OK i know the ice is thin, very thin...

For modern uses and modern versions of VMS bound volume sets are to be avoided.
This is headache central and some. So don't try this in production, or
even at home. In an ideal world I'd have a single 2 TB disk with all my files,
but I can't go there. 7.2 is out of the question for the VAX.

Scenario is this, VAX VMS 7.1 with just under a terabyte and a half of tape archived data of lots of relatively small files. We're quite used 
to a number of bound volume sets, of 3 to 10 members and we back them up 
fine, restore, etc. so despite the odds, with care, they work in our 
circumstances.

So I ask the SAN engineer to give me 30 presentations of 50 gig to my
Alphas which are clustered with my VAX. The Alphas are on 7.3-2, and using
MSCP (CI and LAVC) are serving the SAN disks to the cluster, and specifically
the VAX.

Comes the big day to start using them. Individually they are great, fast
performance, VAX has no issues INITing / mounting etc. , the LTO backups
courtesy of the 'new' Alphas are working fine.

INIT ... 1 to 30 (appropriate labels)

MOUNT/BIND=myname DISK1:, DISK2:, DISK3: ... DISK30: LABEL1:... LABEL30:

 (you know the commands I put them in a command file)

Anyway it gets to the 26th disk and announces:

%MOUNT-F-SETLIMIT, too many volumes in volume set.

Err, a HELP/MESSAGE says "The maximum permissible number of volumes in a
volume set (255) has been reached."

The user action makes me laugh, how on earth does "Find the other volumes
in the set and use them first." relate to the issue I experienced? I know
where they are, I just mounted them, I haven't lost them.

Anyway back to my problem, 25 is a LONG way off 255 - has anyone ever gone 
beyond 25 members of a volume set? What's the maximum anyone is using?

Or (excepting using bound volumes in the first place) is there something
else going wrong here?

Baldrick