XXXX////OOOOppppeeeennnn CCCCoooonnnnffffoooorrrrmmmmaaaannnncccceeee SSSSttttaaaatttteeeemmmmeeeennnntttt
for
HP-UX Release 8.0x
on
HP 9000 Series 600/700/800 Computers
XXXX////OOOOppppeeeennnn PPPPoooorrrrttttaaaabbbbiiiilllliiiittttyyyy GGGGuuuuiiiiddddeeee 3333
Completed by Hewlett-Packard Company
on May 24, 1991.
Document Revision Number 3.2
HHHHPPPP PPPPaaaarrrrtttt NNNNuuuummmmbbbbeeeerrrr BBBB2222333355555555----99990000666600005555
PPPPrrrriiiinnnntttteeeedddd iiiinnnn UUUUSSSSAAAA AAAAuuuugggguuuusssstttt 1111999999991111
9 FFFFiiiirrrrsssstttt EEEEddddiiiittttiiiioooonnnn
EEEE0000888899991111
9
X/Open Conformance Statement XCS-QUE-3.2
Questionnaire
CCCCoooonnnntttteeeennnnttttssss
CCCChhhhaaaapppptttteeeerrrr 1111:::: IIIInnnnttttrrrroooodddduuuuccccttttiiiioooonnnn
CCCChhhhaaaapppptttteeeerrrr 2222:::: IIIInnnntttteeeerrrrnnnnaaaattttiiiioooonnnnaaaalllliiiisssseeeedddd SSSSyyyysssstttteeeemmmm CCCCaaaallllllllssss aaaannnndddd LLLLiiiibbbbrrrraaaarrrriiiieeeessss
Section 2.1: General Attributes
Section 2.2: Process Handling
Section 2.3: File Handling
Section 2.4: General Terminal Interface
Section 2.5: Internationalised System
Interfaces
CCCChhhhaaaapppptttteeeerrrr 3333:::: CCCCoooommmmmmmmaaaannnnddddssss aaaannnndddd UUUUttttiiiilllliiiittttiiiieeeessss
Section 3.1: Basic Utilities
Section 3.2: Development Utilities
Section 3.3: Internationalisation Option
CCCChhhhaaaapppptttteeeerrrr 4444:::: CCCC LLLLaaaannnngggguuuuaaaaggggeeee
X/Open Conformance Statement XCS-QUE-3.2
Questionnaire
CCCChhhhaaaapppptttteeeerrrr 1111:::: IIIInnnnttttrrrroooodddduuuuccccttttiiiioooonnnn
CCCCoooonnnntttteeeennnnttttssss ooooffff tttthhhheeee QQQQuuuueeeessssttttiiiioooonnnnnnnnaaaaiiiirrrreeee
This questionnaire consists of a number of chapters each
of which, with the exception of this first chapter,
relates directly to a specific brandable component.
This first chapter contains introductory material to the
questionnaire explaining its purpose and providing
information for those answering the questions.
The arrangement of subsequent chapters is as follows:-
Chapter XPG3 Volumes Brandable Component
8 _____________________________________________________________________
2 2 & 3 Internationalised System Calls and Libraries
3 1 & 3 Commands and Utilities
4 4 C Language
5 5 ISAM
6 7 XTI Transport Interface
7 4 COBOL Language
8 4 PASCAL Language
9 4 FORTRAN Language
10 5 SQL
11 3 Terminal Interfaces
12 6 Window Management
13 7 PC Interworking
14 2 Inter-Process Communication
15 3 Source Code Transfer
16 4 ADA Language
In some cases these chapters require answers to detailed
questions about the implementation. In the case of
languages other than C, a specification of the
referenced conformance statement is requested.
Each of the conformance statements for a component
contains a specification of the product, the conformance
measurement and the environment in which the product
operates. The specification of the environment allows
the producer to state which other hardware/software
environments also support an identical binary version of
the product. Thus a product can be specified as being
PC compatible, ABI compatible for a specific processor
family, distributed in ANDF form etc.
9
Page 1.1
X/Open Conformance Statement XCS-QUE-3.2
Questionnaire
PPPPuuuurrrrppppoooosssseeee ooooffff tttthhhheeee CCCCoooonnnnffffoooorrrrmmmmaaaannnncccceeee SSSSttttaaaatttteeeemmmmeeeennnntttt
The X/Open Conformance Statement provides details of the
manner in which a specific implementation meets the
definitions contained in the X/Open Portability Guide,
and defines the environment in which conformant
behaviour, and any test results, may be reproduced.
In addition, the X/Open Conformance Statement provides
details of waivers granted by X/Open Company in respect
of product errors of a minor nature, which have a
negligible effect on application portability. Such
waivers, referred to as _t_e_m_p_o_r_a_r_y _w_a_i_v_e_r_s, are granted
for a limited period, during which the implementor
undertakes to effect a correction.
The majority of the definitions in XPG3 are mandatory
and all branded components will conform to these
definitions. There are however a number of optional
features in XPG3 which an implementor can choose to
provide. The conformance statement identifies whether
these optional features have are provided or not.
The options that are identified in the conformance
statement fall into a number of different categories as
follows:-
o+ Major aspects of XPG3 that are stated to be
optional. For example, the development utilities in
the XSI Commands and Utilities definition.
o+ Extensions that may affect defined interfaces. For
example, full internationalisation support which
affects the behaviour of many utilities.
o+ Implementation choices to support different
hardware architectures. For example, the floating
point format provided.
The conformance statement characterises the variances
between the different conforming implementations of the
XPG definitions. The conformance statement is a useful
document for any person who requires knowledge of the
details of a conforming implementation.
Minor implementation choices that should not affect a
portable application, for example the manner in which
the group ownership of a newly created file is
determined are not included in the conformance
statement. A well behaved application should not rely on
behaviour that is stated to be undefined or unspecified
Page 1.2
X/Open Conformance Statement XCS-QUE-3.2
Questionnaire
in the X/Open Portability Guides. Only cases where the
behaviour is explicitly stated to be optional are
considered in the conformance statement.
RRRReeeellllaaaattttiiiioooonnnnsssshhhhiiiipppp ttttoooo tttthhhheeee XXXX////OOOOppppeeeennnn PPPPoooorrrrttttaaaabbbbiiiilllliiiittttyyyy GGGGuuuuiiiiddddeeee
The conformance statement has been developed from the
definitions contained in the X/Open Portability Guide 3.
The following volumes of XPG3 have been used as a source
of information:-
Volume 1 XSI Commands and Utilities
Volume 2 XSI System Interface and Headers
Volume 3 XSI Supplementary Definitions
Volume 4 Programming Languages
Volume 5 Data Management
Volume 6 Window Management
Volume 7 Networking Services
The XSI Supplementary Definitions has only been used to
obtain information regarding the implementation of
Native Language Systems and Source Code Transfer. These
aspects of the supplementary definitions are referenced
in both volumes 1 and 2 of XPG3 and are considered to be
integral with the definitions in these volumes.
In general, additions to the specifications contained in
XPG3 have not been considered in the conformance
statement, unless the presence of these additions could
have an effect on the specifications contained in XPG3.
For example, the implementation of internationalisation
is considered important because this can affect the
behaviour of interfaces in the XPG. On the other hand,
the definition and occurrence of error indications other
than those mentioned in the XPG is not considered
important because these error indications should not be
provided to an application that conforms to the
interfaces provided in the XPG.
RRRReeeellllaaaattttiiiioooonnnnsssshhhhiiiipppp ttttoooo VVVVSSSSXXXX CCCCoooonnnnffffoooorrrrmmmmaaaannnncccceeee TTTTeeeessssttttiiiinnnngggg
VSX Conformance Testing is one element in the
determination of an X/Open branded system. There are a
number of reasons why conformance testing is not, by
itself, adequate as a complete measure of the
conformance of an implementation. As the conformance
tests are improved and enhanced to cover additional
areas within the XPG, the degree of confidence
associated with conformance testing will increase.
Page 1.3
X/Open Conformance Statement XCS-QUE-3.2
Questionnaire
Several of the major implementation options are already
accepted by VSX, and the conformance of these options is
measured. However, there are a considerable number of
areas which are not covered by conformance testing and
which need to be identified in the conformance
statement. The conformance statement acts as a
specification of the implementation and is the basis of
the statement of conformance provided by the
implementor. The conformance tests act as a monitor of
the statement of conformance, providing evidence of any
deviant behaviour in those areas covered by the
conformance tests.
The conformance statement should align with the evidence
provided by the execution of the conformance tests. For
example, if the conformance statement states that the
implementation provides jjjjoooobbbb ccccoooonnnnttttrrrroooollll facilities, then the
conformance tests should have verified that the
implementation provides these facilities according to
the XPG specifications.
CCCCoooommmmpppplllleeeettttiiiinnnngggg tttthhhheeee QQQQuuuueeeessssttttiiiioooonnnnnnnnaaaaiiiirrrreeee
It is expected that the questionnaire will need to be
completed with the assistance of engineering staff who
have an understanding of the manner in which the
Commands and Utilities, the System Interfaces and the
separate Internationalised environment have been
implemented. This may involve more than one person and
the questionnaire has been divided into different
components which can be addressed by these different
people.
FFFFoooorrrrmmmmaaaatttt ooooffff tttthhhheeee QQQQuuuueeeessssttttiiiioooonnnnnnnnaaaaiiiirrrreeee
This questionnaire contains a series of questions about
various aspects of an implementation which may differ
between different XPG conforming implementations. After
each question there is space provided for the user to
enter his answers. Some questions have a simple binary
choice and others require the user to specify a value.
In these cases the answer field is provided. Where the
answer field requires a textual response, the user is
allowed to enter text in free format mode.
In addition to the question and answer fields the
following additional information as appropriate:-
o+ A set of OOOOppppttttiiiioooonnnnssss that may be used to answer the
question. This includes a reference to the
corresponding POSIX Conformance Document where
Page 1.4
X/Open Conformance Statement XCS-QUE-3.2
Questionnaire
appropriate.
o+ A statement of the RRRRaaaattttiiiioooonnnnaaaalllleeee for the question.
o+ An EEEExxxxaaaammmmpppplllleeee of an appropriate form for the answer to
the question.
o+ A RRRReeeeffffeeeerrrreeeennnncccceeee to POSIX standards or to XPG3.
The completed questionnaire forms the conformance
statement which should be a relatively short document,
providing brief answers to the questions with pointers
to the implementor’s documentation to provide additional
detailed documentation.
Page 1.5
X/Open Conformance Statement XCS-QUE-3.2
Questionnaire
CCCChhhhaaaapppptttteeeerrrr 2222:::: IIIInnnntttteeeerrrrnnnnaaaattttiiiioooonnnnaaaalllliiiisssseeeedddd SSSSyyyysssstttteeeemmmm CCCCaaaallllllllssss aaaannnndddd LLLLiiiibbbbrrrraaaarrrriiiieeeessss
PPPPrrrroooodddduuuucccctttt IIIIddddeeeennnnttttiiiiffffiiiiccccaaaattttiiiioooonnnn
Product Identification HP-UX
9 Version/Release No. 8.0x for Series 600/700/800
If you do not supply this component yourself, please
identify below the supplier you reference.
Supplied by HP.
CCCCoooonnnnffffoooorrrrmmmmaaaannnncccceeee RRRReeeeffffeeeerrrreeeennnncccceeee
Indicator of Compliance
VSX Test Suite Release 3.204
9 Testing Agency Name Hewlett-Packard Company
9 Address 3404 East Harmony Rd.
9 Fort Collins, Co 80525-9599
9 USA
EEEEnnnnvvvviiiirrrroooonnnnmmmmeeeennnntttt SSSSppppeeeecccciiiiffffiiiiccccaaaattttiiiioooonnnn
Enter below details of the hardware and software
environment in which testing took place, including
compilation routines and installation procedures (if
any). Sufficient detail must be supplied to enable
conformant behaviour and any test results to be
reproduced.
Setup requirements:
o+ HP 9000 Series 600 700 or 800. Standalone, root
server, and diskless nodes in any supported
configuration.
o+ HP-UX 8.0 for the machine/configuration in use.
o+ 16 Mb memory
o+ Sufficient disk space for the tests to have at least
80Mb free on a single volume or partition.
9
Page 2.1
X/Open Conformance Statement XCS-QUE-3.2
Questionnaire
o+ Loopback cable:
TX -RX
RX -TX
DCD-DTR
DTR-DCD
GND-GND
o+ Mountable empty drive or partition.
o+ There are three I/O architectures possible: device
special files are needed as follows.
S700
mknod /dev/ttyd0p0 c 1 0x204001
mknod /dev/ttyd0p1 c 1 0x205001
mknod /dev/b_special b 7 0x201900
mknod /dev/c_special c 47 0x201900
S800-CIO) (Models 825,835,840,850,855,870)
mknod /dev/ttyd0p1 c 1 0x100001
mknod /dev/ttyd0p2 c 1 0x100002
mknod /dev/b_special b 8 0x000906
mknod /dev/c_special c 7 0x000906
S800-NIO) (Models 815,822,832,842,852)
mknod /dev/ttyd0p1 c 58 0x100001
mknod /dev/ttyd0p2 c 58 0x100002
mknod /dev/b_special b 8 0x000906
mknod /dev/c_special c 7 0x000906
o+ All tests were run self-hosted on the machine being
tested.
o+ Compiler options used : -D_XOPEN_SOURCE -Aa
o+ Libraries used: -lM
o+ Due to security enhancements, a link must be created:
ln -s /etc/group /etc/logingroup
o+ If you wish to test the system with
{_POSIX_CHOWN_RESTRICTED} enabled enter (as superuser)
the command:
setprivgrp -n CHOWN
to disable it, use
setprivgrp -g CHOWN
The formal branding run was done with
Page 2.2
X/Open Conformance Statement XCS-QUE-3.2
Questionnaire
{_POSIX_CHOWN_RESTRICTED} enabled.
o+ If you wish to run the tests with long file names, use
the superuser command
convertfs <filesystem>
The formal branding run was done with long file names.
o+ When the test is to be run on a diskless client:
- Additional inodes are needed in the client kernel.
Regenerate the system (as described in the System
Administration Manual) to set ninode to 712, and
nfile to 1200.
- After clusterizing, ensure that the permissions
for /dev/rdsk are drwxr-xr-x.
TTTTeeeemmmmppppoooorrrraaaarrrryyyy WWWWaaaaiiiivvvveeeerrrrssss
List below references to any temporary waivers granted
by X/Open in respect of minor errors in the product
referenced above. This should include the X/Open
reference and the waiver expiry date. The waivers as
granted shall be made available with this document on
request.
None.
Page 2.3
X/Open Conformance Statement XCS-QUE-3.2
Questionnaire
SSSSeeeeccccttttiiiioooonnnn 2222....1111:::: GGGGeeeennnneeeerrrraaaallll AAAAttttttttrrrriiiibbbbuuuutttteeeessss
9
2.1.1 PPPPOOOOSSSSIIIIXXXX....1111 SSSSuuuuppppppppoooorrrrtttteeeedddd FFFFeeeeaaaattttuuuurrrreeeessss
QQQQuuuueeeessssttttiiiioooonnnn 1111:::: _W_h_i_c_h _o_f _t_h_e _f_o_l_l_o_w_i_n_g _o_p_t_i_o_n_s, _s_p_e_c_i_f_i_e_d _i_n _t_h_e
<<<<uuuunnnniiiissssttttdddd....hhhh>>>> _h_e_a_d_e_r _f_i_l_e, _a_r_e _a_v_a_i_l_a_b_l_e _o_n _t_h_e _s_y_s_t_e_m?
AAAAnnnnsssswwwweeeerrrr::::
Macro Name Meaning Provided
8 ______________________________________________________________________
9 _POSIX_CHOWN_RESTRICTED The use of cccchhhhoooowwwwnnnn(((()))) is restricted Variable
9 _POSIX_JOB_CONTROL Job Control option Yes
9 _POSIX_NO_TRUNC Variable
7 Long pathname components
generate an error
9 _POSIX_SAVED_IDS Yes
7 Effective user and group IDs are
saved
9 _POSIX_VDISABLE Yes
7 Terminal special characters can
be disabled
Options:
When the option is variable a description is required
for the cases over which the variations occur.
Rationale
For an X/Open conforming implementation the
_POSIX_SAVED_IDS option must be provided. The other
options may or may not be provided. The provision of
the file system related options can vary within a
system. For example, a system which has traditionally
supported both System V and BSD type file systems may
provide a mechanism whereby the option is enforced for
certain files or processes but not for others. This
technique can be used to achieve a degree of backwards
compatibility that would not otherwise be possible.
Reference
XPG3 Volume 2 Page 579 - <<<<uuuunnnniiiissssttttdddd....hhhh>>>>.
_POSIX_CHOWN_RESTRICTED is enabled and disabled on a
per-group-id (or system-wide) basis by the
setprivgrp(1m) command. _POISIX_CHOWN_RESTRICTED is
equivalent to not granting the CHOWN privilege.
_POSIX_NO_TRUNC is enabled on a filesystem where long
9
Page 2.1.1
X/Open Conformance Statement XCS-QUE-3.2
Questionnaire
file names are enabled, and disabled on filesystems
where long filenames are disabled. The default short
filename filesystem can be converted to a long
filename filesystem by the convertfs(1m) command.
9
2.1.2 CCCC SSSSttttaaaannnnddddaaaarrrrdddd
QQQQuuuueeeessssttttiiiioooonnnn 2222:::: _D_o_e_s _t_h_e _i_m_p_l_e_m_e_n_t_a_t_i_o_n _o_n_l_y _s_u_p_p_o_r_t CCCCoooommmmmmmmoooonnnn
UUUUssssaaaaggggeeee CCCC _o_r _a_l_s_o _s_u_p_p_o_r_t AAAANNNNSSSSIIII CCCC SSSSttttaaaannnnddddaaaarrrrdddd _i_n_t_e_r_f_a_c_e
_d_e_f_i_n_i_t_i_o_n_s?
Options:
1. Only Common Usage C
2. Both Common Usage C and ANSI C
AAAAnnnnsssswwwweeeerrrr::::
Both Common Usage C and ANSI C are available. Tests
were run using ANSI C.
Rationale
The POSIX.1 standard allows for a conforming system to
support either Common Usage C or ANSI C Standard
interface definitions. The XPG is based on a Common
Usage C definition but does not prohibit an ANSI C
implementation. A Common Usage C definition must
provide function declarations for the C language
functions in the XPG as well as providing function
semantics that conform to the XPG. An ANSI C Standard
interface must provide function prototypes and ANSI C
semantics as well as providing XPG semantics. There
are no known areas of contradiction between the ANSI C
and XPG semantics.
Reference
XPG3 Volume 2 Page 12 - The Compilation Environment
9
Page 2.1.2
X/Open Conformance Statement XCS-QUE-3.2
Questionnaire
2.1.3 LLLLiiiimmmmiiiitttt VVVVaaaalllluuuueeeessss
QQQQuuuueeeessssttttiiiioooonnnn 3333:::: _W_h_a_t _a_r_e _t_h_e _v_a_l_u_e_s _a_s_s_o_c_i_a_t_e_d _w_i_t_h _t_h_e
_f_o_l_l_o_w_i_n_g _l_i_m_i_t_s _s_p_e_c_i_f_i_e_d _i_n _t_h_e <<<<lllliiiimmmmiiiittttssss....hhhh>>>> _h_e_a_d_e_r
_f_i_l_e?
AAAAnnnnsssswwwweeeerrrr::::
Macro Name Meaning Minimum Maximum
8 ______________________________________________________________________________
9 ARG_MAX
7 Max length of argument list and
environment data
77 20478
7 20478
9 CHILD_MAX Max number of processes per user ID 25 Indeterminate
9 LINK_MAX Max number of links to a single file
7 32768
7 32768
9 MAX_CANON 512 512
7 Max bytes in a terminal canonical
input line
9 MAX_INPUT Max bytes in a terminal input queue 512 512
9 NAME_MAX Max characters in a filename 14 255
9 OPEN_MAX Max number of files open in a process 60
7 1024 |-
9 PASS_MAX 8 8
7 Max significant characters in a
password
9 PATH_MAX Max characters in a pathname 1023 1023
9 PIPE_BUF Max bytes in an atomic write to a pipe 8192 8192
9 NGROUPS_MAX 20 20
7 Max number of supplementary group IDs
9 TMP_MAX 17576 17576
7 Max number of unique temporary file
names
|- 60 for 8.01 only.
Options:
Specify a minimum and maximum limit for each limit
value. The minimum limit should be the result of
evaluating the associated macro in <<<<lllliiiimmmmiiiittttssss....hhhh>>>>. The
maximum limit should be the largest value that is
returned from ssssyyyyssssccccoooonnnnffff(((()))) or ppppaaaatttthhhhccccoooonnnnffff(((()))). The maximum
values can be specified as
indeterminate.
Rationale
Each of these limits can vary within bounds set by the
X/Open Portability Guide. The minimum value that a
limit can take on any X/Open conforming system is
given in the corresponding ____PPPPOOOOSSSSIIIIXXXX____ value. A specific
9
Page 2.1.3
X/Open Conformance Statement XCS-QUE-3.2
Questionnaire
conforming implementation may provide a higher minimum
value than this and the maximum value that it provides
can differ from the minimum. Some conforming
implementations may provide a potentially infinite
value as the maximum, in which case the value is
considered to be indeterminate. The minimum value must
always be definitive since the ____PPPPOOOOSSSSIIIIXXXX____ value provides
a known lower bound for the range of possible values.
Reference
XPG3 Volume 2 Page 538 - <<<<lllliiiimmmmiiiittttssss....hhhh>>>>.
QQQQuuuueeeessssttttiiiioooonnnn 4444:::: _W_h_a_t _a_r_e _t_h_e _v_a_l_u_e_s _a_s_s_o_c_i_a_t_e_d _w_i_t_h _t_h_e
_f_o_l_l_o_w_i_n_g _c_o_n_s_t_a_n_t_s _s_p_e_c_i_f_i_e_d _i_n _t_h_e <<<<lllliiiimmmmiiiittttssss....hhhh>>>> _h_e_a_d_e_r
_f_i_l_e?
AAAAnnnnsssswwwweeeerrrr::::
Macro Name Meaning Value
8 ______________________________________________________________
9 CHAR_BIT Number of bits in a char 8
9 LONG_BIT Number of bits in a long 32
9 WORD_BIT Number of bits in a word 32
9 DBL_DIG Digits of precision of a double 15
9 DBL_MAX Maximum decimal value of a double 1.79... E+308
9 FLT_DIG Digits of precision of a float 6
9 FLT_MAX Maximum decimal value of a float 3.4... E+38
Rationale
This set of constants provides useful information
regarding the underlying architecture of the
implementation.
Reference
XPG3 Volume 2 Page 537 - <<<<lllliiiimmmmiiiittttssss....hhhh>>>>.
Page 2.1.4
X/Open Conformance Statement XCS-QUE-3.2
Questionnaire
2.1.4 EEEErrrrrrrroooorrrr CCCCoooonnnnddddiiiittttiiiioooonnnnssss
QQQQuuuueeeessssttttiiiioooonnnn 5555:::: _W_h_i_c_h _o_f _t_h_e _f_o_l_l_o_w_i_n_g _o_p_t_i_o_n_a_l _e_r_r_o_r_s _l_i_s_t_e_d _i_n
_t_h_e _X_P_G _a_r_e _d_e_t_e_c_t_e_d _i_n _t_h_e _c_i_r_c_u_m_s_t_a_n_c_e_s _s_p_e_c_i_f_i_e_d?
AAAAnnnnsssswwwweeeerrrr::::
Function Error Detected
8 ________________________________________
9 access() EINVAL|-
7 Yes
ETXTBSY Yes
9 atof() ERANGE Yes
9 atoi() ERANGE Yes
9 atol() ERANGE Yes
9 cfsetispeed() EINVAL Yes
9 cfsetospeed() EINVAL Yes
9 chmod() EINVAL
7 Yes
9 chown() EINVAL|-
7 Yes
9 closedir() EBADF|- Yes
9 exec ENOMEM|- Yes
ETXTBSY Yes
9 fcntl() EDEADLK|- Yes
9 fdopen() EBADF No
EINVAL Yes
9 feof() EBADF No
9 ferror() EBADF No
9 fileno() EBADF No
9 fopen() EINVAL Yes
ETXTBSY Yes
9 freopen() EINVAL Yes
ETXTBSY Yes
9 fork() ENOMEM Yes
9 fseek() EINVAL Yes
9 ftw() EINVAL Yes
9 getcwd() EACCES|- Yes
9 isatty() EBADF Yes
ENOTTY Yes
9 open() EINVAL Yes
Page 2.1.5
X/Open Conformance Statement XCS-QUE-3.2
Questionnaire
Function Error Detected
8 ________________________________________
9 ETXTBSY Yes
9 opendir() EMFILE|- Yes
ENFILE|- Yes
9 pathconf() EACCES|- Yes
EINVAL|- Yes
ENAMETOOLONG|- Yes
ENOENT|- Yes
ENOTDIR|- Yes
9 fpathconf() EBADF|- Yes
EINVAL|- Yes
9 printf() EINVAL No
9 readdir() EBADF|- Yes
9 rename() ETXTBSY Yes
9 scanf() EINVAL No
9 setvbuf() EBADF No
9 sigaddset() EINVAL|- Yes
9 sigdelset() EINVAL|- Yes
9 sigismember() EINVAL|- Yes
9 strcoll() EINVAL No
9 strerror() EINVAL No
9 strtol() EINVAL Yes
ERANGE Yes
9 strxfrm() EINVAL No
9 unlink() ETXTBSY Yes
Rationale
Each of the above error conditions is marked as
optional in the XPG and an implementation may return
this error in the circumstances specified or may not
provide the error indication. Those items marked with
a ||||---- are also considered to be optional error
conditions in POSIX.1. The EINVAL error condition for
the three functions ssssiiiiggggaaaaddddddddsssseeeetttt(((()))), ssssiiiiggggddddeeeellllsssseeeetttt(((()))) and
ssssiiiiggggiiiissssmmmmeeeemmmmbbbbeeeerrrr(((()))) are mandated in the XPG but are
considered optional in POSIX.1. An X/Open conforming
implementation will always produce these errors, but a
POSIX.1 conforming implementation may not.
Reference
XPG3 Volume 2 Page 32 - Error Numbers.
Page 2.1.6
X/Open Conformance Statement XCS-QUE-3.2
Questionnaire
2.1.5 MMMMaaaatttthhhheeeemmmmaaaattttiiiiccccaaaallll IIIInnnntttteeeerrrrffffaaaacccceeeessss
QQQQuuuueeeessssttttiiiioooonnnn 6666:::: _W_h_a_t _f_o_r_m_a_t _o_f _f_l_o_a_t_i_n_g _p_o_i_n_t _n_u_m_b_e_r_s _a_r_e
_s_u_p_p_o_r_t_e_d _b_y _t_h_i_s _i_m_p_l_e_m_e_n_t_a_t_i_o_n?
AAAAnnnnsssswwwweeeerrrr::::
IEEE floating point format.
Options:
1. IEEE floating point format.
2. Description of floating point format supported.
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.
QQQQuuuueeeessssttttiiiioooonnnn 7777:::: _I_s lllloooonnnngggg ddddoooouuuubbbblllleeee _f_o_r_m _s_u_p_p_o_r_t_e_d _a_n_d _w_h_a_t _p_r_e_c_i_s_i_o_n
_i_s _a_s_s_o_c_i_a_t_e_d _w_i_t_h _t_h_i_s _f_o_r_m?
AAAAnnnnsssswwwweeeerrrr::::
Yes. Long double is supported as a distinct type for
ANSI C. 128 bits. 15 bit exponent, 112 bit mantissa.
See Precision Architecture and Instruction Set, HP
Part 09740-90014, Page 6-5 for more information; both
the 600/700/800 and the 300/400 share this format.
Options:
1. Not supported. Long double equates to double.
2. Description of exponent and mantissa precision
and number of bits associated with the long
double format.
Rationale
The long double format can both vary in length and
precision. If it is supported, other than as a synonym
for double, the format needs to be described.
Reference
XPG3 Volume 2 Page 328 - printf()
Page 2.1.7
X/Open Conformance Statement XCS-QUE-3.2
Questionnaire
XPG3 Volume 2 Page 362 - scanf()
9
2.1.6 DDDDaaaattttaaaa EEEEnnnnccccrrrryyyyppppttttiiiioooonnnn
QQQQuuuueeeessssttttiiiioooonnnn 8888:::: _A_r_e _t_h_e _o_p_t_i_o_n_a_l _d_a_t_a _e_n_c_r_y_p_t_i_o_n _i_n_t_e_r_f_a_c_e_s
_p_r_o_v_i_d_e_d?
AAAAnnnnsssswwwweeeerrrr::::
crypt() Yes
encrypt() No
setkey() No
U.S. Domestic customers may obtain fully capable
copies of encrypt() and setkey() through their
customer support contact.
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.
Reference
XPG3 Volume 2 Page 3 - Status of Interfaces
9
Page 2.1.8
X/Open Conformance Statement XCS-QUE-3.2
Questionnaire
SSSSeeeeccccttttiiiioooonnnn 2222....2222:::: PPPPrrrroooocccceeeessssssss HHHHaaaannnnddddlllliiiinnnngggg
9
2.2.1 PPPPrrrroooocccceeeessssssss GGGGeeeennnneeeerrrraaaattttiiiioooonnnn
QQQQuuuueeeessssttttiiiioooonnnn 9999:::: _W_h_i_c_h _f_i_l_e _t_y_p_e_s (_r_e_g_u_l_a_r, _d_i_r_e_c_t_o_r_y, _F_I_F_O
_s_p_e_c_i_a_l _e_t_c.) _a_r_e _c_o_n_s_i_d_e_r_e_d _t_o _b_e _e_x_e_c_u_t_a_b_l_e?
AAAAnnnnsssswwwweeeerrrr::::
Regular
Options:
A list of the types of file that are considered to be
executable.
Rationale
The EACCES error associated with eeeexxxxeeeecccc 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.
Example
Only regular file types may be executed.
Reference
XPG3 Volume 2 Page 129 - exec
9
2.2.2 PPPPrrrroooocccceeeessssssss TTTTeeeerrrrmmmmiiiinnnnaaaattttiiiioooonnnn
QQQQuuuueeeessssttttiiiioooonnnn 11110000:::: _I_s _t_h_e _S_I_G_C_H_L_D _s_i_g_n_a_l _s_e_n_t _t_o _t_h_e _p_a_r_e_n_t
_p_r_o_c_e_s_s _w_h_e_n _a _c_h_i_l_d _e_x_i_t_s?
AAAAnnnnsssswwwweeeerrrr::::
Yes
Rationale
Some systems support the sending of SIGCHLD in these
circumstances. This is mandatory if job control is
supported.
Reference
XPG3 Volume 2 Page 132 - exit()
Page 2.2.1
X/Open Conformance Statement XCS-QUE-3.2
Questionnaire
2.2.3 PPPPrrrroooocccceeeessssssss EEEEnnnnvvvviiiirrrroooonnnnmmmmeeeennnntttt
QQQQuuuueeeessssttttiiiioooonnnn 11111111:::: _I_s _t_h_e sssseeeettttppppggggiiiidddd(((()))) _i_n_t_e_r_f_a_c_e _p_r_o_v_i_d_e_d?
AAAAnnnnsssswwwweeeerrrr::::
Yes
Rationale
This interface is mandatory on systems which support
job control and may be provided on other systems.
Reference
XPG3 Volume 2 Page 3 - Status of Interfaces
Page 2.2.2
X/Open Conformance Statement XCS-QUE-3.2
Questionnaire
SSSSeeeeccccttttiiiioooonnnn 2222....3333:::: FFFFiiiilllleeee HHHHaaaannnnddddlllliiiinnnngggg
9
2.3.1 AAAAcccccccceeeessssssss CCCCoooonnnnttttrrrroooollll
QQQQuuuueeeessssttttiiiioooonnnn 11112222:::: _W_h_a_t _f_i_l_e _a_c_c_e_s_s _c_o_n_t_r_o_l _m_e_c_h_a_n_i_s_m_s _d_o_e_s _t_h_e
_i_m_p_l_e_m_e_n_t_a_t_i_o_n _p_r_o_v_i_d_e?
AAAAnnnnsssswwwweeeerrrr::::
The operating system supports extended Discretionary
Access Control ("need to know" access restrictions and
permissions) on files, as an optional superset of
user, group, and other mode bits. For general
information, see the new manual entry
Options:
1. Standard access control is provided.
2. Refer to: POSIX.1 Conformance Document Section
2.4.
3. Provide a definition of the additional or
alternate access mechanisms.
Rationale
The XPG (and POSIX) allow an implementation to provide
either additional or alternate file access control
mechanisms other than the standard access control
mechanism. The document should either describe or
provide a reference to the details of alternate or
additional access mechanisms. In particular, the
method by which an application can execute using
standard file access control should be explained and
details of the changes required to utilised the
alternate or additional access mechanisms should be
given.
Reference
XPG3 Volume 2 page 16 - File Access Permissions.
9
Page 2.3.1
X/Open Conformance Statement XCS-QUE-3.2
Questionnaire
2.3.2 FFFFiiiilllleeeessss aaaannnndddd DDDDiiiirrrreeeeccccttttoooorrrriiiieeeessss
QQQQuuuueeeessssttttiiiioooonnnn 11113333:::: _A_r_e _a_n_y _e_x_t_e_n_d_e_d _s_e_c_u_r_i_t_y _c_o_n_t_r_o_l_s _i_m_p_l_e_m_e_n_t_e_d
_t_h_a_t _c_o_u_l_d _c_a_u_s_e ffffssssttttaaaatttt(((()))) _o_r ssssttttaaaatttt(((()))) _t_o _f_a_i_l?
AAAAnnnnsssswwwweeeerrrr::::
No
Rationale
The XPG notes that there could be an interaction
between extended security controls and the success of
ffffssssttttaaaatttt(((()))) and ssssttttaaaatttt(((()))). 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
XPG3 Volume 2 Page 478 - tempnam()
9
2.3.3 FFFFoooorrrrmmmmaaaattttttttiiiinnnngggg IIIInnnntttteeeerrrrffffaaaacccceeeessss
QQQQuuuueeeessssttttiiiioooonnnn 11114444:::: _I_s _t_h_e _L _m_o_d_i_f_i_e_r _t_o pppprrrriiiinnnnttttffff(((()))) _a_n_d ssssccccaaaannnnffff(((())))
_s_u_p_p_o_r_t_e_d _o_n _t_h_i_s _i_m_p_l_e_m_e_n_t_a_t_i_o_n?
AAAAnnnnsssswwwweeeerrrr::::
Yes
Rationale
The XPG notes that the L modifier which is exactly
equivalent to the l modifier when the implementation
does not differentiate between double and long double,
is not supported on all systems and is only included
for compatibility with ANSI C.
Reference
XPG3 Volume 2 Page 328 - printf()
XPG3 Volume 2 Page 362 - scanf()
QQQQuuuueeeessssttttiiiioooonnnn 11115555:::: _D_o_e_s _t_h_e pppprrrriiiinnnnttttffff(((()))) _f_u_n_c_t_i_o_n _p_r_o_d_u_c_e _c_h_a_r_a_c_t_e_r
_s_t_r_i_n_g _r_e_p_r_e_s_e_n_t_a_t_i_o_n_s _f_o_r _I_n_f_i_n_i_t_y _a_n_d _N_a_N _t_o
_r_e_p_r_e_s_e_n_t _t_h_e _r_e_s_p_e_c_t_i_v_e _s_p_e_c_i_a_l _d_o_u_b_l_e
precision values?"
9
Page 2.3.2
X/Open Conformance Statement XCS-QUE-3.2
Questionnaire
AAAAnnnnsssswwwweeeerrrr::::
Yes. It generates "?.000000" for all HP-UX systems.
Rationale
This behaviour is often provided on systems with
mathematical functions that produce these results.
Reference
XPG3 Volume 2 Page 331 - printf()
Page 2.3.3
X/Open Conformance Statement XCS-QUE-3.2
Questionnaire
SSSSeeeeccccttttiiiioooonnnn 2222....4444:::: GGGGeeeennnneeeerrrraaaallll TTTTeeeerrrrmmmmiiiinnnnaaaallll IIIInnnntttteeeerrrrffffaaaacccceeee
9
2.4.1 IIIInnnntttteeeerrrrffffaaaacccceeeessss SSSSuuuuppppppppoooorrrrtttteeeedddd
QQQQuuuueeeessssttttiiiioooonnnn 11116666:::: _A_r_e _t_h_e _f_o_l_l_o_w_i_n_g _t_e_r_m_i_n_a_l _c_o_n_t_r_o_l _i_n_t_e_r_f_a_c_e_s
_p_r_o_v_i_d_e_d?
tcgetpgrp() tcsetpgrp()
AAAAnnnnsssswwwweeeerrrr::::
Yes
Rationale
These interfaces are mandatory for implementations
that support jjjjoooobbbb ccccoooonnnnttttrrrroooollll. Implementations that do not
support jjjjoooobbbb ccccoooonnnnttttrrrroooollll, may either always return the
error indication [ENOSYS] or may provide the interface
with the behaviour specified for an implementation
that supports jjjjoooobbbb ccccoooonnnnttttrrrroooollll. This later case is useful
for implementations which support only part of the jjjjoooobbbb
ccccoooonnnnttttrrrroooollll specifications.
Reference
XPG3 Volume 2 Page 471 - tcgetpgrp
XPG3 Volume 2 Page 475 - tcsetpgrp
9
Page 2.4.1
X/Open Conformance Statement XCS-QUE-3.2
Questionnaire
SSSSeeeeccccttttiiiioooonnnn 2222....5555:::: IIIInnnntttteeeerrrrnnnnaaaattttiiiioooonnnnaaaalllliiiisssseeeedddd SSSSyyyysssstttteeeemmmm IIIInnnntttteeeerrrrffffaaaacccceeeessss
9
2.5.1 CCCCooooddddeeeesssseeeettttssss
QQQQuuuueeeessssttttiiiioooonnnn 11117777:::: _D_o_e_s _t_h_e _i_m_p_l_e_m_e_n_t_a_t_i_o_n _s_u_p_p_o_r_t _t_h_e IIIISSSSOOOO 8888888855559999----
1111::::1111999988887777 _c_o_d_e_s_e_t _f_o_r _d_a_t_a _t_r_a_n_s_m_i_s_s_i_o_n?
AAAAnnnnsssswwwweeeerrrr::::
Yes
Rationale
The XPG defines the ISO 8859-1:1987 as the major
Western European transmission codeset and also
recommends its use as the corresponding internal
codeset.
Reference
XPG3 Volume 3 Page 19 - Character Codesets and Text
Transfer
QQQQuuuueeeessssttttiiiioooonnnn 11118888:::: _D_o_e_s _t_h_e _i_m_p_l_e_m_e_n_t_a_t_i_o_n _u_s_e _t_h_e IIIISSSSOOOO 8888888855559999----1111::::1111999988887777
_a_s _i_t_s _i_n_t_e_r_n_a_l _c_o_d_e_s_e_t?
AAAAnnnnsssswwwweeeerrrr::::
Per user-customer selectable option. Each user may
configure his/her login session to use a selected
codeset. IIIISSSSOOOO 8888888855559999----1111::::1111999988887777 is one such codeset.
Rationale
The XPG defines the ISO 8859-1:1987 as the major
Western European transmission codeset and also
recommends its use as the corresponding internal
codeset.
Reference
XPG3 Volume 3 Page 19 - Character Codesets and Text
Transfer
9
Page 2.5.1
X/Open Conformance Statement XCS-QUE-3.2
Questionnaire
2.5.2 RRRReeeegggguuuullllaaaarrrr EEEExxxxpppprrrreeeessssssssiiiioooonnnn IIIInnnntttteeeerrrrffffaaaacccceeeessss
QQQQuuuueeeessssttttiiiioooonnnn 11119999:::: _W_h_a_t _f_o_r_m _o_f _r_e_g_u_l_a_r _e_x_p_r_e_s_s_i_o_n _s_y_n_t_a_x _i_s
_s_u_p_p_o_r_t_e_d _b_y _t_h_e rrrreeeeggggeeeexxxxpppp(((()))) _i_n_t_e_r_f_a_c_e?
AAAAnnnnsssswwwweeeerrrr::::
Simple Internationalised
Rationale
The rrrreeeeggggeeeexxxxpppp(((()))) interface may support either the simple
regular expression or the simple internationalised
regular expression syntax as defined in the XPG3
Volume 3 - Supplementary Definitions.
Reference
XPG3 Volume 3 Pages 49-51 - Regular Expressions
Page 2.5.2
X/Open Conformance Statement XCS-QUE-3.2
Questionnaire
CCCChhhhaaaapppptttteeeerrrr 3333:::: CCCCoooommmmmmmmaaaannnnddddssss aaaannnndddd UUUUttttiiiilllliiiittttiiiieeeessss
PPPPrrrroooodddduuuucccctttt IIIIddddeeeennnnttttiiiiffffiiiiccccaaaattttiiiioooonnnn
Product Identification HP-UX
9 Version/Release No. 8.0x for Series 600/700/800
If you do not supply this component yourself, please
identify below the supplier you reference.
Supplied by HP.
CCCCoooonnnnffffoooorrrrmmmmaaaannnncccceeee RRRReeeeffffeeeerrrreeeennnncccceeee
Indicator of Compliance
None
EEEEnnnnvvvviiiirrrroooonnnnmmmmeeeennnntttt SSSSppppeeeecccciiiiffffiiiiccccaaaattttiiiioooonnnn
Enter below details of the hardware and software
environment in which conformance is claimed, including
compilation routines and installation procedures (if
any). Sufficient detail must be supplied to enable
conformant behaviour to be reproduced.
Identical to that for Chapter 2 (System Calls and
Libraries).
CCCCoooonnnnffffoooorrrrmmmmaaaannnncccceeee EEEExxxxppppeeeeccccttttaaaattttiiiioooonnnnssss
Volume 1 of XPG3 recognises that convergence of
implementations towards a common specification for
commands and utilities is not yet complete and therefore
does not require a vendor to supply all of the commands
and utilities (and individual options) specified in
XPG3.
This chapter explicitly identifies those commands and
utilities not supplied by the vendor and any supplied
which do not conform to the published specification.
(Reference : XPG3 Volume 1 Page 1).
9
Page 3.1
X/Open Conformance Statement XCS-QUE-3.2
Questionnaire
SSSSeeeeccccttttiiiioooonnnn 3333....1111:::: BBBBaaaassssiiiicccc UUUUttttiiiilllliiiittttiiiieeeessss
9
3.1.1 SSSSuuuuppppppppoooorrrrtttteeeedddd CCCCoooommmmmmmmaaaannnnddddssss
QQQQuuuueeeessssttttiiiioooonnnn 1111:::: _W_h_i_c_h _o_f _t_h_e _b_a_s_i_c _u_t_i_l_i_t_i_e_s (_n_o_n-_d_e_v_e_l_o_p_m_e_n_t
_u_t_i_l_i_t_i_e_s) _d_e_f_i_n_e_d _i_n _t_h_e _X_P_G _a_r_e _n_o_t _p_r_o_v_i_d_e_d _w_i_t_h
_t_h_e _i_m_p_l_e_m_e_n_t_a_t_i_o_n?
AAAAnnnnsssswwwweeeerrrr::::
All are provided.
Options:
A list of utilities that are not provided.
Rationale
The XPG Volume 1 states that “this volume in its
current form is useful only as a guide to portability,
but it is not possible to precisely define or test
conformance to it”. This question determines whether
or not the implementation provides a command of the
name specified in the XPG, it does not attempt to
determine whether it supports the semantics of that
command. The (optional) development utilities are
excluded from this question and are dealt with in the
next section of the questionnaire.
Example
The mmmmaaaaiiiillllxxxx and nnnneeeewwwwggggrrrrpppp commands are not provided.
Reference
XPG3 Volume 1 Page 1 - Introduction
9
3.1.2 CCCCoooommmmmmmmaaaannnndddd BBBBeeeehhhhaaaavvvviiiioooouuuurrrr
QQQQuuuueeeessssttttiiiioooonnnn 2222:::: _I_n _w_h_a_t _w_a_y_s _d_o _t_h_e _c_o_m_m_a_n_d_s _p_r_o_v_i_d_e_d _b_y _t_h_e
_i_m_p_l_e_m_e_n_t_a_t_i_o_n _b_e_h_a_v_e _d_i_f_f_e_r_e_n_t_l_y _f_r_o_m _t_h_e
_s_p_e_c_i_f_i_c_a_t_i_o_n_s _c_o_n_t_a_i_n_e_d _i_n _t_h_e _X_P_G?
AAAAnnnnsssswwwweeeerrrr::::
ps: The -n option is not supported.
Page 3.1.1
X/Open Conformance Statement XCS-QUE-3.2
Questionnaire
Options:
1. The commands behave in the manner specified for
each of the command options detailed in the XPG.
2. A list of deviances for each of the commands is
provided. This list should be in a tabular form
giving the name of the command, the command
option and a description of the deviant
behaviour.
Rationale
This question provides a greater degree of granularity
than the previous question, requiring the semantic
differences associated with the commands to be
specified. Again, the question relates to the basic
utilities rather than the development utilities. The
question only relates to the semantics of the options
specified within the XPG, implementation specific
extensions should not be documented.
Page 3.1.2
X/Open Conformance Statement XCS-QUE-3.2
Questionnaire
SSSSeeeeccccttttiiiioooonnnn 3333....2222:::: DDDDeeeevvvveeeellllooooppppmmmmeeeennnntttt UUUUttttiiiilllliiiittttiiiieeeessss
9
3.2.1 SSSSuuuuppppppppoooorrrrtttteeeedddd CCCCoooommmmmmmmaaaannnnddddssss
QQQQuuuueeeessssttttiiiioooonnnn 3333:::: _W_h_i_c_h _o_f _t_h_e _d_e_v_e_l_o_p_m_e_n_t _u_t_i_l_i_t_i_e_s _d_e_f_i_n_e_d _i_n
_t_h_e _X_P_G _a_r_e _n_o_t _p_r_o_v_i_d_e_d _w_i_t_h _t_h_e _i_m_p_l_e_m_e_n_t_a_t_i_o_n?
AAAAnnnnsssswwwweeeerrrr::::
sdb, dis are not provided. The xdb command provides
the functionality of sdb.
Options:
1. All are provided
2. None are provided
3. A list of utilities that are not provided.
Rationale
The XPG Volume 1 states that “The development
utilities might not be present in all X/Open compliant
systems; in designated (DDDDEEEEVVVVEEEELLLLOOOOPPPPMMMMEEEENNNNTTTT) systems all of
the development utilities must be present and must
conform to the published definition”.
Reference
XPG3 Volume 1 Page 2 - Status of Interfaces
9
3.2.2 CCCCoooommmmmmmmaaaannnndddd BBBBeeeehhhhaaaavvvviiiioooouuuurrrr
QQQQuuuueeeessssttttiiiioooonnnn 4444:::: _I_n _w_h_a_t _w_a_y_s _d_o _t_h_e _d_e_v_e_l_o_p_m_e_n_t _u_t_i_l_i_t_i_e_s
_p_r_o_v_i_d_e_d _b_y _t_h_e _i_m_p_l_e_m_e_n_t_a_t_i_o_n _b_e_h_a_v_e _d_i_f_f_e_r_e_n_t_l_y _f_r_o_m
_t_h_e _s_p_e_c_i_f_i_c_a_t_i_o_n_s _c_o_n_t_a_i_n_e_d _i_n _t_h_e _X_P_G?
AAAAnnnnsssswwwweeeerrrr::::
cc: the -q option is different than as specified.
the -f option is not supported.
Page 3.2.1
X/Open Conformance Statement XCS-QUE-3.2
Questionnaire
Options:
1. The development utilities behave in the manner
specified for each of the options detailed in
the XPG.
2. A list of deviances for each of the utilities is
provided. This list should be in a tabular form
giving the name of the utilities, the option and
a description of the deviant behaviour.
Rationale
This question provides a greater degree of granularity
than the previous question, requiring the semantic
differences associated with the development utilities
to be specified.
Page 3.2.2
X/Open Conformance Statement XCS-QUE-3.2
Questionnaire
SSSSeeeeccccttttiiiioooonnnn 3333....3333:::: IIIInnnntttteeeerrrrnnnnaaaattttiiiioooonnnnaaaalllliiiissssaaaattttiiiioooonnnn OOOOppppttttiiiioooonnnn
3.3.1 CCCCoooommmmmmmmaaaannnnddddssss aaaannnndddd UUUUttttiiiilllliiiittttiiiieeeessss
QQQQuuuueeeessssttttiiiioooonnnn 5555:::: _I_s _a_n _i_n_t_e_r_n_a_t_i_o_n_a_l_i_s_e_d _e_n_v_i_r_o_n_m_e_n_t, _r_e_f_l_e_c_t_i_n_g
_c_h_a_n_g_e_s _i_n _t_h_e _l_o_c_a_l_e _s_e_t_t_i_n_g _a_s _d_e_s_c_r_i_b_e_d _i_n XXXXPPPPGGGG
VVVVoooolllluuuummmmeeee 1111 ---- XXXXSSSSIIII CCCCoooommmmmmmmaaaannnnddddssss aaaannnndddd UUUUttttiiiilllliiiittttiiiieeeessss,
supported?"
AAAAnnnnsssswwwweeeerrrr::::
Options:
1. The commands listed below support
Internationalisation in the manner specified in
XPG3.
2. A list of deviations in the Internationalised
behaviour of the following commands, compared to
that specified in XPG3, is provided.
Command Behaviour Specified in XPG3 Supported
8 ______________________________________________________________________________________
9 ar LC_TIME affects date format Yes
9 awk LC_COLLATE, LC_CTYPE affect regular expression matching Yes
LC_COLLATE affects the behaviour of string comparisons Yes
LC_NUMERIC affects the behaviour of the radix character Yes
9 comm LC_COLLATE affects sorting sequence Yes
9 cp,ln,mv LANG affects yes string Yes
9 cpio LC_COLLATE, LC_CTYPE affect filename pattern matching Yes
LC_TIME affects date format Yes
9 date LC_TIME affects date formatting options Yes
9 ed,red LC_COLLATE, LC_CTYPE affect regular expression matching Yes
LC_CTYPE is used to determine whether characters are printable Yes
9 egrep LC_COLLATE, LC_CTYPE affect regular expression matching Yes
LC_CTYPE is used to determine character classification Yes
(alphabetic, upper-case, lower case)
9 expr LC_COLLATE, LC_CTYPE affect regular expression matching Yes
LC_COLLATE affects the behaviour of relational operators Yes
9 fgrep LC_CTYPE is used to determine character classification Yes
(alphabetic, upper-case, lower case)
9
Page 3.3.1
X/Open Conformance Statement XCS-QUE-3.2
Questionnaire
Command Behaviour Specified in XPG3 Supported
8 ______________________________________________________________________________________
9 find LANG affects yes string
7 Yes
LC_COLLATE, LC_CTYPE affect filename pattern matching Yes
9 grep LC_COLLATE, LC_CTYPE affect regular expression matching Yes
LC_CTYPE is used to determine character classification Yes
(alphabetic, upper-case, lower case)
9 join LC_COLLATE affects sorting sequence Yes
9 lpstat LC_TIME affects date format Yes
9 ls LC_COLLATE affects sorting sequence Yes
LC_CTYPE is used to determine whether a character is printable Yes
LC_TIME affects date format Yes
9 mail LC_TIME affects date format Yes
9 mailx LC_COLLATE, LC_CTYPE affect filename pattern matching Yes
LC_TIME affects date format Yes
9 pg LC_COLLATE, LC_CTYPE affect filename pattern matching Yes
9 pr LC_TIME affects date format Yes
LC_CTYPE is used to determine whether a character is printable Yes
9 ps LC_TIME affects date format Yes
9 rm,rmdir LANG affects yes string Yes
9 sed LC_COLLATE, LC_CTYPE affect regular expression matching Yes
LC_CTYPE is used to determine whether a character is printable Yes
9 sh LC_COLLATE, LC_CTYPE affect filename pattern matching Yes
LC_CTYPE is used to determine whether a character is alphabetic Yes
9 sort LC_COLLATE affects sorting sequence Yes
LC_CTYPE affects character classification (alphabetic, upper Yes
case, printing)
LC_NUMERIC affects the determination of the radix character Yes
9 tar LC_TIME affects date format Yes
LANG affects yes string Yes
9 tr LC_COLLATE, LC_CTYPE affect bracketed expressions Yes
LC_CTYPE affects the definition of the character universe Yes
9 uniq LC_COLLATE affects sorting sequence Yes
9 uucp LC_TIME affects date format Yes
9 uustat LC_TIME affects date format Yes
9 wc LC_CTYPE is used to determine white-space characters Yes
9 who LC_TIME affects date format Yes
9 yacc LC_CTYPE is used to determine character classification Yes
9
Page 3.3.2
X/Open Conformance Statement XCS-QUE-3.2
Questionnaire
Rationale
This behaviour is collectively optional, that is, it
should be provided for all commands listed (subject to
sections 3.1 and 3.2 which identify those commands not
supplied by the vendor and those which do not fully
support the X/Open specification).
Reference
XPG3 Volume 1 Pages 4-5 - Status of Interfaces.
9
3.3.2 RRRReeeegggguuuullllaaaarrrr EEEExxxxpppprrrreeeessssssssiiiioooonnnnssss iiiinnnn CCCCoooommmmmmmmaaaannnnddddssss
QQQQuuuueeeessssttttiiiioooonnnn 6666:::: _W_h_i_c_h _f_o_r_m _o_f _r_e_g_u_l_a_r _e_x_p_r_e_s_s_i_o_n _s_y_n_t_a_x _i_s
_s_u_p_p_o_r_t_e_d _b_y _t_h_o_s_e _c_o_m_m_a_n_d_s _w_h_i_c_h _u_s_e _r_e_g_u_l_a_r
_e_x_p_r_e_s_s_i_o_n_s?
AAAAnnnnsssswwwweeeerrrr::::
Command Regular Expression Syntax Supported
8 _____________________________________________
9 awk EEEExxxxtttteeeennnnddddeeeedddd IIIInnnntttteeeerrrrnnnnaaaattttiiiioooonnnnaaaalllliiiisssseeeedddd
9 csplit Simple Internationalised
9 ed SSSSiiiimmmmpppplllleeee IIIInnnntttteeeerrrrnnnnaaaattttiiiioooonnnnaaaalllliiiisssseeeedddd
9 egrep EEEExxxxtttteeeennnnddddeeeedddd IIIInnnntttteeeerrrrnnnnaaaattttiiiioooonnnnaaaalllliiiisssseeeedddd
9 ex Simple Internationalised
9 expr SSSSiiiimmmmpppplllleeee IIIInnnntttteeeerrrrnnnnaaaattttiiiioooonnnnaaaalllliiiisssseeeedddd
9 grep SSSSiiiimmmmpppplllleeee IIIInnnntttteeeerrrrnnnnaaaattttiiiioooonnnnaaaalllliiiisssseeeedddd
9 lex Extended
9 pg SSSSiiiimmmmpppplllleeee IIIInnnntttteeeerrrrnnnnaaaattttiiiioooonnnnaaaalllliiiisssseeeedddd
9 sdb Not provided.
9 sed SSSSiiiimmmmpppplllleeee IIIInnnntttteeeerrrrnnnnaaaattttiiiioooonnnnaaaalllliiiisssseeeedddd
9 vi Simple Internationalised
Note: An XPG3 conforming system which claims support
for internationalised commands should provide the
regular expression syntax marked in bbbboooolllldddd in the above
table. Where neither options are marked in bbbboooolllldddd either
may be provided.
Page 3.3.3
X/Open Conformance Statement XCS-QUE-3.2
Questionnaire
Rationale
The XPG Volume 3 - XSI Supplementary Definitions
requires that an internationalised set of commands
will provide regular expression syntax for the above
commands in one of the forms specified for that
command. The XPG encourages the implementation of
internationalised regular expressions for all of the
above utilities. It should be noted that the ssssddddbbbb
command is an optional development utility and may not
be available on all XPG conforming systems.
Reference
XPG3 Volume 3 Pages 49-51 - Regular Expressions
Page 3.3.4
X/Open Conformance Statement XCS-QUE-3.2
Questionnaire
CCCChhhhaaaapppptttteeeerrrr 4444:::: CCCC LLLLaaaannnngggguuuuaaaaggggeeee
PPPPrrrroooodddduuuucccctttt IIIIddddeeeennnnttttiiiiffffiiiiccccaaaattttiiiioooonnnn
Product Identification B2412A (600/700/800) or B2413A (700 Only)
9 Version/Release No. for 8.0x
If you do not supply this component yourself, please
identify below the supplier you reference.
Supplied by HP.
CCCCoooonnnnffffoooorrrrmmmmaaaannnncccceeee RRRReeeeffffeeeerrrreeeennnncccceeee
Indicator of Compliance
VSX Test Suite Release 3.204
9 Testing Agency Name Hewlett-Packard Company
9 Address 3404 East Harmony Rd.
9 Fort Collins, Co 80525-9599
9 USA
9
EEEEnnnnvvvviiiirrrroooonnnnmmmmeeeennnntttt SSSSppppeeeecccciiiiffffiiiiccccaaaattttiiiioooonnnn
Enter below details of the hardware and software
environment in which testing took place, including
compilation routines and installation procedures (if
any). Sufficient detail must be supplied to enable
conformant behaviour and any test results to be
reproduced.
Identical to that for Chapter 2 (System Calls and
Libraries).
TTTTeeeemmmmppppoooorrrraaaarrrryyyy WWWWaaaaiiiivvvveeeerrrrssss
List below references to any temporary waivers granted
by X/Open in respect of minor errors in the product
referenced above. This should include the X/Open
reference and the waiver expiry date. The waivers as
Page 4.1
X/Open Conformance Statement XCS-QUE-3.2
Questionnaire
granted shall be made available with this document on
request.
None.
Page 4.2
X/Open Conformance Statement XCS-QUE-3.2
Questionnaire
SSSSeeeeccccttttiiiioooonnnn 4444....1111:::: IIIImmmmpppplllleeeemmmmeeeennnnttttaaaattttiiiioooonnnn LLLLiiiimmmmiiiittttssss
QQQQuuuueeeessssttttiiiioooonnnn 1111:::: _W_h_a_t _l_i_m_i_t_s _d_o_e_s _t_h_e _i_m_p_l_e_m_e_n_t_a_t_i_o_n _i_m_p_o_s_e
_o_n _t_h_e _s_i_g_n_i_f_i_c_a_n_t _p_a_r_t _o_f _a _i_d_e_n_t_i_f_i_e_r?
AAAAnnnnsssswwwweeeerrrr::::
External identifiers 255 characters
9 Non-External identifiers 255 characters
Rationale
The XPG states that, while there is no limit to
the length of an identifier, only a certain number
of characters are significant. The XPG points out
that there must be at least eight characters for a
non-external name, but may be less for external
names.
Reference
XPG 3 Volume 4 Page 3 - Lexical Conventions
9
Page 4.1.1
X/Open Conformance Statement XCS-QUE-3.2
Questionnaire
SSSSeeeeccccttttiiiioooonnnn 4444....2222:::: GGGGeeeennnneeeerrrraaaallll
QQQQuuuueeeessssttttiiiioooonnnn 2222:::: _W_h_a_t _t_r_u_n_c_a_t_i_o_n _r_u_l_e_s _a_r_e _a_p_p_l_i_e_d _w_h_e_n _a
_f_l_o_a_t_i_n_g _v_a_l_u_e _i_s _c_o_n_v_e_r_t_e_d _t_o _a_n _i_n_t_e_g_r_a_l _v_a_l_u_e?
AAAAnnnnsssswwwweeeerrrr::::
Truncation toward zero.
Options:
A description of the manner in which floating
values are converted. The description should
address the rules for truncation of both positive
and negative values.
Rationale
The XPG states that such conversions are machine
dependent. In particular, the XPG points out the
differences related to the truncation of negative
numbers.
Reference
XPG Volume 4 Page 10 - Conversions
QQQQuuuueeeessssttttiiiioooonnnn 3333:::: _W_h_a_t _t_r_u_n_c_a_t_i_o_n _r_u_l_e_s _a_r_e _a_p_p_l_i_e_d _w_h_e_n _u_s_i_n_g
_t_h_e _d_i_v_i_s_i_o_n _o_p_e_r_a_t_o_r _a_n_d _e_i_t_h_e_r _o_f _t_h_e _o_p_e_r_a_n_d_s
_i_s _n_e_g_a_t_i_v_e?
Options:
Truncation towards zero / Truncation away from
zero
AAAAnnnnsssswwwweeeerrrr::::
Round towards zero (IEEE 754)
Rationale
The XPG states that such truncations are machine
dependent.
Reference
XPG Volume 4 Page 16 - Expressions
Page 4.2.1
—