Chapter Contents |
Previous |
Next |
Introduction to POSIX |
As
described in in Chapter 1, "Introduction to the SAS/C Library," in SAS/C Library Reference, Volume 1, the external
int
variable
errno
contains the number of the most recent error or warning
condition
detected by the run-time library. To use this value, include the header file
<errno.h>
.
POSIX and USS Error Numbers |
The
<errno.h>
header file contains
definitions for the macro identifiers that name system error status conditions.
When a SAS/C Library function sets an error status by assigning a nonzero
valued to
errno
, the calling
program can check for a particular value by using the name defined in
<errno.h>
.
The following USS related, POSIX defined
errno
values are defined in
<errno.h>
:
Note:
In addition to the values listed
above, common SAS/C
errno
values are listed in Chapter 1, "Introduction to the SAS/C Library," in SAS/C Library Reference, Volume 1. Also refer to errno.h
for socket-related
errno
values. For a complete listing of all
errno
values, see the SAS/C Compiler and Library Quick Reference
Guide.
Internal Error Numbers |
The
following
errno
values
represent USS internal errors. Contact IBM Technical Support if you receive
one of these errors. These
errno
values are described in more detail in the manual, OpenEdition
Assembler Callable Services.
EIBMCANCELLED
| |
EIBMCONFLICT
| |
EIBMSOCKINUSE
| |
EIBMSOCKOUTOFRANGE
| |
EMVSCATLG
| |
EMVSCVAF
| |
EMVSDYNALC
| |
EMVSPFSFILE
| |
EMVSPFSPERM
| |
EMVSSAF2ERR
| |
EMVSSAFEXTRERR
| |
EOFFLOADBOXDOWN
| |
EOFFLOADBOXERROR
| |
EOFFLOADBOXRESTART
|
Consult
The POSIX.1 Standard: A Programmer's Guide by Fred Zlotnick (1991, Benjamin/Cummings Publishing) or the POSIX
standards for information on the POSIX
errno
values; consult IBM USS documentation for information on the
EMVS- and EIBM-
errno
values.
Because the
errno
values resulting from POSIX functions are well organized and
well-defined, the SAS/C Library does not diagnose many problems that can occur
with these functions, even when it diagnoses similar problems occurring with
OS/390 files. This eases porting programs from other open systems, since
these systems do not, in general, have library diagnostics. In general, the
SAS/C Library will issue diagnostics for failures of USS functionality only
when (a) the failure is certainly the result of programmer error, or (b)
the error is so esoteric that diagnosis is unlikely without a message.
Chapter Contents |
Previous |
Next |
Top of Page |
Copyright © 2001 by SAS Institute Inc., Cary, NC, USA. All rights reserved.