Museum

Home

Lab Overview

Retrotechnology Articles

⇒ Online Manual

Media Vault

Software Library

Restoration Projects

Artifacts Sought

Related Articles

intro(2)

perror(3)

PERROR(3F)                           BSD                            PERROR(3F)



NAME
     perror, gerror, ierrno - get system error messages

SYNOPSIS
     subroutine perror (string)
     character*(*) string

     subroutine gerror (string)
     character*(*) string

     character*(*) function gerror()

     function ierrno()

DESCRIPTION
     perror will write a message to FORTRAN logical unit 0 appropriate to the
     last detected system error.  string will be written preceding the
     standard error message.

     gerror returns the system error message in character variable string.
     gerror can be called either as a subroutine or as a function.

     ierrno 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.

FILES
     /usr/lib/libU77.a

SEE ALSO
     intro(2), perror(3)
     D. L. Wasley, Introduction to the f77 I/O Library

NOTES
     UNIX system error codes are described in intro(2).  The f77 I/O error
     codes and their meanings are

          100  "error in format"
          101  "illegal unit number"
          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"

BUGS
     string in the call to perror can be no longer than 127 characters.

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

Typewritten Software • bear@typewritten.org • Edmonds, WA 98026