xbd_chap02.html

IEEE 1003.1-2003, Single Unix Specification v3

<dt>POSIX2_FORT_DEV</dt>

<dd><sup>[<a href="javascript:open_code('FD')">FD</a>]</sup> <img src="../images/opt-start.gif" alt="[Option Start]" border=
"0"><br>
The system supports the FORTRAN Development Utilities option. <img src="../images/opt-end.gif" alt="[Option End]" border="0"> 

<p>The <a href="../utilities/fort77.html"><i>fort77</i></a> FORTRAN compiler is the only utility in the FORTRAN Development
Utilities option. This is used for the development of FORTRAN language applications, including compilation or translation of
FORTRAN source code.</p>

<p>The <a href="../utilities/fort77.html"><i>fort77</i></a> utility may be provided by a conforming system; however, any system
claiming conformance to the FORTRAN Development Utilities option shall provide the <a href=
"../utilities/fort77.html"><i>fort77</i></a> utility.</p>
</dd>

<dt>POSIX2_FORT_RUN</dt>

<dd><sup>[<a href="javascript:open_code('FR')">FR</a>]</sup> <img src="../images/opt-start.gif" alt="[Option Start]" border=
"0"><br>
The system supports the FORTRAN Runtime Utilities option. <img src="../images/opt-end.gif" alt="[Option End]" border="0"> 

<p>The <a href="../utilities/asa.html"><i>asa</i></a> utility is the only utility in the FORTRAN Runtime Utilities option.</p>

<p>The <a href="../utilities/asa.html"><i>asa</i></a> utility may be provided by a conforming system; however, any system claiming
conformance to the FORTRAN Runtime Utilities option shall provide the <a href="../utilities/asa.html"><i>asa</i></a> utility.</p>
</dd>

<dt>POSIX2_LOCALEDEF</dt>

<dd><br>
The system supports the Locale Creation Utilities option. 

<p>If supported, the system supports the creation of locales as described in the <a href=
"../utilities/localedef.html"><i>localedef</i></a> utility.</p>

<p>The <a href="../utilities/localedef.html"><i>localedef</i></a> utility may be provided by a conforming system; however, any
system claiming conformance to the Locale Creation Utilities option shall provide the <a href=
"../utilities/localedef.html"><i>localedef</i></a> utility.</p>
</dd>

<dt>POSIX2_PBS</dt>

<dd><sup>[<a href="javascript:open_code('BE')">BE</a>]</sup> <img src="../images/opt-start.gif" alt="[Option Start]" border=
"0"><br>
The system supports the Batch Environment Services and Utilities option (see the Shell and Utilities volume of
IEEE&nbsp;Std&nbsp;1003.1-2001, <a href="../utilities/xcu_chap03.html">Chapter 3, Batch Environment Services</a>). <img src=
"../images/opt-end.gif" alt="[Option End]" border="0"> <basefont size="2"> 

<dl>
<dt><b>Note:</b></dt>

<dd>The Batch Environment Services and Utilities option is a combination of mandatory and optional batch services and utilities.
The POSIX_PBS symbolic constant implies the system supports all the mandatory batch services and utilities.</dd>
</dl>

<basefont size="3"></dd>

<dt>POSIX2_PBS_ACCOUNTING</dt>

<dd><br>
The system supports the Batch Accounting option.</dd>

<dt>POSIX2_PBS_CHECKPOINT</dt>

<dd><br>
The system supports the Batch Checkpoint/Restart option.</dd>

<dt>POSIX2_PBS_LOCATE</dt>

<dd><br>
The system supports the Locate Batch Job Request option.</dd>

<dt>POSIX2_PBS_MESSAGE</dt>

<dd><br>
The system supports the Batch Job Message Request option.</dd>

<dt>POSIX2_PBS_TRACK</dt>

<dd><br>
The system supports the Track Batch Job Request option.</dd>

<dt>POSIX2_SW_DEV</dt>

<dd><sup>[<a href="javascript:open_code('SD')">SD</a>]</sup> <img src="../images/opt-start.gif" alt="[Option Start]" border=
"0"><br>
The system supports the Software Development Utilities option. <img src="../images/opt-end.gif" alt="[Option End]" border="0"> 

<p>The utilities in the Software Development Utilities option are used for the development of applications, including compilation
or translation of source code, the creation and maintenance of library archives, and the maintenance of groups of inter-dependent
programs.</p>

<p>The utilities listed below may be provided by the conforming system; however, any system claiming conformance to the Software
Development Utilities option shall provide all of the utilities listed here.</p>

<blockquote>
<pre>
<a href="../utilities/ar.html"><i>ar</i></a>
<a href="../utilities/make.html"><i>make</i></a>
<a href="../utilities/nm.html"><i>nm</i></a>
<a href="../utilities/strip.html"><i>strip</i></a>
</pre>
</blockquote>
</dd>

<dt>POSIX2_UPE</dt>

<dd><sup>[<a href="javascript:open_code('UP')">UP</a>]</sup> <img src="../images/opt-start.gif" alt="[Option Start]" border=
"0"><br>
The system supports the User Portability Utilities option. <img src="../images/opt-end.gif" alt="[Option End]" border="0"> 

<p>The utilities in the User Portability Utilities option shall be implemented on all systems that claim conformance to this
option. Certain utilities are noted as having features that cannot be implemented on all terminal types; if the POSIX2_CHAR_TERM
option is supported, the system shall support all such features on at least one terminal type; see <a href=
"xbd_chap10.html#tag_10_02"><i>Output Devices and Terminal Types</i></a> .</p>

<p>Some of the utilities are required only on systems that also support the Software Development Utilities option, or the
character-at-a-time terminal option (see <a href="xbd_chap10.html#tag_10_02"><i>Output Devices and Terminal Types</i></a> ); such
utilities have this noted in their DESCRIPTION sections. All of the other utilities listed are required only on systems that claim
conformance to the User Portability Utilities option.</p>

<blockquote>
<table cellpadding="3">
<tr valign="top">
<td align="left">
<p class="tent"><br>
<a href="../utilities/alias.html"><i>alias</i></a><br>
<a href="../utilities/at.html"><i>at</i></a><br>
<a href="../utilities/batch.html"><i>batch</i></a><br>
<a href="../utilities/bg.html"><i>bg</i></a><br>
<a href="../utilities/crontab.html"><i>crontab</i></a><br>
<a href="../utilities/split.html"><i>split</i></a><br>
<a href="../utilities/ctags.html"><i>ctags</i></a><br>
<a href="../utilities/df.html"><i>df</i></a><br>
<a href="../utilities/du.html"><i>du</i></a><br>
<a href="../utilities/ex.html"><i>ex</i></a><br>
&nbsp;</p>
</td>
<td align="left">
<p class="tent"><br>
<a href="../utilities/expand.html"><i>expand</i></a><br>
<a href="../utilities/fc.html"><i>fc</i></a><br>
<a href="../utilities/fg.html"><i>fg</i></a><br>
<a href="../utilities/file.html"><i>file</i></a><br>
<a href="../utilities/jobs.html"><i>jobs</i></a><br>
<a href="../utilities/man.html"><i>man</i></a><br>
<a href="../utilities/mesg.html"><i>mesg</i></a><br>
<a href="../utilities/more.html"><i>more</i></a><br>
<a href="../utilities/newgrp.html"><i>newgrp</i></a><br>
<a href="../utilities/nice.html"><i>nice</i></a><br>
&nbsp;</p>
</td>
<td align="left">
<p class="tent"><br>
<a href="../utilities/nm.html"><i>nm</i></a><br>
<a href="../utilities/patch.html"><i>patch</i></a><br>
<a href="../utilities/ps.html"><i>ps</i></a><br>
<a href="../utilities/renice.html"><i>renice</i></a><br>
<a href="../utilities/split.html"><i>split</i></a><br>
<a href="../utilities/strings.html"><i>strings</i></a><br>
<a href="../utilities/tabs.html"><i>tabs</i></a><br>
<a href="../utilities/talk.html"><i>talk</i></a><br>
<a href="../utilities/time.html"><i>time</i></a><br>
<a href="../utilities/tput.html"><i>tput</i></a><br>
&nbsp;</p>
</td>
<td align="left">
<p class="tent"><br>
<a href="../utilities/unalias.html"><i>unalias</i></a><br>
<a href="../utilities/unexpand.html"><i>unexpand</i></a><br>
<a href="../utilities/uudecode.html"><i>uudecode</i></a><br>
<a href="../utilities/uuencode.html"><i>uuencode</i></a><br>
<a href="../utilities/vi.html"><i>vi</i></a><br>
<a href="../utilities/who.html"><i>who</i></a><br>
<a href="../utilities/write.html"><i>write</i></a><br>
&nbsp;</p>
</td>
</tr>
</table>
</blockquote>
</dd>
</dl>

<h3><a name="tag_02_02"></a>Application Conformance</h3>

<p>All applications claiming conformance to IEEE&nbsp;Std&nbsp;1003.1-2001 shall use only language-dependent services for the C
programming language described in <a href="#tag_02_03">Language-Dependent Services for the C Programming Language</a> , shall use
only the utilities and facilities defined in the Shell and Utilities volume of IEEE&nbsp;Std&nbsp;1003.1-2001, and shall fall
within one of the following categories.</p>

<h4><a name="tag_02_02_01"></a>Strictly Conforming POSIX Application</h4>

<p>A Strictly Conforming POSIX Application is an application that requires only the facilities described in
IEEE&nbsp;Std&nbsp;1003.1-2001. Such an application:</p>

<ol>
<li>
<p>Shall accept any implementation behavior that results from actions it takes in areas described in IEEE&nbsp;Std&nbsp;1003.1-2001
as <i>implementation-defined</i> or <i>unspecified</i>, or where IEEE&nbsp;Std&nbsp;1003.1-2001 indicates that implementations may
vary</p>
</li>

<li>
<p>Shall not perform any actions that are described as producing <i>undefined</i> results</p>
</li>

<li>
<p>For symbolic constants, shall accept any value in the range permitted by IEEE&nbsp;Std&nbsp;1003.1-2001, but shall not rely on
any value in the range being greater than the minimums listed or being less than the maximums listed in
IEEE&nbsp;Std&nbsp;1003.1-2001</p>
</li>

<li>
<p>Shall not use facilities designated as <i>obsolescent</i></p>
</li>

<li>
<p>Is required to tolerate and permitted to adapt to the presence or absence of optional facilities whose availability is indicated
by <a href="#tag_02_01_03">POSIX Conformance</a></p>
</li>

<li>
<p>For the C programming language, shall not produce any output dependent on any behavior described in the ISO/IEC&nbsp;9899:1999
standard as <i>unspecified</i>, <i>undefined</i>, or <i>implementation-defined</i>, unless the System Interfaces volume of
IEEE&nbsp;Std&nbsp;1003.1-2001 specifies the behavior</p>
</li>

<li>
<p>For the C programming language, shall not exceed any minimum implementation limit defined in the ISO/IEC&nbsp;9899:1999
standard, unless the System Interfaces volume of IEEE&nbsp;Std&nbsp;1003.1-2001 specifies a higher minimum implementation limit</p>
</li>

<li>
<p>For the C programming language, shall define _POSIX_C_SOURCE to be 200112L before any header is included</p>
</li>
</ol>

<p>Within IEEE&nbsp;Std&nbsp;1003.1-2001, any restrictions placed upon a Conforming POSIX Application shall restrict a Strictly
Conforming POSIX Application.</p>

<h4><a name="tag_02_02_02"></a>Conforming POSIX Application</h4>

<h5><a name="tag_02_02_02_01"></a>ISO/IEC Conforming POSIX Application</h5>

<p>An ISO/IEC Conforming POSIX Application is an application that uses only the facilities described in
IEEE&nbsp;Std&nbsp;1003.1-2001 and approved Conforming Language bindings for any ISO or IEC standard. Such an application shall
include a statement of conformance that documents all options and limit dependencies, and all other ISO or IEC standards used.</p>

<h5><a name="tag_02_02_02_02"></a>&lt;National Body&gt; Conforming POSIX Application</h5>

<p>A &lt;National Body&gt; Conforming POSIX Application differs from an ISO/IEC Conforming POSIX Application in that it also may
use specific standards of a single ISO/IEC member body referred to here as &lt;<i>National Body</i>&gt;. Such an application shall
include a statement of conformance that documents all options and limit dependencies, and all other &lt;National Body&gt; standards
used.</p>

<h4><a name="tag_02_02_03"></a>Conforming POSIX Application Using Extensions</h4>

<p>A Conforming POSIX Application Using Extensions is an application that differs from a Conforming POSIX Application only in that
it uses non-standard facilities that are consistent with IEEE&nbsp;Std&nbsp;1003.1-2001. Such an application shall fully document
its requirements for these extended facilities, in addition to the documentation required of a Conforming POSIX Application. A
Conforming POSIX Application Using Extensions shall be either an ISO/IEC Conforming POSIX Application Using Extensions or a
&lt;National Body&gt; Conforming POSIX Application Using Extensions (see <a href="#tag_02_02_02_01">ISO/IEC Conforming POSIX
Application</a> and <a href="#tag_02_02_02_02">&lt;National Body&gt; Conforming POSIX Application</a> ).</p>

<h4><a name="tag_02_02_04"></a>Strictly Conforming XSI Application</h4>

<p>A Strictly Conforming XSI Application is an application that requires only the facilities described in
IEEE&nbsp;Std&nbsp;1003.1-2001. Such an application:</p>

<ol>
<li>
<p>Shall accept any implementation behavior that results from actions it takes in areas described in IEEE&nbsp;Std&nbsp;1003.1-2001
as <i>implementation-defined</i> or <i>unspecified</i>, or where IEEE&nbsp;Std&nbsp;1003.1-2001 indicates that implementations may
vary</p>
</li>

<li>
<p>Shall not perform any actions that are described as producing <i>undefined</i> results</p>
</li>

<li>
<p>For symbolic constants, shall accept any value in the range permitted by IEEE&nbsp;Std&nbsp;1003.1-2001, but shall not rely on
any value in the range being greater than the minimums listed or being less than the maximums listed in
IEEE&nbsp;Std&nbsp;1003.1-2001</p>
</li>

<li>
<p>Shall not use facilities designated as <i>obsolescent</i></p>
</li>

<li>
<p>Is required to tolerate and permitted to adapt to the presence or absence of optional facilities whose availability is indicated
by <a href="#tag_02_01_04">XSI Conformance</a></p>
</li>

<li>
<p>For the C programming language, shall not produce any output dependent on any behavior described in the ISO&nbsp;C standard as
<i>unspecified</i>, <i>undefined</i>, or <i>implementation-defined</i>, unless the System Interfaces volume of
IEEE&nbsp;Std&nbsp;1003.1-2001 specifies the behavior</p>
</li>

<li>
<p>For the C programming language, shall not exceed any minimum implementation limit defined in the ISO&nbsp;C standard, unless the
System Interfaces volume of IEEE&nbsp;Std&nbsp;1003.1-2001 specifies a higher minimum implementation limit</p>
</li>

<li>
<p>For the C programming language, shall define _XOPEN_SOURCE to be 600 before any header is included</p>
</li>
</ol>

<p>Within IEEE&nbsp;Std&nbsp;1003.1-2001, any restrictions placed upon a Conforming POSIX Application shall restrict a Strictly
Conforming XSI Application.</p>

<h4><a name="tag_02_02_05"></a>Conforming XSI Application Using Extensions</h4>

<p>A Conforming XSI Application Using Extensions is an application that differs from a Strictly Conforming XSI Application only in
that it uses non-standard facilities that are consistent with IEEE&nbsp;Std&nbsp;1003.1-2001. Such an application shall fully
document its requirements for these extended facilities, in addition to the documentation required of a Strictly Conforming XSI
Application.</p>

<h3><a name="tag_02_03"></a>Language-Dependent Services for the C Programming Language</h3>

<p>Implementors seeking to claim conformance using the ISO&nbsp;C standard shall claim POSIX conformance as described in <a href=
"#tag_02_01_03">POSIX Conformance</a> .</p>

<h3><a name="tag_02_04"></a>Other Language-Related Specifications</h3>

<p>IEEE&nbsp;Std&nbsp;1003.1-2001 is currently specified in terms of the shell command language and ISO&nbsp;C. Bindings to other
programming languages are being developed.</p>

<p>If conformance to IEEE&nbsp;Std&nbsp;1003.1-2001 is claimed for implementation of any programming language, the implementation
of that language shall support the use of external symbols distinct to at least 31 bytes in length in the source program text.
(That is, identifiers that differ at or before the thirty-first byte shall be distinct.) If a national or international standard
governing a language defines a maximum length that is less than this value, the language-defined maximum shall be supported.
External symbols that differ only by case shall be distinct when the character set in use distinguishes uppercase and lowercase
characters and the language permits (or requires) uppercase and lowercase characters to be distinct in external symbols.</p>

<hr size="2" noshade>
<center><font size="2"><!--footer start-->
UNIX &reg; is a registered Trademark of The Open Group.<br>
POSIX &reg; is a registered Trademark of The IEEE.<br>
[ <a href="../mindex.html">Main Index</a> | <a href="../basedefs/contents.html">XBD</a> | <a href=
"../utilities/contents.html">XCU</a> | <a href="../functions/contents.html">XSH</a> | <a href="../xrat/contents.html">XRAT</a>
]</font></center>

<!--footer end-->
<hr size="2" noshade>
<hr>
<h4><a name="tag_02_04_01"></a>Footnotes</h4>

<dl compact>
<dt><a name="tag_foot_1">1.</a></dt>

<dd>As an example, the File System profiling option group provides underlying support for pathname resolution and file creation
which are needed by any interface in IEEE&nbsp;Std&nbsp;1003.1-2001 that parses a <i>path</i> argument. If a profile requires
support for the Device Input and Output profiling option group but does not require support for the File System profiling option
group, the profile must specify how pathname resolution is to behave in that profile, how the O_CREAT flag to <a href=
"../functions/open.html"><i>open</i>()</a> is to be handled (and the use of the character <tt>'a'</tt> in the <i>mode</i> argument
of <a href="../functions/fopen.html"><i>fopen</i>()</a> when a filename argument names a file that does not exist), and specify
lots of other details.</dd>

<dt><a name="tag_foot_2">2.</a></dt>

<dd>As an example, IEEE&nbsp;Std&nbsp;1003.1-2001 requires that implementations claiming to support the Range Memory Locking option
also support the Process Memory Locking option. A profile could require that the Range Memory Locking option had to be supplied
without requiring that the Process Memory Locking option be supplied as long as the profile specifies everything an application
writer or system implementor would have to know to build an application or implementation conforming to the profile.</dd>

<dt><a name="tag_foot_3">3.</a></dt>

<dd>Note that the profile could just specify that any use of the features not specified by the profile would produce undefined or
unspecified results.</dd>
</dl>
</body>
</html>