MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » July 2014

RE: BRMS Saving of Spooled Files Question



fixed



Hi,

I was able to confirm that indeed the spooled files were saved as per
your advise provided and will test a restore on one of our testing lpars
this week.

Thank you for the information and feedback, very much appreciated.



Laura Roberts
System Administrator, Information Systems and Technology

306.667.5260
Saskatchewan Blue Cross
sk.bluecross.ca I push2play.ca

Please consider the environment before printing this email.










From: "Steinmetz, Paul" <PSteinmetz@xxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'"
<midrange-l@xxxxxxxxxxxx>,
Date: 22/07/2014 04:11 PM
Subject: RE: BRMS Saving of Spooled Files Question
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



Laura,



Here is good IBM link for spoolfiles, save and restore.

Before when we were using a list, and we had to restore using WRSPLFMBRM,
each spoolfile, one at a time was taking 4 minutes per spoolfile.

There is API available that will speed up the restore process, but we were
not in a position to use the API.

IBM support assisted us with the API, if not the spoolfile restore would
have been 166 days using WRKSPLFMBRM.



This was the reason we switched to the method you already are using.



http://www-01.ibm.com/support/docview.wss?uid=nas8N1011567



Paul



-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Steinmetz, Paul
Sent: Tuesday, July 22, 2014 10:51 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: BRMS Saving of Spooled Files Question



Jim,



I previously used spool file lists, there is a major recovery issue when
trying to restore when using lists.

From experience, Save spooled file data" from *none to *ALL is the way to
go.

Also, IBM no longer recommends using the spoolfile lists.



Paul



-----Original Message-----

From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim
Oberholtzer

Sent: Tuesday, July 22, 2014 10:04 AM

To: 'Midrange Systems Technical Discussion'

Subject: RE: BRMS Saving of Spooled Files Question



Laura:



I would set up a list in BRMS and only save the out queues you really care
about. Then specify the spool list in your control group.



Consider running the spool save separately from the other saves. First
it's not really referentially important and secondly you can use a tape
just for spool data, and keep appending to it until it's full. Then move
on to the next one. Spool data can be saved almost anytime so I'd pick a
time when it's convenient to run it.



--

Jim Oberholtzer

Chief Technical Architect

Agile Technology Architects





-----Original Message-----

From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
LRoberts@xxxxxxxxxxxxxxx<mailto:LRoberts@xxxxxxxxxxxxxxx>

Sent: Tuesday, July 22, 2014 8:15 AM

To: midrange-l@xxxxxxxxxxxx<mailto:midrange-l@xxxxxxxxxxxx>

Subject: BRMS Saving of Spooled Files Question





Hi,



We implemented BRMS 3 months ago and it has been great !! (wish we would
have done it sooner).



We are doing a complete data centre move next month (oh yay) and normally
I do not include saving of any spooled files. I want to include saving
them all in the Full backup just prior to the move (just in case).



I did a Full monthly unattended system backup this Sunday as I wanted to
test this prior. I changed my control group attribute "Save spooled file
data" from *none to *ALL. Is this all I had to do or am I missing
something ?



How do I tell if my spooled files got backed up ? I did a wrksplfbrm,

but there is nothing showing. Doing wrkmedibrm on the full backup media,
but I don't save object level detail so no help there.



Our OS is V7.1 Cume TL13298 and group SF99362 at level 28



Thanks !



Laura Roberts

















This communication, including all attachments, is for the sole use of the
intended recipient(s) and may contain confidential, personal and / or
privileged information. Any unauthorized review, use, disclosure or
distribution is strictly prohibited. If you are not the intended recipient
or a person responsible for delivering this message to an intended
recipient, please contact us immediately so we may correct our records.

Please then delete or destroy the original transmission and any subsequent
reply.

--

This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx<
mailto: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<
mailto: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<
mailto: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<
mailto: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<
mailto: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<
mailto: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 communication, including all attachments, is for the sole use of the intended recipient(s) and may contain confidential, personal and / or privileged information. Any unauthorized review, use, disclosure or distribution is strictly prohibited. If you are not the intended recipient or a person responsible for delivering this message to an intended recipient, please contact us immediately so we may correct our records. Please then delete or destroy the original transmission and any subsequent reply.





Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact