SAVACT, checkpointing and tape movment

Charles, I am not sure what to say except to make sure that you take out
of the equation the wrong tape being used.

Make sure you use the right tape, even expiring the tape or initializing
it if needed.

If everything works when the right tape is being used, then all you need
to worry about is using the correct tape.

If the right tapes are being used & you still have the problem, you may
want to see what processes actually are using the libraries.

There may be some processes that may need to be stopped prior to the
backup & restarted.

Also, a good IPL may do wonders if it hasn't been done in a while.

Make sure you have the latest backup & recovery PTF's loaded as well.

Thanks.
James Salter
Systems Programmer
American Cast Iron Pipe Co
Email: jsalter@xxxxxxxxxx
Phone: (205) 325-3033
Fax: (205) 307-3833


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




from: "Wilt, Charles" <WiltC@xxxxxxxxxx>
subject: RE: SAVACT, checkpointing and tape movment

So, nobody has any thoughts on this??

Charles Wilt

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
bounces@xxxxxxxxxxxx] On Behalf Of Charles Wilt
Sent: Friday, May 30, 2008 1:09 AM
To: midrange-l@xxxxxxxxxxxx
Subject: SAVACT, checkpointing and tape movment

All,



Interesting problem, I've got a SAVLIB command saving two libraries

with

the
following SAVACT parms:

savact(*SYNCLIB) savactwait(5)



Recently, started having problems where the locks by the save job are
interfering with a extranet web application.



It doesn't happen all the time. Looking at the SWA messages on a

night

without problems I see:

17:06:14 - Save starts

17:06:43 - All Objects locked in LIB1

17:06:46 - All objects locked in LIB2, checkpoint processing in

progress

17:10:48 - Checkpoint Processing complete



One a night with problems I see:

17:09:15 - Save starts

17:09:35 - All Objects locked in LIB1

17:09:36 - All objects locked in LIB2, checkpoint processing in

progress

17:55:25 - Checkpoint Processing complete



Now as it turns out, on the nights that have had a problem, the wrong

tape

was being used. Instead of the current save going at the end

(sequence

#16)
of a daily tape, the save was going to the end (sequence #202) of a

full

system save tape.



If I'm reading the v5r3 material I have correctly, the physical tape's

not

supposed to start moving till the checkpoint has been reached. But

this is

a
v5r4 box, perhaps something has changed?



Can anyone confirm or deny that SWA checkpointing would be delayed by

the

need to position the tape to the *END at v5r4?



If the extra tape movement is not the problem, I'm at a lost as to why
checkpointing might take 45 minutes when it usually only takes 4.

These

aren't big libraries, one has 501 objects the other has 81. I see no
messages about the SWA timing out, or objects not being saved, even

with

the
SAVACTWAIT of only 5 seconds.



One last piece of additional information, on the save report all the
logical
files in both libraries have a "Save While Active Timestamp" of 17:09
while
the physical files all have a "Save While Active Timestamp" of 17:55

on a

night with the problem.





Thanks!

Charles Wilt

_________Confidentiality Notice_______________________
This e-mail and any files transmitted with it is
confidential and is intended solely for the use of
the individual(s) or entity(ies) to whom this e-mail
is addressed. If you are not the intended recipient
or the person responsible for delivering the e-mail
to the intended recipient, be advised that you have
received this e-mail in error, and that any use,
disclosure, dissemination, forwarding, printing,
retention or copying of this e-mail is strictly
prohibited. If you have received this e-mail in
error, please immediately return this e-mail to
the sender and delete the e-mail from your system.
Thank you.