RE: BRMS save and restore spooled files

Jim,

If you restore BRMS to the target system so BRMS know what was backed up on the 
tape(s) then you should be fine.  I'm assuming you're restoring Operation 
application and data on the target system too.  

Or as John suggested remote outqs would work very good also for just the spool 
files.

Ken H.

-----Original Message-----
From: midrange-l-bounces+kkh=nwnatural.com@xxxxxxxxxxxx
[mailto:midrange-l-bounces+kkh=nwnatural.com@xxxxxxxxxxxx]On Behalf Of
Jones, John (US)
Sent: Wednesday, February 22, 2006 9:49 AM
To: Midrange Systems Technical Discussion
Subject: RE: BRMS save and restore spooled files


If both LPARs will be up at the same time, set up one or more remote
outqs and let the SPLFs flow over the network.  Configure a VLAN and the
'network' is virtual and contained within the i5 frame.  Very fast.

John A. Jones, CISSP
Americas Information Security Officer
Jones Lang LaSalle, Inc.
V: +1-630-455-2787 F: +1-312-601-1782
john.jones@xxxxxxxxxx

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim Franz
Sent: Wednesday, February 22, 2006 11:34 AM
To: Midrange Systems Technical Discussion
Subject: Re: BRMS save and restore spooled files

Customer is adding a partition and moving part of operation into that
new partition.
Users in that new partition must have all their existing spooled files.
So we need to save and then restore "outqs with spooled files" to
another partition.
Some spooled files are *afpds with overlays. 99.9% are standard *scs.
jim
----- Original Message -----
From: "Holder, Ken" <kkh@xxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Wednesday, February 22, 2006 12:02 PM
Subject: RE: BRMS save and restore spooled files


> Jim
>
> Are you backing up (archiving) spool files currently with BRMS?  Or 
> only in need to verify restoring them to a different partition/system?
>
> Ken
>
> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx
> [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Jim Franz
> Sent: Wednesday, February 22, 2006 4:35 AM
> To: MIDRANGE-L@xxxxxxxxxxxx
> Subject: BRMS save and restore spooled files
>
>
> Can someone confirm that BRMS (V5R3) can save outqs, including the 
> spooled files within, and restore them to another partition, same outq

> name.
> I looked in the BRMS manual and it is unclear if any limitations.
> I did see one limit in the number of spooled files that can be saved 
> at one time, due to directory limits in the IFS.
> Any other limits?
> jim franz
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

> list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, 
> unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take 
> a moment to review the archives at 
> http://archive.midrange.com/midrange-l.
>
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

> list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, 
> unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take 
> a moment to review the archives at 
> http://archive.midrange.com/midrange-l.
> 


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.



This email is for the use of the intended recipient(s) only.  If you have 
received this email in error, please notify the sender immediately and then 
delete it.  If you are not the intended recipient, you must not keep, use, 
disclose, copy or distribute this email without the author's prior permission.  
We have taken precautions to minimize the risk of transmitting software 
viruses, but we advise you to carry out your own virus checks on any attachment 
to this message.  We cannot accept liability for any loss or damage caused by 
software viruses.  The information contained in this communication may be 
confidential and may be subject to the attorney-client privilege. If you are 
the intended recipient and you do not wish to receive similar electronic 
messages from us in future then please respond to the sender to this effect.