MFS on a volume (AREV Specific)
At 01 OCT 2002 04:00:39PM Herb Jacobs wrote:
I downloaded the MFS documentation which was written at AREV 1.1. We are at 3.13. I am trying to install an MFS on a volume, as documented, in the VOC volume pointer as the first value in field 2, ahead of the BFS, in this case RTP57.
When I try to attach the volume, I get an error from RTP49, the Volume Info Reader.
Is the procedure to install an MFS on a volume now different from the documentation I have?
At 01 OCT 2002 08:24PM Richard Hunt wrote:
Herb,
I am just guessing…
Is your MFS program run code saved in the "SYSOBJ" file? Because if it isn't, it is quite possible the MFS is being called before the file it is in, is (attached) available to the system.
At 02 OCT 2002 09:34AM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:
What is the error? The volume MFS syntax hasn't changed, even through to OpenInsight.
World Leaders in all Things RevSoft
At 02 OCT 2002 11:48AM Herb Jacobs wrote:
Thanks for responding. I'm glad you asked. This is a legacy system and unfortunately the SYSMESSAGES file is gone, so I don't get an actual error message, but the code is B10. Perhaps you can tell me the message content.
At 02 OCT 2002 11:53AM Herb Jacobs wrote:
Good thinking, however after using the regular program file, I moved it to VERBS per the doc with the same failure. Might it be trying to run the MFS (INSTALL call perhaps) and its actually a runtime problem?
At 02 OCT 2002 03:43PM Jonathan Bird wrote:
B10 is variable not assigned a value. Maybe you need to check the INSTALL section of your MFS code.
At 02 OCT 2002 08:15PM Richard Hunt wrote:
Ahhhh yes…
As noted above… the B10 is "variable unassigned". So here is something to look at. MFS calls have 7 arguments. And not all 7 arguments are assigned every time this subroutine is called. During the code 1 (read record), the FMC (arg 5) is unassigned. Same with the code 3 (write record), the FMC (arg 5) is unassigned. And with the code 4 (delete record), the FMC (arg 5) and record (arg 6) are unassigned. Also for all the 3 codes listed above, the STATUS (arg 7) is unassigned too.
So if your MFS is checking these unassigned variables, then that B10 "variable unassigned" error message will pop up.
And I have no idea why these variables would pass to a subroutine "unassigned". As a programmer, it is something I would never do. And its been like that for ever!
At 03 OCT 2002 10:06AM Victor Engel wrote:
I think MFS had a few changes between 1.1 and 3.1, although I don't remember what the changes were (some new codes, some old codes removed, something like that). If you download the utility diskettes, you should find a shell that works in the later versions.
Also, what volume are you applying the MFS to? Not REVBOOT, I hope. Have you tried debugging the MFS by attaching it to a single file first? Most of the calls will be the same if it is a file-level MFS vs. a volume-level MFS. If your volume has many files that are used frequently, doing this may save you some headaches.
At 03 OCT 2002 04:14PM Herb Jacobs wrote:
Thanks, Richard. All of that makes good sense, however I think I have a somewhat different situation.
The error occurs during the ATTACH after modifying the VOLUME item in the VOC to add the mfs and the error itself states that it is RTP49 - the Volume info reader - that is encountering the VNAV.
Any clues?
At 07 OCT 2002 07:19AM Hippo wrote:
May be You will be inspired by following note about MFS programming
At 07 OCT 2002 02:02PM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:
Do you get the same error if you place the MFS on individual files?
What is happening in your MFS install code?
What is the contents of the return stack?
World Leaders in all Things RevSoft
At 07 OCT 2002 02:02PM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:
Do you get the same error if you place the MFS on individual files?
What is happening in your MFS install code?
What is the contents of the return stack?
World Leaders in all Things RevSoft