critical impact:

ESUCCESS - not supported (CrUn299)

Problem description

The identified errno values exist on Tru64 UNIX, but not on HP-UX.

The ESUCCESS error value is the most widely used. It is defined as 0, the conventional UNIX success value.

The following list describes the other errno values that do not have equivalents on HP-UX:

• EAIO - Internal AIO operation complete

• EBADRPC - RPC structure is bad

• ECLONEME - Tells open to clone the device

• EDIRTY - Mounting a dirty file-system without force

• EDUPPKG - Duplicate package name

• EFAIL - Cannot start operation

• EFTYPE - Inappropriate file type or format

• EINPROG - Operation in progress

• EMTIMERS - Too many timers

• EPROCLIM - Too many processes

• EPROCUNAVAIL - Bad procedure for program

• EPROGMISMATCH - Program version wrong

• EPROGUNAVAIL - RPC program not available

• ERPCMISMATCH - RPC version is wrong

• EVERSION - Version mismatch

Identifiers

EAIO	EFTYPE	EPROGUNAVAIL
EBADRPC	EINPROG	ERPCMISMATCH
ECLONEME	EMTIMERS	ESUCCESS
EDIRTY	EPROCLIM	EVERSION
EDUPPKG	EPROCUNAVAIL
EFAIL	EPROGMISMATCH

See also

• Background information on kernel impacts
• errno(2)

Solution description

Modify your code. You can define ESUCCESS either in a common header file or with the -DESUCCESS=0 compiler flag.

Enclose code that uses the other errno values within an #ifdef directive. For example, enclose code that uses EFTYPE within #ifdef EFTYPE.

See also

• errno(2)

Problem summary