RE: Saving of Journals and Journal Receivers.

["Haase, Justin C." <justin.haase@xxxxxxxxxxxx>]

Yeah - as I read your thing I thought "Why not just do a CHGJRN *GEN
before starting the backup?" 


--
Justin C. Haase - Solution Engineer
IBM Certified Systems Expert - System i
Kingland Systems Corporation

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Monday, December 11, 2006 4:08 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Saving of Journals and Journal Receivers.

When backing up "normal" libraries we quiesce the applications using
those libraries.  We can pretty much break this down by division.  Each
division has their own set of libraries.  However, due to the way we
implemented our HA software (good, bad or indifferent) we put all of our
journals and journal receivers into one library, #MXJRN.  Now, when I go
to save that library I do not want to quiesce all divisions to back up
that library. 
Would just doing a simple
SAVLIB LIB(#MXJRN) DEV(TAP##) SAVACT(*SYSDFN) SAVACTWAIT(5) be
sufficient?  Would that still skip any receivers in use?  I guess if I
set it up to gen a new receiver just prior to the backup then it
shouldn't be that big of a deal, eh?

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

--
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.



CONFIDENTIALITY NOTICE:  This e-mail communication, including attachments, is 
covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is 
confidential, and may be legally privileged.  If you are not the intended 
recipient or believe you received this communication in error, please reply to 
the sender indicating that fact and delete the copy you received.  In addition, 
retention, dissemination, distribution, copying, or otherwise use of the 
information contained in this communication is strictly prohibited.  Thank you.