HomeAbout Us A-Z IndexSearch

IBM Corporation Conformance Statement

Product Standard: Internationalised System Calls and Libraries Extended V2

Organization International Business Machines Corporation
Author William L. Toth


1. Internationalised System Calls and Libraries Extended V2

Product Information

Product IdentificationVersion/Release NumberProduct Supplier
1. AIX 5L for POWER V5.1 Version 5, Release 1 dated 09-2001 or later (PID 5765-E61) International Business Machines Corporation 

Environment Specification

Testing Environment Binary-compatible Family Portability Environment Indicator of Compliance Compliance Details
1.
IBM RS/6000, Model 43P-240
HARDWARE:Systems using Power(tm) or PowerPC(tm) architecture based processors and 8 or 128 port async cards. Systems not supported are IBM RS/6000 models: 730 and N40. SOFTWARE:AIX 5L for POWER V5.1 dated 9-2001 or later
None. Test Report from Test Suite Test Suite: VSX 4.4.5
Test Report: OSCC-CTR-08-XSH4
2.
IBM RS/6000, Model 43P-240
HARDWARE:Systems using Power(tm) or PowerPC(tm) architecture based processors and 8 or 128 port async cards. Systems not supported are IBM RS/6000 models: 730 and N40. SOFTWARE:AIX 5L for POWER V5.1 dated 9-2001 or later
None. Test Report from Test Suite Test Suite: VSX5.1.6
Test Report: OSCC-CTR-08-XSH5
3.
IBM RS/6000, Model 43P-140
HARDWARE:Systems using Power(tm) or PowerPC(tm) architecture based processors and 8 or 128 port async cards. Systems not supported are IBM RS/6000 models: 730 and N40. SOFTWARE:AIX 5L for POWER V5.1 dated 9-2001 or later
None. Test Report from Test Suite Test Suite: VSTH 5.2.3
Test Report: OSCC-CTR-08-PTHR
4.
IBM RS/6000, Model 43P-240
HARDWARE:Systems using Power(tm) or PowerPC(tm) architecture based processors and 8 or 128 port async cards. Systems not supported are IBM RS/6000 models: 730 and N40. SOFTWARE:AIX 5L for POWER V5.1 dated 9-2001 or later
None. Test Report from Test Suite Test Suite: VSU 5.1.2
Test Report: OSCC-CTR-08-SUS

Temporary Waivers

None.


1.1 General Attributes

1.1.1 Feature Groups

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

Response

Rationale

Reference


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

Rationale

Reference


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

Rationale

Reference


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

Response

Rationale

Reference


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

Response

Rationale

Reference


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

Response

Rationale

Reference


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

Response

Rationale

Reference


1.1.4 Error Conditions

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

Response

Rationale

Reference


1.1.5 Mathematical Interfaces

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

Response

Rationale

Reference


1.1.6 Data Encryption

Question 10: Are the optional data encryption interfaces provided?

Response

Rationale

Reference


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

Rationale

Reference


1.3 File Handling

1.3.1 Access Control

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

Response

Rationale

Reference


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

Rationale

Reference


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

Rationale

Reference


1.4 Internationalised System Interfaces

1.4.1 Coded Character Sets

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

Response

Rationale

Reference


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

Response

Rationale

Reference


1.5 STREAMS

Question 17: What networking services or other character-based I/O device types are implemented using STREAMS in addition to pseudo-terminals?

Response

Rationale

Reference


1.6 Pseudo-Terminals

1.6.1 Master close

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

Response

Rationale

Reference


1.6.2 Slave close

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

Response

Rationale

Reference


1.6.3 Naming Conventions

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

Response

Rationale

Reference


1.7 Polling

Question 21: What types of file can be polled?

Response

Rationale

Reference


1.8 Stack Growth Direction

Question 22: What is the direction of stack growth?

From higher to lower addresses.

Rationale

Reference


1.9 Signal Codes

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

Response

Rationale

Reference


1.10 Set Process Group ID

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

Response

Rationale

Reference


1.11 Signals Generating a Core File

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

Response

Rationale

Reference


1.12 Realtime

1.12.1 Prioritized I/O

Question 26: Does the implementation support _POSIX_PRIORITIZED_IO?

Response

Rationale

Reference


1.12.2 Cancelable Asynchronous I/O Operations

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

Response

Rationale

Reference


1.13 Threads

1.13.1 Cancellation Points

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

Response

Rationale

Reference


1.14 Realtime Threads

1.14.1 Scheduling Policies

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

Response

Rationale

Reference


1.14.2 Scheduling Contention Scope

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

Response

Rationale

Reference


1.14.3 Default Scheduling Contention Scope

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

Response

Rationale

Reference


1.15 C-language Compilation Environment

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

Response

Rationale

Reference


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

Response

Rationale

Reference


2. Appendix

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


Copyright © 2001 International Business Machines Corporation
All rights reserved.


3. Change History

DateNameComment
17-Sep-2001 William L. Toth Updated for AIX 5L, V5.1 9-2001 release 
02-Oct-2000 William L. Toth Updated for AIX 4.3.3, 10-2000 release for OEM Users of AIX 
20-Apr-2000 The Open Group Update data entry for Q27/Q29 for new template 
21-Dec-1999 The Open Group Data Entry for Q27 
23-Jun-1998 The Open Group Data Entry of Appendix Information. 

 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 ]