try changing the local client to use a shared memory connection.

Then try to login.

To get root cause, kill -11 will create a core dump.

Jeff Bach

> -----Original Message-----
> From: Joshua S. Bassi [SMTP:jbassi AT IHWY DOT COM]
> Sent: Tuesday, October 30, 2001 9:32 AM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Re: server is running, but cannot make any connections to it
>
> Try waiting some arbitrary amount of time (10-20 min.) of inactivity and
> then all that is left to do is to kill the process.
>
>
> --
> Joshua S. Bassi
> Independent IT Consultant
> IBM Certified - AIX/HACMP, SAN, Shark
> Tivoli Certified Consultant- ADSM/TSM
> Cell (408)&(831) 332-4006
> jbassi AT ihwy DOT com
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf 
> Of
> Charles Anderson
> Sent: Tuesday, October 30, 2001 6:47 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: server is running, but cannot make any connections to it
>
> Folks,
>
> I have much bad problem.. We're running tsm server 4.1.4 on solaris 2.6.
> The dsmserv process is still running, but I can't make any client (
> administrative or backup ) connections to it.  I'm about to call
> support, but I was wondering if anyone on the list was perhaps awake
> already and had some experienced suggestions as to a relatively painless
> path to take to recover from this.
>
> Thanks,
> ed
>
> Ed Anderson
> Backup / Unix Systems Administrator
> Dept. of Information Systems
> University of Mississippi Medical Center
>
> +++++++++++++++++++++++++++++++++++++
> The information in this email is considered
> confidential information. In the event that
> you received this email by misdelivery/accident
> please delete it and disregard its contents.
> +++++++++++++++++++++++++++++++++++++


**********************************************************************
This email and any files transmitted with it are confidential
and intended solely for the individual or entity to
whom they are addressed.  If you have received this email
in error destroy it immediately.
**********************************************************************