>Does the KSAMXL file close *as well*, or is it *just* the FFF that
>closes?
>
>What's the FFF called, and what file equate (if any) are you using for
>that?
FILE SUPRLEAG=SUPRLEAG.FASTFORM.SUPRLEAG
:LISTFILE SUPRLEAG.FASTFORM,2
ACCOUNT= SUPRLEAG GROUP= FASTFORM
FILENAME CODE ------------LOGICAL RECORD----------- ----SPACE----
SIZE TYP EOF LIMIT R/B SECTORS #X MX
SUPRLEAG VFAST 256B FA 172 172 1 176 1 1
>
>Is this all a single program - any subprograms or calls? If so, are the
>FFF and the KSAMXL in the root program, or in one of the subs? Same one
>or different?
>
It is a single mainline program and does not call any subs (except the MPEiX
intrinsic calls, FOPEN, FREAD, FFFILEINFO, FGETKEYINFO, FWRITE, FCLOSE etc)
>What happens if you change the order of closing of the KSAMXL files
>(assuming this is to an extent arbitrary)?
Haven't tried that.
>Most likely, though, you are passing a filenum to the FCLOSE that is for
>the FFF, not the file you think it is for.
>
Yep, I think MPEiX is getting confused about the file numbers it is issuing
on the VOPENFORMF and the FOPEN of the KSAMXL file.
I removed the FCLOSE of the KSAMXL file and then the VPLUS calls worked ok.
But if I put the FCLOSE of this KSAMXL file back into the program the vplus
calls start to fail.
>Can you display the filenums assigned to each KSAMXL file as it is
>opened, and then display the one you are using just before you close
>each one?
>
FCLOSE WS-TEAMS-FILE-NUM=>+0000<
FOPEN WS-TEAMS-FILE-NUM=>+0018<
FCLOSE WS-TEAMSQ-FILE-NUM=>+0000<
FOPEN WS-TEAMSQ-FILE-NUM=>+0015<
FCLOSE WS-TEAMSQ-FILE-NUM=>+0015<
FOPEN WS-TEAMSQ-FILE-NUM=>+0011<
FCLOSE WS-TEAMSQ-FILE-NUM=>+0011<
FCLOSE WS-TEAMSQ-FILE-NUM=>+0011<
FOPEN WS-TEAMSQ-FILE-NUM=>+0011<
FOPEN WS-GROUPS-FILE-NUM=>+0016<
FCLOSE WS-GROUPS-FILE-NUM=>+0016<
FCLOSE WS-FIXTURES-FILE-NUM=>+0000<
FOPEN WS-FIXTURES-FILE-NUM=>+0016<
FCLOSE WS-FIXTURES-FILE-NUM=>+0016<
FOPEN WS-FIXTURES-FILE-NUM=>+0016<
FCLOSE WS-FIXTURES-FILE-NUM=>+0016<
FOPEN WS-FIXTURES-FILE-NUM=>+0016<
FCLOSE WS-TEAMS-FILE-NUM=>+0018<
FOPEN WS-TEAMS-FILE-NUM=>+0042<
FCLOSE WS-TEAMSQ-FILE-NUM=>+0011<
FOPEN WS-TEAMSQ-FILE-NUM=>+0011<
Before each call to FOPEN I do a call to FCLOSE of the same file to ensure
it is closed before I open/re-open it.
I will have to do some further research into these fopen/fclose calls and I will
get back to you.
>I'm guessing they may not be the same for the offending KSAMXL file.
>
>In which case, you need to look at how the right one got clobbered, or
>the wrong one got used.
>
>(Do I vaguely remember that the FFF uses filenum 0, or at least some
>very low one; if indeed zero, then an initialised - but not assigned -
>variable or array element for the filenum you intended would do it?)
>
>How are you obtaining, and storing, and replaying, the filenums for your
>KSAMXL files? (I assume you are obtaining each one explicitly, not just
>assuming they step up in sequence - a sequence that would be broken if
>the FFF was opened in the middle of all that (or even initially if you
>forgot that a filenum is needed for the FFF, even if VPLUS keeps that
>close to its chest and doesn't reveal it).
>
I get the file numbers from the call to FOPEN. Each field variable is unique
to the program.
Example of fopen:
MOVE "*TEAMS" TO WS-TEAMS-FILE-NAME
CALL INTRINSIC "FOPEN" USING WS-TEAMS-FILE-NAME
\5\
\0\
WS-REC-SIZE
GIVING WS-TEAMS-FILE-NUM
>Long shot if it's none of the above - are you doing anything that
>conflicts with the DL area restrictions (VPLUS Manual Appendix E) ?
Nope, not even going near any of that stuff as far as I know.
>
>--
>Roy Brown 'Have nothing in your houses that you do not know to be
>Kelmscott Ltd useful, or believe to be beautiful' William Morris
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
