perror(3F) 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 vari-
able string. gerror may 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(3C)
BUGS
string in the call to perror can be no longer than 127 char-
acters.
The length of the string returned by gerror is determined by
the calling program.
NOTES
UNIX system error codes are described in intro(2). The For-
tran 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"
Page 1 CX/UX Hf77 Fortran Reference Manual
perror(3F) perror(3F)
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 "read unexpected character"
116 "blank logical input field"
117 "'new' file exists"
118 "can't find 'old' file"
119 "unknown system error"
120 "requires seek ability"
121 "illegal argument"
122 "negative repeat count"
123 "illegal operation for unit"
149 "cannot keep a scratch file"
150 "could not print file upon closing"
151 "could not print & delete file upon closing"
152 "cannot write to a read-only file"
153 "record number greater than maximum"
154 "cannot print a scratch file"
155 "cannot delete a read-only file"
156 "unrecognizable data type"
157 "invalid number of dimensions"
When compiling source with the -Qocs option, an explicit
underscore needs to be added to the end of the routine
names.
When compiling source with the -Qocs option, gerror may not
be called as a function because character values are
returned differently under the 88Open OCS standard.
Page 2 CX/UX Hf77 Fortran Reference Manual