Conformance Statement

Product Standard: Internationalized Terminal Interfaces V2

Organization	IBM Corporation
Author	Manoranjan Sahu

1. Internationalized Terminal Interfaces V2

Product Information

Product Identification	Version/Release Number	Product Supplier
AIX 7 Operating System(PID 5765-G98)	AIX version 7, at either 7.2 TL5 (or later)	International Business Machine Corporation

Environment Specification

	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.2 TL5 (or later)with IBM XL C/C++ for AIX, V16.1, installed on JFS2 filesystems and running in 32bit(ILP32_OFF32) mode	Internationalized System Calls and Libraries Extended V4	None	Test Suite: None Test Report: None

Temporary Waivers

None

1.1 Product Scope

1.1.1 Type of Conformance

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:

Soft Conformance
This comprises a vendor declaration in the Conformance Statement of the differences in behavior of the conformant product and the X/Open Curses, Issue 7 Specification, including the Enhanced Curses Extension.
Hard Conformance
This involves strict conformance to the X/Open Curses, Issue 7 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

Internationalized Terminal Interfaces V2 Product Standard Definition.

1.1.2 Coded Character Sets

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 Internationalized Terminal Interfaces V2 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

Technical Standard, X/Open Curses, Issue 7, Section 1.2, Conformance.

1.2 Supported Terminals

Question 3: 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 Base Definitions, Issue 7, and the Curses interfaces defined in X/Open Curses, Issue 7, 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

Technical Standard, Base Definitions, Issue 7, Chapter 11, General Terminal Interface.

Technical Standard, X/Open Curses, Issue 7, Section 3.9, Synchronous and Networked Asynchronous Terminals.

1.3 Terminfo Source File Limits

Question 4: What limits does the implementation support for a terminfo source file?

Response

Description	Minimum Maximum	Implementation Maximum
Length of a line	1023	2048
Length of a terminal alias	14	2048
Length of a terminal model name	128	256
Length of a single field	128	10240
Length of a string value	1000	10240
Length of a string representing a numeric value	99	99
Magnitude of a numeric value	32767	32767

Rationale

X/Open Curses, Issue 7, specifies that a conformant implementation must declare its actual limits for the above items and defines minimum values that the implementation must support.

Technical Standard, X/Open Curses, Issue 7, Section 7.1.1, Minimum Guaranteed Limits.

1.4 Specific Interfaces

1.4.1 tparm()

Question 5: How does the tparm() function handle parameters in string context?

Response

The long int is converted to a char * pointer

Rationale

If any of the parameters %p1 through %p9 in a parameterized cap string passed to tparm() is used in a string context (for example, if it is popped using %l or %s), the behavior is implementation-defined. Traditionally the long int argument was converted to a pointer which was dereferenced to obtain the string to be used. However, this behavior is not appropriate on implementations where converting char * pointers to long int and back does not preserve their values.

Reference

Technical Standard, X/Open Curses, Issue 7, Chapter 4, tigetflag(), DESCRIPTION.

2. Appendix

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

3. Change History

Date	Name	Comment
New	Manoranjan Sahu	Initial UNIXv7 Submission for AIX V7.2 TL5 release on 09-2020

The Open Group, UNIX and The Open Brand ("X Device") are registered trademarks of The Open Group in the United States and other countries. All other trademarks are the property of their respective owners.