AAAhhhhhh, one little detail... (but more info is needed)
     WHY IS IT TRYING TO ACTIVATE THE GUI INTERFACE ?
     Is this a scheduled event ?
     Is it on a platform that has a GUI interface ? (OS/2 or UNIX)
     I looked on my servers and the only TCP/IP errors that I noticed were
     far enough back where I don't have the activity log information still.
     I did notice that I did, in my own error save file, that what I did
     get was during a reboot of the server....
     *******NOTE: I can't remember where, when, who passed this bit of info
     on but... IF YOU BOUNCE ADSM (my servers are AIX) RUN A NETSTAT AND AS
     LONG AS THERE ARE "CLOSE_WAIT" (or what ever the specific text is) ON
     PORT 1500 (or what ever you assigned as default) DO NOT RESTART THE
     SERVER !
     There might be absolutely nothing to this but like I say... something
     about this is stuck in my head and if I see anything hanging on port
     1500 once ADSM is shut down I wait for it to clear....  OH I REMEMBER!
     If an ADMINISTRATOR was logged on but ADSM dropped their session due
     to lack of activity (thus when I do a q sess I see nothing) and then I
     HALT the server their DSMADM task (if running on the server) hangs
     onto port 1500... I always have to KILL the process to get 1500 freed
     up.  So everytime I halt the server I do a "ps -ef | grep dsm" and
     look for anything... I usually find a dsmadm or a dsmadmc task, then I
     check who the parent process is (usually one of the other folks in the
     group) to make sure someone didn't sneak in something and it was
     messing up, then I kill the process... then within 5 minutes
     everything clears (ck via netstat) from port 1500 and I restart the
     server...
     I view this as a personal problem on my behalf and nothing to do with
     the ADSM code... I truely love the way the servers push idle sessions
     out and then they can reconnect just by pressing enter... and I can't
     knock the folks who have dialed in from home and gotten up to fix a
     bite to eat and had their session get pushed out because I'm probably
     the biggest guilty party of such activity :-(
     JUST DOUBLE CHECK HANGING TASKS ON PORT 1500 WHEN YOU BOUNCE/START
     ADSM...................................
     later
           Dwight
     PS: I don't have logic manuals and I had nothing to do with the
     creation of the code so I can't even begin to guess-duh-mate what end
     results might come from starting the server with a task hung on port
     1500.....


______________________________ Reply Separator _________________________________
Subject: TCP/IP errors
Author:  ADSM-L at unix,uu/dd.RFC-822=ADSM-L\@VM\.MARIST\.EDU
Date:    10/8/96 10:25 PM


This problem is intensifying every week, my backups have been missing or
failing.  All the error logs show TCP errors. I have an AIX server using
v2.1.0.9.

The following is an extract from the servers errorlog on/about the time
all backup fail.


10/06/96   17:21:54  commtcp.c (1658): TcpRead: Error reading data, rc:
73
10/06/96   17:21:54  session.c (1576): sessRecvVerb: Error -50 from call
to 'readRtn'.
10/06/96   17:21:54  cuadmin.c ( 233): cuGetAdmCmdResp: Received a
communication read error: rc: -50
10/06/96   17:21:54  commtcp.c (1435): TcpOpen(): setsockopt(SO_SNDBUF):
errno = 74
10/06/96   17:21:54  commtcp.c (1446): TcpOpen(): setsockopt(SO_RCVBUF):
errno = 74
10/06/96   17:21:54  commtcp.c (1482): TcpOpen(): setsockopt failed on
one or more options
10/06/96   18:29:44  anscrec.c ( 182): QueryRecordData: WmsSendMessage
sending message QUERYLIST failed.  RC=505.
10/06/96   18:29:44  ANS8001E Internal error in this graphical user
interface.  Try one of the following in the order listed:  1) close this
window and reopen it  2) close this object and reopen it  3) shut down
this graphical user interface and restart it  4) save dsmerror.log
residing in the directory specified by DSMG_LOG and contact your service
representative for assistance.|Graphical User Interface - Internal error
10/07/96   06:02:53  TcpRead: Error reading data, rc: 73
10/07/96   06:02:53  sessRecvVerb: Error -50 from call to 'readRtn'.
10/07/96   06:02:53  TcpOpen(): setsockopt(SO_SNDBUF): errno = 74
10/07/96   06:02:53  TcpOpen(): setsockopt(SO_RCVBUF): errno = 74
10/07/96   06:02:53  TcpOpen(): setsockopt failed on one or more options
10/07/96   06:35:34  commtcp.c (1658): TcpRead: Error reading data, rc:
73
10/07/96   06:35:34  session.c (1576): sessRecvVerb: Error -50 from call
to 'readRtn'.
10/07/96   06:35:34  cuadmin.c ( 233): cuGetAdmCmdResp: Received a
communication read error: rc: -50
10/07/96   06:35:34  commtcp.c (1435): TcpOpen(): setsockopt(SO_SNDBUF):
errno = 74
10/07/96   06:35:34  commtcp.c (1446): TcpOpen(): setsockopt(SO_RCVBUF):
errno = 74
10/07/96   06:35:34  commtcp.c (1482): TcpOpen(): setsockopt failed on
one or more options
10/07/96   08:12:26  anscrec.c ( 182): QueryRecordData: WmsSendMessage
sending message QUERYLIST failed.  RC=505.
10/07/96   08:12:26  ANS8001E Internal error in this graphical user
interface.  Try one of the following in the order listed:  1) close this
window and reopen it  2) close this object and reopen it  3) shut down
this graphical user interface and restart it  4) save dsmerror.log
residing in the directory specified by DSMG_LOG and contact your service
representative for assistance.|Graphical User Interface - Internal error


ANY comment/ideas is welcome at this point!

Thanks..
Bill Aughenbaugh
QA/Security Administrator
Aughenbw AT moodys DOT com