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



SAVSECDTA will run fine with the system 100% active. The SAVACT
parameter for SAVDLO is either *YES or *NO. Depending on what you are
doing I would guess that you probably don't have many DLO's and they
probably aren't locked. Do a test SAVDLO to a savf while the system is
active and see.

The SAV might be trickier, again depending on what you run. The SAVACT
parameter for the SAV allows *YES, *NO or *SYNC and the is also a Save
active option parameter you can look at if there are issues. The #1
issue you'll see are locked logand error files for the various web and
WAS servers you may have running. These can usually be omitted from
your save because they'll get recreated on startup if they're missing.
If you need that log information then you'll need to add those servers
to <end a bunch of stuff>

If these are long running saves and you want maximum uptime I would
consider doing something more like this:


Savsecdta

<end a bunch of stuff>

savcfg

monswaque (monitors swa msg queue and will <start a bunch of stuff>
when sync point is reached in next savlib command)

savlib *allusr with *synclib



<end a different bunch of stuff>

savdlo with swa

sav (ifs) with swa

<start a different bunch of stuff>


Regards,

Scott Ingvaldson
Senior IBM Support Specialist
Midwest Region Data Center
Fiserv.



-----Original Message-----
From: Jerry Draper [mailto:midrangel@xxxxxxxxxxxxx]
Sent: Friday, April 24, 2009 12:19 PM
To: Midrange Systems Technical Discussion
Subject: Re: Save While Active Question

In a full backup situation that includes DLO, IFS, and *ALLUSR what is
the best protocol for the SWA part?

We run:

<end a bunch of stuff>

savsecdta

savcfg

savdlo with swa

sav (ifs) with swa

monswaque (monitors swa msg queue and will <start a bunch of stuff> when
sync point is reached in next savlib command)

savlib *allusr with *synclib


How do the savdlo and sav (ifs) work with SWA. We certainly won't be
starting the system up until we arrive at the sync point in the savlib
*allusr piece.

Jerry
--
Jerome Draper, Trilobyte Software Systems, since 1976 iSeries, Network,
and Connectivity Specialists -- iSeries, LAN/WAN/VPN Representing
WinTronix, Synapse, Netopia, HiT, and others .....
(415) 457-3431; www.trilosoft.com



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.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 on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.