[Info-vax] bound volume set limits

[osuvman50 at gmail.com]

On Monday, July 3, 2017 at 3:23:36 PM UTC-4, osuv... at gmail.com wrote:
> On Monday, July 3, 2017 at 1:19:57 PM UTC-4, Baldrick wrote:
> > OK i know the ice is thin, very thin...
> > 
> > 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.
> > 
> 
> > Or (excepting using bound volumes in the first place) is there something
> > else going wrong here?
> > 
> > Baldrick
> 
> Browsing the source code for 7.2, it can throw that error if the RVT (relative
> volume table) is too small when adding a volume to the set.  There is some 
> verbiage in the comments about having to dismount and remount the volume set
> for every 4 volumes added above the minimum RVT size (17).  26 would be at one
> of those break points.

I was able to reproduce your problem on OpenVMS Alpha 8.4 (I already had a command procedure to generate volume sets for testing my sqlite quickview example code).  The fix is to bind the first 26 volumes into a set with one mount, then dismount it and remount with the full 30 devices.  Subsequent mounts only need the one mount because mount will size the RVT appropriately for the number of members it sees in volset.sys.