Phil ESGUERRA ([log in to unmask]) wrote:
: I am troubleshooting this problem wherein a VPLUS user
: suddenly gets disconnected from the HP3000 with an NetIPC error 42.
 
[..snip..]
: Is there a way that I could put a 'trace' of the communication between
: the PC and HP3000, that can show the events happening just before the
: HP3000 disconnects with an error 42?
 
: I kinda remember that Reflection has something similar, but the trace
: is only one-sided. It does not show the PC side trace.
 
- I don't know if this is what you want, but you sure can get all kinds
  of traces from the HP3000 side.  The question is how much detail do you
  want and what kind of formatting tools would you like and/or are appropriate.
 
  NS stack(OSI-model)  Corresponding tracing alternative(s)
  -------------------  ------------------------------------
  7 Application(NS services etc. (means VT also))
 
                       Couple of ways, probably not too useful for your needs.
                       [ :DSLINE <rem_node>;trace=on,<service>,,,
                         :VTSERVER enable_am_trace (service internal trace)
  6 Presentation
  5 Session            NetIPC socket tracing, programmatic only
  4 Transport          :NETCONTROL TRACEON=...;PROT=[TCP|UDP|PXP]
  3 Network            :NETCONTROL TRACEON=...;PROT=[IP|ICMP|PROBE|ARP...]
  2 Link               :LINKCONTROL <linkname>;TRACE=ON,ALL
  1 Physical           LAN analyzers
 
  For all 3k traces there are 3k based formatters.  Personally, I prefer
  link tracing since that shows everything.  of course, there's more to
  analyze and it's more tedious to read but it gives you everything.
  I do have some tools to make life easier with link traces...
 
  Cheers,
  Eero.