Hi Milorad,
Does TNG log on to the machine, or run as a servcie, or .... Can the TNG user be in
the sysadmin group, so he does not require a different userid to connect (It sounds
like they are on the same machine).
Otherwise, we have executed a file containing set commands for userid and password and
restricted access to the file. Not perfect, and really requires using db2 -v option so
the password is not printed in all the output.
HTH, Regards,
Bruce
-----Original Message-----
From: [EMAIL PROTECTED] [SMTP:[EMAIL PROTECTED]]
Sent: Monday, 30 April 2001 17:30
To: [EMAIL PROTECTED]
Subject: DB2EUG: DB2 userid/passwords and scripts
Hi,
We're a Windows NT site running UDB v6.1 and we're in a bit of a pickle at
the moment regarding a number of scripts that were created to support our
datawarehouse environment. The scripts number about 6 and do the
following:
1. Deletes all data in a number of DB2 tables using IMPORT REPLACE
2. Create indexes on a number of db2 tables
3. Run a backup of the database
etc
The problem is that we currently use TNG to schedule the DB2 scripts as
they are dependant on other non-DB2 jobs being run before and after as
part of the warehouse load process ... but unfortunately these scripts in
order to run under TNG contain the userid/password clearly embedded in all
of the DB2 scripts. We need to find an alternative solution ... not sure
how ... but I was wondering how other sites handle their scripting needs.
The alternative was to try and use the DB2 Control/Script Center as this
would encrypt the password ... but this according to management was still
unacceptable.
Is there any way to have the scripts run on the server without explicitly
coding the userid/password in each script ... but by inheriting the DB2
access from the NT server's userid/password that is used to boot the
server.
I would gratefully appreciate any thoughts, comments, suggestions, etc.
Regards and thanks,
Milorad
**********************************************************************
This message and any attachments are confidential and for
the addressee only. If you have received it in error, please
notify the sender. It may be subject to legal privilege or
confidentiality obligations imposed by legislation. TAC email
addresses are for business use only. All email sent to TAC
may be inspected and used by TAC for any lawful purpose.
TAC policy prohibiting transmission of inappropriate material
to its email addresses is strictly enforced.
**********************************************************************
<< File: ATT00001.htm >>
application/ms-tnef
