Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Fri, 25 Mar 2005 @ 20:27:56 GMT


     
  <Prev Next>  
<<First
<Prev
Next> Last>>  


Subj:   How to handle logins in scripts and Ascential DataSTage jobs?
 
From:   Brad.Carlson

We have a pretty small system (4 nodes, growing to 12 in 2Q), but we still have dozens of multlload, fastload and fastexport scripts, not to mention tpump and standard bteq scripts. The logins for these utilities are embedded right in the script. Our scripts are written in Korn Shell (see sample below) and call multiload internally using here files. It doesn't seem very secure when you are dealing with private data. Any one who can see the script can see the password. Any suggestions for how to get around this? Does Teradata have any tools for handling logins so they don't have to be hardcoded?

     ----------------------------------------------
     #!/usr/bin/ksh
     # set some variables here
     mload <<- EOF
             .LOGTABLE userid.logtable;
             .logon tdpid/userid,password;
             /* do setup stuff */
             .BEGIN IMPORT...
                     /* Mload scripting here */
             .END MLOAD;
             /* do wrapup stuff */
     EOF
     RC=$?
     # Handle return code and exit
     exit
     ----------------------------------------------

We will be starting to use Ascential (IBM?) DataStage soon, which will have similar issues. I know we can pass login data as a parameter to a DataStage program, but that login data has to come from somewhere - usually the calling script. We will use Korn Shell scripts to call the DataStage program and pass in the login data. Again, there has to be a better way or at least a way to hide this. Suggestions?



     
  <Prev Next>  
<<First
<Prev
Next> Last>>  
 
 
 
 
 
 
 
 
  
  Top Home Privacy Feedback  
 
 
Copyright for the TeradataForum (TDATA-L), Manta BlueSky    
Copyright 2016 - All Rights Reserved    
Last Modified: 27 Dec 2016