SAVSYS unattended

185 pts.
Tags:
AS/400
Backup & recovery
DataCenter
I attempted to run an unattended SAVSYS on our 9406-810, v5r2. I signed onto the system console and did GO SAVE, took option 20 to set the defaults. I wanted the SAVSYS to run at 03:00 a.m. I then took option 21, to save the entire system. The job sat there for 2 days and did not run. WRKACTJOB status said the job was in DLYW, which is what I would expect. I ended up cancelling the SAVSYS and running it attended this past weekend instead. Anybody else have this problem when they attempted an unattended SAVSYS? Any input is appreciated!

Answer Wiki

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

I can definitely say without a doubt that I have always had problems with the unattended SAVSYS procedure over the years. In the end it always ends up being easier to just go in to work and run it attended. I’ve talked to IBM a couple of time about it and in the end what was happening on the systems I was working on was that the systems never got down to a fully restricted state and the SAVSYS never ran. Even though the SAVSYS is supposed to put the system in a restricted state automatically, many times, the system never gets there and that is usually where the problems lie with the unattended SAVSYS. Hope this helps.

Discuss This Question: 7  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
  • TheQuigs
    You could check into ROBOT/Save by Help Systems. We use it and our System Admin has never had a problem with it running correctly. (There have been tape drive problems, etc., but the system always goes to the restrcited state and the SAVSYS always gets kicked off at the scheduled time.)
    0 pointsBadges:
    report
  • Sneedebree
    Just create a break controlling program, attach it to the console messagequeue. At a specified time you send a cmdmsg from the scheduler to the messagequeue. The breakcontrolling program comes a live. Brings the system into restricted state, savsys and other commands. At the last restart or IPL the system. Have done it severall times with no problems at all. Best regards, Rene Breedveld
    0 pointsBadges:
    report
  • BorisM400
    We had the same problem and it took us some time to figure it out. You have to make sure no message that is sent to the console?s message queue or a user?s message queue that is logged in to the console is blocking the screen. Change these message queues to *NOTIFY otherwise the message pops up on the screen and suspends the process and you have to clear the screen before the save routine can continue.
    0 pointsBadges:
    report
  • ADmobius
    I spoke to an IBM certified systems expert about this and he said the reason that the job never started was because I had logged onto the console at 4:30 p.m. and set the start time for the entire system save to 03:00 a.m. (I wanted the job to start the next day, after midnight at 3:00 a.m.) Since option 20 (define save system and user data defaults) does not offer a date variable this job would never run because it was already after 3:00 a.m. on the current day.
    185 pointsBadges:
    report
  • Dalejanus
    That is very intersting to learn that the job must not run over 24 hours. I have had similar problems and now I wonder if that was part of it. I will try again with a start time of 11:55pm and see what happens. thanks for the info. ---Dale
    0 pointsBadges:
    report
  • Robbiehall
    Hi Dale, if you mean that you think the job cannot run for a long period ie more than 24 hours, then I think that is a misunderstanding. What he means is that if you draw a timeline of a 12 hour period then 03:00 will have already been passed at 04:30, so the start time would not be achieved. WRKJOBSCDE should allow you to choose a WEEKDAY and time for a job. But I would use CL for this type of task and submit it to sbs QCTL so it doesn't get ended when you restrict the system. Just step through the saves in your CL pgm and maybe you will have to add a few MONMSG's the first couple of times you run it. You can get a card and s/w from IBM to run a remote console with a GUI Front Panel too! Personally I prefer to run a full save whilst on site. Cheers Rob
    0 pointsBadges:
    report
  • Dalejanus
    Robbie, I understand you can use WRKJOBSCDE to get lots of flexibility in scheduling jobs. But I think the comment was if you use the GO SAVE menu and select save system, you cannot schedule past midnight. That is what may have tripped me up in the past. I have tried writing CL programs to do an unattended system backup, but have never had much success with it. It seems the simplest way is to run it manually. But I'll give it a shot tonight and see what happens. ---Dale
    0 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