×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Joe,
If you don't care about possible data relationships in the library syncing with other libraries you will be fine using *LIB. *LIB synchronizes the entire library. *SYSDFN only synchronizes each object to itself: aka data could be out of sync.
Gary Monnier
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Joe Pluta
Sent: Friday, March 02, 2012 2:23 PM
To: Midrange Systems Technical Discussion
Subject: Save While Active
I'm a neophyte when it comes to save while active. I want to save a
smallish production library (under 100GB) during production to replicate it for testing on another machine. I want to do this daily during offpeak (but still production) hours. I noticed a couple of options on the SAVACT: *LIB vs *SYSDFN. Since I'm only saving one lib, *SYNCLIB seems superfluous.
Anyway, does anyone have any recommendations for using save while active? I realize this is what it's meant for, but that doesn't mean there aren't considerations. I'm much more worried about minimizing delays to production than I am about getting a 100% clean image for the test machine. Because of that, I'm leaning towards
SAVACTWAIT(*NOCMTBDY) but I'd love to hear other people's experiences.
--
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.
midrange.com
