Novell NETWARE 6-DOCUMENTATION Manual page 2428

Viewing Winsock 2.0 Statistics
Viewing Winsock information can help you understand how the applications
on your server are interacting with the Winsock APIs provided in NetWare.
Error status conditions are distinguished with yellow and red for quick
identification.
To view Winsock resource information, diagnostic and debug information for
sockets, information for transport providers and active name space providers,
and a small set of general statistics, access the NetWare Winsock 2
Communication Framework page by clicking the Winsock 2.0 link in the
navigation frame.
The main content on this page shows the transport providers and active name
space providers, and a small set of general statistics as well as the following
links:
Winsock 2 Resources link
Opens the Winsock 2 Resources page. From this page you can view all
the Winsock resources that are currently in use, open sockets, Winsock 2
events, sockets that are used by a particular application, and protocol
objects within an active session and the number that are active.
To view a list of Winsock 2 sockets in use, click the Winsock 2 Socket
List link.
If an error condition exists (indicated by the status being highlighted
yellow or red), you might want to view the details of that socket. To
view the details of a socket and socket status, click the link for the
socket number you want to view on the Winsock 2 Socket list page.
To view the details of the error, click the Last Error link in the
Detailed Information for Socket Number x page.
To close an individual socket, click the Close Socket button at the
bottom of the socket detail page.
To view a list of all the events used by Winsock 2, click the Winsock 2
Event List link.
This list shows the socket number used by the event, the event
handle, the wait count, the wait status, the owning thread, and the
application that the event is used by.
If a socket number is listed, a link to the details page for that socket
is provided.
The Owning Thread link disassembles the code stack of the thread
that created the event.
Managing Servers Remotely
55