Re: SAVACT *SYNCLIB and SQL READ

[Charles Wilt <charles.wilt@xxxxxxxxx>]

I second this...

In fact you can take it a step further...

Our application data is split between 5 libraries.  But my daily save is
done in two parts, one uses SWA for the 3 library still being used
(modified) after 5pm.  Then the other two are saved normally.

Charles




On Wed, Apr 22, 2015 at 12:21 PM, Jim Oberholtzer <
midrangel@xxxxxxxxxxxxxxxxx> wrote:

> Jim,
>
> There should not be a problem with what you're suggesting, but I wonder if
> your synch point is way too wide with *ALLUSR.
>
> Instead consider the more limited list of libraries that need the
> referential integrity synchronization across them.  I'll bet that list is a
> reasonably short one.  Application 1 has library A, B, C, and D do a synch
> point for those four libraries.  You don't mention if you use BRMS but you
> can very easily set up lists of libraries, each list having a synch point.
>
> The other thing to consider is the "ragged save".   See:
> http://iprodeveloper.com/availability/ragged-save-while-active among other
> resources for Ragged save.  I think there is a Redbook about them too.
> Ragged save requires journaling to be turned on in the collections
> (libraries) where you use it.
>
> --
> Jim Oberholtzer
> Chief Technical Architect
> Agile Technology Architects
>
> -----Original Message-----
> From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim
> Franz
> Sent: Wednesday, April 22, 2015 11:07 AM
> To: Midrange Systems Technical Discussion
> Subject: SAVACT *SYNCLIB and SQL READ
>
> Our warehouse product does a large number of sql reads (many at a time) to
> pull big tables into the warehouse. Till now, we keep them from starting
> till our SAVLIB with SAVACT=*SYNCLIB has reached it's checkpoint across the
> libraries (*ALLUSR), which takes 30 minutes.
> If the SQL is only reading (Select ...) then other than memory and cpu is
> there any issue with both SAVLIB with SAVACT, and SQL Select at same time?
> V7R1 (trying to narrow or remove the outage window with existing hardware)
>
> 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.