XXXX////OOOOppppeeeennnn CCCCoooonnnnffffoooorrrrmmmmaaaannnncccceeee SSSSttttaaaatttteeeemmmmeeeennnntttt QQQQuuuueeeessssttttiiiioooonnnnnnnnaaaaiiiirrrreeee
TTTTyyyyppppeeee:::: XXXXPPPPGGGG4444 CCCCoooommmmppppoooonnnneeeennnntttt
CCCCoooommmmppppoooonnnneeeennnntttt NNNNaaaammmmeeee:::: XXXXPPPPGGGG4444 CCCCoooommmmmmmmaaaannnnddddssss aaaannnndddd UUUUttttiiiilllliiiittttiiiieeeessss
Completed by: Tom Shem, Hewlett-Packard Company
_________________________________________
(name and organisation)
on: Oct 13, 1994
_________________________________________
(date)
_X_P_G_4 _C_o_m_m_a_n_d_s _a_n_d _U_t_i_l_i_t_i_e_s
1. CCCCoooommmmmmmmaaaannnnddddssss aaaannnndddd UUUUttttiiiilllliiiittttiiiieeeessss
PPPPrrrroooodddduuuucccctttt IIIIddddeeeennnnttttiiiiffffiiiiccccaaaattttiiiioooonnnn
Product Identification HP-UX 9000 Operating System
_________________________________________
Version/Release No. HP-UX 10.X for the Series 800
_________________________________________
If you do not supply this component yourself, please
identify below the supplier you reference:
IIIInnnnddddiiiiccccaaaattttoooorrrr ooooffff CCCCoooommmmpppplllliiiiaaaannnncccceeee
None defined for this component.
EEEEnnnnvvvviiiirrrroooonnnnmmmmeeeennnntttt SSSSppppeeeecccciiiiffffiiiiccccaaaattttiiiioooonnnn
a. Testing Environment:
o+ HP-UX 10.X Operating System
o+ HP 9000 Series 800
b. Binary-compatible Family:
HP 9000 Series 800 computers (all models).
c. The environment contains an XPG4 branded
Internationalised System Calls and Libraries
component.
TTTTeeeemmmmppppoooorrrraaaarrrryyyy WWWWaaaaiiiivvvveeeerrrrssss
None.
2 X/Open Conformance Statement Questionnaire
_X_P_G_4 _C_o_m_m_a_n_d_s _a_n_d _U_t_i_l_i_t_i_e_s
2. CCCChhhhooooiiiicccceeee ooooffff CCCCoooonnnnffffoooorrrrmmmmaaaannnncccceeee SSSSppppeeeecccciiiiffffiiiiccccaaaattttiiiioooonnnn
Question 1: Which specification are you using as a basis for
listing any deviant behaviour of the product?
Response:
This Conformance Statement lists, in the chapter
entitled CCCCoooommmmmmmmaaaannnnddddssss aaaannnndddd UUUUttttiiiilllliiiittttiiiieeeessss ---- PPPPOOOOSSSSIIIIXXXX CCCCoooommmmppppaaaattttiiiibbbbiiiilllliiiittttyyyy,
all the discrepancies between the product behaviour and
that specified in X/Open CAE Specification, Commands
and Utilities, Issue 4 (C203) and X/Open CAE
Specification, System Interface Definitions, Issue 4
(C204).
Rationale:
The XPG4 Commands and Utilities Component Definition
requires that the discrepancies between product
behaviour and either of the two specifications shown
above be documented.
Reference:
Component Definitions, Version 1 (July 1992), Part 2 of
X/Open Systems and Branded Products: XPG4, Section 3.2,
XPG4 Commands and Utilities.
X/Open Conformance Statement Questionnaire 3
_X_P_G_4 _C_o_m_m_a_n_d_s _a_n_d _U_t_i_l_i_t_i_e_s
3. CCCCoooommmmmmmmaaaannnnddddssss aaaannnndddd UUUUttttiiiilllliiiittttiiiieeeessss ---- PPPPOOOOSSSSIIIIXXXX CCCCoooommmmppppaaaattttiiiibbbbiiiilllliiiittttyyyy
3.1 BBBBaaaassssiiiicccc UUUUttttiiiilllliiiittttiiiieeeessss
3.1.1 SSSSuuuuppppppppoooorrrrtttteeeedddd CCCCoooommmmmmmmaaaannnnddddssss
Question 1: Which of the basic utilities (non-development
utilities) defined in X/Open CAE Specification, Commands and
Utilities, Issue 4, are not provided with the
implementation?
Response:
All the basic utilities except _p_a_t_c_h and _t_a_l_k are
provided.
Rationale:
This question determines whether or not the
implementation provides a command of the name specified
in X/Open CAE Specification, Commands and Utilities,
Issue 4; 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 _d_i_s command is not provided.
Reference:
Component Definitions, Version 1 (July 1992), Part 2 of
X/Open Systems and Branded Products: XPG4, Section 3.2,
XPG4 Commands and Utilities.
3.1.2 CCCCoooommmmmmmmaaaannnndddd BBBBeeeehhhhaaaavvvviiiioooouuuurrrr
Question 2: In what ways do the commands provided by the
implementation behave differently from the specifications
contained in X/Open CAE Specification, Commands and
Utilities, Issue 4?
Response:
4 X/Open Conformance Statement Questionnaire
_X_P_G_4 _C_o_m_m_a_n_d_s _a_n_d _U_t_i_l_i_t_i_e_s
_______________________________________________________________________________
Command Behaviour
Utility Option Remarks
_______________________________________________________________________________
_a_d_m_i_n ----aaaa,,,, ----dddd,,,, ----eeee,,,, ----ffff,,,, Does not support blank-separated
----mmmm,,,, ----rrrr option arguments.
Does not support -- as an operand.
_______________________________________________________________________________
_a_r ----CCCC,,,, ----TTTT Option not supported.
Does not support -- as an operand.
_______________________________________________________________________________
_a_t ----tttt Option not supported.
----llll,,,, ----qqqq Option combination not supported.
_______________________________________________________________________________
_c_d Does not support -- as an operand.
_______________________________________________________________________________
_c_r_o_n_t_a_b ----eeee Option not supported.
Does not support -- as an operand.
_______________________________________________________________________________
_d_f ----PPPP Option not supported.
Does not support -- as an operand.
_______________________________________________________________________________
_d_u ----kkkk Option not supported.
Does not report non-stat()able files or
unreadable directories, nor is the exit
status affected by these conditions.
_______________________________________________________________________________
_e_x ----cccc,,,, ----ssss Option not supported.
Does not support -- as an operand.
_______________________________________________________________________________
_h_a_s_h ----rrrr Option not supported.
Is not a built-in utility.
_______________________________________________________________________________
_f_i_n_d Does not support -- as an operand.
_______________________________________________________________________________
_m_a_i_l Does not support -- as an operand.
_______________________________________________________________________________
_n_i_c_e ----nnnn Option not supported.
_______________________________________________________________________________
_n_l ----bbbb,,,, ----dddd,,,, ----ffff,,,, ----hhhh,,,, Does not support blank-separated
----iiii,,,, ----llll,,,, ----nnnn,,,, ----ssss,,,, option arguments.
----vvvv,,,, ----wwww
Does not support -- as an operand.
_______________________________________________________________________________
_n_m ----AAAA,,,, ----gggg,,,, ----PPPP,,,, ----tttt Option not supported.
Does not support -- as an operand.
_______________________________________________________________________________
|8|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|
|8|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|
X/Open Conformance Statement Questionnaire 5
_X_P_G_4 _C_o_m_m_a_n_d_s _a_n_d _U_t_i_l_i_t_i_e_s
_______________________________________________________________________________
Command Behaviour, Continued
Utility Option Remarks
_______________________________________________________________________________
_n_o_h_u_p Does not support -- as an operand.
_______________________________________________________________________________
_p_a_c_k Does not support -- as an operand.
_______________________________________________________________________________
_p_a_t_c_h Command not supported.
_______________________________________________________________________________
_p_a_x Option not supported.
----oooo
_______________________________________________________________________________
_p_r ----cccc Option not supported.
_______________________________________________________________________________
_p_s
----gggg,,,, ----pppp,,,, ----tttt,,,, ----uuuu
Does not support blank-separated elements in list
arguments.
Option not supported.
----AAAA,,,, ----GGGG,,,, ----nnnn,,,, ----oooo,,,,
----UUUU
_______________________________________________________________________________
_s_t_r_i_n_g_s Does not support -- as an operand.
_______________________________________________________________________________
_t_a_l_k Command not supported.
_______________________________________________________________________________
_t_i_m_e ----pppp Option not supported.
Does not support -- as an operand.
_______________________________________________________________________________
_t_s_o_r_t Does not support -- as an operand.
_______________________________________________________________________________
_u_n_p_a_c_k Does not support -- as an operand.
_______________________________________________________________________________
_v_i Does not support blank-separated option arguments.
----tttt,,,, ----wwww
----cccc Option not supported.
Does not support -- as an operand.
_______________________________________________________________________________
_w_h_o ----uuuu Forces -T option on.
----TTTT
Session ID and remote hostname also shown. (On
s700, cnode name instead of hostname).
_______________________________________________________________________________
_x_a_r_g_s Option not supported.
----EEEE,,,, ----IIII,,,, ----LLLL
Does not support -- as an operand.
_______________________________________________________________________________
|8|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|
|8|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|
Rationale:
6 X/Open Conformance Statement Questionnaire
_X_P_G_4 _C_o_m_m_a_n_d_s _a_n_d _U_t_i_l_i_t_i_e_s
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 X/Open CAE Specification, Commands and
Utilities, Issue 4; implementation-specific extensions
should not be documented.
Reference:
Component Definitions, Version 1 (July 1992), Part 2 of
X/Open Systems and Branded Products: XPG4, Section 3.2,
XPG4 Commands and Utilities.
3.2 DDDDeeeevvvveeeellllooooppppmmmmeeeennnntttt UUUUttttiiiilllliiiittttiiiieeeessss
3.2.1 SSSSuuuuppppppppoooorrrrtttteeeedddd CCCCoooommmmmmmmaaaannnnddddssss
Question 3: Which of the development utilities defined in
XPG4 are not provided with the implementation?
Response:
All the development utilities except _d_i_s are provided.
Rationale:
The development utilities are required to exist on
designated DEVELOPMENT systems but may not be present
on all XSI-conformant systems.
Reference:
X/Open CAE Specification, Commands and Utilities, Issue
4, Section 1.3.2, Development.
3.2.2 CCCCoooommmmmmmmaaaannnndddd BBBBeeeehhhhaaaavvvviiiioooouuuurrrr
Question 4: In what ways do the commands provided by the
implementation behave differently from the specifications
contained in X/Open CAE Specification, Commands and
Utilities, Issue 4?
X/Open Conformance Statement Questionnaire 7
_X_P_G_4 _C_o_m_m_a_n_d_s _a_n_d _U_t_i_l_i_t_i_e_s
Response:
_______________________________________________________________________________
Command Behaviour
Utility Option Remarks
_______________________________________________________________________________
_c_t_a_g_s Does not tag C typedefs by default. (-t option does this.)
_______________________________________________________________________________
_d_i_s Command not supported.
_______________________________________________________________________________
_m_4 Does not support blank-separated option arguments.
----DDDD,,,, ----UUUU
Does not support -- as an operand.
_______________________________________________________________________________
_m_a_k_e Does not support ....PPPPOOOOSSSSIIIIXXXX target.
Does not support -- as an operand.
_______________________________________________________________________________
_p_r_s Does not support blank-separated option arguments.
----cccc,,,, ----dddd,,,, ----rrrr
Does not support -- as an operand.
_______________________________________________________________________________
_r_m_d_e_l Does not support -- as an operand.
_______________________________________________________________________________
_s_a_c_t Does not support -- as an operand.
_______________________________________________________________________________
_s_t_r_i_p Does not support -- as an operand.
_______________________________________________________________________________
_u_n_g_e_t Does not support -- as an operand.
_______________________________________________________________________________
_v_a_l Does not support -- as an operand.
_______________________________________________________________________________
_w_h_a_t Does not support -- as an operand.
_______________________________________________________________________________
|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|
|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|7|
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 X/Open CAE Specification, Commands and
Utilities, Issue 4; implementation-specific extensions
should not be documented.
Reference:
X/Open CAE Specification, Commands and Utilities, Issue
4, Section 1.3.2, Development.
8 X/Open Conformance Statement Questionnaire
_X_P_G_4 _C_o_m_m_a_n_d_s _a_n_d _U_t_i_l_i_t_i_e_s
3.3 FFFFOOOORRRRTTTTRRRRAAAANNNN OOOOppppttttiiiioooonnnn
3.3.1 FFFFOOOORRRRTTTTRRRRAAAANNNN UUUUttttiiiilllliiiittttyyyy
Question 5: Is the FORTRAN _f_o_r_t_7_7 utility provided?
Response:
Yes.
Rationale:
The _f_o_r_t_7_7 utility is the command level interface to
the FORTRAN compiler, which need not be provided.
Reference:
X/Open CAE Specification, Commands and Utilities, Issue
4, Section 1.3.3, FORTRAN.
3.3.2 CCCCoooommmmmmmmaaaannnndddd BBBBeeeehhhhaaaavvvviiiioooouuuurrrr
Question 6: In what ways does the _f_o_r_t_7_7 utility provided by
the implementation behave differently from the specification
contained in X/Open CAE Specification, Commands and
Utilities, Issue 4?
_R_e_s_p_o_n_s_e:
Option Remarks
_____________________________
_-_O_n
An optimization
level cannot be
specified using this
option. Use the +_O_n
option instead. See
_f_o_r_t_7_7(1) in the
_H_P-_U_X _R_e_f_e_r_e_n_c_e.
_R_a_t_i_o_n_a_l_e_:
X/Open Conformance Statement Questionnaire 9
_X_P_G_4 _C_o_m_m_a_n_d_s _a_n_d _U_t_i_l_i_t_i_e_s
This question provides a greater degree of granularity
than the previous question, requiring the semantic
differences associated with the command 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 X/Open CAE Specification, Commands and
Utilities, Issue 4; implementation-specific extensions
should not be documented.
_R_e_f_e_r_e_n_c_e_:
X/Open CAE Specification, Commands and Utilities, Issue
4, Section 1.3.3, FORTRAN.
_3_._4 PPPPoooossssssssiiiibbbbllllyyyy UUUUnnnnssssuuuuppppppppoooorrrrttttaaaabbbblllleeee UUUUttttiiiilllliiiittttiiiieeeessss aaaannnndddd OOOOppppttttiiiioooonnnnssss
Question 7: Which of the following utilities and utility
options are not supported on the implementation?
_R_e_s_p_o_n_s_e:
Utility Option Supported
____________________________
_a_r ----ssss Supported
_c_a_n_c_e_l Supported
_c_u Supported
_l_p ----mmmm Supported
_l_p ----oooo Supported
_l_p ----tttt Supported
_l_p ----wwww Supported
_l_p_s_t_a_t Supported
_s_o_r_t ----zzzz Supported
_t_a_b_s ++++mmmm Supported
_u_u_c_p Supported
_u_u_l_o_g Supported
_u_u_n_a_m_e Supported
_u_u_p_i_c_k Supported
_u_u_s_t_a_t Supported
_u_u_t_o Supported
_u_u_x Supported
_R_a_t_i_o_n_a_l_e_:
A number of utilities and utility options are marked as
possibly unsupportable features, and the functionality
associated with these need not be present in a
conforming implementation.
_R_e_f_e_r_e_n_c_e_:
10 X/Open Conformance Statement Questionnaire
_X_P_G_4 _C_o_m_m_a_n_d_s _a_n_d _U_t_i_l_i_t_i_e_s
X/Open CAE Specification, Commands and Utilities, Issue
4, Section 1.7, Portability.
_3_._5 SSSSppppeeeecccciiiiffffiiiicccc CCCCoooommmmmmmmaaaannnnddddssss aaaannnndddd UUUUttttiiiilllliiiittttiiiieeeessss
3.5.1 aaaatttt
Question 8: How does the _a_t command interpret a non-null
_S_H_E_L_L environment variable?
Response:
Uses _s_h irrespective of the setting of _S_H_E_L_L.
Rationale:
The interpretation of the _S_H_E_L_L environment variable
can cause _a_t to invoke different versions of the shell
on some implementations.
Reference:
X/Open CAE Specification, Commands and Utilities, Issue
4, Chapter 3, Utilities, _a_t, ENVIRONMENT VARIABLES,
_S_H_E_L_L.
3.5.2 aaaawwwwkkkk
Question 9: What is the limit on the number of open streams
provided by _a_w_k?
Response:
60 open streams.
Rationale:
The number of open streams that are available to _a_w_k
may differ between implementations, possibly depending
on the number of streams that are available to a
process ({FOPEN_MAX}).
Reference:
X/Open CAE Specification, Commands and Utilities, Issue
4, Chapter 3, Utilities, _a_w_k, Input/Output and General
Functions, close().
X/Open Conformance Statement Questionnaire 11
_X_P_G_4 _C_o_m_m_a_n_d_s _a_n_d _U_t_i_l_i_t_i_e_s
3.5.3 bbbbaaaattttcccchhhh
Question 10: How does the _b_a_t_c_h command interpret a non-null
_S_H_E_L_L environment variable?
Response:
Uses _s_h irrespective of the setting of _S_H_E_L_L.
Rationale:
The interpretation of the _S_H_E_L_L environment variable
can cause _b_a_t_c_h to invoke different versions of the
shell on some implementations.
Reference:
X/Open CAE Specification, Commands and Utilities, Issue
4, Chapter 3, Utilities, _b_a_t_c_h, ENVIRONMENT VARIABLES,
_S_H_E_L_L.
3.5.4 cccc88889999
Question 11: Which defined names are automatically provided
by the compiler?
Response:
Series 700 Series 800
_______________________________________
__DATE__ __DATE__
__FILE__ __FILE__
__LINE__ __LINE__
__STDC__ __STDC__
__TIME__ __TIME__
__PA_RISC1_1 (opt) __PA_RISC1_1 (opt)
__hp9000s700
__hp9000s800 __hp9000s800
__hppa __hppa
__hpux __hpux
__unix __unix
Rationale:
The automatic provision of defined names by the
compiler can cause these names to be unavailable in the
name space for defined names.
12 X/Open Conformance Statement Questionnaire
_X_P_G_4 _C_o_m_m_a_n_d_s _a_n_d _U_t_i_l_i_t_i_e_s
Reference:
X/Open CAE Specification, Commands and Utilities, Issue
4, Chapter 3, Utilities, _c_8_9, OPTIONS, -D.
X/Open Conformance Statement Questionnaire 13
_X_P_G_4 _C_o_m_m_a_n_d_s _a_n_d _U_t_i_l_i_t_i_e_s
Question 12: When multiple input files are specified, where
does _c_8_9 direct identification messages designating the
start of each input file processing?
Response:
Standard output.
Rationale:
These messages, if produced, must be written to one or
the other of standard output and standard error, but
not to both. The destination of these messages is
useful in determining redirections that are necessary
to identify the input files from which warning messages
are generated.
Reference:
X/Open CAE Specification, Commands and Utilities, Issue
4, Chapter 3, Utilities, _c_8_9, STDOUT and STDERR.
Question 13: What are the limits associated with external
symbols imposed by _c_8_9?
Response:
Minimum Implementation
Description Maximum Maximum
_______________________________________________________________________________
Number of significant bytes 31 255
Number of source or object files 511
variable; see _c_8_9(1) in the _H_P-_U_X _R_e_f_e_r_e_n_c_e
Total number of external symbols 4095 dependent upon available system resources
Rationale:
These limits vary between implementations and cannot be
reset by the user. The XCU definition gives the minimum
maximum value for each of the values. Some
applications may require larger limits than these
minimum maxima.
Reference:
X/Open CAE Specification, Commands and Utilities, Issue
4, Chapter 3, Utilities, _c_8_9, EXTENDED DESCRIPTION,
External Symbols.
14 X/Open Conformance Statement Questionnaire
_X_P_G_4 _C_o_m_m_a_n_d_s _a_n_d _U_t_i_l_i_t_i_e_s
3.5.5 ccccaaaannnncccceeeellll
Question 14: Is the submitter of an _l_p job notified when the
job is cancelled by someone else?
Response:
Yes.
Rationale:
It is useful for the submitter of a job to be notified
of its cancellation, rather than having to interrogate
the line printer queue to obtain this information.
Reference:
X/Open CAE Specification, Commands and Utilities, Issue
4, Chapter 3, Utilities, _c_a_n_c_e_l, ENVIRONMENT VARIABLES,
_L_A_N_G.
3.5.6 ccccpppp
Question 15: What is the effect of alternate access control
mechanisms on file copies?
Response:
If the target is a new file or directory, it inherits
the Access Control List of the original file, altered
to reflect any difference in ownership. See _a_c_l(5) in
the _H_P-_U_X _R_e_f_e_r_e_n_c_e.
Rationale:
Because of the additional restrictions on creating
files and reading data from files, the _c_p utility may
not behave as described when alternate access control
mechanisms are in use.
Reference:
X/Open CAE Specification, Commands and Utilities, Issue
4, Chapter 3, Utilities, _c_p, DESCRIPTION, final
paragraph.
X/Open Conformance Statement Questionnaire 15
_X_P_G_4 _C_o_m_m_a_n_d_s _a_n_d _U_t_i_l_i_t_i_e_s
3.5.7 ddddaaaatttteeee
Question 16: Does _d_a_t_e permit the setting of the date and
time?
Response:
Yes.
Rationale:
Some systems, particularly those that are hosted as
part of a total system environment, do not allow the
_d_a_t_e command to set the date. On such systems, the
setting of the date can only be accomplished from the
host environment.
Reference:
X/Open CAE Specification, Commands and Utilities, Issue
4, Chapter 3, Utilities, _d_a_t_e, OPERANDS, mmddhhmm[yy].
3.5.8 eeeexxxx
Question 17: What restrictions are imposed on the set of
commands within the _r_h_s of the _m_a_p command?
Response:
1. The maximum number of characters in the _r_h_s is
limited to 240.
2. Tail recursion is not allowed.
Rationale:
Implementations may impose restrictions on the commands
that can be used by macros in visual mode.
Reference:
X/Open CAE Specifications, Commands and Utilities,
Issue 4, Chapter 3, Utilities, _e_x, EXTENDED
DESCRIPTION, Command Descriptions in ex, Map.
16 X/Open Conformance Statement Questionnaire
_X_P_G_4 _C_o_m_m_a_n_d_s _a_n_d _U_t_i_l_i_t_i_e_s
3.5.9 ffffcccc
Question 18: Is the history list mechanism disabled for
users with appropriate privileges who do not set _H_I_S_T_F_I_L_E?
Response:
No.
Rationale:
XPG4 states that an implementation may, in certain
circumstances, disable the history list mechanism for
users with appropriate privileges who do not set
_H_I_S_T_F_I_L_E. This could have some security implications.
Reference:
X/Open CAE Specification, Commands and Utilities, Issue
4, Chapter 3, Utilities, _f_c, ENVIRONMENT VARIABLES,
_H_I_S_T_F_I_L_E.
3.5.10 ffffoooorrrrtttt77777777
Question 19: When multiple input files are specified, where
does _f_o_r_t_7_7 direct identification messages designating the
start of each input file processing?
Response:
Standard error.
Rationale:
These messages, if produced, must be written to one or
the other of standard output and standard error, but
not to both. The destination of these messages is
useful in determining redirections that are necessary
to identify the input files from which warning messages
are generated.
Reference:
X/Open CAE Specification, Commands and Utilities, Issue
4, Chapter 3, Utilities, _f_o_r_t_7_7, STDERR.
X/Open Conformance Statement Questionnaire 17
_X_P_G_4 _C_o_m_m_a_n_d_s _a_n_d _U_t_i_l_i_t_i_e_s
Question 20: What are the limits associated with external
symbols imposed by _f_o_r_t_7_7?
Response:
Minimum Implementation
Description Maximum Maximum
_______________________________________________________________________________
Number of significant bytes 31 255
Number of source or object files 511
variable; see _f_o_r_t_7_7(1) in the _H_P-_U_X _R_e_f_e_r_e_n_c_e
Total number of external symbols 4095 dependent upon available system resources
Rationale:
These limits vary between implementations and cannot be
reset by the user. The XCU definition gives the minimum
maximum value for each of the values. Some
applications may require larger limits than these
minimum maxima.
Reference:
X/Open CAE Specification, Commands and Utilities, Issue
4, Chapter 3, Utilities, _f_o_r_t_7_7, EXTENDED DESCRIPTION,
External Symbols.
3.5.11 lllleeeexxxx
Question 21: Where are error messages sent when the _l_e_x ----tttt
ooooppppttttiiiioooonnnn iiiissss nnnnooootttt ssssppppeeeecccciiiiffffiiiieeeedddd????
Response:
Standard error.
Rationale:
These messages can be directed to either standard
output or standard error according to XPG4, though the
messages are not allowed to be directed to both. An
application may wish to redirect these messages to a
file.
Reference:
X/Open CAE Specification, Commands and Utilities, Issue
4, Chapter 3, Utilities, _l_e_x, STDOUT.
18 X/Open Conformance Statement Questionnaire
_X_P_G_4 _C_o_m_m_a_n_d_s _a_n_d _U_t_i_l_i_t_i_e_s
3.5.12 llllnnnn
Question 22: Can _l_n create links to a directory?
Response:
Yes.
Rationale:
Implementations may disallow the creation of hard links
to a directory, even though the executing process has
the appropriate privileges.
Reference:
X/Open CAE Specification, Commands and Utilities, Issue
4, Chapter 3, Utilities, _l_n, OPERANDS, _s_o_u_r_c_e__f_i_l_e.
3.5.13 llllooooccccaaaalllleeeeddddeeeeffff
Question 23: What is the default character mapping used when
the _l_o_c_a_l_e_d_e_f ----ffff ooooppppttttiiiioooonnnn iiiissss nnnnooootttt ssssppppeeeecccciiiiffffiiiieeeedddd????
Response:
ASCII.
Rationale:
XPG4 does not define a specific character mapping as
the default for conforming systems. This character
mapping provides encoding information for the members
of the portable character set required by XPG4.
Reference:
X/Open CAE Specification, Commands and Utilities, Issue
4, Chapter 3, Utilities, _l_o_c_a_l_e_d_e_f, OPTIONS, -f.
X/Open Conformance Statement Questionnaire 19
_X_P_G_4 _C_o_m_m_a_n_d_s _a_n_d _U_t_i_l_i_t_i_e_s
3.5.14 llllpppp
Question 24: What _l_p option or operator command is used to
suppress the printing of a banner page?
Response:
----oooo nnnnbbbb
Rationale:
The user may require that banner pages are suppressed
in cases where pre-printed forms are used and the
stationary is of a non-standard length.
Reference:
X/Open CAE Specification, Commands and Utilities, Issue
4, Chapter 3, Utilities, _l_p, DESCRIPTION.
3.5.15 llllssss
Question 25: How many bytes are in a block as reported by
_l_s?
Response:
512 bytes in a block.
Rationale:
The block size used by _l_s to report the number of
blocks occupied by a file varies from system to system;
often this depends on the underlying file system
architecture.
Reference:
X/Open CAE Specification, Commands and Utilities, Issue
4, Chapter 3, Utilities, _l_s, OPTIONS, -s.
20 X/Open Conformance Statement Questionnaire
_X_P_G_4 _C_o_m_m_a_n_d_s _a_n_d _U_t_i_l_i_t_i_e_s
3.5.16 mmmmaaaakkkkeeee
Question 26: What additional variables does _m_a_k_e add to its
environment?
Response:
None.
Rationale:
The implementation of _m_a_k_e may set certain environment
variables on invocation of _m_a_k_e. These variables may
not be set by the user, thus reducing the name space
for environment variables.
Reference:
X/Open CAE Specification, Commands and Utilities, Issue
4, Chapter 3, Utilities, _m_a_k_e, EXTENDED DESCRIPTION,
Makefile Execution.
Question 27: Does the default _M_A_K_E_F_L_A_G_S environment variable
contain additional implementation-dependent options?
Response:
The default _M_A_K_E_F_L_A_G_S environment variable has the
value ----bbbb.
Rationale:
The implementation of _m_a_k_e may set certain default
_M_A_K_E_F_L_A_G_S options on invocation of _m_a_k_e. These
variables are in addition to those set by the user on
the command line and could affect the processing of
_m_a_k_e.
Reference:
X/Open CAE Specification, Commands and Utilities, Issue
4, Chapter 3, Utilities, _m_a_k_e, EXTENDED DESCRIPTION,
Makefile Execution.
X/Open Conformance Statement Questionnaire 21
_X_P_G_4 _C_o_m_m_a_n_d_s _a_n_d _U_t_i_l_i_t_i_e_s
3.5.17 nnnneeeewwwwggggrrrrpppp
Question 28: Does _n_e_w_g_r_p allow users who are not listed as a
member of a group which has no password to change to that
group?
Response:
No.
Rationale:
On some implementations, a user who is not listed as a
member of a group may change to that group in the case
that there is no password associated with the group.
Reference:
X/Open CAE Specification, Commands and Utilities, Issue
4, Chapter 3, Utilities, _n_e_w_g_r_p, DESCRIPTION.
Question 29: Are there any other implementation-specific
authorisation restrictions that affect _n_e_w_g_r_p?
Response:
No.
Rationale:
Some implementations may impose accounting or other
restrictions that could cause _n_e_w_g_r_p to deny activity
to a group member. For example, a resource quota
system could be implemented on a group basis that would
limit the ability to join a group until the resources
were available to the group.
Reference:
X/Open CAE Specification, Commands and Utilities, Issue
4, Chapter 3, Utilities, _n_e_w_g_r_p, DESCRIPTION.
22 X/Open Conformance Statement Questionnaire
_X_P_G_4 _C_o_m_m_a_n_d_s _a_n_d _U_t_i_l_i_t_i_e_s
3.5.18 nnnniiiicccceeee aaaannnndddd rrrreeeennnniiiicccceeee
Question 30: What are the limits and default values used by
_n_i_c_e and _r_e_n_i_c_e?
Response:
Maximum _n_i_c_e value is 19.
Minimum _n_i_c_e value is 1.
Default _n_i_c_e increment is 10.
Rationale:
Each of these values differs between implementations
and the range of values gives the user some control
over the relative priority of processes.
Reference:
X/Open CAE Specification, Commands and Utilities, Issue
4, Chapter 3, Utilities, _n_i_c_e, DESCRIPTION.
3.5.19 ppppaaaaxxxx
Question 31: What is the default archive format used by _p_a_x?
Response:
Extended _t_a_r.
Rationale:
The implementation has the choice as to which format it
shall use as the default when it is creating files.
When it is reading an archive created in either
extended _t_a_r or extended _c_p_i_o format (or any other
format that it understands), the _p_a_x utility will read
the archive in the format as written.
Reference:
X/Open CAE Specification, Commands and Utilities, Issue
4, Chapter 3, Utilities, _p_a_x, DESCRIPTION.
X/Open Conformance Statement Questionnaire 23
_X_P_G_4 _C_o_m_m_a_n_d_s _a_n_d _U_t_i_l_i_t_i_e_s
Question 32: How does _p_a_x handle reading and writing of
archives that span multiple files?
Response:
When end of archive medium is detected, _p_a_x prompts the
user for the next volume of the archive, and allows the
user to specify the location of the next volume.
Rationale:
In many cases _p_a_x will take actions, such as prompting
the user for the device name to use for the next
archive file, when the current archive file is full.
There may be extensions to the syntax of _p_a_x which
allow the user to specify the address to use to access
subsequent files.
Reference:
X/Open CAE Specification, Commands and Utilities, Issue
4, Chapter 3, Utilities, _p_a_x, DESCRIPTION.
Question 33: How does _p_a_x handle invalid filenames when it
is extracting files from an archive?
Response:
_p_a_x issues the error message: "Bad ASCII pathname".
The file is not extracted.
Rationale:
An implementation may either extract the data
associated with these files into files named in an
implementation-defined manner or may issue an error
indicating that the file is being ignored. If _p_a_x
extracts the file, it is necessary for the user either
to be informed of the file that is used or to know the
algorithm that _p_a_x uses in generating these filenames.
Reference:
X/Open CAE Specification, Commands and Utilities, Issue
4, Chapter 3, Utilities, _p_a_x, EXTENDED DESCRIPTION, The
cpio Filename.
24 X/Open Conformance Statement Questionnaire
_X_P_G_4 _C_o_m_m_a_n_d_s _a_n_d _U_t_i_l_i_t_i_e_s
3.5.20 pppprrrriiiinnnnttttffff
Question 34: Does _p_r_i_n_t_f support the e, E, f, g and G
floating point conversion specifications?
Response:
Yes.
Rationale:
The support of these conversions is not required on an
XCU conforming system.
Reference:
X/Open CAE Specification, Commands and Utilities, Issue
4, Chapter 3, Utilities, _p_r_i_n_t_f, EXAMPLES.
3.5.21 sssshhhh
Question 35: Is the environment variable _I_F_S ignored when
the shell is invoked?
Response:
Yes.
Rationale:
The XCU definition allows that the _s_h command ignore
the setting of the _I_F_S environment variable on
invocation. The setting of this variable has been used
to breach security on systems which use the shell to
interpret a call to the _s_y_s_t_e_m() and _e_x_e_c_v_p()
interfaces.
Reference:
X/Open CAE Specification, Commands and Utilities, Issue
4, Chapter 3, Utilities, _s_h, ENVIRONMENT VARIABLES,
_I_F_S.
X/Open Conformance Statement Questionnaire 25
_X_P_G_4 _C_o_m_m_a_n_d_s _a_n_d _U_t_i_l_i_t_i_e_s
3.5.22 ttttoooouuuucccchhhh
Question 36: What is the latest date after the Epoch that
can be used by _t_o_u_c_h?
Response:
01:00 18 January, 2038 UTC
Rationale:
Because of the limitations on the storage of times in
the ssssttttaaaatttt structure associated with a file, there is a
limitation on the valid dates that can be specified to
_t_o_u_c_h. This is directly related to the value that can
be stored in the integral type ttttiiiimmmmeeee____tttt.
Reference:
X/Open CAE Specification, Commands and Utilities, Issue
4, Chapter 3, Utilities, _t_o_u_c_h, OPTIONS, -t.
3.5.23 yyyyaaaacccccccc
Question 37: What are the limits of _y_a_c_c’s internal tables?
Response:
Minimum Implementation
Description Maximum Maximum
_______________________________________________________________________________
Number of tokens 126 2000
Number of non-terminals 200
variable; see _y_a_c_c(1) in the _H_P-_U_X _R_e_f_e_r_e_n_c_e
Number of rules 300 dependent upon available system resources
Number of states 600
variable; see _y_a_c_c(1) in the _H_P-_U_X _R_e_f_e_r_e_n_c_e
Length of rules 5200 dependent upon available system resources
Number of actions 4000
variable; see _y_a_c_c(1) in the _H_P-_U_X _R_e_f_e_r_e_n_c_e
Rationale:
These internal table sizes vary between implementations
and cannot be reset by the user. The XCU definition
gives the minimum maximum value for each of the table
values.
Reference:
26 X/Open Conformance Statement Questionnaire
_X_P_G_4 _C_o_m_m_a_n_d_s _a_n_d _U_t_i_l_i_t_i_e_s
X/Open CAE Specification, Commands and Utilities, Issue
4, Chapter 3, Utilities, _y_a_c_c, EXTENDED DESCRIPTION,
Limits.
XXXX////OOOOppppeeeennnn CCCCoooonnnnffffoooorrrrmmmmaaaannnncccceeee SSSSttttaaaatttteeeemmmmeeeennnntttt QQQQuuuueeeessssttttiiiioooonnnnnnnnaaaaiiiirrrreeee
TTTTyyyyppppeeee:::: XXXXPPPPGGGG4444 PPPPrrrrooooffffiiiilllleeee
PPPPrrrrooooffffiiiilllleeee NNNNaaaammmmeeee:::: XXXXPPPPGGGG4444 BBBBaaaasssseeee
Completed by: Tom Shem, Hewlett-Packard Company
_________________________________________
(name and organisation)
on: Oct 6, 1994
_________________________________________
(date)
_X_P_G_4 _B_a_s_e
4. XXXXPPPPGGGG4444 BBBBaaaasssseeee
PPPPrrrroooodddduuuucccctttt IIIIddddeeeennnnttttiiiiffffiiiiccccaaaattttiiiioooonnnn
Product Identification HP-UX Operating System
_________________________________________
Version/Release No. HP-UX 10.X for the Series 800
_________________________________________
If you do not supply this product yourself, please
identify below the supplier you reference:
Product Identification HP-UX ANSI C Compiler
_________________________________________
Version/Release No. Version A.10.00, HP-UX Release 10.0
_________________________________________
If you do not supply this product yourself, please
identify below the supplier you reference:
EEEEnnnnvvvviiiirrrroooonnnnmmmmeeeennnntttt SSSSppppeeeecccciiiiffffiiiiccccaaaattttiiiioooonnnn
a. Binary-compatible Family:
HP 9000 Series 800 (all models)
b. Special instructions for configuring the Product(s) to
meet the Conformance Requirements of this profile:
None.
28 X/Open Conformance Statement Questionnaire
_X_P_G_4 _B_a_s_e
TTTTeeeemmmmppppoooorrrraaaarrrryyyy WWWWaaaaiiiivvvveeeerrrrssss
Waiver Number Expiry Date
___________________________
4.1 CCCCoooommmmppppoooonnnneeeennnnttttssss
Completed CSQs for all the following XPG4 components are
attached.
4.1.1 XXXXPPPPGGGG4444 IIIInnnntttteeeerrrrnnnnaaaattttiiiioooonnnnaaaalllliiiisssseeeedddd SSSSyyyysssstttteeeemmmm CCCCaaaallllllllssss aaaannnndddd LLLLiiiibbbbrrrraaaarrrriiiieeeessss
4.1.2 XXXXPPPPGGGG4444 CCCCoooommmmmmmmaaaannnnddddssss aaaannnndddd UUUUttttiiiilllliiiittttiiiieeeessss
4.1.3 XXXXPPPPGGGG4444 CCCC LLLLaaaannnngggguuuuaaaaggggeeee
XXXX////OOOOppppeeeennnn CCCCoooonnnnffffoooorrrrmmmmaaaannnncccceeee SSSSttttaaaatttteeeemmmmeeeennnntttt QQQQuuuueeeessssttttiiiioooonnnnnnnnaaaaiiiirrrreeee
TTTTyyyyppppeeee:::: XXXXPPPPGGGG4444 CCCCoooommmmppppoooonnnneeeennnntttt
CCCCoooommmmppppoooonnnneeeennnntttt NNNNaaaammmmeeee:::: XXXXPPPPGGGG4444 IIIInnnntttteeeerrrrnnnnaaaattttiiiioooonnnnaaaalllliiiisssseeeedddd SSSSyyyysssstttteeeemmmm CCCCaaaallllllllssss
aaaannnndddd LLLLiiiibbbbrrrraaaarrrriiiieeeessss
_X_P_G_4 _B_a_s_e
Completed by: Tom Shem, Hewlett-Packard Company
_________________________________________
(name and organisation)
on: Oct 6, 1994
_________________________________________
(date)
30 X/Open Conformance Statement Questionnaire
_X_P_G_4 _I_n_t_e_r_n_a_t_i_o_n_a_l_i_s_e_d _S_y_s_t_e_m _C_a_l_l_s _a_n_d _L_i_b_r_a_r_i_e_s
5. IIIInnnntttteeeerrrrnnnnaaaattttiiiioooonnnnaaaalllliiiisssseeeedddd SSSSyyyysssstttteeeemmmm CCCCaaaallllllllssss aaaannnndddd LLLLiiiibbbbrrrraaaarrrriiiieeeessss
PPPPrrrroooodddduuuucccctttt IIIIddddeeeennnnttttiiiiffffiiiiccccaaaattttiiiioooonnnn
Product Identification HP-UX Operating System
_________________________________________
Version/Release No. HP-UX 10.X for the Series 800
_________________________________________
If you do not supply this component yourself, please
identify below the supplier you reference:
IIIInnnnddddiiiiccccaaaattttoooorrrr ooooffff CCCCoooommmmpppplllliiiiaaaannnncccceeee
Test report from VSX4.
Test suite release number 4.3.2
Test report reference number
EEEEnnnnvvvviiiirrrroooonnnnmmmmeeeennnntttt SSSSppppeeeecccciiiiffffiiiiccccaaaattttiiiioooonnnn
a. Testing Environment:
o+ HP 9000 Series 800. Standalone only.
o+ Sufficient disk space for the tests to have at
least 80Mb free on a single volume or partition.
o+ Loopback cable:
TX -RX
RX -TX
DCD-DTR
DTR-DCD
GND-GND
o+ Mountable empty drive or partition.
o+ All tests were run self-hosted on the machine
being tested.
X/Open Conformance Statement Questionnaire 31
_X_P_G_4 _I_n_t_e_r_n_a_t_i_o_n_a_l_i_s_e_d _S_y_s_t_e_m _C_a_l_l_s _a_n_d _L_i_b_r_a_r_i_e_s
o+ Compiler options used:
----AAAAaaaa ----DDDD____XXXXPPPPGGGG4444 ----llllMMMM
o+ Due to security enhancements and a new file
system, links must be created:
llllnnnn ----ssss ////uuuussssrrrr////bbbbiiiinnnn////kkkksssshhhh ////bbbbiiiinnnn////kkkksssshhhh
llllnnnn ----ssss ////uuuussssrrrr////bbbbiiiinnnn////sssshhhh ////bbbbiiiinnnn////sssshhhh
llllnnnn ----ssss ////uuuussssrrrr////bbbbiiiinnnn////ccccsssshhhh ////bbbbiiiinnnn////ccccsssshhhh
llllnnnn ----ssss ////uuuussssrrrr////bbbbiiiinnnn////rrrrmmmm ////bbbbiiiinnnn////rrrrmmmm
llllnnnn ----ssss ////uuuussssrrrr////bbbbiiiinnnn////llllssss ////bbbbiiiinnnn////llllssss
llllnnnn ----ssss ////uuuussssrrrr////ccccccccssss////bbbbiiiinnnn////mmmmaaaakkkkeeee ////bbbbiiiinnnn////mmmmaaaakkkkeeee
llllnnnn ----ssss ////uuuussssrrrr////ccccccccssss////bbbbiiiinnnn////aaaarrrr ////bbbbiiiinnnn////aaaarrrr
llllnnnn ----ssss ////oooopppptttt////aaaannnnssssiiiicccc////bbbbiiiinnnn////cccc88889999 ////bbbbiiiinnnn////cccccccc
llllnnnn ----ssss ////oooopppptttt////aaaannnnssssiiiicccc////bbbbiiiinnnn////cccc88889999 ////bbbbiiiinnnn////cccc88889999
llllnnnn ----ssss ////oooopppptttt////aaaannnnssssiiiicccc////bbbbiiiinnnn////cccc88889999 ////uuuussssrrrr////ccccccccssss////bbbbiiiinnnn////cccc88889999
llllnnnn ----ssss ////uuuussssrrrr////ssssbbbbiiiinnnn////rrrreeeennnniiiicccceeee ////uuuussssrrrr////bbbbiiiinnnn////rrrreeeennnniiiicccceeee
llllnnnn ----ssss ////uuuussssrrrr////ssssbbbbiiiinnnn////mmmmoooouuuunnnntttt ////eeeettttcccc////mmmmoooouuuunnnntttt
llllnnnn ----ssss ////uuuussssrrrr////ssssbbbbiiiinnnn////uuuummmmoooouuuunnnntttt ////eeeettttcccc////uuuummmmoooouuuunnnntttt
llllnnnn ----ssss ////vvvvaaaarrrr////ttttmmmmpppp ////uuuussssrrrr////ttttmmmmpppp
llllnnnn ----ssss ////eeeettttcccc////ggggrrrroooouuuupppp ////eeeettttcccc////llllooooggggiiiinnnnggggrrrroooouuuupppp
o+ If you wish to test the system with
{_POSIX_CHOWN_RESTRICTED} enabled, enter (as
superuser) the command:
sssseeeettttpppprrrriiiivvvvggggrrrrpppp ----nnnn CCCCHHHHOOOOWWWWNNNN
to disable it, use
sssseeeettttpppprrrriiiivvvvggggrrrrpppp ----gggg CCCCHHHHOOOOWWWWNNNN
The formal branding run was done with
{_POSIX_CHOWN_RESTRICTED} enabled. If you wish
to test the system with {_POSIX_NO_TRUNC}
enabled, do not run the test suite on a file
system set up for short file names. The formal
branding run was done on a file system with long
file names, so {_POSIX_NO_TRUNC} is enabled.
b. Binary-compatible Family:
HP 9000 Series 800 (all models)
32 X/Open Conformance Statement Questionnaire
_X_P_G_4 _I_n_t_e_r_n_a_t_i_o_n_a_l_i_s_e_d _S_y_s_t_e_m _C_a_l_l_s _a_n_d _L_i_b_r_a_r_i_e_s
TTTTeeeemmmmppppoooorrrraaaarrrryyyy WWWWaaaaiiiivvvveeeerrrrssss
None.
5.1 GGGGeeeennnneeeerrrraaaallll AAAAttttttttrrrriiiibbbbuuuutttteeeessss
5.1.1 XXXXPPPPGGGG4444 FFFFeeeeaaaattttuuuurrrreeee GGGGrrrroooouuuuppppssss
Question 1: Which of the following Feature Groups are
supported by the implementation?
Response:
POSIX.2 C-language Binding YES
Shared Memory YES
Encryption YES
Enhanced Internationalisation YES
Note: All the interfaces in all these groups must exist
on all XPG4 XSI-conformant systems, and each interface
must either behave according to the description in
System Interfaces and Headers, Issue 4, or indicate an
error, with _e_r_r_n_o set to [ENOSYS].
Support for particular Feature Groups may be required
in order to conform to particular X/Open Profiles.
Support for a Feature Group can only be claimed if _a_l_l
interfaces in that group behave according to the
relevant descriptions in System Interfaces and Headers,
Issue 4.
Rationale:
System Interfaces and Headers, Issue 4 states that the
system may provide one or more of the Feature Groups
listed.
Reference:
X/Open CAE Specification, System Interfaces and
Headers, Issue 4, Section 1.2, Conformance and Section
1.3, Feature Groups.
X/Open Conformance Statement Questionnaire 33
_X_P_G_4 _I_n_t_e_r_n_a_t_i_o_n_a_l_i_s_e_d _S_y_s_t_e_m _C_a_l_l_s _a_n_d _L_i_b_r_a_r_i_e_s
5.1.2 PPPPOOOOSSSSIIIIXXXX....1111 SSSSuuuuppppppppoooorrrrtttteeeedddd FFFFeeeeaaaattttuuuurrrreeeessss
Question 2: Which of the following options, specified in the
<<<<uuuunnnniiiissssttttdddd....hhhh>>>> header file, are available on the system?
Response:
Macro Name Meaning Provided
______________________________________________________________
_POSIX_CHOWN_RESTRICTED Variable
The use of _c_h_o_w_n() is
restricted to a process
with appropriate
privileges, and to changing
the group ID of a file only
to the effective group ID
of the process or one of
its supplementary group
IDs.
_POSIX_NO_TRUNC Variable
Pathname components longer
than {NAME_MAX) generate an
error.
_POSIX_VDISABLE Yes
Terminal special characters
defined in <<<<tttteeeerrrrmmmmiiiioooossss....hhhh>>>> can
be disabled using this
character value.
_POSIX_SAVED_IDS Yes
Each process has a saved
set-user-ID and a saved
set-group-ID.
_POSIX_JOB_CONTROL Yes
Implementation supports job
control.
The variable {{{{____PPPPOOOOSSSSIIIIXXXX____CCCCHHHHOOOOWWWWNNNN____RRRREEEESSSSTTTTRRRRIIIICCCCTTTTEEEEDDDD}}}} is enabled for
each process for which its effective group ID or one of
its supplementary group IDs has the CHOWN privilege.
This is manipulated with the sssseeeettttpppprrrriiiivvvvggggrrrrpppp(1M) utility, as
described in the Testing Environment section above.
The variable {{{{____PPPPOOOOSSSSIIIIXXXX____NNNNOOOO____TTTTRRRRUUUUNNNNCCCC}}}} is enabled for each path
that resides (or would reside) on a long file name file
system, and disabled for other paths. All file systems
shipped with the HP-UX product are long name file
systems. Short name file systems can be created with
the nnnneeeewwwwffffssss(1M) utility, and converted to long name file
systems with the ccccoooonnnnvvvveeeerrrrttttffffssss(1M) utility.
Rationale:
34 X/Open Conformance Statement Questionnaire
_X_P_G_4 _I_n_t_e_r_n_a_t_i_o_n_a_l_i_s_e_d _S_y_s_t_e_m _C_a_l_l_s _a_n_d _L_i_b_r_a_r_i_e_s
For an XSI-conformant implementation, all of these
POSIX features must be provided. In some cases the
feature need not be provided for all files or devices
supported by the implementation.
Reference:
X/Open CAE Specification, System Interfaces and
Headers, Issue 4, Chapter 4, Headers, <<<<uuuunnnniiiissssttttdddd....hhhh>>>>.
X/Open Conformance Statement Questionnaire 35
_X_P_G_4 _I_n_t_e_r_n_a_t_i_o_n_a_l_i_s_e_d _S_y_s_t_e_m _C_a_l_l_s _a_n_d _L_i_b_r_a_r_i_e_s
5.1.3 FFFFllllooooaaaatttt,,,, SSSSttttddddiiiioooo aaaannnndddd LLLLiiiimmmmiiiitttt VVVVaaaalllluuuueeeessss
Question 3: What are the values associated with the
following constants specified in the <<<<ffffllllooooaaaatttt....hhhh>>>> header file?
Response:
Macro Name Meaning Value
__________________________________________________________________________
FLT_RADIX Radix of the exponent representation. 2
FLT_MANT_DIG 24
Number of base-FLT_RADIX digits in the
float significand.
DBL_MANT_DIG 53
Number of base-FLT_RADIX digits in the
double significand.
LDBL_MANT_DIG 113
Number of base-FLT_RADIX digits in the
long double significand.
FLT_DIG 6
Number of decimal digits, _q, such that
any floating point number with _q digits
can be rounded into a float
representation and back again without
change to the _q digits.
DBL_DIG 15
Number of decimal digits, _q, such that
any floating point number with _q digits
can be rounded into a double
representation and back again without
change to the _q digits.
LDBL_DIG 33
Number of decimal digits, _q, such that
any floating point number with _q digits
can be rounded into a long double
representation and back again without
change to the _q digits.
FLT_MIN_EXP -125
Minimum negative integer such that
FLT_RADIX raised to that power minus 1 is
a normalised float.
DBL_MIN_EXP -1021
Minimum negative integer such that
FLT_RADIX raised to that power minus 1 is
a normalised double.
LDBL_MIN_EXP -16381
Minimum negative integer such that
FLT_RADIX raised to that power minus 1 is
a normalised long double.
FLT_MIN_10_EXP -37
Minimum negative integer such that 10
raised to that power is in the range of
normalised floats.
DBL_MIN_10_EXP -307
Minimum negative integer such that 10
raised to that power is in the range of
normalised doubles.
LDBL_MIN_10_EXP -4931
Minimum negative integer such that 10
raised to that power is in the range of
normalised long doubles.
36 X/Open Conformance Statement Questionnaire
_X_P_G_4 _I_n_t_e_r_n_a_t_i_o_n_a_l_i_s_e_d _S_y_s_t_e_m _C_a_l_l_s _a_n_d _L_i_b_r_a_r_i_e_s
Macro Name Meaning Value
__________________________________________________________________________
FLT_MAX_EXP 128
Maximum integer such that FLT_RADIX
raised to that power minus 1 is a
representable finite float.
DBL_MAX_EXP 1024
Maximum integer such that FLT_RADIX
raised to that power minus 1 is a
representable finite double.
LDBL_MAX_EXP 16384
Maximum integer such that FLT_RADIX
raised to that power minus 1 is a
representable finite long double.
FLT_MAX_10_EXP 38
Maximum integer such that 10 raised to
that power is in the range of
representable finite floats.
DBL_MAX_10_EXP 308
Maximum integer such that 10 raised to
that power is in the range of
representable finite doubles.
LDBL_MAX_10_EXP 4932
Maximum integer such that 10 raised to
that power is in the range of
representable finite long doubles.
FLT_MAX Maximum representable finite float. 3.40282347E+38
DBL_MAX Maximum representable finite double. 1.797 ... E+308
LDBL_MAX Maximum representable finite long double. 1.189 ... E4932
FLT_EPSILON 1.19209290E-07
Difference between 1.0 and the least
value greater than 1.0 that is
representable as a float.
DBL_EPSILON 2.220 ... E-16
Difference between 1.0 and the least
value greater than 1.0 that is
representable as a double.
LDBL_EPSILON 1.925 ... E-34
Difference between 1.0 and the least
value greater than 1.0 that is
representable as a long double.
FLT_MIN Minimum normalised positive float. 1.17549435E-38
DBL_MIN Minimum normalised positive double. 2.225 ... E-308
LDBL_MIN Minimum normalised positive long double. 3.362 ... E-4932
Rationale:
This set of constants provides useful information
regarding the underlying architecture of the
implementation.
Reference:
X/Open CAE Specification, System Interfaces and
Headers, Issue 4, Chapter 4, Headers, <<<<ffffllllooooaaaatttt....hhhh>>>>.
X/Open Conformance Statement Questionnaire 37
_X_P_G_4 _I_n_t_e_r_n_a_t_i_o_n_a_l_i_s_e_d _S_y_s_t_e_m _C_a_l_l_s _a_n_d _L_i_b_r_a_r_i_e_s
Question 4: What are the values associated with the
following constants (optionally specified in the <<<<lllliiiimmmmiiiittttssss....hhhh>>>>
header file)?
Response:
Macro Name Meaning Minimum Maximum
_______________________________________________________________
ARG_MAX 20478 Indeterminate
Maximum length of argument to
the _e_x_e_c functions including
the environment data.
CHILD_MAX 25 Indeterminate
Maximum number of processes
per user ID.
LINK_MAX 32767 32767
Maximum number of links to a
single file.
MAX_CANON 512 512
Maximum number of bytes in a
terminal canonical input line.
NAME_MAX 14 255
Maximum number of bytes
allowed in a terimnal input
queue.
OPEN_MAX 60 1024
Maximum number of open files
that one process can have open
at any one time.
PATH_MAX 1023 1023
Maximum number of bytes in a
pathname (including the
terminating null).
PIPE_BUF 8192 8192
Maximum number of bytes that
is guaranteed to be atomic
when writing to a pipe.
STREAM_MAX 60 1024
Number of streams that one
process can have open at one
time.
TZNAME_MAX 19 19
Maximum number of bytes
supported for the name of a
time zone.
Rationale:
Each of these limits can vary within bounds set by
System Interfaces and Headers, Issue 4. The minimum
value that a limit can take on any XSI conforming
system is given in the corresponding _POSIX_ value. A
specific 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 _POSIX_ value provides a
known lower bound for the range of possible values.
38 X/Open Conformance Statement Questionnaire
_X_P_G_4 _I_n_t_e_r_n_a_t_i_o_n_a_l_i_s_e_d _S_y_s_t_e_m _C_a_l_l_s _a_n_d _L_i_b_r_a_r_i_e_s
Reference:
X/Open CAE Specification, System Interfaces and
Headers, Issue 4, Chapter 4, Headers, <<<<lllliiiimmmmiiiittttssss....hhhh>>>>.
X/Open Conformance Statement Questionnaire 39
_X_P_G_4 _I_n_t_e_r_n_a_t_i_o_n_a_l_i_s_e_d _S_y_s_t_e_m _C_a_l_l_s _a_n_d _L_i_b_r_a_r_i_e_s
Question 5: What are the values associated with the
following constants specified in the <<<<lllliiiimmmmiiiittttssss....hhhh>>>> header file?
Response:
Macro Name Meaning Minimum Maximum
_______________________________________________________________
BC_BASE_MAX 99 99
Maximum _i_b_a_s_e and _o_b_a_s_e values
allowed by the _b_c utility.
BC_DIM_MAX 2048 2048
Maximum number of elements
permitted in an array by the
_b_c utility.
BC_SCALE_MAX 99 99
Maximum scale value allowed by
the _b_c utility.
BC_STRING_MAX 1000 1000
Maximum length of a string
constant accepted by the _b_c
utility.
COLL_WEIGHTS_MAX 4 4
Maximum number of weights that
can be assigned to an entry of
the LC_COLLATE order keyword
in the locale definition file.
EXPR_NEST_MAX 32 32
Maximum number of expressions
that can be nested within
parentheses by the expr
utility.
LINE_MAX 2048 2048
Maximum length in bytes
including the trailing newline
of a utility’s input line when
the utility is described as
processing text files.
NGROUPS_MAX 20 20
Maximum number of simultaneous
supplementary group IDs per
process.
RE_DUP_MAX 255 255
Maximum number of repeated
occurrences of a regular
expression permited when using
interval notation.
Rationale:
40 X/Open Conformance Statement Questionnaire
_X_P_G_4 _I_n_t_e_r_n_a_t_i_o_n_a_l_i_s_e_d _S_y_s_t_e_m _C_a_l_l_s _a_n_d _L_i_b_r_a_r_i_e_s
Each of these limits can vary within bounds set by
System Interfaces and Headers, Issue 4. The minimum
value that a limit can take on any XSI conforming
system is given in the corresponding _POSIX_ or
_POSIX2_ value. A specific 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
_POSIX_ or _POSIX2_ value provides a known lower bound
for the range of possible values.
Reference:
X/Open CAE Specification, System Interfaces and
Headers, Issue 4, Chapter 4, Headers, <<<<lllliiiimmmmiiiittttssss....hhhh>>>>.
X/Open Conformance Statement Questionnaire 41
_X_P_G_4 _I_n_t_e_r_n_a_t_i_o_n_a_l_i_s_e_d _S_y_s_t_e_m _C_a_l_l_s _a_n_d _L_i_b_r_a_r_i_e_s
Question 6: What are the values associated with the
following numerical constants specified in the <<<<lllliiiimmmmiiiittttssss....hhhh>>>>
header file?
Response:
Macro Name Meaning Value
_________________________________________________________________
CHAR_BIT Number of bits in a cccchhhhaaaarrrr. 8
CHAR_MAX Maximum value of a cccchhhhaaaarrrr. 127
INT_MAX Maximum value of an iiiinnnntttt. 2147483647
LONG_BIT Number of bits in a lllloooonnnngggg iiiinnnntttt. 32
LONG_MAX Maximum value of a lllloooonnnngggg iiiinnnntttt. 2147483647
MB_LEN_MAX 4
Maximum number of bytes in a character, for
any supported locale.
SCHAR_MAX Maximum value of a ssssiiiiggggnnnneeeedddd cccchhhhaaaarrrr. 127
SHRT_MAX Maximum value of a sssshhhhoooorrrrtttt. 32767
SSIZE_MAX Maximum value of an object of type ssssssssiiiizzzzeeee____tttt. 2147483647
UCHAR_MAX Maximum value of an uuuunnnnssssiiiiggggnnnneeeedddd cccchhhhaaaarrrr. 255
UINT_MAX Maximum value of an uuuunnnnssssiiiiggggnnnneeeedddd iiiinnnntttt. 4294967295
ULONG_MAX Maximum value of an uuuunnnnssssiiiiggggnnnneeeedddd lllloooonnnngggg iiiinnnntttt. 4294967295
USHRT_MAX Maximum value of an uuuunnnnssssiiiiggggnnnneeeedddd sssshhhhoooorrrrtttt iiiinnnntttt. 65535
WORD_BIT Number of bits in a word or iiiinnnntttt. 32
Rationale:
This set of constants provides useful information
regarding the underlying architecture of the
implementation.
Reference:
X/Open CAE Specification, System Interfaces and
Headers, Issue 4, Chapter 4, Headers, <<<<lllliiiimmmmiiiittttssss....hhhh>>>>.
Question 7: What are the values associated with the
following numerical constants specified in the <<<<ssssttttddddiiiioooo....hhhh>>>>
header file?
Response:
42 X/Open Conformance Statement Questionnaire
_X_P_G_4 _I_n_t_e_r_n_a_t_i_o_n_a_l_i_s_e_d _S_y_s_t_e_m _C_a_l_l_s _a_n_d _L_i_b_r_a_r_i_e_s
Macro Name Meaning Value
_______________________________________________
FOPEN_MAX 60
Number of streams which the
implementation guarantees can
be open simultaneously.
L_tmpnam 25
Maximum size of character
array to hold _t_m_p_n_a_m() output.
TMP_MAX 17576
Minimum number of unique
filenames generated by
_t_m_p_n_a_m(), which is the maximum
number of times an application
can call _t_m_p_n_a_m() reliably.
Rationale:
This set of constants provide useful information about
the implementation.
Reference:
X/Open CAE Specification, System Interfaces and
Headers, Issue 4, Chapter 4, Headers, <<<<ssssttttddddiiiioooo....hhhh>>>>.
X/Open Conformance Statement Questionnaire 43
_X_P_G_4 _I_n_t_e_r_n_a_t_i_o_n_a_l_i_s_e_d _S_y_s_t_e_m _C_a_l_l_s _a_n_d _L_i_b_r_a_r_i_e_s
5.1.4 EEEErrrrrrrroooorrrr CCCCoooonnnnddddiiiittttiiiioooonnnnssss
Question 8: Which of the following option errors listed in
System Interfaces and Headers, Issue 4 are detected in the
circumstances specified?
Response:
Function Error Detected
______________________________________________
_a_c_c_e_s_s() EINVAL Yes
ETXTBSY Yes
_a_c_o_s() EDOM Yes
_a_s_i_n() EDOM Yes
ERANGE Yes
_a_t_a_n() EDOM Yes
ERANGE Yes
_a_t_a_n_2() EDOM Yes
ERANGE Yes
_c_a_t_c_l_o_s_e() EBADF Yes
EINTR Yes
_c_a_t_g_e_t_s() EBADF Yes
EINTR Yes
_c_a_t_o_p_e_n() EACCES Yes
EMFILE Yes
ENAMETOOLONG Yes
ENFILE Yes
ENOENT Yes
ENOMEM Yes
ENOTDIR Yes
_c_e_i_l() EDOM Yes
_c_f_s_e_t_i_s_p_e_e_d() EINVAL Yes
_c_f_s_e_t_o_s_p_e_e_d() EINVAL Yes
_c_h_m_o_d() EINVAL Yes
_c_h_o_w_n() EINVAL Yes
_c_l_o_s_e_d_i_r() EBADF Yes
EINTR Yes
_c_o_s() EDOM Yes
ERANGE Yes
_c_o_s_h() EDOM Yes
_e_r_f() EDOM Yes
ERANGE Yes
_e_r_f_c() EDOM Yes
44 X/Open Conformance Statement Questionnaire
_X_P_G_4 _I_n_t_e_r_n_a_t_i_o_n_a_l_i_s_e_d _S_y_s_t_e_m _C_a_l_l_s _a_n_d _L_i_b_r_a_r_i_e_s
Function Error Detected
______________________________________________
ERANGE Yes
_e_x_e_c ENOMEM Yes
ETXTBSY Yes
_e_x_p() EDOM Yes
ERANGE Yes
_f_a_b_s() EDOM Yes
ERANGE Yes
_f_c_n_t_l() EDEADLK Yes
_f_d_o_p_e_n() EBADF Yes
EINVAL Yes
EMFILE Yes
ENOMEM Yes
_f_g_e_t_c() ENOMEM Yes
ENXIO Yes
_f_g_e_t_w_c() ENOMEM Yes
ENXIO Yes
EILSEQ Yes
_f_i_l_e_n_o() EBADF No
_f_l_o_o_r() EDOM Yes
_f_m_o_d() EDOM Yes
ERANGE Yes
_f_o_p_e_n() EINVAL Yes
EMFILE Yes
ENOMEM Yes
ETXTBSY Yes
_f_o_r_k() ENOMEM Yes
_f_p_a_t_h_c_o_n_f() EBADF Yes
EINVAL Yes
_f_p_r_i_n_t_f() EINVAL No
EILSEQ Yes
_f_p_u_t_c() ENOMEM Yes
ENXIO Yes
_f_p_u_t_w_c() ENOMEM Yes
ENXIO Yes
EILSEQ Yes
_f_r_e_o_p_e_n() EINVAL Yes
ENOMEM Yes
ETXTBSY Yes
_f_r_e_x_p() EDOM Yes
_f_s_e_e_k() EINVAL Yes
X/Open Conformance Statement Questionnaire 45
_X_P_G_4 _I_n_t_e_r_n_a_t_i_o_n_a_l_i_s_e_d _S_y_s_t_e_m _C_a_l_l_s _a_n_d _L_i_b_r_a_r_i_e_s
Function Error Detected
______________________________________________
EPIPE Yes
_f_t_w() EINVAL Yes
_g_e_t_c_w_d() EACCES Yes
ENOMEM Yes
_g_e_t_g_r_g_i_d() EIO Yes
EINTR Yes
EMFILE Yes
ENFILE Yes
_g_e_t_g_r_n_a_m() EIO Yes
EINTR Yes
EMFILE Yes
ENFILE Yes
_g_e_t_l_o_g_i_n() EMFILE Yes
ENFILE Yes
ENXIO Yes
_g_e_t_p_a_s_s() EINTR Yes
EIO Yes
EMFILE Yes
ENFILE Yes
ENXIO Yes
_g_e_t_p_w_n_a_m() EIO Yes
EINTR Yes
EMFILE Yes
ENFILE Yes
_g_e_t_p_w_u_i_d() EIO Yes
EINTR Yes
EMFILE Yes
_h_s_e_a_r_c_h() ENOMEM Yes
_h_y_p_o_t() EDOM Yes
ERANGE Yes
_i_c_o_n_v() EBADF Yes
_i_c_o_n_v___c_l_o_s_e() EBADF Yes
_i_c_o_n_v___o_p_e_n() EMFILE Yes
ENFILE Yes
ENOMEM Yes
EINVAL Yes
_i_s_a_t_t_y() EBADF Yes
ENOTTY Yes
_j_0() EDOM Yes
ERANGE Yes
_j_1() EDOM Yes
ERANGE Yes
46 X/Open Conformance Statement Questionnaire
_X_P_G_4 _I_n_t_e_r_n_a_t_i_o_n_a_l_i_s_e_d _S_y_s_t_e_m _C_a_l_l_s _a_n_d _L_i_b_r_a_r_i_e_s
Function Error Detected
______________________________________________
_j_n() EDOM Yes
ERANGE Yes
_l_d_e_x_p() EDOM Yes
ERANGE Yes
_l_g_a_m_m_a() EDOM Yes
ERANGE Yes
_l_i_n_k() EPERM Yes
EXDEV Yes
_l_o_g() EDOM Yes
ERANGE Yes
_l_o_g_1_0() EDOM Yes
ERANGE Yes
_m_b_l_e_n() EILSEQ Yes
_m_b_s_t_o_w_c_s() EILSEQ Yes
_m_b_t_o_w_c() EILSEQ Yes
_m_o_d_f() EDOM Yes
ERANGE Yes
_o_p_e_n() EINVAL Yes
ETXTBSY Yes
_o_p_e_n_d_i_r() EMFILE Yes
ENFILE Yes
_p_a_t_h_c_o_n_f() EACCES Yes
EINVAL Yes
ENAMETOOLONG Yes
ENOENT Yes
ENOTDIR Yes
_p_o_w() EDOM Yes
ERANGE Yes
_p_u_t_e_n_v() ENOMEM Yes
_r_e_a_d() ENXIO Yes
_r_e_a_d_d_i_r() EBADF Yes
_r_e_n_a_m_e() ETXTBSY Yes
_s_e_t_v_b_u_f() EBADF No
_s_i_g_a_c_t_i_o_n() EINVAL Yes
_s_i_g_a_d_d_s_e_t() EINVAL No
_s_i_g_d_e_l_s_e_t() EINVAL No
_s_i_g_i_s_m_e_m_b_e_r() EINVAL No
_s_i_g_n_a_l() EINVAL Yes
X/Open Conformance Statement Questionnaire 47
_X_P_G_4 _I_n_t_e_r_n_a_t_i_o_n_a_l_i_s_e_d _S_y_s_t_e_m _C_a_l_l_s _a_n_d _L_i_b_r_a_r_i_e_s
Function Error Detected
______________________________________________
_s_i_n() EDOM Yes
ERANGE Yes
_s_i_n_h() EDOM Yes
ERANGE Yes
_s_q_r_t() EDOM Yes
_s_t_r_c_o_l_l() EINVAL No
_s_t_r_e_r_r_o_r() EINVAL No
_s_t_r_x_f_r_m() EINVAL No
_t_a_n() EDOM Yes
ERANGE Yes
_t_a_n_h() EDOM Yes
ERANGE Yes
_t_c_d_r_a_i_n() EIO Yes
_t_c_f_l_u_s_h() EIO Yes
_t_c_s_e_n_d_b_r_e_a_k() EIO Yes
_t_c_s_e_t_a_t_t_r() EIO Yes
_t_m_p_f_i_l_e() EMFILE Yes
ENOMEM Yes
_t_t_y_n_a_m_e() EBADF Yes
ENOTTY Yes
_u_n_g_e_t_w_c() EILSEQ Yes
_u_n_l_i_n_k() ETXTBSY Yes
_w_c_s_c_o_l_l() EINVAL No
_w_c_s_t_o_m_b_s() EILSEQ Yes
_w_c_s_x_f_r_m() EINVAL No
_w_r_i_t_e() ENXIO Yes
_y_0() EDOM Yes
ERANGE Yes
_y_1() EDOM Yes
ERANGE Yes
_y_n() EDOM Yes
ERANGE Yes
Rationale:
48 X/Open Conformance Statement Questionnaire
_X_P_G_4 _I_n_t_e_r_n_a_t_i_o_n_a_l_i_s_e_d _S_y_s_t_e_m _C_a_l_l_s _a_n_d _L_i_b_r_a_r_i_e_s
Each of the above error conditions is marked as
optional in System Interfaces and Headers, Issue 4 and
an implementation may return this error in the
cirumstances specified or may not provide the error
indication.
Reference:
X/Open CAE Specification, System Interfaces and
Headers, Issue 4, Section 2.3, Error Numbers.
X/Open Conformance Statement Questionnaire 49
_X_P_G_4 _I_n_t_e_r_n_a_t_i_o_n_a_l_i_s_e_d _S_y_s_t_e_m _C_a_l_l_s _a_n_d _L_i_b_r_a_r_i_e_s
5.1.5 MMMMaaaatttthhhheeeemmmmaaaattttiiiiccccaaaallll IIIInnnntttteeeerrrrffffaaaacccceeeessss
Question 9: What format of floating-point numbers is
supported by this implementation?
Response:
IEEE floating point format.
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.
Reference:
X/Open CAE Specification, System Interfaces and
Headers, Issue 4, Section 1.6, Relationship to Formal
Standards.
5.1.6 DDDDaaaattttaaaa EEEEnnnnccccrrrryyyyppppttttiiiioooonnnn
Question 10: Are the optional data encryption interfaces
provided?
Response:
Function Provided
____________________
_c_r_y_p_t() Yes
_e_n_c_r_y_p_t() No
_s_e_t_k_e_y() No
The U.S. Department of Defense does not allow
"munitions" such as decryption routines to be exported
from the U.S. Therefore, encryption functionality is
available from _e_n_c_r_y_p_t() and _s_e_t_k_e_y(), but not
decryption functionality.
U.S. domestic customers may obtain fully capable copies
of these routines through their customer support
contract.
50 X/Open Conformance Statement Questionnaire
_X_P_G_4 _I_n_t_e_r_n_a_t_i_o_n_a_l_i_s_e_d _S_y_s_t_e_m _C_a_l_l_s _a_n_d _L_i_b_r_a_r_i_e_s
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.
It is also possible that the implementation of the
_e_n_c_r_y_p_t() function may be affected by export
restrictions, in which case, the restrictions should be
documented here.
For example, historical implementations have supplied
all three of these routines outside the U.S.A., but due
to export restrictions on the decoding algorithm, a
dummy version of _e_n_c_r_y_p_t() is provided that does
encoding but no decoding.
Reference:
X/Open CAE Specification, System Interfaces and
Headers, Issue 4, Section 1.2, Conformance.
5.2 PPPPrrrroooocccceeeessssssss HHHHaaaannnnddddlllliiiinnnngggg
5.2.1 PPPPrrrroooocccceeeessssssss GGGGeeeennnneeeerrrraaaattttiiiioooonnnn
Question 11: Which file types (regular, directory, FIFO,
special, and so on) are considered to be executable?
Response:
Regular.
Rationale:
The [EACCES] error associated with _e_x_e_c 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.
Reference:
X/Open CAE Specification, System Interfaces and
Headers, Issue 4, Chapter 3, Functions, _e_x_e_c.
X/Open Conformance Statement Questionnaire 51
_X_P_G_4 _I_n_t_e_r_n_a_t_i_o_n_a_l_i_s_e_d _S_y_s_t_e_m _C_a_l_l_s _a_n_d _L_i_b_r_a_r_i_e_s
5.3 FFFFiiiilllleeee HHHHaaaannnnddddlllliiiinnnngggg
5.3.1 AAAAcccccccceeeessssssss CCCCoooonnnnttttrrrroooollll
Question 12: What file access control mechanisms does the
implementation provide?
Response:
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. This has the
characteristics of an "additional file access control
mechanism". For general information, see the _a_c_l(5)
entry in the HP-UX Reference Manual.
Rationale:
System Interfaces and Headers, Issue 4 notes that
implementations may provide _a_d_d_i_t_i_o_n_a_l or _a_l_t_e_r_n_a_t_e
file access control mechanisms, or both.
Reference:
X/Open CAE Specification, System Interface Definitions,
Issue 4, Chapter 2, Glossary, file access permissions.
5.3.2 FFFFiiiilllleeeessss aaaannnndddd DDDDiiiirrrreeeeccccttttoooorrrriiiieeeessss
Question 13: Are any additional or alternate file access
control mechanisms implemented that could cause _f_s_t_a_t() or
_s_t_a_t() to fail?
Response:
No.
Rationale:
System Interfaces and Headers, Issue 4 notes that there
could be an interaction between additional and
alternate access controls and the success of _f_s_t_a_t()
and _s_t_a_t(). 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.
52 X/Open Conformance Statement Questionnaire
_X_P_G_4 _I_n_t_e_r_n_a_t_i_o_n_a_l_i_s_e_d _S_y_s_t_e_m _C_a_l_l_s _a_n_d _L_i_b_r_a_r_i_e_s
Reference:
X/Open CAE Specification, System Interfaces and
Headers, Issue 4, Chapter 3, Functions, _f_s_t_a_t() and
_s_t_a_t().
X/Open Conformance Statement Questionnaire 53
_X_P_G_4 _I_n_t_e_r_n_a_t_i_o_n_a_l_i_s_e_d _S_y_s_t_e_m _C_a_l_l_s _a_n_d _L_i_b_r_a_r_i_e_s
5.3.3 FFFFoooorrrrmmmmaaaattttttttiiiinnnngggg IIIInnnntttteeeerrrrffffaaaacccceeeessss
Question 14: Does the _p_r_i_n_t_f() function produce character
string representations for Infinity and NaN to represent the
respective values?
Response:
Yes. It generates the following strings for the indicated values:
Value String
____________________
+Infinity ++.000000
-Infinity ---.000000
NaN ?.000000
Rationale:
This behaviour is often provided on systems with
mathematical functions that produce these results.
Reference:
X/Open CAE Specification, System Interfaces and
Headers, Issue 4, Chapter 3, Functions, _f_p_r_i_n_t_f().
5.4 IIIInnnntttteeeerrrrnnnnaaaattttiiiioooonnnnaaaalllliiiisssseeeedddd SSSSyyyysssstttteeeemmmm IIIInnnntttteeeerrrrffffaaaacccceeeessss
5.4.1 CCCCooooddddeeeedddd CCCChhhhaaaarrrraaaacccctttteeeerrrr SSSSeeeettttssss
Question 15: What coded character sets are supported by the
implementation?
Response:
ISO 8859-1:1987 is supported, and others can be
selected by users as their internal coded character set
on a per-session basis. However, as not all of them
contain the portable character set, HP does not claim
"support" for these as XPG4 coded character sets.
Rationale:
System Interface Definitions, Issue 4 states that
conforming implementations support one or more coded
character sets, and that each of these includes the
portable character set.
Reference:
54 X/Open Conformance Statement Questionnaire
_X_P_G_4 _I_n_t_e_r_n_a_t_i_o_n_a_l_i_s_e_d _S_y_s_t_e_m _C_a_l_l_s _a_n_d _L_i_b_r_a_r_i_e_s
X/Open CAE Specification, System Interface Definitions,
Issue 4, Chapter 4, Character Set.
Question 16: What is the implementation’s underlying
internal codeset?
Response:
Per user-customer selectable option, each user may
configure his/her login session to use a selected
codeset. ISO 8859-1:1987 is one such codeset.
Rationale:
It is useful to be aware of the underlying codeset of
the implementation.
Reference:
X/Open CAE Specification, System Interface Definitions,
Issue 4, Chapter 4, Character Set.
X/Open Conformance Statement Questionnaire 55
—