RE: Tape category *SHARE400 *NOSHARE and restore from type 21 Save

We normally assign tapes to be used for Options 21 or 22 to category AVAIL2122. These are (hopefully) initialized and blank. We then SETTAPCGY to AVAIL2122 so when the Option 21/22 looks for a *MOUNTED category it can find a tape. And the tape is re-assigned to OPTION2122 when the save is completed.

So far, we haven't had to do a complete system restore from one of our tapes, although we regularly restore bits and pieces so the programmers can figure out what the users have been doing worng! When we load such tapes into the tape monster we assign them to category TOBRESTORE so the backup process can't grab them by mistake.

Are we setting ourselves up for problems if we ever need a complete restore?

Paul E Musselman
PaulMmn@xxxxxxxxxxxxx

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jack Woehr
Sent: Wednesday, March 07, 2018 1:41 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: Tape category *SHARE400 *NOSHARE and restore from type 21 Save

Well, what confused me, Jim, is that a tape was produced in a standalone
drive and GO SAVE seems to have no notion itself of *SHARE400 etc.

I certainly have, in using tape libraries, changed a fresh tape from
*NOSHARE to *SHARE400 routinely, as our tape libraries are themselves
shared.

I just wondered if there was some "magic" NOSHARE bit at Save type 21 time
that spoiled a tape forever from being restored to a different LPAR.