|
Darrell, Forget Robot. You can do this from the console with a start time anytime in the next 23:59:59 just with OS/400. If you want longer than 24 hours, there is a TAA Tool (what else?): http://www.taatool.com/document/L_save2.htm Al Al Barsa, Jr. Barsa Consulting Group, LLC 400>390 "i" comes before "p", "x" and "z" e gads Our system's had more names than Elizabeth Taylor! 914-251-1234 914-251-9406 fax http://www.barsaconsulting.com http://www.taatool.com http://www.as400connection.com Darrell A Martin <DMartin@moreycor p.com> To Sent by: Midrange Systems Technical midrange-l-bounce Discussion s@xxxxxxxxxxxx <midrange-l@xxxxxxxxxxxx> cc 11/18/2006 02:30 Subject PM "Automated" run of SAVSYS or other BRMS backup Please respond to Midrange Systems Technical Discussion <midrange-l@midra nge.com> Greetings: Links to specific documents that answer my questions directly will be warmly received, in fact may be preferred! I would like to know the most straightforward way to run an automated "save everything" -- the equivalent of a GO SAVE 21. ****Is this the best choice in my situation??**** Knowing how to do this by Saturday, December 2 may extend my time at the zoo that day! (I have a BlackBerry "terminal on my hip" and Robot/Alert to my cell phone for problems....) My environment will be Period End Saturday afternoons. The tape library will be loaded in advance (duh). We use Robot/Schedule for automation. I can use Robot to bring down interactive subsystems and run preliminary jobs. That is already in production or clearly understood. When the prelim stuff is complete I want Robot to kick off the backup. I plan to arrive during the backup job, which currently takes about 4 hours, and go from there. Handling the system restart is also a question, for the future, but since I eventually want Robot to start kicking off jobs as soon as the system is back up, I think Help/Systems (Robot) excellent tech support people will probably be my best resource. Darrell Darrell A. Martin - 630-754-2187 Manager, Computer Operations dmartin@xxxxxxxxxxxxx This e-mail, including attachments, may contain information that is confidential and/or proprietary, and may only be used by the person to whom this email is addressed. If the recipient of this e-mail is not the intended recipient or an authorized agent, the reader is hereby notified that any dissemination, distribution, or copying of this e-mail is prohibited. If this e-mail has been delivered to you in error, please notify the sender by replying to this message and deleting this e-mail immediately. -- 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.
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.
midrange.com
