This form contains a series of questions that need to be answered. As you go about answering the questions, please keep the following things in mind:

• While it is not required that each question be answered at this time, all questions must have answers before the response is submitted to The Open Group for review and publication.
• Press the "Save" button at any time to save work in progress. Once the work has been saved, there is the option to continue editing if required.
• Many questions have instructions to assist in development of answers. They are marked with the indicator. Please look at the instructions carefully.
• Although HTML markup can be included in answers, this is not recommended apart from basic tags such as <p> and <br>, since incorrect markup could effect the format of other items in the document.
• Questions on this system should be addressed to the Conformance Statement manager at The Open Group.

Enter the name of the Organization that produced the implementation and the name of the author of the Conformance Statement.

1. Commands and Utilities v2

Product Information

Environment Specification

Answer the questions for each binary-compatible family. Alternately, provide the answers in the Appendix at the end of this document.

	Testing Environment	Binary-compatible Family	Portability Environment	Indicator of Compliance	Compliance Details
			Select from this list Internationalised System Calls and Libraries Internationalised System Calls and Libraries Extended Internationalised System Calls and Libraries Extended V2	Select from this list Test Report from Test Suite	Test Suite: Test Report:
			Select from this list Internationalised System Calls and Libraries Internationalised System Calls and Libraries Extended Internationalised System Calls and Libraries Extended V2	Select from this list Test Report from Test Suite	Test Suite: Test Report:
			Select from this list Internationalised System Calls and Libraries Internationalised System Calls and Libraries Extended Internationalised System Calls and Libraries Extended V2	Select from this list Test Report from Test Suite	Test Suite: Test Report:
			Select from this list Internationalised System Calls and Libraries Internationalised System Calls and Libraries Extended Internationalised System Calls and Libraries Extended V2	Select from this list Test Report from Test Suite	Test Suite: Test Report:
			Select from this list Internationalised System Calls and Libraries Internationalised System Calls and Libraries Extended Internationalised System Calls and Libraries Extended V2	Select from this list Test Report from Test Suite	Test Suite: Test Report:

Temporary Waivers

1.1 Feature Groups

Question 1: Which of the following feature groups are supported by the implementation?

Response

UNIX Extension

Yes   No

Conformance to this Product Standard does not require extensions to the cc and c89 commands identified by the UNIX Extension feature group to be supported. However, support of this extended functionality is required for conformance to the UNIX Product Standard.

Rationale

Support for the UNIX Extension is not required for conformance to this Product Standard.

Reference

Commands and Utilities V2 Product Standard Definition.

UNIX Product Standard Definition.

1.2 POSIX.2 Supported Features

Question 2: Which of the following options, specified in the <unistd.h> header, are available on the system?

Response

Macro Name	Meaning	Provided
_POSIX2_C_BIND	Implementation supports the C language binding option.	Yes   No
_POSIX2_C_DEV	Implementation supports the C language development utilities option.	Yes   No
_POSIX2_CHAR_TERM	Implementation supports at least one terminal type.	Yes   No
_POSIX2_FORT_DEV	Implementation supports the FORTRAN Development Utilities Option.	Yes   No
_POSIX2_FORT_RUN	Implementation supports the FORTRAN Run-time Utilities.	Yes   No
_POSIX2_LOCALEDEF	Implementation supports the creation of locales by the localedef utility.	Yes   No
_POSIX2_SW_DEV	Implementation supports the Software Developments Utilities Option.	Yes   No
_POSIX2_UPE	Implementation supports the User Portability Utilities Option.	Yes   No

Rationale

For an Commands and Utilities V2 conformant implementation, _POSIX2_C_BIND, _POSIX2_CHAR_TERM, _POSIX2_LOCALDEF and _POSIX2_UPE must be supported. The other constants identify optional functionality that an implementation may or may not choose to support.

Reference

CAE Specification, System Interfaces and Headers, Issue 4, Version 2, Chapter 4, Headers, <unistd.h>.

1.3 Development Utilities

1.3.1 Supported Commands

Question 3: Which of the Software development utilities are not provided with the implementation?

Response

All development utilities are provided. None of the development utilities are provided. All the development utilities except dis are provided.

Rationale

The development utilities are required to exist on designated DEVELOPMENT systems but may not be present on all XSI-conformant systems. The dis utility is defined as optional and need not be present even on systems that support the remainder of the development utilities.

Reference

CAE Specification, Commands and Utilities, Issue 4, Version 2, Section 1.3.1, Optional, and Section 1.3.2, Development.

1.4 FORTRAN Option

1.4.1 FORTRAN Utility

Question 4: Is the FORTRAN fort77 utility provided?

Response

Yes   No

Rationale

The fort77 utility is the command level interface to the FORTRAN compiler, which need not be provided.

Reference

CAE Specification, Commands and Utilities, Issue 4, Version 2, Section 1.3.3, FORTRAN.

1.5 Possibly Unsupportable Utilities and Options

Question 5: Which of the following utilities and utility options are not supported on the implementation?

Response

Utility	Option	Supported
ar	-s	Supported   Unsupported
cancel		Supported   Unsupported
cu		Supported   Unsupported
lp	-m	Supported   Unsupported
	-o	Supported   Unsupported
	-t	Supported   Unsupported
	-w	Supported   Unsupported
lpstat		Supported   Unsupported
sort	-z	Supported   Unsupported
tabs	+m	Supported   Unsupported
uucp		Supported   Unsupported
uulog		Supported   Unsupported
uuname		Supported   Unsupported
uupick		Supported   Unsupported
uustat		Supported   Unsupported
uuto		Supported   Unsupported
uux		Supported   Unsupported

Rationale

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.

Reference

CAE Specification, Commands and Utilities, Issue 4, Version 2, Section 1.7, Portability.

1.6 Specific Commands and Utilities

1.6.1 at

Question 6: How does the at command interpret a non-null SHELL environment variable?

Response

Uses the shell specified in the SHELL environment variable. Uses the login shell from the user database. Uses sh irrespective of the setting of SHELL.

Rationale

The interpretation of the SHELL environment variable can cause at to invoke different versions of the shell on some implementations.

Reference

CAE Specification, Commands and Utilities, Issue 4, Version 2, Chapter 3, Utilities, at, ENVIRONMENT VARIABLES, SHELL.

1.6.2 awk

Question 7: What is the limit on the number of open streams provided by awk?

Response

open streams.

Rationale

The number of open streams that are available to awk may differ between implementations, possibly depending on the number of streams that are available to a process ({FOPEN_MAX}).

Reference

CAE Specification, Commands and Utilities, Issue 4, Version 2, Chapter 3, Utilities, awk, Input/Output and General Functions, close(\|).

1.6.3 batch

Question 8: How does the batch command interpret a non-null SHELL environment variable?

Response

Uses the shell specified in the SHELL environment variable. Uses the login shell from the user database. Uses sh irrespective of the setting of SHELL.

Rationale

The interpretation of the SHELL environment variable can cause batch to invoke different versions of the shell on some implementations.

Reference

CAE Specification, Commands and Utilities, Issue 4, Version 2, Chapter 3, Utilities, batch, ENVIRONMENT VARIABLES, SHELL.

---

1.6.4 c89

Question 9: Which defined names are automatically provided by the compiler?

Response

Provide a list of macro names built into the compiler or a reference to the appropriate system documentation.

Rationale

The automatic provision of defined names by the compiler can cause these names to be unavailable in the name space for defined names.

Reference

CAE Specification, Commands and Utilities, Issue 4, Version 2, Chapter 3, Utilities, c89, OPTIONS, -D.

Question 10: When multiple input files are specified, where does c89 direct identification messages designating the start of each input file processing?

Response

Standard output. Standard error. These messages are not generated.

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

CAE Specification, Commands and Utilities, Issue 4, Version 2, Chapter 3, Utilities, c89, STDOUT and STDERR.

Question 11: What are the limits associated with external symbols imposed by c89?

Response

Description	Minimum Maximum	Implementation Maximum
Number of significant bytes	31
Number of external symbols per source or object file	511
Total number of external symbols	4095

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

CAE Specification, Commands and Utilities, Issue 4, Version 2, Chapter 3, Utilities, c89, EXTENDED DESCRIPTION, External Symbols.

1.6.5 cancel

Question 12: Is the submitter of an lp job notified when the job is cancelled by someone else?

Response

Yes   No

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

CAE Specification, Commands and Utilities, Issue 4, Version 2, Chapter 3, Utilities, cancel.

1.6.6 cp

Question 13: What is the affect of alternate access control mechanisms on file copies?

Response

If the implementation has an alternate access control mechanism, describe the effect of the controls on file copying or an indication of where these controls are documented.

Rationale

Because of the additional restrictions on creating files and reading data from files, the cp utility may not behave as described when alternate access control mechanisms are in use.

Reference

CAE Specification, Commands and Utilities, Issue 4, Version 2, Chapter 3, Utilities, cp, DESCRIPTION (final paragraph).

1.6.7 date

Question 14: Does date permit the setting of the date and time?

Response

Yes   No

Rationale

Some systems, particularly those that are hosted as part of a total system environment, do not allow the date command to set the date. On such systems, the setting of the date can only be accomplished from the host environment.

Reference

CAE Specification, Commands and Utilities, Issue 4, Version 2, Chapter 3, Utilities, date, OPERANDS, mmddhhmm[yy].

1.6.8 ex

Question 15: What restrictions are imposed on the set of commands within the rhs of the map command?

Response

Provide a list of restrictions, if any, in the space below. Alternately, a reference to the system documentation where these restrictions are described is acceptable.

Rationale

Implementations may impose restrictions on the commands that can be used by macros in visual mode.

Reference

CAE Specifications, Commands and Utilities, Issue 4, Version 2, Chapter 3, Utilities, ex, EXTENDED DESCRIPTION, Command Descriptions in ex, Map.

1.6.9 fc

Question 16: Is the history list mechanism disabled for users with appropriate privileges who do not set HISTFILE?

Response

Yes   No

Rationale

The specification states that an implementation may, in certain circumstances, disable the history list mechanism for users with appropriate privileges who do not set HISTFILE. This could have some security implications.

Reference

CAE Specification, Commands and Utilities, Issue 4, Version 2, Chapter 3, Utilities, fc, ENVIRONMENT VARIABLES, HISTFILE.

1.6.10 fort77

Question 17: When multiple input files are specified, where does fort77 direct identification messages designating the start of each input file processing?

Response

Standard output. Standard error. These messages are not generated. Not applicable.

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

CAE Specification, Commands and Utilities, Issue 4, Version 2, Chapter 3, Utilities, fort77, STDERR.

Question 18: What are the limits associated with external symbols imposed by fort77?

Response

Description	Minimum Maximum	Implementation Maximum
Number of significant bytes	31
Number of external symbols per source or object file	511
Total number of external symbols	4095

Rationale

These limits vary between implementations and cannot be reset by the user. The specification gives the minimum maximum value for each of the values. Some applications may require larger limits than these minimum maxima.

Reference

CAE Specification, Commands and Utilities, Issue 4, Version 2, Chapter 3, Utilities, fort77, EXTENDED DESCRIPTION, External Symbols.

1.6.11 lex

Question 19: Where are error messages sent when the lex -t option is not specified?

Response

Standard output. Standard error. Not applicable.

Rationale

These messages can be directed to either standard output or standard error, though the messages are not allowed to be directed to both. An application may wish to redirect these messages to a file.

Reference

CAE Specification, Commands and Utilities, Issue 4, Version 2, Chapter 3, Utilities, lex, STDOUT.

1.6.12 ln

Question 20: Can ln create links to a directory?

Response

Yes   No

Rationale

Implementations may disallow the creation of hard links to a directory, even though the executing process has the appropriate privileges.

Reference

CAE Specification, Commands and Utilities, Issue 4, Version 2, Chapter 3, Utilities, ln, OPERANDS, source_file.

1.6.13 localedef

Question 21: What is the default character mapping used when the localedef -f option is not specified?

Response

Either enter the name of the default character mapping used by localedef, or alternatively provide a reference to your system documentation where this character mapping file is described.

Rationale

The specification 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.

Reference

CAE Specification, Commands and Utilities, Issue 4, Version 2, Chapter 3, Utilities, localedef, OPTIONS, -f.

1.6.14 lp

Question 22: What lp option or operator command is used to suppress the printing of a banner page?

Response

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

CAE Specification, Commands and Utilities, Issue 4, Version 2, Chapter 3, Utilities, lp, DESCRIPTION.

1.6.15 ls

Question 23: How many bytes are in a block as reported by ls?

Response

Rationale

The block size used by ls 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

CAE Specification, Commands and Utilities, Issue 4, Version 2, Chapter 3, Utilities, ls, OPTIONS, -s.

1.6.16 make

Question 24: What additional variables does make add to its environment?

Response

If additional variables are provided by make enter a list of these variables; alternatively provide a reference to the system documentation where such a list can be found. If no additional variables are provided, enter "None".

Rationale

The implementation of make may set certain environment variables on invocation of make. These variables may not be set by the user, thus reducing the name space for environment variables.

Reference

CAE Specification, Commands and Utilities, Issue 4, Version 2, Chapter 3, Utilities, make, EXTENDED DESCRIPTION, Makefile Execution.

Question 25: Does the default MAKEFLAGS environment variable contain additional implementation-dependent options?

Response

If additional options are provided in MAKEFLAGS enter a list of these options; alternatively provide a reference to the system documentation where such a list can be found. If no additional options are provided, enter "None".

Rationale

The implementation of make may set certain default MAKEFLAGS options on invocation of make. These variables are in addition to those set by the user on the command line and could affect the processing of make.

Reference

CAE Specification, Commands and Utilities, Issue 4, Version 2, Chapter 3, Utilities, make, EXTENDED DESCRIPTION, Makefile Execution.

1.6.17 newgrp

Question 26: Does newgrp allow users who are not listed as a member of a group which has no password to change to that group?

Response

Yes   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

CAE Specification, Commands and Utilities, Issue 4, Version 2, Chapter 3, Utilities, newgrp, DESCRIPTION.

Question 27: Are there any other implementation-specific authorisation restrictions that affect newgrp?

Response

If additional authorisations are required, provide a list of these restrictions; alternatively provide a reference to the system documentation where such a list can be found. If there are no such authorisation restrictions, enter "None".

Rationale

Some implementations may impose accounting or other restrictions that could cause newgrp 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

CAE Specification, Commands and Utilities, Issue 4, Version 2, Chapter 3, Utilities, newgrp, DESCRIPTION.

1.6.18 nice and renice

Question 28: What are the limits and default values used by nice and renice?

Response

Maximum nice value
Minimum nice value
Default nice value

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

CAE Specification, Commands and Utilities, Issue 4, Version 2, Chapter 3, Utilities, nice, DESCRIPTION.

1.6.19 pax

Question 29: What is the default archive format used by pax?

Response

If your default format is implementation-dependent, place a description of the format in the box below. Otherwise, enter "Extended tar." or "Extended cpio."

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 tar or extended cpio format (or any other format that it understands), the pax utility will read the archive in the format as written.

Reference

CAE Specification, Commands and Utilities, Issue 4, Version 2, Chapter 3, Utilities, pax, DESCRIPTION.

Question 30: How does pax handle reading and writing of archives that span multiple files?

Response

Provide a description of how pax reads and writes archives that exceed the size of the output/input media. Alternatively specify where it is documented.

Rationale

In many cases pax 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 pax which allow the user to specify the address to use to access subsequent files.

Reference

CAE Specification, Commands and Utilities, Issue 4, Version 2, Chapter 3, Utilities, pax, DESCRIPTION.

Question 31: How does pax handle invalid filenames when it is extracting files from an archive?

Response

Provide a description of how pax handles invalid filenames on extraction, detailing the type of error message produced or the algorithm used to generate a filename. Alternatively specify where it is documented.

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 pax 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 pax uses in generating these filenames.

Reference

CAE Specification, Commands and Utilities, Issue 4, Version 2, Chapter 3, Utilities, pax, EXTENDED DESCRIPTION, The cpio Filename.

1.6.20 printf

Question 32: Does printf support the e, E, f, g and G floating point conversion specifications?

Response

Yes   No

Rationale

The support of these conversions is optional.

Reference

CAE Specification, Commands and Utilities, Issue 4, Version 2, Chapter 3, Utilities, printf, EXAMPLES.

1.6.21 sh

Question 33: Is the environment variable IFS ignored when the shell is invoked?

Response

Yes   No

Rationale

The specification allows that the sh command ignore the setting of the IFS 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 system() and execvp() interfaces.

Reference

CAE Specification, Commands and Utilities, Issue 4, Version 2, Chapter 3, Utilities, sh, ENVIRONMENT VARIABLES, IFS.

1.6.22 touch

Question 34: What is the latest date after the Epoch that can be used by touch?

Response

Rationale

Because of the limitations on the storage of times in the stat structure associated with a file, there is a limitation on the valid dates that can be specified to touch. This is directly related to the value that can be stored in the integral type time_t.

Reference

CAE Specification, Commands and Utilities, Issue 4, Version 2, Chapter 3, Utilities, touch, OPTIONS, -t.

1.6.23 yacc

Question 35: What are the limits of yacc's internal tables?

Response

Description	Minimum Maximum	Implementation Maximum
Number of tokens	126
Number of non-terminals	200
Number of rules	300
Number of states	600
Length of rules	5200
Number of actions	4000

Rationale

These internal table sizes vary between implementations and cannot be reset by the user. The specification gives the minimum maximum value for each of the table values.

Reference

CAE Specification, Commands and Utilities, Issue 4, Version 2, Chapter 3, Utilities, yacc, EXTENDED DESCRIPTION, Limits.

2. Appendix

Copyright © 
All rights reserved.

3. Change History