...
> As of MPE/iX 5.0 (actually 4.5) when file number 0 became a
> valid file number to use in intrinsic calls, I have dealt
> with numerous programs that were failing (in user mode, not PM)
> that inadvertantly called FCLOSE (0). The symptoms would vary ...
I believe that file number 0 is a result of moving from MPE V
to MPE XL (i/X), that is native mode file numbers are one less
than the CM equivalent. What happened in release 4.5 is that
you no longer needed to be privileged to pass 0 as the file
number to most (all?) of the intrinsics. This was done to support
POSIX.
Jeff (basically saying the same thing as Erik) Vance