OK, since no one responded to my rambling earlier, I'll try asking a more
definite question.

The showconn listing below should have one more socket to display.

showconn job=#j10948


JOBNUM  INTRO DATE AND TIME    LDEV   USERNAME
 REMOTE ADDRESS  RPORT  LPORT  FLAGS   PIN(PROGRAM)
#J10948 THU MAR  2 2000 02:40    10   ASPCPLTS,MGR.CUTEST1,DATA
    192.168.1.26  1534  31011  utcind 1936(PCCNTL.PGMS.SPECTEST)
                        31012  utl-nt 1879(PCCNTL.PGMS.SPECTEST)
                        31013  utl-nt  158(PCCNTL.PGMS.SPECTEST)
    192.168.1.26  1499  31014  utcind 1367(PCCNTL.PGMS.SPECTEST)

Total processes checked:   21
Processes with sockets :    4
Total sockets open     :    4

The showproc listing shows pin 525 in the MSG state. This is the pin that
should have opened socket 31010.
What is this MSG state?
Does anyone know why a process trying to initialize a socket would get into
this state and never leave?
If there is something wrong with the socket is there a way to *reset* a
particular socket number in NETTOOL or some such utility?

%filter "showproc job=#j10948" "PCCNTL"
B151  0:00.425  IPC    J10948      1936 (PCCNTL.PGMS.SPECTEST) spectest
B151  0:00.396  IPC    J10948      1879 (PCCNTL.PGMS.SPECTEST) spectest
B151  0:00.383  IPC    J10948      158  (PCCNTL.PGMS.SPECTEST) spectest
B151  0:00.877  IPC    J10948      1367 (PCCNTL.PGMS.SPECTEST) spectest
B151  0:00.227  MSG    J10948      525  (PCCNTL.PGMS.SPECTEST) spectest
%

Thanks to anyone who can shed some light.

Tony White