Failures          (Socket - IM)

DESCRIPTION
"Failures" shows the number of unsuccessful Immediate (IM) socket requests to
a Sun MTP system's Socket Server.


VALUES
When shown, "Failures" is a cardinal integer count. The value is left blank when
the Socket Server is not activated (see below).


INTERPRETATION
An IM socket request from an application can fail for a few reasons: the TRANSID
might not be present in the Sun MTP Program Control Table (PCT), the DATA 
argument might exceed the 35 character limit, or some other reason. Sun MTP 
prints a message into $KIXSYS/unikixmain.err for each failure. The message 
resembles the following example:

KIX2346E Socket request of type IM failed with EIBRESP=28 TRANSIDERR


CONCLUSIONS
This datapoint provides a general idea of the volume of unsuccessful IM requests
made to Socket Server. It does not, however, indicate why requests have failed.
Examine the error log file (see above) to identify the cause of any failures.
Note that Sun MTP cannot possibly record the number of failures that occur 
without a successful socket connection to the Socket Server. The application
must first connect to the Server for Sun MTP to recognize the existence of the
request. 

The Socket Screen does not display any values when the Socket Server is not 
activated. Sun MTP must be initiated with the -p parameter to activate the Socket
Server. The -p parameter takes a port number for an argument. For example, to 
run the Socket Server so that it listens on port 7000, you could start Sun MTP 
as follows:

$ kixstart -p 7000 
