|
On Friday 08 February 2002 5:00 am, barsa@barsaconsulting.com wrote: > Neither of the follow two solutions actually work in batch, but they > provide the same effective feature if you are willing to tie up the > console. > > No, but there is an option on the GO SAVE menu option 21, 22 and 23 to > start at a given time of the day within the next 24 hours. This does > limit you to the next 24 hours, and exposes a security exposure. > There is a TAA Tool menu GO SAVE2 that handles more than 24 hours out, > checks for active jobs, and plugs the security holes. > > see: > > http://www.taatool.com/document/L_save2.htm > > It does seem to be a typo in the heading. > > Al Missed the name of the original poster... And if you aren't worried about the security exposure (console in a secure computer room, etc) you could have a look at how we added a bigger delay - see http://www.dbg400.net/samples.html in the Usenet section. Regards, Martin -- martin@dbg400.net jamaro@firstlinux.net http://www.dbg400.net /"\ DBG/400 - DataBase Generation utilities - AS/400 / iSeries Open \ / Source free test environment tools and others (file/spool/misc) X [this space for hire] ASCII Ribbon Campaign against HTML mail & news / \
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.