Defect in XBD limits.h

[yyyyyyyy@xxxxxxxxxx]

        Defect report from : William L. Toth , IBM Austin

(Please direct followup comments direct to yyyyyyyyyyyyyy@xxxxxxxxxxxxx)

@ page 252 line 8814 section limits.h comment {WLT-VSRTC-3}

Problem:

Edition of Specification (Year): 2004

Defect code :  3. Clarification required

The description of TRACE_NAME_MAX and TRACE_EVENT_NAME_MAX doesn't state 
whether or not the length includes the terminating null character.

The references from the  standard.

TRC {TRACE_EVENT_NAME_MAX}
 Maximum length of the trace event name.
 Minimum Acceptable Value: {_POSIX_TRACE_EVENT_NAME_MAX}

TRC {TRACE_NAME_MAX}
 Maximum length of the trace generation version string or of the trace   stream 
name.
 Minimum Acceptable Value: {_POSIX_TRACE_NAME_MAX}


TRC {_POSIX_TRACE_EVENT_NAME_MAX}
 The length in bytes of a trace event name.
 Value: 30

TRC {_POSIX_TRACE_NAME_MAX}
 The length in bytes of a trace generation version string or a trace     stream 
name. Value: 8

Other "NAME" definitions state whether or not the terminating null is included 
in the length. for example:

{_POSIX_HOST_NAME_MAX}
 Maximum length of a host name (not including the terminating null)
  as returned from the gethostname( ) function.
 Value: 255

{_POSIX_NAME_MAX}
 Maximum number of bytes in a filename (not including terminating        null).
 Value: 14

Action:

Following the examples above, add the wording "(not including terminating null)