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!
Free Guide: Managing storage for virtual environments
Complete a brief survey to get a complimentary 70-page whitepaper featuring the best methods and solutions for your virtual environment, as well as hypervisor-specific management advice from TechTarget experts. Don’t miss out on this exclusive content!