 |
 |
Archives of the TeradataForum
Message Posted: Wed, 27 Jul 2005 @ 15:49:31 GMT
| Subj: | | Re: Using rexec/rsh from Windows client |
| |
| From: | | Victor Sokovin |
| | You may want to consider one more tool here. If you run your jobs on Unix with nohup and redirect the output to a log file. You can scan
the log file with some combination of sed, awk, and perl. With this setup you can ignore the issues of network failures etc. I use this type of
architecture for a backup solution I built for our application. The master script runs in nohup and calls other scripts in the process. At the end
of each child script I scan the output log for the results (row counts, status, error messages) and insert them into a table. If any child script
returns an error the master script sends an email to the help desk staff. I retain the logs for 30 days, and as much of the table as there is
space for. | |
This is a great way of avoiding the rsh. The reason we could not use it was that we wanted our jobs to be "transactional", i.e., they should
either go through on both Windows and Unix or fail and rollback where they started. I know your approach could potentially be extended to this
level but I don't think the extension will always come easy or it will be transparent enough to be accepted by all parties. But yet again, it is a
great messaging type of communication between jobs on different platforms and it should be considered before going rsh.
Regards,
Victor
| |
