Reply to MPThreading & V3

*** Original Author:  ADSM-L @ MARIST - ** Remote User **; 03/22/98 08:30pm

>Received: from VM.MARIST.EDU by AUDUCADM.DUC.AUBURN.EDU (IBM MVS SMTP V3R1)
>   with TCP; Sun, 22 Mar 98 20:29:49 CST
>Received: from VM.MARIST.EDU by VM.MARIST.EDU (IBM VM SMTP V2R3)
>   with BSMTP id 3176; Sun, 22 Mar 98 20:22:22 EST
>Received: from VM.MARIST.EDU (NJE origin LISTSERV@MARIST) by VM.MARIST.EDU
> (LMail V1.2b/1.8b) with BSMTP id 4035; Sun, 22 Mar 1998 20:22:21 -0500
>Received: from VM.MARIST.EDU by VM.MARIST.EDU (LISTSERV release 1.8c) with NJE
>          id 7660 for ADSM-L AT VM.MARIST DOT EDU; Sun, 22 Mar 1998 20:22:18 
> -0500
>Received: from MARIST (NJE origin SMTP@MARIST) by VM.MARIST.EDU (LMail
>          V1.2b/1.8b) with BSMTP id 4023; Sun, 22 Mar 1998 20:22:18 -0500
>Received: from wormhole by VM.MARIST.EDU (IBM VM SMTP V2R3) with TCP; Sun, 22
>          Mar 98 20:22:02 EST
>Received: (from uucp@localhost) by wormhole (SMI-8.6/8.6.12) id MAA15285 for
>          <ADSM-L AT vm.marist DOT edu>; Mon, 23 Mar 1998 12:23:17 +1100
>Received: from nccfx400.dss.gov.au(203.13.15.26) by wormhole via smap (V1.3) id
>          sma015221; Mon Mar 23 12:23:15 1998
>Received: from top1dt1.dss.gov.au by nccfx400.dss.gov.au; Mon, 23 Mar 1998
>          12:18:59 +1100
>Received: by top1dt1.dss.gov.au(Lotus SMTP MTA v1.1 (385.6 5-6-1997))  id
>          4A2565D0.000D03F5 ; Mon, 23 Mar 1998 12:22:09 +1000
>X-Lotus-FromDomain: NOTES
>Mime-Version: 1.0
>Content-type: text/plain; charset=US-ASCII
>Message-ID:  <4A2565D0.000CCD18.00 AT top1dt1.dss.gov DOT au>
>Date:         Mon, 23 Mar 1998 12:22:07 +1000
>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:         "Field, Anthony" <Anthony.Field AT CENTRELINK.GOV DOT AU>
>Subject:      MPThreading & V3
>To:           ADSM-L AT VM.MARIST DOT EDU
>
Hi all,

Can anyone tell me what the MPThreading option is and what does it do. It
shows up when I query the options for an ADSM v3.1 server on OS/390. By
default it is set to no but I can change it to yes.

I can't seem to find any info on it in the manuals.

Tony

*** Comments From: STEWAJM - Stewart, Mike; 03/23/98 07:43am
It enables dispatching on multiple TCB's, allowing
multiprocessing.  However, according to IBM support,
it can result in 'degradation.'  They are
working on 'optimizing' TCB switching.

My ADSM system is extremely CPU bound, and one of the
things I was really looking for was multiprocessing.
When my schedules expire, for example, ADSM basically locks up for
an hour while it drives one CPU at 100%.  Same at start up
time when schedule manager is building schedules.
During these times ADSM bascially doesn't respond to
administrative commands (or responds _very_ slowly),
and won't accept client sessions.

So I was very interested in the multiprocessing which was
supposed to be in V3.  I tried MPthreading for a day.
It fixed the lock up problem.  But everything else
ran _much_ slower.  For example, retreiving a list of
files for restore took a long time.  So I turned
MPthreading back off.