Defect in XSH sysconf

[yyyyyyy@xxxxxxx]

        Defect report from : Joanna Farley , Sun Microsystems

(Please direct followup comments direct to yyyyyyyyyyyyyy@xxxxxxxxxxxxx)

@ page 1469 line 45434 section sysconf objection {sunw-jf03-ld3}

Problem:

Defect code :  1. Error

We believe there is an issue with the description of _XOPEN_XCU_VERSION 
in SUSv3 and its usefulness for future product standards used for the 
creation of brands. 
   
In XPG3, XPG4, SUS, and SUSv2 (as well as with POSIX.1 and POSIX.2), it 
was possible to mix and match .1 and .2 implementations. (you could 
choose to implement XSH5 and XCU3 for instance, and get brands for XSH5 
conformance without getting a brand for XCU5 conformance.)  

This made sense since POSIX.1 and POSIX.2 were separate standards. With 
SUSv3, we have a single standard that covers functions and utilities.

In SUSv3 it seems that the description of _XOPEN_XCU_VERSION and what it 
should be set to is missing in the SUSv3 <unistd.h> description.  It's 
in the previous <unistd.h> description of SUSv2 (XSH5 page 1195). 

The reason for the removing of _XOPEN_XCU_VERSION is documented in
bwg2001-006 and covers the rationale as mentioned above (ie there is
now only one standard that covers functions and utilities).

We believe bwg2001-006 has not been fully applied to SUSv3 as there
are other occurences of _XOPEN_XCU_VERSION in sysconf() and that these
should also be removed as it can't be required to be understood by 
sysconf() with no definition of what it means.

See:
XBD page 409 (_SC_XOPEN_XCU_VERSION unistd.h definition)  
XSH page 1469 (_XOPEN_XCU_VERSION and _SC_XOPEN_XCU_VERSION in 
sysconf table)  
XSH page 1665 (index for _SC_XOPEN_XCU_VERSION and _XOPEN_XCU_VERSION)  
   

Action:

Remove XBD page 409 line 14520

Remove XSH page 1469 line 45434