Once upon a time …

There was a very useful facility in ARev by which one could install a MFS on a volume rather than just on a file. This was done by putting in the VOC file a volume pointer record in which the volume's MFS was specified.

Does anyone know :-

a) Is this another legacy feature from Arev which is lying hidden in OI for the benefits of the adventurous, brave and/or foolhardy?

b) If so, has anyone used it and does it work?

c) If so, how is the control installed? Is it via SYSDICT? What is the format to be used?

Any help very welcome

For anyone interested …

Just had email response from RTI, who clearly don't look at this forum or, if they do, don't respond if they haven't an impressive answer. What a cynic I am - could it be a consequence of using Revelation products and/or support? No, I'd probably be a lot worse if I used anything else!

Answer seems to be that Volume MFS facility doesn't exist in OI.

Pity!

Richard-

Our policy for the online discussion is to let a message sit here for a while to see if another developer can answer the question ably. If not, we answer.

Usually, we don't have to- we have a very technical community who go out of their way to answer questions and share knowledge. We encourage this, and our sitting back is one way we do it. There's no need for us to 'hog' all the answers, nor could we answer all questions first if we tried.

Thanks-

Mike Ruane

Mike

Thanks - it's very useful to find how you handle queries on the discussion forum.

I wasn't seriously criticising your support which I have found generally to be very responsive and helpful. I hope you didn't read it that way.

I suppose I was just a little disappointed that the very useful Volume MFS facility seems to be one of the very few Arev features not to be found in OI (even if many may be undocumented but still work, such as dependent indexing).

Richard

Try placing the entry into the SYSPTRS table. I've just tested this, and here's my entry:

SAMPLE_APP

VOLUME

ZZ64K_MFS²RTP57

X:\AREV\312\SAMPLE

From the system monitor or exec line:

RUN ATTACH_TABLE "SAMPLE_APP"

Got a file listing of SAMPLE_BP, then edited SYSTABLES, SAMPLE_BP:

ZZ64K_MFS²RTP57*X:\AREV\312\SAMPLE

SAMPLE_BP

GLOBAL

QUICKDEX.MFS²ZZ64K_MFS²RTP57

SAMPLE_BP*GLOBAL²²²000000000040X:\AREV\312\SAMPLE\REV67247.LK

Wrote out a 100,000 byte record, and sure enough, it failed and returned the FS499 code from ZZ64K_MFS.

SYSPTRS is a combination of the old QFILE/SYSALIAS files from ARev, with the volume pointer reference from the VOC file.

The Sprezzatura Group

World Leaders in all things RevSoft

Thanks, Sprezz

View this thread on the forum...