Page 2 of 2
Posted: Mon Jan 31, 2005 10:49 am
by ogmios
I don't think that's supported in DataStage, it will try to use the fields user id and password whether you fill it in or not.
If DataStage did a more general authorization you could get e.g. Oracle and DB2 to work on the local machine without passwords.
Ogmios
Posted: Mon Jan 31, 2005 10:58 am
by leomauer
ogmios wrote:I don't think that's supported in DataStage, it will try to use the fields user id and password whether you fill it in or not.
If DataStage did a more general authorization you could get e.g. Oracle and DB2 to work on the local machine without passwords.
Ogmios
It does work with our DS installation.
It does not prompt either.
And regarding "trusted" user connection from Sainath.Srinivasan response: in test environment there is nothing wrong to execute under developer ID connecting to test database, where in production job should be executed under prod id that has the required permissions.
I do not see anything wrong with it but of course there may be other opinions.
Posted: Mon Jan 31, 2005 11:02 am
by Sainath.Srinivasan
You can get your user name from @LOGNAME.
Can you connect from your OS to your dbms with this alone? Say for Oracle, something like 'sqlplus username@OracleSID'? If yes, then you can try to leave the password blank and substitute @LOGNAME for username and your Oracle may understand it.