HomeAbout Us A-Z IndexSearch

IBM Corporation Conformance Statement

Product Standard: Internationalized System Calls and Libraries Extended V3

Organization International Business Machines Corporation
Author Willam L. Toth


1. Internationalized System Calls and Libraries Extended V3

Product Information

Product IdentificationVersion/Release NumberProduct Supplier
1. AIX 6 Operating System(PID 5765-G62) Version 6, Release 1, Modification 2 SP1 International Business Machines Corporation 

Environment Specification

Testing Environment Binary-compatible Family Portability Environment Indicator of Compliance Compliance Details
1.
IBM System p Server: Model 570, VIO client.
HARDWARE: Systems using CHRP system architecture with POWER(tm) processors and 2, 8 or 128 port async cards. SOFTWARE: AIX 6 Operating System, Version 6.1.2 SP1 or later with IBM XL C/C++ for AIX, V10.1, installed on JFS2 filesystems and running in 32bit(ILP32_OFF32) mode
None. Test Report from Test Suite Test Suite: VSX 4.6.9
Test Report: OSCC-CTR-13-XSH4
2.
IBM p Series Server: Model 550.
HARDWARE: Systems using CHRP system architecture with POWER(tm) processors and 2, 8 or 128 port async cards. SOFTWARE: AIX 6 Operating System, Version 6.1.2 SP1 or later with IBM XL C/C++ for AIX, V10.1, installed on JFS2 filesystems and running in 32bit(ILP32_OFF32) mode
None. Test Report from Test Suite Test Suite: VSX 5.2.12
Test Report: OSCC-CTR-13-XSH5
3.
IBM System p Server: Model 570, VIO client.
HARDWARE: Systems using CHRP system architecture with POWER(tm) processors and 2, 8 or 128 port async cards. SOFTWARE:AIX 6 Operating System, Version 6.1.2 SP1 or later with IBM XL C/C++ for AIX, V10.1, installed on JFS2 filesystems and running in 32bit(ILP32_OFF32) mode
None. Test Report from Test Suite Test Suite: VSU 5.2.11
Test Report: OSCC-CTR-13-SUS
4.
IBM p Series Server: Model 510.
HARDWARE: Systems using CHRP system architecture with POWER(tm) processors and 2, 8 or 128 port async cards. SOFTWARE: AIX 6 Operating System, Version 6.1.2 SP1 or later with IBM XL C/C++ for AIX, V10.1, installed on JFS2 filesystems and running in 32bit(ILP32_OFF32) mode
None. Test Report from Test Suite Test Suite: VSTH 5.4.8
Test Report: OSCC-CTR-13-PTHR
5.
IBM p Series Server: Model 510.
HARDWARE: Systems using CHRP system architecture with POWER(tm) processors and 2, 8 or 128 port async cards. SOFTWARE: AIX 6 Operating System, Version 6.1.2 SP1 or later with IBM XL C/C++ for AIX, V10.1, installed on JFS2 filesystems and running in 32bit(ILP32_OFF32) mode
None. Test Report from Test Suite Test Suite: VSART 1.1.8
Test Report: OSCC-CTR-13-ART
6.
IBM p Series Server: Model 510.
HARDWARE: Systems using CHRP system architecture with POWER(tm) processors and 2, 8 or 128 port async cards. SOFTWARE: AIX 6 Operating System, Version 6.1.2 SP1 or later with IBM XL C/C++ for AIX, V10.1, installed on JFS2 filesystems and running in 32bit(ILP32_OFF32) mode
None. Test Report from Test Suite Test Suite: VSRT 5.3.9
Test Report: OSCC-CTR-13-RT
7.
IBM System p Server: Model 570, VIO client.
HARDWARE: Systems using CHRP system architecture with POWER(tm) processors and 2, 8 or 128 port async cards. SOFTWARE: AIX 6 Operating System, Version 6.1.2 SP1 or later with IBM XL C/C++ for AIX, V10.1, installed on JFS2 filesystems and running in 32bit(ILP32_OFF32) mode
None. Test Report from Test Suite Test Suite: VSRTE 1.1.9
Test Report: OSCC-CTR-13-RTE

Temporary Waivers

None.


1.1 General Attributes

1.1.1 XSI Option Groups

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

Response


1.1.2 Options

Question 2: Which of the following options are supported by the implementation?

Response


1.1.3 POSIX.1 Supported Features

Question 3: For each of the symbolic constants, specified in the <unistd.h> header file, are the associated features always available on the system?

Response


1.1.4 Float, Stdio, and Limit Values

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

Response


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

Response


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

Response


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

Response


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

Response


1.1.5 Error Conditions

Question 9: Which of the following option errors, ( denoted by "may fail" within the specification ), listed in System Interfaces, Issue 6 are detected in the circumstances specified?

Response


1.1.6 Mathematical Interfaces

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

Response


Question 11: Which floating-point exceptions are supported by this implementation for the fegetexecptflag(), feraiseexcept(), fesetexecptflag(), and fetestexecptflag() functions?

Response


Question 12: Which floating-point rounding directions are supported by this implementation for the fegetround(), and fesetround() functions?

Response


Question 13: Is a non-stop floating-point exception mode supported by this implementation?

Response


1.1.7 Data Encryption

Question 14: Are the optional data encryption interfaces provided?

Response


1.2 Process Handling

1.2.1 Process Generation

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

Response


1.3 File Handling

1.3.1 Access Control

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

Response


1.3.2 Files and Directories

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

Response


1.4 Internationalized System Interfaces

1.4.1 Coded Character Sets

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

Response


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

Response


1.5 Pseudo-Terminals

1.5.1 Master close

Question 20: Does closing the master side of a pseudo-terminal flush all queued input and output?

Response


1.5.2 Slave close

Question 21: Does closing the slave side of a pseudo-terminal cause a zero-length message to be sent to the master?

Response


1.5.3 Naming Conventions

Question 22: What naming conventions are associated with the master side of pseudo-terminal devices?

Response


1.6 Polling

Question 23: What types of file can be polled?

Response


1.7 Stack Growth Direction

Question 24: What is the direction of stack growth?

Response


1.8 Signal Codes

Question 25: Which of the following si_code values may be generated?

Response


1.9 Set Process Group ID

Question 26: Does the setpgrp() function create a new session?

Response


1.10 Signals Generating a Core File

Question 27: Does the implementation generate a core file when the following signals are delivered to a process?

Response


1.11 Sockets

1.11.1 Listen Queues

Question 28: What is the limit the implementation places on the length of a socket's listen queue?

Response


1.11.2 Address Families, Socket Types, and Protocols

Question 29: What combinations of address family, socket types, and protocols does the implementation support?

Response


1.11.3 Socket Types

Question 30: What socket types does the implementation support?

Response


1.12 Threads

1.12.1 Cancellation Points

Question 31: Which functions have cancellation points that occur when a thread is executing?

Response


1.13 C-language Compilation Environment

Question 32: What C-language compilation environments are provided?

Response


Question 33: What execution environments are provided on the system under test?

Response


1.14 Realtime

1.14.1 Prioritized I/O

Question 34: Does the implementation support _POSIX_PRIORITIZED_IO?

Response


1.14.2 Cancelable Asynchronous I/O Operations

Question 35: If the Realtime Option Group is supported, what asynchronous I/O operations are cancelable with aio_cancel()?

Response


1.15 Realtime Threads

1.15.1 Scheduling Policies

Question 36: If the Realtime Threads Option Group is supported, what scheduling policy is associated with SCHED_OTHER?

Response


1.15.2 Scheduling Contention Scope

Question 37: If the Realtime Threads Option Group is supported, what scheduling contention scopes are supported: PTHREAD_SCOPE_PROCESS, PTHREAD_SCOPE_SYSTEM, or both?

Response


1.15.3 Default Scheduling Contention Scope

Question 38: If the Realtime Threads Option Group is supported, what is the default scheduling contention scope when a process is created?

Response


2. Appendix

This appendix contains additional, explanatory material that was provided by the vendor.


Copyright © 2009 International Business Machines Corporation
All rights reserved.


3. Change History

DateNameComment
07-Apr-2009 Conformance Administrator Noted in Appendix section the corrected response to Question 34 
07-Apr-2009 Conformance Administrator Correction of files the system supports for _POSIX_PRIORITIZED_IO in Question 34 
27-Feb-2009 William L. Toth UNIX03 Submission for AIX 6 Operating System Version 6.1.2 SP1 release 
03-Aug-2006 Willliam L. Toth UNIX03 Submission for the 8-2006 AIX V5.3 release 
16-Nov-2004 Conformance Administrator Correct LDBL_EPSILON entry in Question 4. 
09-Sep-2004 William L. Toth Initial UNIX03 Submission on the 8-2004 AIX V5.2 release 

 Copyright © 1998-2011 The Open Group. All Rights Reserved.

 The Open Group and Boundaryless Information Flow are trademarks and UNIX is a registered trademark of The Open Group in the United States and other countries. All other trademarks are the property of their respective owners.


[ Home ] [ The Open Brand ] [ Conformance Statement Library ] [ Search Conformance Statements ] [ Send Feedback ]