|
System reply list entries (WRKRPYLE, ADDRPYLE) ----- Original Message ----- From: "McGivern, Tom" <Tom.McGivern@Yum.com> To: <midrange-l@midrange.com> Sent: Wednesday, October 23, 2002 1:54 PM Subject: RE: system save How do replies get replied to? (Write-protected/un-initialized/non-expired tapes) or just plain ol' "give me the next tape"... (C G) ? -----Original Message----- From: Todd kidwell [mailto:Todd.kidwell@3cc.co.wayne.mi.us] Sent: Wednesday, October 23, 2002 1:45 PM To: midrange-l@midrange.com Subject: RE: system save Andy / Ken, You are correct about needing to sign on to the console prior to the save being run. BRMS provides a program (Q1ACCON) that can be set as the Initial Program of a user profile. Once you sign on, the program goes into a "wait" state, which I believe is waiting for commands to appear in a specified data queue. If you know the password to the profile, you can use a function key to get to a command line. I have specified *SignOff as the Initial Menu so that if the Initial Program is exited, the job is signed off. I have a job schedule entry that uses a BRMS-supplied command (StrBkuBRM) which has a parameter for SbmJob(*CONSOLE). My guess is that the backup commands are sent to the data queue that the monitor program is watching and then executes them as they receive them. BTW, I also use this process to run a quarterly unattended Reclaim Storage. I personally think this is a great way to do the full system saves. All I need to do is make sure that sometime during the week (or month) I get down to the console (which is in a very secure location) and sign on using the monitor profile. If I do forget to sign on, nothing happens. The job for the scheduler kicks off, but since there is nothing monitoring the queue, nothing gets started. HTH, Todd Kidwell (Netstar) AS/400 System Administrator (313) 224-0578 _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. This communication is confidential and may be legally privileged. If you are not the intended recipient, (i) please do not read or disclose to others, (ii) please notify the sender by reply mail, and (iii) please delete this communication from your system. Failure to follow this process may be unlawful. Thank you for your cooperation. _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com 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.