Home Page for the TeradataForum

Archives of the TeradataForum

Message Posted: Fri, 25 Mar 2005 @ 22:52:18 GMT

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

Subj:   Re: How to handle logins in scripts and Ascential DataSTage jobs?
From:   Samuel Chu


Here is what I have to your questions.

There is no logon module that I know of from NCR/TERADATA at this time.

I have seen NETBACKUP and NETVAULT use $LOGON environmental variable in the UNIX environment and you can hide the environmental variable so only root and creator has access to it.

Imagine using a .logon file in your UNIX environment with the following line in it (using Korn shell as example).

     #! /usr/bin/ksh
     export SYS=
     export USER=
     export PSWD=

Build this into the .profile of each user so those environmental variables are defined at each user's logon time. In Korn shell environment, you can execute the .logon file with ". .logon" to export the environmental variables. Once this is done, you can use echo $SYS to check for the value for tdpid. The echo $USER will show you the user id you will be using for the session.

You can then code your script as following to pick up the scripts (Change variable name to suite your security need).

     .logon $SYS/$USER,$PSWD;

The .run of a file is great idea except fastload does not support .run command. I don't believe MLOAD support that either, don't remember exactly.

If you ever work with NCR professional service they have a utility call DWSTAR and it used similar concept. You can expand and change to suit your need.

If you decide to develope a C version or pearl version of those logon module please share with the rest of us then we would have a standard module we can all use.

Hope this helps,

Samuel Chu
Gap Inc.
DataBase Engineer

  <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: 28 Jun 2020