ADSM-L

Re: ADSM MVS Multitasking

1996-07-17 09:01:56
Subject: Re: ADSM MVS Multitasking
From: "Pittson, Timothy ,Corp,US" <tpittson AT HIMAIL.HCC DOT COM>
Date: Wed, 17 Jul 1996 09:01:56 -0400
James,
        ADSM is capable of multi-tasking on MVS insofar as you can run multiple
concurrent processes running within ADSM..  However,  in relation to
MVS, ADSM is restricted to 1 CP. For instance, if you have a 3090-500J
mainframe running MVS, ADSM can only use 1 of the 5 processors or about
20% of your total processing capacity. This has been a big restriction
for us as we normally see ADSM topped out at 99% CPU utilization during
incremental backups for 6-10 hours every night   With newer and faster
mainframes I don't think this is as big a problem but is definitely an
issue for folks running older mainframes like us (21 mips per engine)
and may also be an issue with some of the early CMOS mainframes.

Tim Pittson
tpittson AT himail.hcc DOT com

>----------
>From:  James Kleberg[SMTP:Kleberg_James_R/svoa0001 AT SSB DOT COM]
>Sent:  Wednesday, July 17, 1996 8:38 AM
>To:    Multiple recipients of list ADSM-L
>Subject:       ADSM MVS Multitasking
>
>        On Page 3 of the ADSM V2R1 Performance Tuning Guide (section
>     entitled "Communication Protocols), the following statements are
>made:
>
>        "On MVS the major performance distinction is that TCP/IP runs
>as a
>     single task on a single central processor (CP). ..... In addition,
>the
>     ADSM MVS server is also restricted to a single CP, but has
>     multi-tasking capabilities."
>
>        Could someone elaborate on the MVS server's architecture and
>     whether or not any multi-processing is possible?  What about
>migrating
>     data from one copy group to the next vs. normal backup activity?
>
>        Thanks.
>
<Prev in Thread] Current Thread [Next in Thread>