RE: Full save with IASP

I've never dealt with iASP before, but I know a bit so I thought it might help. That's why my plan calls for using an iASP.


Additional files will be added to the iASP Tue-Sat at 0300, so it would be static during my backup window.

#1. We're allergic to "buy" around here, so that doesn't seem likely.

#2. Would I just use a SAV command like a normal IFS save for the iACS? Any way to keep it on the same tape as the GO SAVE 21?



-----Original Message-----
From: Jim Oberholtzer [mailto:midrangel@xxxxxxxxxxxxxxxxx]
Sent: Wednesday, April 25, 2018 11:33 AM
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxx>
Subject: RE: Full save with IASP

Justin:

That's one of the big reasons iASP was created was to do just what you are doing now.

While Rob is correct that the save/restore times for IFS based objects is depended on a bunch of factors, it really does not matter much if it's in an iASP or not.

The trick is determining if the iASP is volatile to the point where it needs frequent back up, or is it reasonably static? You can do a full save of the *SYSBAS objects without the iASP to set that up for recovery, clearly saving
time there, and then save the iASP on a separate save. I do this since a
recovery is two steps anyway. Also depending on the reason for the recovery on *SYSBAS you may not need to recover the iASP independently anyway.

So:
1) Buy BRMS and let it back up the system while you sleep. Does it automatically. Three months of your time and it pays for itself. It will handle the iASP too. Backup *SYSBAS, start the system then back up iASP.
Simple.

2) Set up two saves. One for the *SYSBAS and do that one at 0:darkthirty as needed. The second save can be done any time you want to just to the iASP, again depending on the data you put there.


--
Jim Oberholtzer
Agile Technology Architects