SAVSYS runs for half and an hour

35 pts.
Tags:
iseries v5r4
SAVSYS
Recently, We executed SAVSYS in restricted state. I know that SAVSYS usually runs for about 10 minutes. But, at that time , SAVSYS had run half and an hour. I don't know why SAVSYS runs much time. I know that SAVSYS save LIC, SAVSECDTA,SAVCFG. But I have know idea about what is bad. I don't know SAVSYS detail behavior. IBM support said "Need JOBLOG" But, We can't get JOBLOG. We can't SAVSYS again. The machine has 3TB disk strage. Our clients use about 40 percent. Any suggestions would be appreciated! Help me !

Software/Hardware used:
v5r4 9406-550

Answer Wiki

Thanks. We'll let you know when a new response is added.

Hi,

From my knowledge i see savsys will run some time around 30min. In your case, i see that you want the system to be in down for an minimal amount of time.

In actual , savsys wil be perfomed under restricted state, it will get comprise of copy of lic, sec & cfg datas.

you can go for three separate saves,

savsys dev(tap01) omit(*secdta, *cfgdta) – Perfom this when the system to be restricted state(endsbs *all *immed)
savsecdta dev(tap01) – perform this when the system in active state
savcfgdta dev(tap01) – perform this when the system in active state

I guess by this, you can drastically reduce the savsys time, and reduce your downtime for the system.

Regards
Anand

Discuss This Question: 14  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Skillset400
    Hi, From my knowledge i see savsys will run some time around 30min. In your case, i see that you want the system to be in down for an minimal amount of time. In actual , savsys wil be perfomed under restricted state, it will get comprise of copy of lic, sec & cfg datas. you can go for three separate saves, savsys dev(tap01) omit(*secdta, *cfgdta) - Perfom this when the system to be restricted state(endsbs *all *immed) savsecdta dev(tap01) - perform this when the system in active state savcfgdta dev(tap01) - perform this when the system in active state I guess by this, you can drastically reduce the savsys time, and reduce your downtime for the system. Regards Anand
    150 pointsBadges:
    report
  • Kagacchi
    thanks for the reply, And I appreciate your suggestion. >From my knowledge i see savsys will run some time around 30min. In your case, i see >that you want the system to be in down for an minimal amount of time. yes, I want so. In addition, As you know ,SAVSYS should not take half and an hour. I wonder if LIC is broken. I wonder if the machine has HW or SW trouble. Do you know in which cases SAVSYS needs a long time ?
    35 pointsBadges:
    report
  • WoodEngineer
    When you write, "SAVSYS had run half and an hour" does that mean 1.5 hours or 0.5 hours? Our SAVSYS (Model 520, V5R4) runs in about half an hour (0.5). 1.5 hours sounds pretty long.
    6,715 pointsBadges:
    report
  • CarterC19
    You know, my SAVSYS just ran a lot longer than usual this last time, and poking around the SYSOPR messages from the prior IPL time showed a couple CPF32A6 'Cross reference notification 1061 for request 2, problem type 1' messages for a couple objects in the SYSIBM library. Those objects no longer show up in PDM but *do* show up as taking up space when I run a RTVDSKINF. So, I think I have a couple damaged objects that caused the SAVSYS to take an abnormally long period to run, and will be running a RCLSTG to repair same. You might want to look at the SYSOPR messages from the last IPL, if you still have them, to see if you have something similar.
    220 pointsBadges:
    report
  • Batman47
    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.
    1,050 pointsBadges:
    report
  • Splat
    Next time you run the SAVSYS, sign off using SIGNOFF LOG(*LIST). That should give you a job log to dig through for problems.
    7,395 pointsBadges:
    report
  • TomLiotta
    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
    125,585 pointsBadges:
    report
  • Kagacchi
    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.
    35 pointsBadges:
    report
  • TomLiotta
    ...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
    125,585 pointsBadges:
    report
  • DanD
    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.
    2,865 pointsBadges:
    report
  • Abigail
    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.
    645 pointsBadges:
    report
  • WoodEngineer
    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.
    6,715 pointsBadges:
    report
  • Kagacchi
    thanks much for all replies. I would like to do some check that are permitted.
    35 pointsBadges:
    report
  • RossHowatson
    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.
    295 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following