| |
|
| |
Home • About Us •A-Z Index• Search • Inquiries • Register• Login• Press • Shop | |
|
|
| Organization | IBM |
|---|---|
| Author | Manoranjan Sahu |
| Product Identification | Version/Release Number | Product Supplier |
|---|---|---|
| AIX 7 Operating System(PID 5765-G98) | Version 7, at either 7.1 TL5 (or later), or 7.2 TL2 (or later) | International Business Machines Corporation |
| Testing Environment | Binary-compatible Family | Portability Environment | Indicator of Compliance | Compliance Details |
|---|---|---|---|---|
| IBM p Series and System p UNIX Servers | HARDWARE: Systems using CHRP system architecture with POWER(tm) processors and 2, 8 or 128 port async cards. SOFTWARE: AIX Version 7, at either 7.1 TL5 (or later), or 7.2 TL2 (or later) with IBM XL C/C++ for AIX, V13.1, installed on JFS2 filesystems and running in 32bit(ILP32_OFF32) mode | Internationalised System Calls and Libraries Extended | None | Test Suite: none Test Report: none |
None
Question 1: What is the state of conformance of this product?
Response
Soft Conformance.
Rationale
Two sets of conformance rules are defined within this Product Standard:
This comprises a vendor declaration in the Conformance Statement of the differences in behavior of the conformant product and the X/Open Curses, Issue 4, Version 2 Specification, including the Enhanced Curses Extension.
This involves strict conformance to the X/Open Curses, Issue 4, Version 2 Specification, including the Enhanced Curses Extension, and use of the test suite as the Indicator of Compliance. The running of the relevant test cases is determined by a parameter of the VSU5 Test Suite.
Reference
Internationalised Terminal Interfaces Product Standard Definition.
Question 2: Which coded character sets are supported by the chtype data type?
Response
ISO 8859-1 IBM PC-850
Rationale
An implementation that claims BASE, BASE 95 or UNIX conformance and Internationalised Terminal Interfaces conformance must support at least octet-based code sets (such as ISO 8859-1), within the chtype data type. Support for other coded character sets is implementation-defined.
Reference
CAE Specification, X/Open Curses, Issue 4, Section 1.2, Conformance.
Question 3: Which character attributes are supported by the implementation?
Response
| A_ALTCHARSET | Supported |
| A_HORIZONTAL | Not supported |
| A_LEFT | Not supported |
| A_LOW | Not supported |
| A_RIGHT | Not supported |
| A_TOP | Not supported |
| A_VERTICAL | Not supported |
Rationale
An implementation that claims BASE or BASE 95 conformance and Internationalised Terminal Interfaces conformance must support at least the character attributes: A_BLINK, A_BOLD, A_DIM, A_REVERSE, A_STANDOUT and A_UNDERLINE. Support for other character attributes, listed above, is implementation-defined.
Reference
CAE Specification, X/Open Curses, Issue 4, Chapter 5, Headers.
Question 4: Which of the following terminal types are supported by the implementation (if any)?
Response
| Synchronous | No |
|---|---|
| A character cannot be transmitted by a single key stroke only in blocks | No |
| The refresh() routine must redraw the entire screen contents in order to perform any update | No |
| It is not possible to disable echo | No |
| There are additional limitations defined below | No |
| Networked Asynchronous | Yes |
|---|---|
| A character cannot be transmitted by a single key stroke only in blocks | No |
| The refresh() routine must redraw the entire screen contents in order to perform any update | No |
| It is not possible to disable echo | No |
| There are additional limitations defined below | No |
| Non-standard Asynchronous | No |
|---|---|
| A character cannot be transmitted by a single key stroke only in blocks | No |
| The refresh() routine must redraw the entire screen contents in order to perform any update | no |
| It is not possible to disable echo | No |
| There are additional limitations defined below | No |
Rationale
The General Terminal Interface described in System Interface Definitions, Issue 4, Version 2, and the Curses interfaces defined in X/Open Curses, Issue 4, are provided to control terminals connected to asynchronous communication ports. They may also be used to control synchronous, networked asynchronous or non-standard directly-connected asynchronous terminals, subject to possible implementation-defined limitations.
Reference
CAE Specification, System Interface Definitions, Issue 4, Version 2, Chapter 9, General Terminal Interface.
CAE Specification, X/Open Curses, Issue 4, Section 3.9, Synchronous and Networked Asynchronous Terminals.
Question 5: What limits does the implementation support for a terminfo source file?
Response
| Length of a line | 2048 |
| Length of a terminal alias | 2048 |
| Length of a terminal model name | 256 |
| Length of a single field | 10240 |
| Length of a string value | 10240 |
| Length of a string representing a numeric value | 99 |
| Magnitude of a numeric value | 32767 |
Rationale
X/Open Curses, Issue 4, specifies that a conformant implementation must declare its actual limits for the above items and defines minimum values that the implementation must support.
Copyright © 2017 International Business Machines Corporation
All rights reserved.
| Date | Name | Comment |
|---|---|---|
| New | Manoranjan Sahu | Initial UNIX03 Submission for AIX V7.1 TL5 and AIX V7.2 TL2 release on 10-2017 |
Copyright © 1998-2017 The Open Group. All Rights Reserved.
OSF/1, Motif, UNIX, and the "X" device are registered trademarks in
the U.S. and other countries, and IT DialTone and The Open Group are
trademarks of The Open Group.