From: Todd Benson <caduceass@...>
Date: 2007-10-25T22:49:34+09:00
Subject: Re: Making ODBC connections without explicitly coding a password

On 10/25/07, Anne Burgess <anne@cantsfield.com> wrote:
> We're developing Ruby programs which read and write from/to DB2 tables
> on a mainframe.  We're the first people in the company to use Ruby so
> are rather feeling our way.  So far we've been using our own IDs and
> passwords, explicitly coded, to make ODBC connections to access
> development tables, but I've learnt that due to our security rules I
> won't be allowed to know the password for the ID which will access live
> tables.  Can anyone please suggest a way round explicitly coding the
> password?  Thank you.

You can prompt for a password, but of course that doesn't work for
automated scripts.

If your DBAs know what they are doing, then security shouldn't be a
problem with live tables.  I'm assuming that you will only be doing
queries and not inserts/updates?

Todd