Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community

At 18 MAY 1998 06:29:08AM Geoff Gullick wrote:

Iam trying to add an MFS to an OI file but it doesnt seem to work. and I'm afraid the sample in the help file is not very clear.

Can nay one point me in the right direction

When I run the routine it does give ne any errors but it return "FS"

and doesnt install the MFS

My Test code is listed beow;-

* The subroutine TEST installs or removes the MFS "TEST_MFS" *

Subroutine Test(Null)

Declare Subroutine Set_MFS, Set_Status

Declare Function Msg

$Insert Msg_equates

Errcodes = 0

Action = 3

Msgdef="

Msgdef=RC"

Msgdef=Enter action code"

Action=Msg("",Msgdef)

Tablename =FLEX_DO"

Mfslist =TEST_MFS*FLEX"

Set_Status (0)

Set_MFS(Tablename, Mfslist, Action)

If Get_Status(ErrCodes) Then

Dummy=Msg("",Errcodes)

End

Return

* *

SUBROUTINE TEST_MFS(A,B,C,D,E,F,G,H,I,J,K,L,M,N,O,P,Q,R,S,T,U,V)

DECLARE FUNCTION MSG

@RECORD=HELLO WORLD"

Dummy=Msg("","hello world")

Return


At 18 MAY 1998 06:55AM Geoff Gullick wrote:

P.S. Is there any more detailed documetation available regarding OI and MFS's ?


At 18 MAY 1998 08:54AM Don Bakke wrote:

Geoff,

Tablename =FLEX_DO" Mfslist =TEST_MFS*FLEX" Set_Status (0) Set_MFS(Tablename, Mfslist, Action)

I haven't yet worked with a custom MFS in OI but I believe you are supposed to create the MFS within SYSPROG. From the code above you have created it within the application FLEX.

dbakke@srpcs.com

SRP Computer Solutions


At 18 MAY 1998 09:54AM Carl Pates wrote:

Hi Don,

] I believe you are supposed to create the MFS within SYSPROG.

Well, that's the *official* story, but you can create them in your app as long as you reference them in the table's MFS list with the appropriate AppID suffix:

i.e. MY_MFS written in MY_APP. To use it you'd use:

MY_MFS*MY_APP

in the MFS list for the table, which is it's physical name in the SYSOBJ table.

Of course, if you need to maintain the table from ARev and OI then the best place is SYSPROG where the MFS code won't be saved with an AppID suffix.

cpates@sprezzatura.com

Sprezzatura Ltd

World Leaders in all things RevSoft


At 18 MAY 1998 10:16AM Don Bakke wrote:

Well, the things you know!

Thanks,

dbakke@srpcs.com

SRP Computer Solutions


At 18 MAY 1998 11:02AM Carl Pates wrote:

Hey, 'Sad Git' is my middle name!


At 19 MAY 1998 07:51AM Cameron Revelation wrote:

Geoff,

When I run the routine it does give ne any errors but it return "FS" and doesnt install the MFS

That's easy … your MFS is not an MFS, it is not responding to MFS instructions, and it is not setting up @file.error correctly.

1. Develop your MFS in the SYSPROG application. That is the only supported application for developing an MFS/BFS in.

2. The FILE.SYSTEM.EQUATES and FILE.SYSTEM.ONGOSUB inserts are often used to help implement an MFS.

3. Always remove the MFS before adding it, and always save the database definition after adding it. This fixes a synchronization issue if you have added the MFS to the table (i.e. put it in the media map) but have not saved the database definition.

<code>

* first remove it (in case it is already in the media map)
 Set_Status(FALSE$)
 Set_MFS(Table, MFS_NAME$, 5)

* add the MFS
 Set_Status(FALSE$)
 Set_MFS(Table, MFS_NAME$, 1)
 if Get_Status(Code) then
   Error =An error occurred adding the MFS to the ": Table: " table."
   Error := "||Error Code: ": Code
   gosub ErrMsg
 end

* update database definition
 Set_Status(FALSE$)
 Define_Database(@dbid, TRUE$, "", "")
 if Get_Status(Code) then
   Error =An error occurred saving the ": @dbid: " database definition."
   Error := "||Error Code: ": Code
   gosub ErrMsg
 end

</code>

Cameron Purdy

info@revelation.com


At 19 MAY 1998 12:43PM DSig (SigSolutions) wrote:

Geoff,

Do you have an MFS shell to work from? If not let me know and I will email you one.

There are very specific things that an mfs must do in order to work correctly and the only way to see these is to work from a shell.

Also, I would strongly suggest that you contact RTI and see if they still have their "MFS Developers" manual and sample disk. This will save you a lot of headaches.

Dsig

David Tod Sigafoos ~ SigSolutions

dsig@teleport.com cis: 70302,77 voice:503-639-8080


At 21 MAY 1998 09:08AM Aaron Kaplan wrote:

Actually, on the ARev side, just put in the name of the MFS, so if it's SECURITY_MFS*MYAPP in OI, then the same file in ARev would be SECURITY_MFS*MYAPP. ARev just grabs the name and looks at it as is, so it will take.

Besides, I've done it.

akaplan@sprezzatura.com

Sprezzatura, Inc.

www.sprezzatura.com_zz.jpg


At 21 MAY 1998 11:23AM Carl Pates wrote:

Well so have I!


At 25 MAY 1998 05:58AM Oystein Reigem wrote:

David,

Do you have an MFS shell to work from? If not let me know and I will email you one.

Please mail me one too. Thanks in advance.

- Oystein -

Øystein Reigem, Humanities Information Technologies, Harald Haarfagresgt 31, N-5007 Bergen, Norway. Tel: +47 55 58 32 42. Fax: +47 55 58 94 70. E-mail: oystein.reigem@hd.uib.no


At 04 JUN 1998 01:35PM Aaron Kaplan wrote:

Well, I did it first.

So there.

Hmmph.

akaplan@sprezzatura.com

Sprezzatura, Inc.

www.sprezzatura.com_zz.jpg


At 04 JUN 1998 02:06PM Carl Pates wrote:

Prove it!


At 13 JUN 1998 01:14PM Aaron Kaplan wrote:

Check the audit log for WINSIPP*STPROC**AUDIT_MFS.

akaplan@sprezzatura.com

Sprezzatura, Inc.

www.sprezzatura.com_zz.jpg

View this thread on the forum...

  • third_party_content/community/commentary/forums_nonworks/e2a180078598315d85256608003999a5.txt
  • Last modified: 2024/01/04 21:00
  • by 127.0.0.1