Conformance Statement

Product Standard: Commands and Utilities V5

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.

Organization
Author

1. Commands and Utilities V5

Product Information

Enter the product name, version/release number, and product supplier for each product required to meet the conformance requirements.

Product Identification	Version/Release Number	Product Supplier

Environment Specification

Product registration applies to software products operating in a specific hardware or hardware/software environment.
A product may be registered in all members of a binary-compatible family of products on the basis of a single test report.

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

Testing Environment	Binary-compatible Family	Portability Environment	Indicator of Compliance	Compliance Details
				Test Suite: Test Report:
				Test Suite: Test Report:
				Test Suite: Test Report:
				Test Suite: Test Report:
				Test Suite: Test Report:

Temporary Waivers

Enter the waiver number and expiry date for each temporary waiver granted by The Open Group.

	Waiver Number	Expiry Date

1.1 POSIX.2 Supported Features

Question 1: 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
_POSIX2_C_DEV	Implementation supports the C Language Development Utilities option.	Yes No
_POSIX2_CHAR_TERM	Implementation supports at least one terminal type.	Yes
_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
_POSIX2_PBS	Implementation supports the Batch Environment Services and Utilities option.	Yes No
_POSIX2_PBS_ACCOUNTING	Implementation supports the Batch Accounting option.	Yes No
_POSIX2_PBS_CHECKPOINT	Implementation supports the Batch Checkpoint/Restart option.	Yes No
_POSIX2_PBS_LOCATE	Implementation supports the Locate Batch Job Request option.	Yes No
_POSIX2_PBS_MESSAGE	Implementation supports the Batch Job Message Request option.	Yes No
_POSIX2_PBS_TRACK	Implementation supports the Track Batch Job Request option.	Yes No
_POSIX2_SW_DEV	Implementation supports the Software Developments Utilities option.	Yes No
_POSIX2_UPE	Implementation supports the User Portability Utilities option.	Yes
_XOPEN_UUCP	Implementation supports the UUCP Utilities option.	Yes No

Rationale

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

Reference

Technical Standard, Base Definitions, Issue 7, Chapter 13, Headers, <unistd.h>.

1.2 Development Utilities

1.2.1 Supported Commands

Question 2: Is the XSI Development Utilities option supported by this implementation?

Response

Yes No

Rationale

The development utilities are required to exist on designated DEVELOPMENT systems but may not be present on all XSI-conformant systems.

Reference

Technical Standard, Base Definitions, Issue 7, Section 2.1.4.2, XSI Shell and Utilities Conformance.

1.3 FORTRAN Option

1.3.1 FORTRAN Utility

Question 3: 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

Technical Standard, Base Definitions, Issue 7, Section 2.1.6.2, Shell and Utilities.

1.4 Specific Commands and Utilities

1.4.1 at

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

Response

Rationale

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

Reference

Technical Standard, Shell and Utilities, Issue 7, Chapter 4, Utilities, at, ENVIRONMENT VARIABLES, SHELL.

Question 5: What is the full pathname of the directory in which the at.allow and at.deny files are located?

Response

Rationale

The location of the directory where at and batch look for the at.allow and at.deny files may differ between implementations.

Reference

Technical Standard, Shell and Utilities, Issue 7, Chapter 4, Utilities, at, DESCRIPTION.

Technical Standard, Shell and Utilities, Issue 7, Chapter 4, Utilities, batch, DESCRIPTION.

1.4.2 awk

Question 6: 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 ({STREAM_MAX}).

Reference

Technical Standard, Shell and Utilities, Issue 7, Chapter 4, Utilities, awk, Input/Output and General Functions, close().

1.4.3 batch

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

Response

Rationale

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

Reference

Technical Standard, Shell and Utilities, Issue 7, Chapter 4, Utilities, batch, ENVIRONMENT VARIABLES, SHELL.

1.4.4 c99

Question 8: 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

Technical Standard, Shell and Utilities, Issue 7, Chapter 4, Utilities, c99, OPTIONS, -D.

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

Response

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

Technical Standard, Shell and Utilities, Issue 7, Chapter 4, Utilities, c99, STDOUT and STDERR.

Question 10: What are the limits associated with external symbols imposed by c99?

Response

If the implementation limits are limited by memory, then the answer should say so; for example "511 but MEMORY LIMITED".

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

Technical Standard, Shell and Utilities, Issue 7, Chapter 4, Utilities, c99, EXTENDED DESCRIPTION, External Symbols.

1.4.5 cp

Question 11: 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

Technical Standard, Shell and Utilities, Issue 7, Chapter 4, Utilities, cp, DESCRIPTION (final paragraph).

1.4.6 crontab

Question 12: What is the full pathname of the directory in which the cron.allow and cron.deny files are located?

Response

Rationale

The location of the directory where crontab looks for the cron.allow and cron.deny files may differ between implementations.

Reference

Technical Standard, Shell and Utilities, Issue 7, Chapter 4, Utilities, crontab, DESCRIPTION.

1.4.7 date

Question 13: 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

Technical Standard, Shell and Utilities, Issue 7, Chapter 4, Utilities, date, OPERANDS, mmddhhmm[yy].

1.4.8 ex

Question 14: 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. Alternatively, 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

Technical Standard, Shell and Utilities, Issue 7, Chapter 4, Utilities, ex, EXTENDED DESCRIPTION, Command Descriptions in ex, Map.

1.4.9 fc

Question 15: 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

Technical Standard, Shell and Utilities, Issue 7, Chapter 4, Utilities, fc, ENVIRONMENT VARIABLES, HISTFILE.

1.4.10 fort77

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

Response

If the implementation does not support the fort77 utility, select "not applicable".

Rationale

Reference

Technical Standard, Shell and Utilities, Issue 7, Chapter 4, Utilities, fort77, STDERR.

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

Response

If the implementation does not support the fort77 utility, state "not applicable" in the 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. If the responses are not supported then the fort77 utility is not supported.

Reference

Technical Standard, Shell and Utilities, Issue 7, Chapter 4, Utilities, fort77, EXTENDED DESCRIPTION, External Symbols.

1.4.11 lex

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

Response

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

Technical Standard, Shell and Utilities, Issue 7, Chapter 4, Utilities, lex, STDOUT.

1.4.12 ln

Question 19: 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

Technical Standard, Shell and Utilities, Issue 7, Chapter 4, Utilities, ln, OPERANDS, source_file.

1.4.13 localedef

Question 20: 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

Technical Standard, Shell and Utilities, Issue 7, Chapter 4, Utilities, localedef, OPTIONS, -f.

1.4.14 lp

Question 21: 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

Technical Standard, Shell and Utilities, Issue 7, Chapter 4, Utilities, lp, DESCRIPTION.

1.4.15 ls

Question 22: How many bytes are in a block as reported by ls when -k is not used?

Response

Rationale

When the -k option is not specified, 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

Technical Standard, Shell and Utilities, Issue 7, Chapter 4, Utilities, ls, OPTIONS, -s.

1.4.16 make

Question 23: 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

Technical Standard, Shell and Utilities, Issue 7, Chapter 4, Utilities, make, EXTENDED DESCRIPTION, Macros.

Question 24: Does the default MAKEFLAGS environment variable contain additional implementation-defined 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

Technical Standard, Shell and Utilities, Issue 7, Chapter 4, Utilities, make, EXTENDED DESCRIPTION, Macros.

1.4.17 newgrp

Question 25: 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

Technical Standard, Shell and Utilities, Issue 7, Chapter 4, Utilities, newgrp, DESCRIPTION.

Question 26: Are there any other implementation-defined authorization restrictions that affect newgrp?

Response

If additional authorizations 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

Technical Standard, Shell and Utilities, Issue 7, Chapter 4, Utilities, newgrp, DESCRIPTION.

1.4.18 nice and renice

Question 27: 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

Technical Standard, Shell and Utilities, Issue 7, Chapter 4, Utilities, nice, DESCRIPTION.

1.4.19 pax

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

Response

Enter "pax", "ustar" or "cpio".

Rationale

The implementation has a choice in which format to use when creating archives. When it is reading an archive created in any format that it understands, the pax utility will read the archive in the format as written.

Reference

Technical Standard, Shell and Utilities, Issue 7, Chapter 4, Utilities, pax, DESCRIPTION.

Question 29: 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

Technical Standard, Shell and Utilities, Issue 7, Chapter 4, Utilities, pax, DESCRIPTION.

Question 30: 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

Technical Standard, Shell and Utilities, Issue 7, Chapter 4, Utilities, pax, EXTENDED DESCRIPTION, cpio Filename.

1.4.20 printf

Question 31: 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

Technical Standard, Shell and Utilities, Issue 7, Chapter 4, Utilities, printf, EXTENDED DESCRIPTION.

1.4.21 touch

Question 32: 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 type time_t.

Reference

Technical Standard, Shell and Utilities, Issue 7, Chapter 4, Utilities, touch, OPTIONS, -d and -t.

1.4.22 yacc

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

Response

If the implementation limits are limited by memory, then the answer should say so; for example "5200 but MEMORY LIMITED".

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

Technical Standard, Shell and Utilities, Issue 7, Chapter 4, Utilities, yacc, EXTENDED DESCRIPTION, Limits.

1.5 C-language Programming Environments

1.5.1 Supported Environments

Question 34: What C-language programming environments are provided?

Response

Programming Environment	Provided
The implementation provides a C-language programming environment with 32-bit int, long, pointer and off_t types.	Yes No
The implementation provides a C-language programming environment with 32-bit int, long and pointer types and an off_t type using at least 64 bits.	Yes No
The implementation provides a C-language programming environment with 32-bit int, and 64-bit long, pointer and off_t types.	Yes No
The implementation provides a C-language programming environment with int using at least 32-bits, and long, pointer and off_t types using at least 64 bits.	Yes No

Rationale

Shell and Utilities, Issue 7 defines these scenarios as possible C-language programming environment offerings.

Reference

Technical Standard, Shell and Utilities, Issue 7, Chapter 4, Utilities, c99,

1.5.2 Default Environment

Question 35: What C-language programming environment is the default?

Response

Programming Environment	Provided
The implementation's default C-language programming environment provides 32-bit int, long, pointer and off_t types.	Yes No
The implementation's default C-language programming environment provides 32-bit int, long and pointer types and an off_t type using at least 64 bits.	Yes No
The implementation's default C-language programming environment provides 32-bit int, and 64-bit long, pointer and off_t types.	Yes No
The implementation's default C-language programming environment provides int using at least 32-bits, and long, pointer and off_t types using at least 64 bits.	Yes No

Rationale

Shell and Utilities, Issue 7 specifies that the default must be one of the above. Note that the third choice overlaps with the fourth choice.

Reference

Technical Standard, Shell and Utilities, Issue 7, Chapter 4, Utilities, c99,

1.6 Batch Environment Services Option

1.6.1 Batch Job Attributes

Question 36: Does qalter attempt to alter the attributes of a batch job in the RUNNING state?

Response

If the implementation does not support the Batch Environment Services option select "Not applicable"

Rationale

The specification states that an attempt to alter the attributes of a batch job in the RUNNING state is implementation-defined.

Reference

Technical Standard, Shell and Utilities, Issue 7, Chapter 4, Utilities, qalter

1.6.2 Batch Job Hold Types

Question 37: Does the implementation define other hold types for the qalter , qhold, qrls and qselect utilities?

Response

If the implementation does not support the Batch Environment Services option select "Not applicable"

If Yes describe their internal behavior and how they affect the behavior of these utilities.

Rationale

The specification states that an implementation may define other keep types for these utilities and that the conformance document shall describe any additional keep types, how they are specified, their internal behavior, and how they affect the behavior of the utility.

Reference

Technical Standard, Shell and Utilities, Issue 7, Chapter 4, Utilities, qalter, qhold, qrls and qselect.

1.6.3 Batch Job Join Types

Question 38: Does the implementation define other join types for the qalter and qsub utilities ?

Response

If the implementation does not support the Batch Environment Services option select "Not applicable"

If Yes describe their internal behavior and how they affect the behavior of these utilities.

Rationale

Reference

Technical Standard, Shell and Utilities, Issue 7, Chapter 4, Utilities, qalter and qsub.

1.6.4 Batch Job Keep Types

Question 39: Does the implementation define other keep types for the qalter and qsub utilities?

Response

If the implementation does not support the Batch Environment Services option select "Not applicable"

If Yes describe their internal behavior and how they affect the behavior of these utilities.

Rationale

Reference

Technical Standard, Shell and Utilities, Issue 7, Chapter 4, Utilities, qalter and qsub.

1.6.5 Batch Job Mail Types

Question 40: Does the implementation define other mail types for the qalter and qsub utilties?

Response

If the implementation does not support the Batch Environment Services option select "Not applicable"

If Yes describe their internal behavior and how they affect the behavior of these utilities.

Rationale

Reference

Technical Standard, Shell and Utilities, Issue 7, Chapter 4, Utilities, qalter and qsub.

1.6.6 Mail Address Interpretation

Question 41: How do the qalter and qsub utilities interpret the mail_address argument to the -M option?

Response

If the implementation does not support the Batch Environment Services option enter "Not applicable"

Rationale

The specification states that the interpretation of mail_address is implementation-defined.

Reference

Technical Standard, Shell and Utilities, Issue 7, Chapter 4, Utilities, qalter and qsub.

1.6.7 Locating a Batch Job on Other Servers

Question 42: Does the qalter utility attempt to locate a batch job on other servers?

Response

If the implementation does not support the Batch Environment Services option select "Not applicable"

Rationale

The specification states that whether or not the qalter utility attempts to locate the batch job on other batch servers is implementation-defined.

Reference

Technical Standard, Shell and Utilities, Issue 7, Chapter 4, Utilities, qalter.

1.6.8 Output of Diagnostic Messages

Question 43: Do the qdel,qhold,qmove,qmsg,qrerun,qrls,qsig and qstat utilities wait to output a diagnostic message while attempting to locate a job on other servers?

Response

If the implementation does not support the Batch Environment Services option select "Not applicable"

Utility Name	Output a Diagnostic?
qdel
qhold
qmove
qmsg
qrerun
qrls
qsig
qstat

Rationale

The specification states that whether or not these utilities wait to output the diagnostic message while attempting to locate the job on other servers is implementation-defined.

Reference

Technical Standard, Shell and Utilities, Issue 7, Chapter 4, Utilities, qdel,qhold,qmove,qmsg,qrerun,qrls,qsig and qstat.

1.6.9 Implementation-defined File for qmsg

Question 44: What is the name and location of the implementation-defined file that the qmsg utility writes the message to if neither -O nor the -E options are specified?

Response

If the implementation does not support the Batch Environment Services option enter "Not applicable"

Rationale

The specification states that if neither the -O nor the -E option is presented to the qmsg utility, the utility shall write the message into an implementation-defined file and that the conformance document shall describe the name and location of the implementation-defined file.

Reference

Technical Standard, Shell and Utilities, Issue 7, Chapter 4, Utilities, qmsg.

1.6.10 Matching Job_Name Attribute For qselect

Question 45: What is the format that the qselect utility supports for matching against the Job_Name attribute for the -N option?

Response

If the implementation does not support the Batch Environment Services option enter "Not applicable"

Rationale

The specification states that an implementation shall describe in the conformance document the format it supports for matching against the Job_Name attribute.

Reference

Technical Standard, Shell and Utilities, Issue 7, Chapter 4, Utilities, qselect.

1.6.11 Default Batch Server For qselect

Question 46: How does the qselect utility determine the default batch server?

Response

If the implementation does not support the Batch Environment Services option enter "Not applicable"

Rationale

The specification states that if the option-argument describes only a batch queue, the qselect utility shall select only batch jobs from the batch queue of the specified name at the default batch server. The means by which qselect determines the default server is implementation-defined.

Reference

Technical Standard, Shell and Utilities, Issue 7, Chapter 4, Utilities, qselect.

1.6.12 Implementation-defined Information for the -f option to qstat

Question 47: What additional implementation-defined information, if any, about the batch job or batch queue are displayed for the -f option to the qstat utility?

Response

If the implementation does not support the Batch Environment Services option enter "Not applicable"

If the implementation-defined information changes when the -f option is used in combination with other options please describe it below

Rationale

The specification states that the additional contents and format of a full display are implementation-defined.

Reference

Technical Standard, Shell and Utilities, Issue 7, Chapter 4, Utilities, qstat.

1.6.13 Priority Attribute For -p Option To qsub

Question 48: What is the value of the Priority attribute if the -p option is not presented to the qsub utility?

Response

If the implementation does not support the Batch Environment Services option enter "Not applicable"

Rationale

The specification states that if the -p option is not presented to the qsub utility, the value of the Priority attribute is implementation-defined.

Reference

Technical Standard, Shell and Utilities, Issue 7, Chapter 4, Utilities, qsub.

1.6.14 Default Destination for qsub

Question 49: What is the default destination if the -q option is not presented to the qsub utility?

Response

If the implementation does not support the Batch Environment Services option enter "Not applicable"

Rationale

The specification states that if the -q option is not presented to the qsub utility, the qsub utility shall submit the batch job to the default destination. The mechanism for determining the default destination is implementation-defined.

Reference

Technical Standard, Shell and Utilities, Issue 7, Chapter 4, Utilities, qsub.

1.6.15 Default Shell for qsub

Question 50: What is the mechanism for setting and determining the value of the default shell for the qsub utility?

Response

If the implementation does not support the Batch Environment Services option enter "Not applicable"

Rationale

The specification states that the conformance document shall describe the mechanism used to set the default shell and determine the current value of the default shell. An implementation shall provide a means for the installation to set the default shell to the login shell of the user under which the batch job is to execute.

Reference

Technical Standard, Shell and Utilities, Issue 7, Chapter 4, Utilities, qsub.

1.6.16 Shell Script Format for qsub

Question 51: What is the format of shell commments recognized by the qsub utility for the script file argument?

Response

If the implementation does not support the Batch Environment Services option enter "Not applicable"

Rationale

The specification states that the qsub utility shall continue to process a directive prefix line until after a is encountered. An implementation may ignore lines which, according to the syntax of the shell that will interpret the script, are comments. An implementation shall describe in the conformance document the format of any shell comments that it will recognize.

Reference

Technical Standard, Shell and Utilities, Issue 7, Chapter 4, Utilities, qsub.

2. Appendix

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

3. Change History

Date	Name	Comment
New

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