*** Original Author: ADSM-L @ MARIST - ** Remote User **; 04/22/98 09:40am
>Received: from VM.MARIST.EDU by AUDUCADM.DUC.AUBURN.EDU (IBM MVS SMTP V3R1)
> with TCP; Wed, 22 Apr 98 09:40:31 CDT
>Received: from VM.MARIST.EDU by VM.MARIST.EDU (IBM VM SMTP V2R3)
> with BSMTP id 6013; Wed, 22 Apr 98 10:21:52 EDT
>Received: from VM.MARIST.EDU (NJE origin LISTSERV@MARIST) by VM.MARIST.EDU
> (LMail V1.2b/1.8b) with BSMTP id 4558; Wed, 22 Apr 1998 10:21:46 -0400
>Received: from VM.MARIST.EDU by VM.MARIST.EDU (LISTSERV release 1.8c) with NJE
> id 7101 for ADSM-L AT VM.MARIST DOT EDU; Wed, 22 Apr 1998 10:21:41
> -0400
>Received: from MARIST (NJE origin SMTP@MARIST) by VM.MARIST.EDU (LMail
> V1.2b/1.8b) with BSMTP id 4544; Wed, 22 Apr 1998 10:21:41 -0400
>Received: from smtp3.ny.us.ibm.com by VM.MARIST.EDU (IBM VM SMTP V2R3) with
> TCP; Wed, 22 Apr 98 10:21:19 EDT
>Received: from relay3.server.ibm.com (relay3.server.ibm.com 9.14.2.100 ) by
> smtp3.ny.us.ibm.com (8.8.7/8.8.7) with ESMTP id KAA38336 for
> <ADSM-L AT VM.MARIST DOT EDU>; Wed, 22 Apr 1998 10:14:10 -0400
>Received: from US.IBM.COM (d03lms03.boulder.ibm.com 9.99.80.13 ) by
> relay3.server.ibm.com (8.8.7/8.8.7) with SMTP id KAA111376 for
> <ADSM-L AT VM.MARIST DOT EDU>; Wed, 22 Apr 1998 10:17:41 -0400
>Received: by US.IBM.COM (Soft-Switch LMS 2.0) with snapi via D03AU018 id
> 5030300020240395; Wed, 22 Apr 1998 10:28:49 -0400
>MIME-Version: 1.0
>Content-Type: text/plain; charset=iso-8859-1
>Content-Transfer-Encoding: quoted-printable
>Message-ID: <5030300020240395000002L052*@MHS>
>Date: Wed, 22 Apr 1998 10:28:50 -0400
>Reply-To: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>Sender: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>From: Bob La Brie <labrie AT US.IBM DOT COM>
>Subject: Re: Hung Server
>To: ADSM-L AT VM.MARIST DOT EDU
>
Rick, Have you applied PTF service UQ16502 etc. to bring ADSM upto 3.=
1.0.2.
This is the latest ADSM
server for MVS and is now available via PTF.?...I see y=
ou
indicated V3 R1.
We recently discovered a problem where certain threads =
can get
hung when ADSM attempts
to synchornize 2 threads. PQ14970 addresses this probl=
em and I
have a fix test currently
waiting to be verified on ADSM V2.
This APAR is targeted to be included with the next PTF =
service
level along with the
reclamation utilities. If it happens again take a com=
m dump
with SDATA=3D(CSA,RGN,LSQA),
open PMR and put the dump on testcase or index FTP ser=
ver.
If you can enter commands from the MVS console while =
it's
hung issue SHOW THREADS...
I might be able to verify whether it's PQ14970 from t=
hat.
Thanks, Bob La Brie ADSM Development
ADSM-L AT VM.MARIST DOT EDU on 04/22/98 06:48:00 AM
Please respond to ADSM-L AT VM.MARIST DOT EDU
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: Hung Server
ADSMer's,
Let's get the technical info out of the way:
Server: OS/390 V3 R1
Clients: NT 4.0, Novell 3.x, 4.x, V3 R1
I need some help with a problem we had last night. I saw a pos=
t
similar to my problem, and was wondering what the outcome was. Last
night when the backups starting running, the clients established
sessions with the server. It appeared that even though the sessions
were established, no tapes were being written to. As more and more
schedules kicked off, more sessions started until we hit our Maxsession=
s
threshold. We tried to cancel the sessions, but that did not work. We=
had to bring the ADSM server down and back up, and bounce all the
Services and Schedulers. The backups ran fine after that. We did not
see any error messages at all??? Any help would be much appreciated.
Thanks in advance,
Rick Smith
Maritz, Inc.
Storage & Security Administration
smithrr AT maritz DOT com
(314) 827-1584
=
*** Comments From: STEWAJM - Stewart, Mike; 04/22/98 10:41am
I highly recommend the 3.1.02 level of code for the
OS/390 server.
I was experiencing the 'hung sessions' problem, as
well as many other problems at the 3.1 level of code.
3.1.02 seems to have fixed many (but not all) of them.
|
