I've been running it weekly since 1996...I've never seen that happen.

I'd bet lunch somebody just thinks they changed it to 23:00.

Assuming you usually delay the save till 23:00:00, consider using GO SAVE
option 20 - Define save system and user data defaults to define the default
time as 23:00:00 instead of *CURRENT.

Then you don't have to change it when running option 21, just press enter.


On Thu, Dec 11, 2014 at 4:07 PM, paultherrien <
paultherrien@xxxxxxxxxxxxxxxxxx> wrote:

Has anyone ever encountered running the SAVSYS command and entering the
time instead of ‘*CURRENT’ and have the SAVSYS kick off immediately?

We are on V7R1 and occasionally when we run the GO SAVE option 21 the save
starts running immediately even though we have keyed in the time as 230000.

Thanks in advance,


Paul Therrien
Andeco Software, LLC
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].