|
Archives of the TeradataForumMessage Posted: Fri, 18 Nov 2005 @ 16:12:42 GMT
David, Are you looking for some sort of wrapper script that would be called from Control-EM that would then call the appropriate job's to load the data? That can be easily done via a shell script on UNIX. You can even set it up so that your logon strings are parameters or environmental variables that are passed to the different scripts, thus keeping the passwords for the jobs more secure. A rough example I threw together from a proc script I had. This script did some error handling and variable setting prior to calling the scripts, but that is just generally good coding practices. This was called by scheduler and the scripts called then did the bteq, fastload, fastexport, mload, or tpump stuff they needed to do. And each one checks to see if the child process exited with a bad error code and fail's the proc job if it did. Hope this helps. Thanks, BillG Script excerpt below. #!/bin/ksh #### #do other stuff here #### #Calls script ksh $DW_BIN_DIR/script1.ksh if [[ $? -eq $EFATAL ]] then exitScript $EFATAL; fi #Calls script ksh $DW_BIN_DIR/script2.ksh if [[ $? -eq $EFATAL ]] then exitScript $EFATAL; fi #Calls script ksh $DW_BIN_DIR/script3.ksh if [[ $? -eq $EFATAL ]] then exitScript $EFATAL; fi #Calls script ksh $DW_BIN_DIR/script4.ksh if [[ $? -eq $EFATAL ]] then exitScript $EFATAL; fi #### #do more stuff here ####
| ||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||
Copyright 2016 - All Rights Reserved | ||||||||||||||||||||||||||||||||||||||||||||||||
Last Modified: 15 Jun 2023 | ||||||||||||||||||||||||||||||||||||||||||||||||