This form contains a series of questions that need to be answered. As you go about answering the questions, please keep the following things in mind:

• While it is not required that each question be answered at this time, all questions must have answers before the response is submitted to The Open Group for review and publication.
• Press the "Save" button at any time to save work in progress. Once the work has been saved, there is the option to continue editing if required.
• Many questions have instructions to assist in development of answers. They are marked with the indicator. Please look at the instructions carefully.
• Although HTML markup can be included in answers, this is not recommended apart from basic tags such as <p> and <br>, since incorrect markup could effect the format of other items in the document.
• Questions on this system should be addressed to the Conformance Statement manager at The Open Group.

Enter the name of the Organization that produced the implementation and the name of the author of the Conformance Statement.

1. Internationalised System Calls and Libraries

Product Information

Environment Specification

Answer the questions for each binary-compatible family. Alternately, provide the answers in the Appendix at the end of this document.

	Testing Environment	Binary-compatible Family	Portability Environment	Indicator of Compliance	Compliance Details
			None.	Select from this list Test Report from Test Suite	Test Suite: Test Report:
			None.	Select from this list Test Report from Test Suite	Test Suite: Test Report:
			None.	Select from this list Test Report from Test Suite	Test Suite: Test Report:
			None.	Select from this list Test Report from Test Suite	Test Suite: Test Report:
			None.	Select from this list Test Report from Test Suite	Test Suite: Test Report:

Temporary Waivers

1.1 General Attributes

1.1.1 Feature Groups

Question 1: Which of the following Feature Groups are supported by the implementation?

Response

POSIX.2 C-language Binding	Yes   No
Shared Memory	Yes   No
Encryption	Yes   No
Enhanced Internationalisation	Yes   No

The POSIX.2 C-language Binding Feature Group is mandatory when associated with an implementation that conforms to Issue 4 or later of the CAE Specification for Commands and Utilities. Otherwise it is optional.

All the interfaces in all feature groups must exist, whether or not the feature group is supported, and each interface must either behave according to the description in System Interfaces and Headers, Issue 4, Version 2, or indicate an error, with errno set to [ENOSYS].

Support for a Feature Group can only be claimed if all interfaces in that group behave according to the relevant descriptions in System Interfaces and Headers, Issue 4, Version 2.

Rationale

System Interfaces and Headers, Issue 4, Version 2 states that the system may provide one or more of the Feature Groups listed. It further states (on page 855) that support for certain feature groups (e.g., POSIX2 C-language Binding) is mandatory when associated with an implementation that conforms to Issue 4 or later of the CAE Specification for Commands and Utilities; that is, when the value of _XOPEN_XCU_VERSION is greater that or equal to 4.

Reference

CAE Specification, System Interfaces and Headers, Issue 4, Version 2, Section 1.2, Conformance, Section 1.3, Feature Groups and Chapter 4, Headers, <unistd.h>.

1.1.2 POSIX.1 Supported Features

Question 2: Which of the following options, specified in the <unistd.h> header file, are available on the system?

Response

Where indicated in the following table, select one of the options given (either "Yes" or "Variable"). Select "Variable" if there are system dependent or file_system dependent configuration procedures that can remove or modify any or all of these features.

Macro Name	Meaning	Provided
_POSIX_CHOWN_RESTRICTED	The use of chown() is restricted to a process with appropriate privileges, and to changing the group ID of a file only to the effective group ID of the process or one of its supplementary group IDs.	Yes Variable
_POSIX_NO_TRUNC	Pathname components longer than {NAME_MAX) generate an error.	Yes Variable
_POSIX_VDISABLE	Terminal special characters defined in <termios.h> can be disabled using this character value.	Yes Variable
_POSIX_SAVED_IDS	Each process has a saved set-user-ID and a saved set-group-ID.	Yes Variable
_POSIX_JOB_CONTROL	Implementation supports job control.	Yes Variable

Rationale

For a conformant implementation, all of these POSIX features must be provided. In some cases the feature need not be provided for all files or devices supported by the implementation.

Reference

CAE Specification, System Interfaces and Headers, Issue 4, Version 2, Chapter 4, Headers, <unistd.h>.

1.1.3 Float, Stdio and Limit Values

Question 3: What are the values associated with the following constants specified in the <float.h> header file?

Response

Macro Name	Meaning	Value
FLT_RADIX	Radix of the exponent representation.
FLT_MANT_DIG	Number of base-FLT_RADIX digits in the float significand.
DBL_MANT_DIG	Number of base-FLT_RADIX digits in the double significand.
LDBL_MANT_DIG	Number of base-FLT_RADIX digits in the long double significand.
FLT_DIG	Number of decimal digits, q, such that any floating point number with q digits can be rounded into a float representation and back again without change to the q digits.
DBL_DIG	Number of decimal digits, q, such that any floating point number with q digits can be rounded into a double representation and back again without change to the q digits.
LDBL_DIG	Number of decimal digits, q, such that any floating point number with q digits can be rounded into a long double representation and back again without change to the q digits.
FLT_MIN_EXP	Minimum negative integer such that FLT_RADIX raised to that power minus 1 is a normalised float.
DBL_MIN_EXP	Minimum negative integer such that FLT_RADIX raised to that power minus 1 is a normalised double.
LDBL_MIN_EXP	Minimum negative integer such that FLT_RADIX raised to that power minus 1 is a normalised long double.
FLT_MIN_10_EXP	Minimum negative integer such that 10 raised to that power is in the range of normalised floats.
DBL_MIN_10_EXP	Minimum negative integer such that 10 raised to that power is in the range of normalised doubles.
LDBL_MIN_10_EXP	Minimum negative integer such that 10 raised to that power is in the range of normalised long doubles.
FLT_MAX_EXP	Maximum integer such that FLT_RADIX raised to that power minus 1 is a representable finite float.
DBL_MAX_EXP	Maximum integer such that FLT_RADIX raised to that power minus 1 is a representable finite double.
LDBL_MAX_EXP	Maximum integer such that FLT_RADIX raised to that power minus 1 is a representable finite long double.
FLT_MAX_10_EXP	Maximum integer such that 10 raised to that power is in the range of representable finite floats.
DBL_MAX_10_EXP	Maximum integer such that 10 raised to that power is in the range of representable finite doubles.
LDBL_MAX_10_EXP	Maximum integer such that 10 raised to that power is in the range of representable finite long doubles.
FLT_MAX	Maximum representable finite float.
DBL_MAX	Maximum representable finite double.
LDBL_MAX	Maximum representable finite long double.
FLT_EPSILON	Difference between 1.0 and the least value greater than 1.0 that is representable as a float.
DBL_EPSILON	Difference between 1.0 and the least value greater than 1.0 that is representable as a double.
LDBL_EPSILON	Difference between 1.0 and the least value greater than 1.0 that is representable as a long double.
FLT_MIN	Minimum normalised positive float.
DBL_MIN	Minimum normalised positive double.
LDBL_MIN	Minimum normalised positive long double.

Rationale

This set of constants provides useful information regarding the underlying architecture of the implementation.

Reference

CAE Specification, System Interfaces and Headers, Issue 4, Version 2, Chapter 4, Headers, <float.h>.

Question 4: What are the values associated with the following constants (optionally specified in the <limits.h> header file)?

Response

After each table entry below add the values for your implementation. These values may be stated to be "Unlimited" if your implementation does not impose a limit.

Macro Name	Meaning	Value
ARG_MAX	Maximum length of argument to the exec functions including the environment data.
CHILD_MAX	Maximum number of processes per user ID.
LINK_MAX	Maximum number of links to a single file.
MAX_CANON	Maximum number of bytes in a terminal canonical input line.
MAX_INPUT	Maximum number of bytes for which space will be available in a terminal input queue.
NAME_MAX	Maximum number of bytes in a filename (not including terminating null).
OPEN_MAX	Maximum number of open files that one process can have open at any one time.
PATH_MAX	Maximum number of bytes in a pathname (including the terminating null).
PIPE_BUF	Maximum number of bytes that is guaranteed to be atomic when writing to a pipe.
STREAM_MAX	Number of streams that one process can have open at one time.
TZNAME_MAX	Maximum number of bytes supported for the name of a time zone.

Rationale

Each of these limits can vary within bounds set by System Interfaces and Headers, Issue 4, Version 2. The minimum permitted value is specified in Chapter 4, <limits.h> of CAE Specification, System Interfaces and Headers, Issue 4, Version 2.

Reference

CAE Specification, System Interfaces and Headers, Issue 4, Version 2, Chapter 4, Headers, <limits.h>.

Question 5: What are the values associated with the following constants specified in the <limits.h> header file?

Response

After each table entry in the table below add the values for your implementation. These values may be stated to be "Unlimited" if your implementation does not impose a limit.

Macro Name	Meaning	Value
BC_BASE_MAX	Maximum ibase and obase values allowed by the bc utility.
BC_DIM_MAX	Maximum number of elements permitted in an array by the bc utility.
BC_SCALE_MAX	Maximum scale value allowed by the bc utility.
BC_STRING_MAX	Maximum length of a string constant accepted by the bc utility.
COLL_WEIGHTS_MAX	Maximum number of weights that can be assigned to an entry of the LC_COLLATE order keyword in the locale definition file.
EXPR_NEST_MAX	Maximum number of expressions that can be nested within parentheses by the expr utility.
LINE_MAX	Maximum length in bytes including the trailing newline of a utility's input line when the utility is described as processing text files.
NGROUPS_MAX	Maximum number of simultaneous supplementary group IDs per process.
RE_DUP_MAX	Maximum number of repeated occurrences of a regular expression permitted when using interval notation.

Rationale

Each of these limits can vary within bounds set by System Interfaces and Headers, Issue 4, Version 2. The minimum permitted value is specified in Chapter 4, <limits.h> of CAE Specification, System Interfaces and Headers, Issue 4, Version 2.

Reference

CAE Specification, System Interfaces and Headers, Issue 4, Version 2, Chapter 4, Headers, <limits.h>.

Question 6: What are the values associated with the following numerical constants specified in the <limits.h> header file?

Response

Macro Name	Meaning	Value
CHAR_BIT	Number of bits in a char.
CHAR_MAX	Maximum value of a char.
INT_MAX	Maximum value of an int.
LONG_BIT	Number of bits in a long int.
LONG_MAX	Maximum value of a long int.
MB_LEN_MAX	Maximum number of bytes in a character, for any supported locale.
SCHAR_MAX	Maximum value of a signed char.
SHRT_MAX	Maximum value of a short.
SSIZE_MAX	Maximum value of an object of type ssize_t.
UCHAR_MAX	Maximum value of an unsigned char.
UINT_MAX	Maximum value of an unsigned int.
ULONG_MAX	Maximum value of an unsigned long int.
USHRT_MAX	Maximum value of an unsigned short int.
WORD_BIT	Number of bits in a word or int.

Rationale

This set of constants provides useful information regarding the underlying architecture of the implementation.

Reference

CAE Specification, System Interfaces and Headers, Issue 4, Version 2, Chapter 4, Headers, <limits.h>.

Question 7: What are the values associated with the following numerical constants specified in the <stdio.h> header file?

Response

Macro Name	Meaning	Value
FILENAME_MAX	Maximum size in bytes of the longest filename string that the implementation guarantees can be opened.
FOPEN_MAX	Number of streams which the implementation guarantees can be open simultaneously.
L_ctermid	Maximum size of character array to hold ctermid() output.
L_tmpnam	Maximum size of character array to hold tmpnam() output.
TMP_MAX	Minimum number of unique filenames generated by tmpnam(), which is the maximum number of times an application can call tmpnam() reliably.

Rationale

This set of constants provide useful information about the implementation.

Reference

CAE Specification, System Interfaces and Headers, Issue 4, Version 2, Chapter 4, Headers, <stdio.h>.

1.1.4 Error Conditions

Question 8: Which of the following option errors listed in System Interfaces and Headers, Issue 4, Version 2 are detected in the circumstances specified?

Response

Function	Error	Detected
access()	EINVAL	Yes   No
	ETXTBSY	Yes   No
acos()	EDOM	Yes   No
asin()	EDOM	Yes   No
	ERANGE	Yes   No
atan()	EDOM	Yes   No
	ERANGE	Yes   No
atan2()	EDOM	Yes   No
	ERANGE	Yes   No
catclose()	EBADF	Yes   No
	EINTR	Yes   No
catgets()	EBADF	Yes   No
	EINTR	Yes   No
catopen()	EACCES	Yes   No
	EMFILE	Yes   No
	ENAMETOLONG	Yes   No
	ENFILE	Yes   No
	ENOENT	Yes   No
	ENOMEM	Yes   No
	ENOTDIR	Yes   No
ceil()	EDOM	Yes   No
cfsetispeed()	EINVAL	Yes   No
cfsetospeed()	EINVAL	Yes   No
chmod()	EINVAL	Yes   No
chown()	EINVAL	Yes   No
closedir()	EBADF	Yes   No
	EINTR	Yes   No
cos()	EDOM	Yes   No
	ERANGE	Yes   No
cosh()	EDOM	Yes   No
erf()	EDOM	Yes   No
	ERANGE	Yes   No
erfc()	EDOM	Yes   No
	ERANGE	Yes   No
exec	ENOMEM	Yes   No
	ETXTBSY	Yes   No
exp()	EDOM	Yes   No
	ERANGE	Yes   No
fabs()	EDOM	Yes   No
	ERANGE	Yes   No
fclose()	ENXIO	Yes   No
fcntl()	EDEADLK	Yes   No
fdopen()	EBADF	Yes   No
	EINVAL	Yes   No
	EMFILE	Yes   No
	ENOMEM	Yes   No
fflush()	ENXIO	Yes   No
fgetc()	ENOMEM	Yes   No
	ENXIO	Yes   No
fgetpos()	EBADF	Yes   No
	ESPIPE	Yes   No
fgetwc()	ENOMEM	Yes   No
	ENXIO	Yes   No
	EILSEQ	Yes   No
fileno()	EBADF	Yes   No
floor()	EDOM	Yes   No
fmod()	EDOM	Yes   No
	ERANGE	Yes   No
fopen()	EINVAL	Yes   No
	EMFILE	Yes   No
	ENOMEN	Yes   No
	ETXTBSY	Yes   No
fork()	ENOMEM	Yes   No
fpathconf()	EBADF	Yes   No
	EINVAL	Yes   No
fprintf()	EINVAL	Yes   No
	EILSEQ	Yes   No
fputc()	ENOMEM	Yes   No
	ENXIO	Yes   No
fputwc()	ENOMEM	Yes   No
	ENXIO	Yes   No
	EILSEQ	Yes   No
freopen()	EINVAL	Yes   No
	ENOMEM	Yes   No
	ENXIO	Yes   No
	ETXTBSY	Yes   No
frexp()	EDOM	Yes   No
fscanf()	EILSEQ	Yes   No
	EINVAL	Yes   No
	ENOMEM	Yes   No
	ENXIO	Yes   No
fsetpos()	EBADF	Yes   No
	ESPIPE	Yes   No
ftw()	EINVAL	Yes   No
getcwd()	EACCES	Yes   No
	ENOMEM	Yes   No
getgrgid()	EIO	Yes   No
	EINTR	Yes   No
	EMFILE	Yes   No
	ENFILE	Yes   No
getgrnam()	EIO	Yes   No
	EINTR	Yes   No
	EMFILE	Yes   No
	ENFILE	Yes   No
getlogin()	EMFILE	Yes   No
	ENFILE	Yes   No
	ENXIO	Yes   No
getpass()	EINTR	Yes   No
	EIO	Yes   No
	EMFILE	Yes   No
	ENFILE	Yes   No
	ENXIO	Yes   No
getpwnam()	EIO	Yes   No
	EINTR	Yes   No
	EMFILE	Yes   No
	ENFILE	Yes   No
getpwuid()	EIO	Yes   No
	EINTR	Yes   No
	EMFILE	Yes   No
	ENFILE	Yes   No
hcreate()	ENOMEM	Yes   No
hsearch()	ENOMEM	Yes   No
hypot()	EDOM	Yes   No
	ERANGE	Yes   No
iconv()	EBADF	Yes   No
iconv_close()	EBADF	Yes   No
iconv_open()	EMFILE	Yes   No
	ENFILE	Yes   No
	ENOMEM	Yes   No
	EINVAL	Yes   No
isatty()	EBADF	Yes   No
	ENOTTY	Yes   No
j0()	EDOM	Yes   No
	ERANGE	Yes   No
j1()	EDOM	Yes   No
	ERANGE	Yes   No
jn()	EDOM	Yes   No
	ERANGE	Yes   No
ldexp()	EDOM	Yes   No
	ERANGE	Yes   No
lgamma()	EDOM	Yes   No
	ERANGE	Yes   No
log()	EDOM	Yes   No
	ERANGE	Yes   No
log10()	EDOM	Yes   No
	ERANGE	Yes   No
mblen()	EILSEQ	Yes   No
mbstowcs()	EILSEQ	Yes   No
mbtowc()	EILSEQ	Yes   No
modf()	EDOM	Yes   No
	ERANGE	Yes   No
open()	EINVAL	Yes   No
	ETXTBSY	Yes   No
opendir()	EMFILE	Yes   No
	ENFILE	Yes   No
pathconf()	EACCES	Yes   No
	EINVAL	Yes   No
	ENAMETOOLONG	Yes   No
	ENOENT	Yes   No
	ENOTDIR	Yes   No
popen()	EMFILE	Yes   No
	EINVAL	Yes   No
pow()	EDOM	Yes   No
	ERANGE	Yes   No
putenv()	ENOMEM	Yes   No
read()	ENXIO	Yes   No
readdir()	EBADF	Yes   No
rename()	ETXTBSY	Yes   No
setvbuf()	EBADF	Yes   No
sigaction()	EINVAL	Yes   No
sigaddset()	EINVAL	Yes   No
sigdelset()	EINVAL	Yes   No
sigismember()	EINVAL	Yes   No
signal()	EINVAL	Yes   No
sin()	EDOM	Yes   No
	ERANGE	Yes   No
sinh()	EDOM	Yes   No
	ERANGE	Yes   No
sqrt()	EDOM	Yes   No
strcoll()	EINVAL	Yes   No
strerror()	EINVAL	Yes   No
strtod()	EINVAL	Yes   No
strtol()	EINVAL	Yes   No
strtoul()	EINVAL	Yes   No
strxfrm()	EINVAL	Yes   No
system()	ECHILD	Yes   No
tan()	EDOM	Yes   No
	ERANGE	Yes   No
tanh()	EDOM	Yes   No
	ERANGE	Yes   No
tcdrain()	EIO	Yes   No
tcflow()	EIO	Yes   No
tcflush()	EIO	Yes   No
tcsendbreak()	EIO	Yes   No
tcsetattr()	EIO	Yes   No
tmpfile()	EMFILE	Yes   No
	ENOMEM	Yes   No
ttyname()	EBADF	Yes   No
	ENOTTY	Yes   No
ungetwc()	EILSEQ	Yes   No
unlink()	ETXTBSY	Yes   No
wcscoll()	EINVAL	Yes   No
wcstod()	EINVAL	Yes   No
wcstol()	EINVAL	Yes   No
wcstombs()	EILSEQ	Yes   No
wcstoul()	EINVAL	Yes   No
wcsxfrm()	EINVAL	Yes   No
write()	ENXIO	Yes   No
y0()	EDOM	Yes   No
	ERANGE	Yes   No
y1()	EDOM	Yes   No
	ERANGE	Yes   No
yn()	EDOM	Yes   No
	ERANGE	Yes   No

Rationale

Each of the above error conditions is marked as optional in System Interfaces and Headers, Issue 4, Version 2 and an implementation may return this error in the circumstances specified or may not provide the error indication.

Reference

CAE Specification, System Interfaces and Headers, Issue 4, Version 2, Section 2.3, Error Numbers.

1.1.5 Mathematical Interfaces

Question 9: What format of floating-point numbers is supported by this implementation?

Response

Either use the default answer or provide a description of the floating point format used by your implementation.

Rationale

Most implementations support IEEE floating point format either in hardware or software. Some implementations support other formats with different exponent and mantissa accuracy. These differences need to be defined.

Reference

CAE Specification, System Interfaces and Headers, Issue 4, Version 2, Section 1.6, Relationship to Formal Standards.

1.1.6 Data Encryption

Question 10: Are the optional data encryption interfaces provided?

Response

Mark each of the following table entries appropriately. If your implementation is effected by any export restrictions imposed by the US Government, indicate these restrictions in the following area.

Function	Provided
crypt()	Yes   No
encrypt()	Yes   No
setkey()	Yes   No

Export Restrictions:

Rationale

Normally, an implementation will either provide all three of these routines or will provide none of them at all. If the routines are not provided, then the implementation must provide a dummy interface which always raises an ENOSYS error condition.

It is also possible that the implementation of the encrypt() function may be affected by export restrictions, in which case, the restrictions should be documented here.

For example, historical implementations have supplied all three of these routines outside the U.S.A., but due to export restrictions on the decoding algorithm, a dummy version of encrypt() is provided that does encoding but no decoding.

Reference

CAE Specification, System Interfaces and Headers, Issue 4, Version 2, Section 1.2, Conformance.

1.2 Process Handling

1.2.1 Process Generation

Question 11: Which file types (regular, directory, FIFO, special, and so on) are considered to be executable?

Response

Enter the file types that are executable on your implementation in the area below.

Rationale

The [EACCES] error associated with exec functions occurs in circumstances when the implementation does not support execution of files of the type specified. A list of these file types needs to be provided.

Reference

CAE Specification, System Interfaces and Headers, Issue 4, Version 2, Chapter 3, System Interfaces, exec.

1.3 File Handling

1.3.1 Access Control

Question 12: What file access control mechanisms does the implementation provide?

Response

Either indicate that "Standard access control is provided.", that the reader should "Refer to the POSIX.1 Conformance Document, Section 2.4", or provide a detailed description of the access control and/or additional or alternate access mechanisms on your implementation.

Rationale

System Interfaces and Headers, Issue 4, Version 2 notes that implementations may provide additional or alternate file access control mechanisms, or both.

Reference

CAE Specification, System Interface Definitions, Issue 4, Version 2, Chapter 2, Glossary, file access permissions.

1.3.2 Files and Directories

Question 13: Are any additional or alternate file access control mechanisms implemented that could cause fstat() or stat() to fail?

Response

Yes   No

Rationale

System Interfaces and Headers, Issue 4, Version 2 notes that there could be an interaction between additional and alternate access controls and the success of fstat() and stat(). This would suggest that an implementation can allow access to a file but not allow the process to gain information about the status of the file.

Reference

CAE Specification, System Interfaces and Headers, Issue 4, Version 2, Chapter 3, System Interfaces, fstat() and stat().

1.3.3 Formatting Interfaces

Question 14: Does the printf() function produce character string representations for Infinity and NaN to represent the respective values?

Response

Yes   No

Rationale

This behaviour is often provided on systems with mathematical functions that produce these results.

Reference

CAE Specification, System Interfaces and Headers, Issue 4, Version 2, Chapter 3, System Interfaces, fprintf().

1.4 Internationalised System Interfaces

1.4.1 Coded Character Sets

Question 15: What coded character sets are supported by the implementation?

Response

Rationale

System Interface Definitions, Issue 4, Version 2 states that conforming implementations support one or more coded character sets, and that each of these includes the portable character set.

Reference

CAE Specification, System Interface Definitions, Issue 4, Version 2, Chapter 4, Character Set.

Question 16: What is the implementation's underlying internal codeset?

Response

If the implementation does not use ISO 8859-1:1987, provide the name or description of the underlying codeset.

Rationale

It is useful to be aware of the underlying codeset of the implementation.

Reference

CAE Specification, System Interface Definitions, Issue 4, Version 2, Chapter 4, Character Set.

2. Appendix

Copyright © 
All rights reserved.

3. Change History