<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: TDC: Data errors in INET (internet) record in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/tdc-data-errors-in-inet-internet-record/m-p/3976685#M83009</link>
    <description>Stupid question : where is the T of TDC standing for (yes I know Perf Data Coll) ?&lt;BR /&gt;&lt;BR /&gt;Wim</description>
    <pubDate>Tue, 10 Apr 2007 10:22:57 GMT</pubDate>
    <dc:creator>Wim Van den Wyngaert</dc:creator>
    <dc:date>2007-04-10T10:22:57Z</dc:date>
    <item>
      <title>TDC: Data errors in INET (internet) record</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tdc-data-errors-in-inet-internet-record/m-p/3976684#M83008</link>
      <description>&lt;!--!*#--&gt;There are problems with the data reported by TDC within both the "TCP" and the "ICMP" parts of the INET data record. These problems affect all current and previous releases of TDC V2.x and TDC_RT V2.x.&lt;BR /&gt;&lt;BR /&gt;TDC_INET data records: "TCP" data&lt;BR /&gt;---------------------------------&lt;BR /&gt;&lt;BR /&gt;The "TCP" data problem described here will be dealt with in a future release, which will also correct previously-collected data records as they are read.&lt;BR /&gt;&lt;BR /&gt;A data item, TDC_INET_TCP_RCVDUPBYTE, SHOULD have been represented in the INET record, between TDC_INET_TCP_RCVDUPPACK and TDC_INET_TCP_RCVPARTDUPPACK; that data item was omitted from the record definition.&lt;BR /&gt;&lt;BR /&gt;For now, the following TDC_INET_TCP_* data items can be interpreted as described below.&lt;BR /&gt;&lt;BR /&gt;The effect of the data item omission is that:&lt;BR /&gt;&lt;BR /&gt;1) The value reported for TDC_INET_TCP_RCVPARTDUPPACK is actually the value that would have been reported for the missing TDC_INET_TCP_RCVDUPBYTE;&lt;BR /&gt;&lt;BR /&gt;2) The value reported for TDC_INET_TCP_RCVPARTDUPBYTE is actually the value that should have been reported for TDC_INET_TCP_RCVPARTDUPPACK;&lt;BR /&gt;&lt;BR /&gt;3) The value reported for TDC_INET_TCP_RCVOOPACK is actually the value that should have been reported for TDC_INET_TCP_RCVPARTDUPBYTE;&lt;BR /&gt;&lt;BR /&gt;4) And, in general, for the following list of data items, the correct value is the value reported for the immediately following data item in the TDC INET record (and in the list below):&lt;BR /&gt;&lt;BR /&gt;TDC_INET_TDC_RCVPARTDUPPACK&lt;BR /&gt;TDC_INET_TCP_RCVPARTDUPBYTE&lt;BR /&gt;TDC_INET_TCP_RCVOOPACK&lt;BR /&gt;TDC_INET_TCP_RCVOOBYTE&lt;BR /&gt;TDC_INET_TCP_RCVPACKAFTERWIN&lt;BR /&gt;TDC_INET_TCP_RCVBYTEAFTERWIN&lt;BR /&gt;TDC_INET_TCP_RCVAFTERCLOSE&lt;BR /&gt;TDC_INET_TCP_RCVWINPROBE&lt;BR /&gt;TDC_INET_TCP_RCVDUPACK&lt;BR /&gt;TDC_INET_TCP_RCVACKTOOMUCH&lt;BR /&gt;TDC_INET_TCP_RCVACKPACK&lt;BR /&gt;TDC_INET_TCP_RCVACKBYTE&lt;BR /&gt;TDC_INET_TCP_RCVWINUPD&lt;BR /&gt;TDC_INET_TCP_NOOUTPUTBUFFS&lt;BR /&gt;TDC_INET_TCP_SKIPCHECKSUM&lt;BR /&gt;TDC_INET_TCP_PENDINGCONNECTIONDROPPED&lt;BR /&gt;TDC_INET_TCP_IGNORED_TSOPT&lt;BR /&gt;TDC_INET_TCP_PROCESSING_TSOPT&lt;BR /&gt;TDC_INET_TCP_RECYCLED_TPS&lt;BR /&gt;&lt;BR /&gt;Note that a correct value for TDC_INET_TCP_RECYCLED_TPS cannot be recovered.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;TDC_INET data records: "ICMP" data&lt;BR /&gt;---------------------------------&lt;BR /&gt;&lt;BR /&gt;Only the first 3 of the 8 "ICMP" data items provide valid values: TDC_INET_ICMP_ERROR, TDC_INET_ICMP_OLDSHORT, and TDC_INET_ICMP_OLDICMP.&lt;BR /&gt;&lt;BR /&gt;A "going-forward" fix for the "ICMP" data will also be provided in a future release. That fix will not be able to recover values for the other 5 "ICMP" data items from previously-collected data records when reading files.&lt;BR /&gt;&lt;BR /&gt;Lee Clark&lt;BR /&gt;OpenVMS Engineering</description>
      <pubDate>Fri, 06 Apr 2007 10:15:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tdc-data-errors-in-inet-internet-record/m-p/3976684#M83008</guid>
      <dc:creator>clarklk</dc:creator>
      <dc:date>2007-04-06T10:15:14Z</dc:date>
    </item>
    <item>
      <title>Re: TDC: Data errors in INET (internet) record</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tdc-data-errors-in-inet-internet-record/m-p/3976685#M83009</link>
      <description>Stupid question : where is the T of TDC standing for (yes I know Perf Data Coll) ?&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Tue, 10 Apr 2007 10:22:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tdc-data-errors-in-inet-internet-record/m-p/3976685#M83009</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2007-04-10T10:22:57Z</dc:date>
    </item>
    <item>
      <title>Re: TDC: Data errors in INET (internet) record</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/tdc-data-errors-in-inet-internet-record/m-p/3976686#M83010</link>
      <description>"The" - I think.</description>
      <pubDate>Tue, 10 Apr 2007 10:49:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/tdc-data-errors-in-inet-internet-record/m-p/3976686#M83010</guid>
      <dc:creator>Sebastian Bazley</dc:creator>
      <dc:date>2007-04-10T10:49:18Z</dc:date>
    </item>
  </channel>
</rss>

