RE: P7 V7R3 to P9 V7R3 migration recommendations / suggestions -- MIDRANGE-L

Subject: RE: P7 V7R3 to P9 V7R3 migration recommendations / suggestions
From: "Musselman, Paul" <pmusselman@xxxxxxxxxxxxxxxx>
Date: Thu, 1 Nov 2018 20:10:37 +0000
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

What's the system overhead difference between a single-threaded restore in restricted state vs 4-at-a-time in mostly restricted?

I know the system has to read the library header from the tape, then spend a lot of time allocating space. In fully-restricted state it doesn't have to check for any kind of conflict, and just grabs space then restores data. In mostly-restricted, you have 4 jobs grabbing for space.

What's the tipping point between the two?

Or has faster system hardware overcome the conflict?

Paul E Musselman
PaulMmn@xxxxxxxxxxxxx

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: P7 V7R3 to P9 V7R3 migration recommendations / suggestions , Jim Oberholtzer
RE: P7 V7R3 to P9 V7R3 migration recommendations / suggestions , Rob Berendt

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.