*** Original Author: ADSM-L @ MARIST - ** Remote User **; 04/07/98 03:42am
>Received: from VM.MARIST.EDU by AUDUCADM.DUC.AUBURN.EDU (IBM MVS SMTP V3R1)
> with TCP; Tue, 07 Apr 98 03:42:26 CDT
>Received: from VM.MARIST.EDU by VM.MARIST.EDU (IBM VM SMTP V2R3)
> with BSMTP id 3029; Tue, 07 Apr 98 04:38:42 EDT
>Received: from VM.MARIST.EDU (NJE origin LISTSERV@MARIST) by VM.MARIST.EDU
> (LMail V1.2b/1.8b) with BSMTP id 0315; Tue, 7 Apr 1998 04:38:41 -0400
>Received: from VM.MARIST.EDU by VM.MARIST.EDU (LISTSERV release 1.8c) with NJE
> id 5546 for ADSM-L AT VM.MARIST DOT EDU; Tue, 7 Apr 1998 04:38:39
> -0400
>Received: from MARIST (NJE origin SMTP@MARIST) by VM.MARIST.EDU (LMail
> V1.2b/1.8b) with BSMTP id 0303; Tue, 7 Apr 1998 04:38:39 -0400
>Received: from vevdmz01.nestec.ch by VM.MARIST.EDU (IBM VM SMTP V2R3) with TCP;
> Tue, 07 Apr 98 04:38:37 EDT
>Received: from vevnat01.nestec.ch by vevdmz01.nestec.ch with SMTP (Microsoft
> Exchange Internet Mail Service Version 5.0.1460.8) id 2G9BK94M; Tue,
> 7 Apr 1998 10:38:54 +0200
>Received: by vevnat01.nestec.ch with SMTP (Microsoft Exchange Server Internet
> Mail Connector Version 4.0.995.52) id
> <01BD6211.6AB2C9F0 AT vevnat01.nestec DOT ch>; Tue, 7 Apr 1998
> 10:39:18 +020
>X-Mailer: Microsoft Exchange Server Internet Mail Connector Version 4.0.995.52
>MIME-Version: 1.0
>Content-Type: text/plain; charset="iso-8859-1"
>Content-Transfer-Encoding: quoted-printable
>Message-ID:
> <c=CH%a=INFONET%p=NESTLE%l=VEVICS03-980407083905Z-1478 AT vevnat01.nestec DOT
> ch>
>Date: Tue, 7 Apr 1998 10:39:05 +0200
>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: "Lambelet,Rene,VEVEY,FC-SIL/INF." <Rene.Lambelet AT NESTLE DOT
>COM>
>Subject: Re: ADSM MVS No acceess during long running queries
>To: ADSM-L AT VM.MARIST DOT EDU
>
>Hello Andreas,
>
>I once read something on the list saying you could try the server =
parameter:
>
>MPTHREADING YES instead of NO. It allows ADSM to use // TCB's.
>
>Please tell us if this is a solution.
>
>Ren=E9 Lambelet - (3543 - *A581=20
>Nestec SA - 55, Av. Nestl=E9 - CH-1800 Vevey
>T=E9l: ++41/21/924'35'43 / Fax: ++41/21/924'45'89
>E-Mail: rene.lambelet AT nestle DOT com
>
>
>
>-----Original Message-----
>From: buser andreas SMTP:andreas.buser AT BASLER DOT CH
>Sent: Tuesday, April 07, 1998 4:29 PM
>To: ADSM-L AT VM.MARIST DOT EDU
>Subject: ADSM MVS No acceess during long running queries
>
>Does anyone have the same Problem which I reported to IBM:
>
>If we do a long running query on ADSM MVS Server V3.1.0, no further
>Console Cmds are posssible. NO Client can connect to the server, not
>even Admin Clients, until this request has finished.
>
>We saw this problem 1-2 years ago in v2.1 of ADSM. Why do we have to go
>though that pain again.
>
>What is the PTF Nummer for Version 3 for ADSM MVS ?
>
>Kind Regards
>A. Buser
>
>------------------------------------------
>Andreas Buser
>
>
>Tel: 0041 61 285 73 21
>
>Email: Andreas.Buser AT Basler DOT ch
>
>Adress:
>
>Andreas Buser
>Abt. Informatik
>Aeschengraben 21
>4002 Basel
>Switzerland
*** Comments From: STEWAJM - Stewart, Mike; 04/07/98 07:37am
I don't seem to have the problem with long admin commands locking
up ADSM. However I have other situations where ADSM
locks up and won't respond to clients, admin session, etc.
For example at the end of my scheduled backup window,
ADSM issues a message for all the nodes which missed the
scheduled backup. During this time ADSM pretty much locks up.
I tried turned on multithreading, and it did fix this problem.
However I turned it off pretty quickly because performance
for other operations slowed significantly.
IBM was working on improving multitasking. Maybe it is in
the maintenance which was placed on the FTP server?
I haven't seen the list of problems fixed by this maintenance.
|
