HPUX man pages für Kapitel 5 HPUX man pages für Kapitel 5
OVwRegIntro - introduction to OpenView Windows registration files
UIL - The user interface language file format
X_Open - Pointer manual entry for X/Open XPG3 Conformance Statements
X_Open_300 : OPEN MAX Max number of files open in a process 60 1024 PASS MAX Max significant characters in a 8 8 password PATH_MAX Max characters in a pathname 1023 1023 PIPE_BUF Max bytes in an atomic write to a pipe 8192 8192 NGROUPS MAX Max number of supplementary group IDs 20 20 TMP MAX Max number of unique temporary file 17576 17576 names Options: Specify a minimum and maximum limit for each limit value. The minimum limit should be the result of evaluating the associated macro in <limits.h>. The maximum limit should be the largest value that is returned from sysconf() or pathconf(). 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 _POSIX_ value. A specific 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 _POSIX_ value provides a known lower bound for the range of possible values. Reference XPG3 Volume 2 Page 538 - <limits.h>. Question 4: What are the values associated with the following constants specified in the <limits.h> header file? Answer: Macro Name Meaning Value ______________________________________________________________ CHAR_BIT Number of bits in a char 8 LONG_BIT Number of bits in a long 32 WORD_BIT Number of bits in a word 32 DBL_DIG Digits of precision of a double 15 DBL_MAX Maximum decimal value of a double 1.79... E+308 FLT_DIG Digits of precision of a float 6 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 - <limits.h>. Page 2.1.4 X/Open Conformance Statement XCS-QUE-3.2 Questionnaire 2.1.4 Error Conditions Question 5: Which of the following optional errors listed in the XPG are detected in the circumstances specified? Answer: Function Error Detected ________________________________________ access() EINVAL- Yes ETXTBSY Yes atof() ERANGE Yes atoi() ERANGE Yes atol() ERANGE Yes cfsetispeed() EINVAL Yes cfsetospeed() EINVAL Yes chmod() EINVAL Yes chown() EINVAL- Yes closedir() EBADF- Yes exec ENOMEM- Yes ETXTBSY Yes fcntl() EDEADLK- Yes fdopen() EBADF No EINVAL Yes feof() EBADF No ferror() EBADF No fileno() EBADF No fopen() EINVAL Yes ETXTBSY Yes freopen() EINVAL Yes ETXTBSY Yes fork() ENOMEM Yes fseek() EINVAL Yes ftw() EINVAL Yes getcwd() EACCES- Yes isatty() EBADF Yes ENOTTY Yes open() EINVAL Yes Page 2.1.5 X/Open Conformance Statement XCS-QUE-3.2 Questionnaire Function Error Detected ________________________________________ ETXTBSY Yes opendir() EMFILE- Yes ENFILE- Yes pathconf() EACCES- Yes EINVAL- Yes ENAMETOOLONG- Yes ENOENT- Yes ENOTDIR- Yes fpathconf() EBADF- Yes EINVAL- Yes printf() EINVAL No readdir() EBADF- Yes rename() ETXTBSY Yes scanf() EINVAL No setvbuf() EBADF No sigaddset() EINVAL- Yes sigdelset() EINVAL- Yes sigismember() EINVAL- Yes strcoll() EINVAL No strerror() EINVAL No strtol() EINVAL Yes ERANGE Yes strxfrm() EINVAL No 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 sigaddset(), sigdelset() and sigismember() 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 Mathematical Interfaces Question 6: What format of floating point numbers are supported by this implementation? Answer: 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. Question 7: Is long double form supported and what precision is associated with this form? Answer: 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() 2.1.6 Data Encryption Question 8: Are the optional data encryption interfaces provided? Answer: 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 Page 2.1.8 X/Open Conformance Statement XCS-QUE-3.2 Questionnaire Section 2.2: Process Handling 2.2.1 Process Generation Question 9: Which file types (regular, directory, FIFO special etc.) are considered to be executable? Answer: Regular Options: A list of the types of file that are considered to be executable. Rationale The EACCES error associated with exec 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 2.2.2 Process Termination Question 10: Is the SIGCHLD signal sent to the parent process when a child exits? Answer: 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 Process Environment Question 11: Is the setpgid() interface provided? Answer: 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 Section 2.3: File Handling 2.3.1 Access Control Question 12: What file access control mechanisms does the implementation provide? Answer: 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. Page 2.3.1 X/Open Conformance Statement XCS-QUE-3.2 Questionnaire 2.3.2 Files and Directories Question 13: Are any extended security controls implemented that could cause fstat() or stat() to fail? Answer: No Rationale The XPG notes that there could be an interaction between extended security controls and the success of fstat() and stat(). 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() 2.3.3 Formatting Interfaces Question 14: Is the L modifier to printf() and scanf() supported on this implementation? Answer: 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() Question 15: Does the printf() function produce character string representations for Infinity and NaN to represent the respective special double precision values?" Page 2.3.2 X/Open Conformance Statement XCS-QUE-3.2 Questionnaire Answer: 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 Section 2.4: General Terminal Interface 2.4.1 Interfaces Supported Question 16: Are the following terminal control interfaces provided? tcgetpgrp() tcsetpgrp() Answer: Yes Rationale These interfaces are mandatory for implementations that support job control. Implementations that do not support job control, may either always return the error indication [ENOSYS] or may provide the interface with the behaviour specified for an implementation that supports job control. This later case is useful for implementations which support only part of the job control specifications. Reference XPG3 Volume 2 Page 471 - tcgetpgrp XPG3 Volume 2 Page 475 - tcsetpgrp Page 2.4.1 X/Open Conformance Statement XCS-QUE-3.2 Questionnaire Section 2.5: Internationalised System Interfaces 2.5.1 Codesets Question 17: Does the implementation support the ISO 8859- 1:1987 codeset for data transmission? Answer: 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 Question 18: Does the implementation use the ISO 8859-1:1987 as its internal codeset? Answer: 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 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 Page 2.5.1 X/Open Conformance Statement XCS-QUE-3.2 Questionnaire 2.5.2 Regular Expression Interfaces Question 19: What form of regular expression syntax is supported by the regexp() interface? Answer: Simple Internationalised Rationale The regexp() 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 Chapter 3: Commands and Utilities Product Identification Product Identification HP-UX Version/Release No. 8.0x for Series 300/400 If you do not supply this component yourself, please identify below the supplier you reference. Supplied by HP. Conformance Reference Indicator of Compliance None Environment Specification 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). Conformance Expectations 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). Page 3.1 X/Open Conformance Statement XCS-QUE-3.2 Questionnaire Section 3.1: Basic Utilities 3.1.1 Supported Commands Question 1: Which of the basic utilities (non-development utilities) defined in the XPG are not provided with the implementation? Answer: 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 mailx and newgrp commands are not provided. Reference XPG3 Volume 1 Page 1 - Introduction 3.1.2 Command Behaviour Question 2: In what ways do the commands provided by the implementation behave differently from the specifications contained in the XPG? Answer: 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 Section 3.2: Development Utilities 3.2.1 Supported Commands Question 3: Which of the development utilities defined in the XPG are not provided with the implementation? Answer: 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 (DEVELOPMENT) 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 3.2.2 Command Behaviour Question 4: In what ways do the development utilities provided by the implementation behave differently from the specifications contained in the XPG? Answer: 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 nm: the -3 -f -V and -x options are not supported. the functionality of -e is provided by -g the functionality of -f and -x are the defaults. 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 Section 3.3: Internationalisation Option 3.3.1 Commands and Utilities Question 5: Is an internationalised environment, reflecting changes in the locale setting as described in XPG Volume 1 - XSI Commands and Utilities, supported?" Answer: 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 ______________________________________________________________________________________ ar LC_TIME affects date format Yes 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 comm LC_COLLATE affects sorting sequence Yes cp,ln,mv LANG affects yes string Yes cpio LC_COLLATE, LC_CTYPE affect filename pattern matching Yes LC_TIME affects date format Yes date LC_TIME affects date formatting options Yes ed,red LC_COLLATE, LC_CTYPE affect regular expression matching Yes LC_CTYPE is used to determine whether characters are printable Yes egrep LC_COLLATE, LC_CTYPE affect regular expression matching Yes LC_CTYPE is used to determine character classification Yes (alphabetic, upper-case, lower case) expr LC_COLLATE, LC_CTYPE affect regular expression matching Yes LC_COLLATE affects the behaviour of relational operators Yes fgrep LC_CTYPE is used to determine character classification Yes (alphabetic, upper-case, lower case) Page 3.3.1 X/Open Conformance Statement XCS-QUE-3.2 Questionnaire Command Behaviour Specified in XPG3 Supported ______________________________________________________________________________________ find LANG affects yes string Yes LC_COLLATE, LC_CTYPE affect filename pattern matching Yes grep LC_COLLATE, LC_CTYPE affect regular expression matching Yes LC_CTYPE is used to determine character classification Yes (alphabetic, upper-case, lower case) join LC_COLLATE affects sorting sequence Yes lpstat LC_TIME affects date format Yes 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 mail LC_TIME affects date format Yes mailx LC_COLLATE, LC_CTYPE affect filename pattern matching Yes LC_TIME affects date format Yes pg LC_COLLATE, LC_CTYPE affect filename pattern matching Yes pr LC_TIME affects date format Yes LC_CTYPE is used to determine whether a character is printable Yes ps LC_TIME affects date format Yes rm,rmdir LANG affects yes string Yes sed LC_COLLATE, LC_CTYPE affect regular expression matching Yes LC_CTYPE is used to determine whether a character is printable Yes sh LC_COLLATE, LC_CTYPE affect filename pattern matching Yes LC_CTYPE is used to determine whether a character is alphabetic Yes 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 tar LC_TIME affects date format Yes LANG affects yes string Yes tr LC_COLLATE, LC_CTYPE affect bracketed expressions Yes LC_CTYPE affects the definition of the character universe Yes uniq LC_COLLATE affects sorting sequence Yes uucp LC_TIME affects date format Yes uustat LC_TIME affects date format Yes wc LC_CTYPE is used to determine white-space characters Yes who LC_TIME affects date format Yes yacc LC_CTYPE is used to determine character classification Yes 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. 3.3.2 Regular Expressions in Commands Question 6: Which form of regular expression syntax is supported by those commands which use regular expressions? Answer: Command Regular Expression Syntax Supported _____________________________________________ awk Extended Internationalised csplit Simple Internationalised ed Simple Internationalised egrep Extended Internationalised ex Simple Internationalised expr Simple Internationalised grep Simple Internationalised lex Extended pg Simple Internationalised sdb Not provided. sed Simple Internationalised vi Simple Internationalised Note: An XPG3 conforming system which claims support for internationalised commands should provide the regular expression syntax marked in bold in the above table. Where neither options are marked in bold 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 sdb 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 Chapter 4: C Language Product Identification Product Identification ANSI C: B2371A Version/Release No. for 8.0x If you do not supply this component yourself, please identify below the supplier you reference. Supplied by HP. Conformance Reference Indicator of Compliance VSX Test Suite Release 3.204 Testing Agency Name Hewlett-Packard Company Address 3404 East Harmony Rd. Fort Collins, Co 80525-9599 USA Environment Specification 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). Temporary Waivers 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 Section 4.1: Implementation Limits Question 1: What limits does the implementation impose on the significant part of a identifier? Answer: External identifiers 255 characters 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 Page 4.1.1 X/Open Conformance Statement XCS-QUE-3.2 Questionnaire Section 4.2: General Question 2: What truncation rules are applied when a floating value is converted to an integral value? Answer: 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 Question 3: What truncation rules are applied when using the division operator and either of the operands is negative? Options: Truncation towards zero / Truncation away from zero Answer: 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
X_Open_800 : OPEN MAX Max number of files open in a process 60 1024 - PASS MAX Max significant characters in a 8 8 password PATH_MAX Max characters in a pathname 1023 1023 PIPE_BUF Max bytes in an atomic write to a pipe 8192 8192 NGROUPS MAX Max number of supplementary group IDs 20 20 TMP MAX Max number of unique temporary file 17576 17576 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 <limits.h>. The maximum limit should be the largest value that is returned from sysconf() or pathconf(). 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 _POSIX_ value. A specific 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 _POSIX_ value provides a known lower bound for the range of possible values. Reference XPG3 Volume 2 Page 538 - <limits.h>. Question 4: What are the values associated with the following constants specified in the <limits.h> header file? Answer: Macro Name Meaning Value ______________________________________________________________ CHAR_BIT Number of bits in a char 8 LONG_BIT Number of bits in a long 32 WORD_BIT Number of bits in a word 32 DBL_DIG Digits of precision of a double 15 DBL_MAX Maximum decimal value of a double 1.79... E+308 FLT_DIG Digits of precision of a float 6 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 - <limits.h>. Page 2.1.4 X/Open Conformance Statement XCS-QUE-3.2 Questionnaire 2.1.4 Error Conditions Question 5: Which of the following optional errors listed in the XPG are detected in the circumstances specified? Answer: Function Error Detected ________________________________________ access() EINVAL- Yes ETXTBSY Yes atof() ERANGE Yes atoi() ERANGE Yes atol() ERANGE Yes cfsetispeed() EINVAL Yes cfsetospeed() EINVAL Yes chmod() EINVAL Yes chown() EINVAL- Yes closedir() EBADF- Yes exec ENOMEM- Yes ETXTBSY Yes fcntl() EDEADLK- Yes fdopen() EBADF No EINVAL Yes feof() EBADF No ferror() EBADF No fileno() EBADF No fopen() EINVAL Yes ETXTBSY Yes freopen() EINVAL Yes ETXTBSY Yes fork() ENOMEM Yes fseek() EINVAL Yes ftw() EINVAL Yes getcwd() EACCES- Yes isatty() EBADF Yes ENOTTY Yes open() EINVAL Yes Page 2.1.5 X/Open Conformance Statement XCS-QUE-3.2 Questionnaire Function Error Detected ________________________________________ ETXTBSY Yes opendir() EMFILE- Yes ENFILE- Yes pathconf() EACCES- Yes EINVAL- Yes ENAMETOOLONG- Yes ENOENT- Yes ENOTDIR- Yes fpathconf() EBADF- Yes EINVAL- Yes printf() EINVAL No readdir() EBADF- Yes rename() ETXTBSY Yes scanf() EINVAL No setvbuf() EBADF No sigaddset() EINVAL- Yes sigdelset() EINVAL- Yes sigismember() EINVAL- Yes strcoll() EINVAL No strerror() EINVAL No strtol() EINVAL Yes ERANGE Yes strxfrm() EINVAL No 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 sigaddset(), sigdelset() and sigismember() 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 Mathematical Interfaces Question 6: What format of floating point numbers are supported by this implementation? Answer: 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. Question 7: Is long double form supported and what precision is associated with this form? Answer: 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() 2.1.6 Data Encryption Question 8: Are the optional data encryption interfaces provided? Answer: 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 Page 2.1.8 X/Open Conformance Statement XCS-QUE-3.2 Questionnaire Section 2.2: Process Handling 2.2.1 Process Generation Question 9: Which file types (regular, directory, FIFO special etc.) are considered to be executable? Answer: Regular Options: A list of the types of file that are considered to be executable. Rationale The EACCES error associated with exec 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 2.2.2 Process Termination Question 10: Is the SIGCHLD signal sent to the parent process when a child exits? Answer: 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 Process Environment Question 11: Is the setpgid() interface provided? Answer: 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 Section 2.3: File Handling 2.3.1 Access Control Question 12: What file access control mechanisms does the implementation provide? Answer: 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. Page 2.3.1 X/Open Conformance Statement XCS-QUE-3.2 Questionnaire 2.3.2 Files and Directories Question 13: Are any extended security controls implemented that could cause fstat() or stat() to fail? Answer: No Rationale The XPG notes that there could be an interaction between extended security controls and the success of fstat() and stat(). 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() 2.3.3 Formatting Interfaces Question 14: Is the L modifier to printf() and scanf() supported on this implementation? Answer: 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() Question 15: Does the printf() function produce character string representations for Infinity and NaN to represent the respective special double precision values?" Page 2.3.2 X/Open Conformance Statement XCS-QUE-3.2 Questionnaire Answer: 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 Section 2.4: General Terminal Interface 2.4.1 Interfaces Supported Question 16: Are the following terminal control interfaces provided? tcgetpgrp() tcsetpgrp() Answer: Yes Rationale These interfaces are mandatory for implementations that support job control. Implementations that do not support job control, may either always return the error indication [ENOSYS] or may provide the interface with the behaviour specified for an implementation that supports job control. This later case is useful for implementations which support only part of the job control specifications. Reference XPG3 Volume 2 Page 471 - tcgetpgrp XPG3 Volume 2 Page 475 - tcsetpgrp Page 2.4.1 X/Open Conformance Statement XCS-QUE-3.2 Questionnaire Section 2.5: Internationalised System Interfaces 2.5.1 Codesets Question 17: Does the implementation support the ISO 8859- 1:1987 codeset for data transmission? Answer: 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 Question 18: Does the implementation use the ISO 8859-1:1987 as its internal codeset? Answer: 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 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 Page 2.5.1 X/Open Conformance Statement XCS-QUE-3.2 Questionnaire 2.5.2 Regular Expression Interfaces Question 19: What form of regular expression syntax is supported by the regexp() interface? Answer: Simple Internationalised Rationale The regexp() 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 Chapter 3: Commands and Utilities Product Identification Product Identification HP-UX 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. Conformance Reference Indicator of Compliance None Environment Specification 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). Conformance Expectations 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). Page 3.1 X/Open Conformance Statement XCS-QUE-3.2 Questionnaire Section 3.1: Basic Utilities 3.1.1 Supported Commands Question 1: Which of the basic utilities (non-development utilities) defined in the XPG are not provided with the implementation? Answer: 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 mailx and newgrp commands are not provided. Reference XPG3 Volume 1 Page 1 - Introduction 3.1.2 Command Behaviour Question 2: In what ways do the commands provided by the implementation behave differently from the specifications contained in the XPG? Answer: 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 Section 3.2: Development Utilities 3.2.1 Supported Commands Question 3: Which of the development utilities defined in the XPG are not provided with the implementation? Answer: 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 (DEVELOPMENT) 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 3.2.2 Command Behaviour Question 4: In what ways do the development utilities provided by the implementation behave differently from the specifications contained in the XPG? Answer: 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 Section 3.3: Internationalisation Option 3.3.1 Commands and Utilities Question 5: Is an internationalised environment, reflecting changes in the locale setting as described in XPG Volume 1 - XSI Commands and Utilities, supported?" Answer: 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 ______________________________________________________________________________________ ar LC_TIME affects date format Yes 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 comm LC_COLLATE affects sorting sequence Yes cp,ln,mv LANG affects yes string Yes cpio LC_COLLATE, LC_CTYPE affect filename pattern matching Yes LC_TIME affects date format Yes date LC_TIME affects date formatting options Yes ed,red LC_COLLATE, LC_CTYPE affect regular expression matching Yes LC_CTYPE is used to determine whether characters are printable Yes egrep LC_COLLATE, LC_CTYPE affect regular expression matching Yes LC_CTYPE is used to determine character classification Yes (alphabetic, upper-case, lower case) expr LC_COLLATE, LC_CTYPE affect regular expression matching Yes LC_COLLATE affects the behaviour of relational operators Yes fgrep LC_CTYPE is used to determine character classification Yes (alphabetic, upper-case, lower case) Page 3.3.1 X/Open Conformance Statement XCS-QUE-3.2 Questionnaire Command Behaviour Specified in XPG3 Supported ______________________________________________________________________________________ find LANG affects yes string Yes LC_COLLATE, LC_CTYPE affect filename pattern matching Yes grep LC_COLLATE, LC_CTYPE affect regular expression matching Yes LC_CTYPE is used to determine character classification Yes (alphabetic, upper-case, lower case) join LC_COLLATE affects sorting sequence Yes lpstat LC_TIME affects date format Yes 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 mail LC_TIME affects date format Yes mailx LC_COLLATE, LC_CTYPE affect filename pattern matching Yes LC_TIME affects date format Yes pg LC_COLLATE, LC_CTYPE affect filename pattern matching Yes pr LC_TIME affects date format Yes LC_CTYPE is used to determine whether a character is printable Yes ps LC_TIME affects date format Yes rm,rmdir LANG affects yes string Yes sed LC_COLLATE, LC_CTYPE affect regular expression matching Yes LC_CTYPE is used to determine whether a character is printable Yes sh LC_COLLATE, LC_CTYPE affect filename pattern matching Yes LC_CTYPE is used to determine whether a character is alphabetic Yes 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 tar LC_TIME affects date format Yes LANG affects yes string Yes tr LC_COLLATE, LC_CTYPE affect bracketed expressions Yes LC_CTYPE affects the definition of the character universe Yes uniq LC_COLLATE affects sorting sequence Yes uucp LC_TIME affects date format Yes uustat LC_TIME affects date format Yes wc LC_CTYPE is used to determine white-space characters Yes who LC_TIME affects date format Yes yacc LC_CTYPE is used to determine character classification Yes 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. 3.3.2 Regular Expressions in Commands Question 6: Which form of regular expression syntax is supported by those commands which use regular expressions? Answer: Command Regular Expression Syntax Supported _____________________________________________ awk Extended Internationalised csplit Simple Internationalised ed Simple Internationalised egrep Extended Internationalised ex Simple Internationalised expr Simple Internationalised grep Simple Internationalised lex Extended pg Simple Internationalised sdb Not provided. sed Simple Internationalised vi Simple Internationalised Note: An XPG3 conforming system which claims support for internationalised commands should provide the regular expression syntax marked in bold in the above table. Where neither options are marked in bold 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 sdb 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 Chapter 4: C Language Product Identification Product Identification B2412A (600/700/800) or B2413A (700 Only) Version/Release No. for 8.0x If you do not supply this component yourself, please identify below the supplier you reference. Supplied by HP. Conformance Reference Indicator of Compliance VSX Test Suite Release 3.204 Testing Agency Name Hewlett-Packard Company Address 3404 East Harmony Rd. Fort Collins, Co 80525-9599 USA Environment Specification 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). Temporary Waivers 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 Section 4.1: Implementation Limits Question 1: What limits does the implementation impose on the significant part of a identifier? Answer: External identifiers 255 characters 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 Page 4.1.1 X/Open Conformance Statement XCS-QUE-3.2 Questionnaire Section 4.2: General Question 2: What truncation rules are applied when a floating value is converted to an integral value? Answer: 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 Question 3: What truncation rules are applied when using the division operator and either of the operands is negative? Options: Truncation towards zero / Truncation away from zero Answer: 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
acl - introduction to access control lists
active.times - list of active Usenet newsgroups
ascii - map of ASCII character set
Audio - audio application interface and demo program Remarks: Beginning with Release 8.07, the HP-UX operating system includes audio software comprised of an Audio Application Program Interface (AAPI) and some example programs. The audio software package contains client and server components, which can run on separate systems. Audio data may reside on still a third system. In all cases, however, the server must run on a Series 700 system equipped with audio hardware (to determine the presence of audio hardware, check the hardware manual provided with the system or look for audio jacks on the back of the computer enclosure).
audit - introduction to HP-UX Auditing System
blinclink - SoftBench Incremental Linker
context - process context
control.ctl - specify handling of Usenet control messages
dirent.h - format of directory streams and directory entries
distrib.pats - default values for Usenet Distribution header
dld.sl - dynamic loader
encapsulate - SoftBench Encapsulator
environ - user environment
expire.ctl - control file for Usenet article expiration
fcntl - file control options
ftpaccess - ftpd configuration file
ftpconversions - ftpd conversions database
ftphosts - ftpd individual user host access file
groff_font - format of groff device and font description files
groff_out - groff intermediate output format
hier - file system hierarchy
history - record of current and recently expired Usenet articles
hostname - host name resolution description
hosts.nntp.nolimit - list of hosts that feed NNTP news
hpnls - HP Native Language Support (NLS) Model
inn.conf - configuration data for InterNetNews programs
innwatch.ctl - control Usenet supervision by innwatch
intro - introduction to miscellany
ioctl - generic device control commands
lang - description of supported languages
langinfo - language information constants
limits - implementation-specific constants
man - macros for formatting entries in this manual
manuals - Current list of HP-UX documentation
math - math functions and constants
MIFF - ImageMagick's file format for raster images. MIFF is an acronym for Magick Image File Format.
mknod.h - macros for handling device numbers
mm - the MM macro package for formatting documents
moderators - mail addresses for moderated Usenet newsgroups
ndir.h - format of HP-UX directory streams
newsfeeds - determine where Usenet articles get sent
newslog - description of Usenet log files
nlio - Native Language I/O (NLIO) Subsystem
nnrp.access - access file for on-campus NNTP sites
nntpsend.ctl - list of sites to feed via nntpsend
overview.fmt - format of news overview database
passwd.nntp - passwords for connecting to remote NNTP servers
pbm - portable bitmap file format
pgm - portable graymap file format
pnm - portable anymap file format
portnls - MPE Native Language Support routines
ppm - portable pixmap file format
Quantize - ImageMagick's color reduction algorithm.
quota - disk quotas Remarks The HP-UX default is to allow chown(2). This can interfere with the disk quota mechanism. See the WARNINGS section, below.
rcsintro - description of RCS commands
regexp - regular expression and pattern matching notation definitions
rplay.conf - remote play sound database
rplay.hosts - remote play host authentication database
rplay.servers - remote play servers database
signal - Description of signals
smail/* - configuration files used by smail
softbench - The SoftBench Software Development Environment
softinit - Invocation Specifications for the SoftBench Software Development Environment
stat.h - file-specific information
stdarg.h - macros for handling variable argument lists
stdsyms - description of HP-UX header file organization
suffix - file-name suffix conventions
term - conventional names for terminals
types - primitive system data types
unistd.h - standard structures and symbolic constants
values - machine-dependent values
varargs - handle variable argument list
variables - variables format for snmpget(1), snmpwalk(1), and snmpnext(1)
X_Open - Pointer manual entry for X/Open XPG3 Conformance Statements
x_open_300 : OPEN MAX Max number of files open in a process 60 1024 PASS MAX Max significant characters in a 8 8 password PATH_MAX Max characters in a pathname 1023 1023 PIPE_BUF Max bytes in an atomic write to a pipe 8192 8192 NGROUPS MAX Max number of supplementary group IDs 20 20 TMP MAX Max number of unique temporary file 17576 17576 names Options: Specify a minimum and maximum limit for each limit value. The minimum limit should be the result of evaluating the associated macro in <limits.h>. The maximum limit should be the largest value that is returned from sysconf() or pathconf(). 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 _POSIX_ value. A specific 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 _POSIX_ value provides a known lower bound for the range of possible values. Reference XPG3 Volume 2 Page 538 - <limits.h>. Question 4: What are the values associated with the following constants specified in the <limits.h> header file? Answer: Macro Name Meaning Value ______________________________________________________________ CHAR_BIT Number of bits in a char 8 LONG_BIT Number of bits in a long 32 WORD_BIT Number of bits in a word 32 DBL_DIG Digits of precision of a double 15 DBL_MAX Maximum decimal value of a double 1.79... E+308 FLT_DIG Digits of precision of a float 6 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 - <limits.h>. Page 2.1.4 X/Open Conformance Statement XCS-QUE-3.2 Questionnaire 2.1.4 Error Conditions Question 5: Which of the following optional errors listed in the XPG are detected in the circumstances specified? Answer: Function Error Detected ________________________________________ access() EINVAL- Yes ETXTBSY Yes atof() ERANGE Yes atoi() ERANGE Yes atol() ERANGE Yes cfsetispeed() EINVAL Yes cfsetospeed() EINVAL Yes chmod() EINVAL Yes chown() EINVAL- Yes closedir() EBADF- Yes exec ENOMEM- Yes ETXTBSY Yes fcntl() EDEADLK- Yes fdopen() EBADF No EINVAL Yes feof() EBADF No ferror() EBADF No fileno() EBADF No fopen() EINVAL Yes ETXTBSY Yes freopen() EINVAL Yes ETXTBSY Yes fork() ENOMEM Yes fseek() EINVAL Yes ftw() EINVAL Yes getcwd() EACCES- Yes isatty() EBADF Yes ENOTTY Yes open() EINVAL Yes Page 2.1.5 X/Open Conformance Statement XCS-QUE-3.2 Questionnaire Function Error Detected ________________________________________ ETXTBSY Yes opendir() EMFILE- Yes ENFILE- Yes pathconf() EACCES- Yes EINVAL- Yes ENAMETOOLONG- Yes ENOENT- Yes ENOTDIR- Yes fpathconf() EBADF- Yes EINVAL- Yes printf() EINVAL No readdir() EBADF- Yes rename() ETXTBSY Yes scanf() EINVAL No setvbuf() EBADF No sigaddset() EINVAL- Yes sigdelset() EINVAL- Yes sigismember() EINVAL- Yes strcoll() EINVAL No strerror() EINVAL No strtol() EINVAL Yes ERANGE Yes strxfrm() EINVAL No 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 sigaddset(), sigdelset() and sigismember() 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 Mathematical Interfaces Question 6: What format of floating point numbers are supported by this implementation? Answer: 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. Question 7: Is long double form supported and what precision is associated with this form? Answer: 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() 2.1.6 Data Encryption Question 8: Are the optional data encryption interfaces provided? Answer: 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 Page 2.1.8 X/Open Conformance Statement XCS-QUE-3.2 Questionnaire Section 2.2: Process Handling 2.2.1 Process Generation Question 9: Which file types (regular, directory, FIFO special etc.) are considered to be executable? Answer: Regular Options: A list of the types of file that are considered to be executable. Rationale The EACCES error associated with exec 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 2.2.2 Process Termination Question 10: Is the SIGCHLD signal sent to the parent process when a child exits? Answer: 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 Process Environment Question 11: Is the setpgid() interface provided? Answer: 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 Section 2.3: File Handling 2.3.1 Access Control Question 12: What file access control mechanisms does the implementation provide? Answer: 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. Page 2.3.1 X/Open Conformance Statement XCS-QUE-3.2 Questionnaire 2.3.2 Files and Directories Question 13: Are any extended security controls implemented that could cause fstat() or stat() to fail? Answer: No Rationale The XPG notes that there could be an interaction between extended security controls and the success of fstat() and stat(). 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() 2.3.3 Formatting Interfaces Question 14: Is the L modifier to printf() and scanf() supported on this implementation? Answer: 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() Question 15: Does the printf() function produce character string representations for Infinity and NaN to represent the respective special double precision values?" Page 2.3.2 X/Open Conformance Statement XCS-QUE-3.2 Questionnaire Answer: 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 Section 2.4: General Terminal Interface 2.4.1 Interfaces Supported Question 16: Are the following terminal control interfaces provided? tcgetpgrp() tcsetpgrp() Answer: Yes Rationale These interfaces are mandatory for implementations that support job control. Implementations that do not support job control, may either always return the error indication [ENOSYS] or may provide the interface with the behaviour specified for an implementation that supports job control. This later case is useful for implementations which support only part of the job control specifications. Reference XPG3 Volume 2 Page 471 - tcgetpgrp XPG3 Volume 2 Page 475 - tcsetpgrp Page 2.4.1 X/Open Conformance Statement XCS-QUE-3.2 Questionnaire Section 2.5: Internationalised System Interfaces 2.5.1 Codesets Question 17: Does the implementation support the ISO 8859- 1:1987 codeset for data transmission? Answer: 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 Question 18: Does the implementation use the ISO 8859-1:1987 as its internal codeset? Answer: 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 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 Page 2.5.1 X/Open Conformance Statement XCS-QUE-3.2 Questionnaire 2.5.2 Regular Expression Interfaces Question 19: What form of regular expression syntax is supported by the regexp() interface? Answer: Simple Internationalised Rationale The regexp() 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 Chapter 3: Commands and Utilities Product Identification Product Identification HP-UX Version/Release No. 8.0x for Series 300/400 If you do not supply this component yourself, please identify below the supplier you reference. Supplied by HP. Conformance Reference Indicator of Compliance None Environment Specification 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). Conformance Expectations 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). Page 3.1 X/Open Conformance Statement XCS-QUE-3.2 Questionnaire Section 3.1: Basic Utilities 3.1.1 Supported Commands Question 1: Which of the basic utilities (non-development utilities) defined in the XPG are not provided with the implementation? Answer: 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 mailx and newgrp commands are not provided. Reference XPG3 Volume 1 Page 1 - Introduction 3.1.2 Command Behaviour Question 2: In what ways do the commands provided by the implementation behave differently from the specifications contained in the XPG? Answer: 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 Section 3.2: Development Utilities 3.2.1 Supported Commands Question 3: Which of the development utilities defined in the XPG are not provided with the implementation? Answer: 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 (DEVELOPMENT) 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 3.2.2 Command Behaviour Question 4: In what ways do the development utilities provided by the implementation behave differently from the specifications contained in the XPG? Answer: 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 nm: the -3 -f -V and -x options are not supported. the functionality of -e is provided by -g the functionality of -f and -x are the defaults. 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 Section 3.3: Internationalisation Option 3.3.1 Commands and Utilities Question 5: Is an internationalised environment, reflecting changes in the locale setting as described in XPG Volume 1 - XSI Commands and Utilities, supported?" Answer: 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 ______________________________________________________________________________________ ar LC_TIME affects date format Yes 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 comm LC_COLLATE affects sorting sequence Yes cp,ln,mv LANG affects yes string Yes cpio LC_COLLATE, LC_CTYPE affect filename pattern matching Yes LC_TIME affects date format Yes date LC_TIME affects date formatting options Yes ed,red LC_COLLATE, LC_CTYPE affect regular expression matching Yes LC_CTYPE is used to determine whether characters are printable Yes egrep LC_COLLATE, LC_CTYPE affect regular expression matching Yes LC_CTYPE is used to determine character classification Yes (alphabetic, upper-case, lower case) expr LC_COLLATE, LC_CTYPE affect regular expression matching Yes LC_COLLATE affects the behaviour of relational operators Yes fgrep LC_CTYPE is used to determine character classification Yes (alphabetic, upper-case, lower case) Page 3.3.1 X/Open Conformance Statement XCS-QUE-3.2 Questionnaire Command Behaviour Specified in XPG3 Supported ______________________________________________________________________________________ find LANG affects yes string Yes LC_COLLATE, LC_CTYPE affect filename pattern matching Yes grep LC_COLLATE, LC_CTYPE affect regular expression matching Yes LC_CTYPE is used to determine character classification Yes (alphabetic, upper-case, lower case) join LC_COLLATE affects sorting sequence Yes lpstat LC_TIME affects date format Yes 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 mail LC_TIME affects date format Yes mailx LC_COLLATE, LC_CTYPE affect filename pattern matching Yes LC_TIME affects date format Yes pg LC_COLLATE, LC_CTYPE affect filename pattern matching Yes pr LC_TIME affects date format Yes LC_CTYPE is used to determine whether a character is printable Yes ps LC_TIME affects date format Yes rm,rmdir LANG affects yes string Yes sed LC_COLLATE, LC_CTYPE affect regular expression matching Yes LC_CTYPE is used to determine whether a character is printable Yes sh LC_COLLATE, LC_CTYPE affect filename pattern matching Yes LC_CTYPE is used to determine whether a character is alphabetic Yes 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 tar LC_TIME affects date format Yes LANG affects yes string Yes tr LC_COLLATE, LC_CTYPE affect bracketed expressions Yes LC_CTYPE affects the definition of the character universe Yes uniq LC_COLLATE affects sorting sequence Yes uucp LC_TIME affects date format Yes uustat LC_TIME affects date format Yes wc LC_CTYPE is used to determine white-space characters Yes who LC_TIME affects date format Yes yacc LC_CTYPE is used to determine character classification Yes 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. 3.3.2 Regular Expressions in Commands Question 6: Which form of regular expression syntax is supported by those commands which use regular expressions? Answer: Command Regular Expression Syntax Supported _____________________________________________ awk Extended Internationalised csplit Simple Internationalised ed Simple Internationalised egrep Extended Internationalised ex Simple Internationalised expr Simple Internationalised grep Simple Internationalised lex Extended pg Simple Internationalised sdb Not provided. sed Simple Internationalised vi Simple Internationalised Note: An XPG3 conforming system which claims support for internationalised commands should provide the regular expression syntax marked in bold in the above table. Where neither options are marked in bold 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 sdb 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 Chapter 4: C Language Product Identification Product Identification ANSI C: B2371A Version/Release No. for 8.0x If you do not supply this component yourself, please identify below the supplier you reference. Supplied by HP. Conformance Reference Indicator of Compliance VSX Test Suite Release 3.204 Testing Agency Name Hewlett-Packard Company Address 3404 East Harmony Rd. Fort Collins, Co 80525-9599 USA Environment Specification 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). Temporary Waivers 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 Section 4.1: Implementation Limits Question 1: What limits does the implementation impose on the significant part of a identifier? Answer: External identifiers 255 characters 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 Page 4.1.1 X/Open Conformance Statement XCS-QUE-3.2 Questionnaire Section 4.2: General Question 2: What truncation rules are applied when a floating value is converted to an integral value? Answer: 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 Question 3: What truncation rules are applied when using the division operator and either of the operands is negative? Options: Truncation towards zero / Truncation away from zero Answer: 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
x_open_800 : OPEN MAX Max number of files open in a process 60 1024 - PASS MAX Max significant characters in a 8 8 password PATH_MAX Max characters in a pathname 1023 1023 PIPE_BUF Max bytes in an atomic write to a pipe 8192 8192 NGROUPS MAX Max number of supplementary group IDs 20 20 TMP MAX Max number of unique temporary file 17576 17576 names