*** Original Author: ADSM-L @ MARIST - ** Remote User **; 04/07/98 10:57am
>Received: from VM.MARIST.EDU by AUDUCADM.DUC.AUBURN.EDU (IBM MVS SMTP V3R1)
> with TCP; Tue, 07 Apr 98 10:56:47 CDT
>Received: from VM.MARIST.EDU by VM.MARIST.EDU (IBM VM SMTP V2R3)
> with BSMTP id 3678; Tue, 07 Apr 98 11:39:30 EDT
>Received: from VM.MARIST.EDU (NJE origin LISTSERV@MARIST) by VM.MARIST.EDU
> (LMail V1.2b/1.8b) with BSMTP id 1737; Tue, 7 Apr 1998 11:39:28 -0400
>Received: from VM.MARIST.EDU by VM.MARIST.EDU (LISTSERV release 1.8c) with NJE
> id 9449 for ADSM-L AT VM.MARIST DOT EDU; Tue, 7 Apr 1998 11:39:23
> -0400
>Received: from MARIST (NJE origin SMTP@MARIST) by VM.MARIST.EDU (LMail
> V1.2b/1.8b) with BSMTP id 1723; Tue, 7 Apr 1998 11:39:23 -0400
>Received: from mercury.csc.com by VM.MARIST.EDU (IBM VM SMTP V2R3) with TCP;
> Tue, 07 Apr 98 11:39:22 EDT
>Received: from va-fch34.vtc.csc.com (csc.com) 20.1.6.97 by mercury.csc.com
> with smtp (Exim 1.82 #3) id 0yMaTL-0001ew-01; Tue, 7 Apr 1998
> 11:39:39 -0400
>Received: by csc.com(Lotus SMTP MTA Internal build v1.2_13 (582.1 3-2-1998))
> id 852565DF.00560917 ; Tue, 7 Apr 1998 11:39:44 -0400
>X-Lotus-FromDomain: CSC
>Mime-Version: 1.0
>Content-type: text/plain; charset=us-ascii
>Content-Disposition: inline
>Message-ID: <852565DF.00557798.00 AT csc DOT com>
>Date: Tue, 7 Apr 1998 11:39:12 -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: Virginia Hysock <Virginia_L_Hysock AT CSC DOT COM>
>Subject: ADSM CPU Dispatch Priority
>To: ADSM-L AT VM.MARIST DOT EDU
>
ADSM MVS Server 2.1.13
Can anyone running an MVS server provide me with information on the
dispatch priority you assign to ADSM? We are experiencing some frustrating
problems in getting admin tasks performed due to lack of cpu, and were
wondering what others might be doing in this area. We had difficulty
completing migration, reclamation and copy pool tasks all week last week
(monthend). Thanks for any info you can provide,
Ginny
*** Comments From: STEWAJM - Stewart, Mike; 04/07/98 12:40pm
We run ADSM at the same dispatching priority as the other
'random' STC's, such as job schedulers, print management,
and other what-nots. This is just below JES,VTAM,TCP, etc.,
but above batch and TSO. Why?
Because ADSM (currently) only dispatches on one CPU and
we have a 4-processor box, ADSM is limited to 1/4th of our
processors at a time. That, coupled with scheduling
some of the more cpu-intensive operations during 'off-hours'
seems to keep ADSM from impacting our interactive/batch
workloads too much.
I assume that once ADSM does a better job of multi-tasking
it will be able to consume more than 1 processor, and
we will probably have to revisit our dispatch priority
to keep ADSM from interfering too much with
more critical work.
In your case, either ADSM is spinning one processor as fast
as it can, in which case there isn't any more to give it,
or other workload is taking the CPU, and you'll have to
decide if you really want to slow down the other workload by taking
the CPU away from it to give to ADSM.
|
