I've seem these problems when a program issues an FCLOSE against a
zero (0) fnum while in PM.  This occurred because the code did not
check for a non-zero value in the fnum before issuing the FCLOSE call
in an error-handling routine that was invoked due to a problem that was
encountered prior to doing the anticipated HPFOPEN that would have
loaded the fnum.  I've also seen the case whereby the fnum was not
initialized and thus had some non-zero value from the stack in it
cause the same type of problem.  In the case of $STDLIST and $STDIN,
fnum values of zero and one (0/1) are meaningful and in PM, can
close this files.

Given that I'm unfamiliar with PERL and whether or not it uses PM,
this may or may not be a possibility....


At 05:58 PM 12/14/1999 -0700, ABOOTORAB,MICHAEL (HP-PaloAlto,ex1) wrote:
>If I remember correctly , MPE/ix opens the stdlist and stdin for every
>process and
>will not allow  user codes ( unless PM) to fclose the streams directly.
>
>Otherwise a user process will be able to close stdin or stdlist while read
>or
>write is in progress ( I may not be right on every word!).
>
>
>In two of the crashes we have experienced , the system dump shows operating
>system code in "nl.pub.sys" was attempting to fclose the stdlist and the
>file
>pointer was not correct. the program that was running was perl5.perl.perl.
>
>I'll will post more as information becomes available.
>
>Michael
X-no-Archive:yes

/jf
                               _\\///_
                              (' o-o ')
___________________________ooOo_( )_OOoo____________________________________

                       Wednesday, December 15th

           Today in 1791 - The "Bill of Rights", the 1st of 10
                           amendments, went into effect.

___________________________________Oooo_____________________________________
                             oooO  (    )
                            (    )  )  /
                             \  (   (_/
                              \_)