Comments on: SAVSYS runs for half and an hour http://itknowledgeexchange.techtarget.com/itanswers/savsys-runs-for-half-and-an-hour/ Thu, 20 Jun 2013 09:42:01 +0000 hourly 1 By: rosshowatson http://itknowledgeexchange.techtarget.com/itanswers/savsys-runs-for-half-and-an-hour/#comment-74647 rosshowatson Tue, 09 Mar 2010 00:59:02 +0000 #comment-74647 Was the tape cleaned off before the save was run? If not then it had to process through 10 minutes of the tape before the save started. Did the system have to look for a tape in the tape library before starting?

Clean up history files (QHST*) and any excessive journals in QSYS.

Someone else said apply the PTF’s which would reduce what you are saving. Look for extra items in library QSYS that should not be there.

Backup and Recovery guide, look at what the SAVSYS command actually runs.

Try testing this on a Virtual Tape drive if possible.

I would be interested in knowing what the solution is.

]]> By: kagacchi http://itknowledgeexchange.techtarget.com/itanswers/savsys-runs-for-half-and-an-hour/#comment-74577 kagacchi Sun, 07 Mar 2010 14:35:21 +0000 #comment-74577 thanks much for all replies.

I would like to do some check that are permitted.

]]> By: woodengineer http://itknowledgeexchange.techtarget.com/itanswers/savsys-runs-for-half-and-an-hour/#comment-74548 woodengineer Fri, 05 Mar 2010 17:09:43 +0000 #comment-74548 Maybe this will help . . . A few years ago we did an Option 21 Save – save entire system. The documentation says it will end all subsystems then launch the save. After waiting much too long for the job to complete, we discovered that some of the subsystems we created were not ended. This was keeping the save from running properly. Next time I manually ended all those subsystem before launching the Save Entiry System and it ran very nicely.

]]> By: abigail http://itknowledgeexchange.techtarget.com/itanswers/savsys-runs-for-half-and-an-hour/#comment-74539 abigail Fri, 05 Mar 2010 14:30:45 +0000 #comment-74539 Permanently applying PTF’s will speed up the SAVSYS process. We process SAVCFG & SAVSECDTA nightly during non peak hours….neither is adversly affecting users or processes.

]]> By: dand http://itknowledgeexchange.techtarget.com/itanswers/savsys-runs-for-half-and-an-hour/#comment-74538 dand Fri, 05 Mar 2010 14:30:25 +0000 #comment-74538 Savsys also saves LIC/SLIC and the library QSYS. Since we can’t do much to affect LIC, I would check the QSYS library and verify no one has put user objects in that library. Do a DSPOBJD to an outfile and query it for owner, creation date and size and see if there is a large user file in the lib.

]]> By: tomliotta http://itknowledgeexchange.techtarget.com/itanswers/savsys-runs-for-half-and-an-hour/#comment-74526 tomliotta Fri, 05 Mar 2010 07:49:33 +0000 #comment-74526 …I would like to do that I can now.

Then run SAVSECDTA to a savefile and see how long it takes. You can do that at essentially any time. Obviously, as with any test, the less activity on the system, the better indication you’ll get. But if you need to do something now, then run some tests now.

Tom

]]> By: kagacchi http://itknowledgeexchange.techtarget.com/itanswers/savsys-runs-for-half-and-an-hour/#comment-74525 kagacchi Fri, 05 Mar 2010 02:55:12 +0000 #comment-74525 thanks for everyone’s replies.

I mean SAVSYS had run 1.5 hour.

In QHST, just these messages showed near SAVSYS.
“CPF0968 60 info System ended to restricted condition.
QSYSARB4 QSYS 553406 10/02/20 12:32:41.220256 QSYS
CPC3702 00 info Save System (SAVSYS) command has completed processing.
DSP01 QSECOFR 610293 10/02/20 13:53:10.579304 QSECOFR
CPC3701 00 完了 210 objects saved from library QSYS2.
DSP01 QSECOFR 610293 10/02/20 13:53:23.298200 QSECOFR”

It is my fault that I didn’t export JOBLOG.
Next time I run the SAVSYS, I will SIGNOFF LOG(*LIST).

Yes, as you said , We think that there’s usually no need for a SAVSYS unless an upgrade or PTF package is being applied along with it.
When we runs SAVSYS next time , we will transport the machine.
If SAVSYS runs for 1.5 hour next time,
We may not have enough time to solve this problem.

So, I would like to do that I can now.

]]> By: tomliotta http://itknowledgeexchange.techtarget.com/itanswers/savsys-runs-for-half-and-an-hour/#comment-74522 tomliotta Fri, 05 Mar 2010 00:03:16 +0000 #comment-74522 First, determine why a SAVSYS is needed. There’s usually no need for a SAVSYS unless an upgrade or PTF package is being applied along with it. Otherwise, a SAVSECDTA and SAVCFG can be done by themselves. No need even for restricted state; both of those can be directed to savefiles.

Then, determine the amount of time that a SAVSECDTA takes by itself. A SAVSYS that lengthens significantly is quite possibly due to the expansion of authorities in a system. Those would be reflected in a lengthening SAVSECDTA as well.

If that gives a hint of the problem, then there are lots of possibilities for correction.

Tom

]]> By: splat http://itknowledgeexchange.techtarget.com/itanswers/savsys-runs-for-half-and-an-hour/#comment-74518 splat Thu, 04 Mar 2010 22:23:41 +0000 #comment-74518 Next time you run the SAVSYS, sign off using SIGNOFF LOG(*LIST). That should give you a job log to dig through for problems.

]]> By: batman47 http://itknowledgeexchange.techtarget.com/itanswers/savsys-runs-for-half-and-an-hour/#comment-74515 batman47 Thu, 04 Mar 2010 20:43:00 +0000 #comment-74515 Yes, review your QSYSOPR message queue and also look at QHST during the save. You are correct, a SAVSYS should only take about 10 minutes, not 30. The last time my SAVSYS took about 30 it was because of a tape drive problem.

]]>