4.4BSD/usr/share/man/cat3f/ierrno.0

Compare this file to the similar file:
Show the results in this format:

F>=1  .if 3F<=8 .    if 3F>1 .if 3F<6 .ds an-extra3 "BSD Program-



PERROR(3F)             BSD Reference Manual            PERROR(3F)

mer's Manual
NNAAMMEE
       perror, gerror, ierrno - get system error messages

SSYYNNOOPPSSIISS
       ssuubbrroouuttiinnee ppeerrrroorr ((ssttrriinngg))
       cchhaarraacctteerr**((**)) ssttrriinngg

       ssuubbrroouuttiinnee ggeerrrroorr ((ssttrriinngg))
       cchhaarraacctteerr**((**)) ssttrriinngg

       cchhaarraacctteerr**((**)) ffuunnccttiioonn ggeerrrroorr(())

       ffuunnccttiioonn iieerrrrnnoo(())

DDEESSCCRRIIPPTTIIOONN
       _P_e_r_r_o_r will write a message  to  fortran  logical  unit  0
       appropriate  to  the  last  detected system error.  _S_t_r_i_n_g
       will be written preceding the standard error message.

       _G_e_r_r_o_r returns the system error message in character vari-
       able  _s_t_r_i_n_g_.  _G_e_r_r_o_r may be called either as a subroutine
       or as a function.

       _I_e_r_r_n_o will return the error number of the  last  detected
       system  error.   This number is updated only when an error
       actually occurs.  Most routines and  I/O  statements  that
       might  generate such errors return an error code after the
       call; that value is a  more  reliable  indicator  of  what
       caused the error condition.

FFIILLEESS
       /usr/lib/libU77.a

SSEEEE AALLSSOO
       intro(2), perror(3)
       D. L. Wasley, _I_n_t_r_o_d_u_c_t_i_o_n _t_o _t_h_e _f_7_7 _I_/_O _L_i_b_r_a_r_y

BBUUGGSS
       _S_t_r_i_n_g  in  the  call  to _p_e_r_r_o_r can be no longer than 127
       characters.

       The length of the string returned by _g_e_r_r_o_r is  determined
       by the calling program.

NNOOTTEESS
       UNIX  system  error  codes are described in _i_n_t_r_o(2).  The
       f77 I/O error codes and their meanings are:

            100  ``error in format''
            101  ``illegal unit number''



4.2 Berkeley Distribution  June 5, 1993                         1








PERROR(3F)             BSD Reference Manual            PERROR(3F)


            102  ``formatted i/o not allowed''
            103  ``unformatted i/o not allowed''
            104  ``direct i/o not allowed''
            105  ``sequential i/o not allowed''
            106  ``can't backspace file''
            107  ``off beginning of record''
            108  ``can't stat file''
            109  ``no * after repeat count''
            110  ``off end of record''
            111  ``truncation failed''
            112  ``incomprehensible list input''
            113  ``out of free space''
            114  ``unit not connected''
            115  ``invalid data for integer format term''
            116  ``invalid data for logical format term''
            117  ``'new' file exists''
            118  ``can't find 'old' file''
            119  ``opening  too  many  files  or  unknown  system
            error''
            120  ``requires seek ability''
            121  ``illegal argument''
            122  ``negative repeat count''
            123  ``illegal operation for unit''
            124  ``invalid data for d, e, f, or g format term''






























4.2 Berkeley Distribution  June 5, 1993                         2