| Copy IBI$FOCUS:fuselib.olb,linkfuse.com,userf.mar to the new directory.
Assign [newdirectory]fuselib.exe to the logical "fuselib".
Copy the .obj for your subroutine (which must have the same
name as your subroutine) to the new directory.
Enter the new subroutine in userf.mar and linkfuse.com.
Assemble, link, enjoy.
Good luck.
Curtis Coppersmith 232-2246
|
| I am trying to get my own GETPRV subroutine installed to dearchive
an archived FORTRAN file from PROMIS. I have written the subroutine
in PASCAL, using all the neat 'keyed' and 'sequential' access options.
I have tested it directly on the file as a program and it works
fine. I converted it into a MODULE, and it compiles fine, too.
The problem is, that when I go through all the steps to link
it into FUSELIB, (installed in my own sub-directory just like .0-.2
of this topic), it links together smoothly, no error messages. Then,
when I try to use it ... IT USES THE SAMPLE 'C' GETPRV :-{
I checked FUSELIB.MAP and saw two versions of GETPRV with the
same version number. One said it was VAX C and the other in VAX
Pascal, of course. So I started from scratch, then I did a
LIBRARY/DELETE to get rid of the 'C' version, and THEN tried to
install my GETPRV. When I tried to LINK, it gave me an error, something
about USERF tried to link with undefined procedure GETPRV and CLSPRV.
It seems that I have it in the wrong order or defined incorrectly.
Perhaps it was trying to access the 'C' GETPRV and didn't even find
my Pascal GETPRV.
What am I doing wrong here ?
|
| Gee, when they were pasing out brains, I was in a meeting!!! I figured
out my own mistake. Really stupid. Doesn't have anything to do with
FOCUS at all. I just forgot to put the little [GLOBAL] attributes
on GETPRV and CLSPRV. After I did that, it linked just fine.
SWS
P.S - Anyone interested in what my procedure looks like or what
it does ?
|