|
Hi Jorge My experience is that you will have to leave the console signed on and waiting on some kind of trigger to proceed with the backup process. The SAVSYS *HAS* to be done interactively so batch is simply not an option. The options I can think of are to use a break handling program (as you suggested), have the console program wait on a dataqueue or to just have the program wait for a period of time or until a time. Using the break message or data queue options you can trigger the backup to start from the job scheduler or some other batch/system management process if that is what you are after. The break handling option has some merit in that you will probably have to do this in some form anyway as both of the other methods need to ensure that any messages received by the console are handled. If you have an interactive job running on the console waiting until midnight tomorrow and someone sends a break message to all work stations your program will hang until the message is dealt with. By the way I have written something like this myself - using the timer method - and got it to work so I am not just idly speculating. At the time I was in the fortunate position of having a system to experiment on and ample time to work through as many of the wrinkles as I could. I have since used BRMS (for other reasons) and have found that it's console function - required for exactly this scenario - works like a charm. I would seriously weigh up BRMS against what you need to do - by the time I had added all the functions I needed to make the whole shebang work as a generic process for multiple systems - and this included control file driven, optional day, week, and month end processing (before and after), different backup regimes and scheduling and housekeeping control schedules - I had duplicated (no doubt in a basic sense) many functions BRMS provided. Hope this helps regards Evan Harris
Hello List Members - My question is pretty simple and it has to do with a Batch Job been able to "somehow" signon to an interactive session on DSP01 (System Console) directly attached to the iSeries (AS/400) with the user profile of QSECOFR And the reason for this requirement . . . : "Weekly unattended backup of the entire machine" That includes Save of System, Save of *NONSYS Libraries, Save of Configuration data, Save of Security data, Save of Folders, Save of IFS, Save of Licensed Programs. I know of some vendors that can be of help. However budget restrictions do not allow that to happen. Here are a list of the case scenarios I have been able to consider. Case 1. I know that a break message handler program will work if the DSP01 "interactive session" has already been established with the profile of QSECOFR. Case 2. I think if there is a different DSP01 "interactive session" with a user profile different to QSECOFR. Probably thru one of the Security APIs I can change that and I am back to case 1. Case 3. There are no "interactive sessions" at all Your ideas will be appreciated. Jorge Moreno Systems Analyst Overseas Military car Sales Woodbury, New York
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.