One way is to put it in your environment. If you're in a shell script, export (bourne-shell and derivitives) or setenv (C shell and derivitives) should help there. If it's a perl script calling another perl script, see the %ENV hash.

Another way, since this is DB2, is to discard the password and username altogether. Run it as a user who has the authority to do what you need, and no password is required. DB2 will use the OS authentication to confirm who you are. This is how I've generally done this - avoids all the hassles of dealing with passwords in plain-text perl code.

######################################################################
+#######
# This functions will store and retreive pass using crypt
# Usage:

=begin COMMENT
$LocationOfTheScriptsDirectory='D:\InstallV3';
$passFile="$LocationOfTheScriptsDirectory\\as.txt";
$passEncrFile="$LocationOfTheScriptsDirectory\\ass.txt";
$key='test';
$pas='zest';
storePass($key,$pas,$passEncrFile,$passFile);
$P=retreivePass($key,$passEncrFile);
print $P;

$WhoAmI=`whoami`;
@SystemUserid=split(/\\/,$WhoAmI);
$MyUserId=trim($SystemUserid[1]);
#crypt -e myuserid < MyPass.txt > mpcr.txt
$MP=`crypt -d $MyUserId < mpcr.txt`;
$MyPassword=trim($MP);


=end COMMENT
=cut
sub storePass #($Key,$Pass,$passEncrFile,$passFile)
{
    my($Key,$Pass,$passEncrFile,$passFile)= @_;
    my($enc);
    open (OFH,">$passFile") || die "Can't open OFH file: \n";
    print OFH $Pass;
    close OFH;
    #create $passEncrFile that will hold pass encrypted value
    $enc=`crypt -e $Key < $passFile > $passEncrFile`;
    #remove passFile
    unlink ($passFile);
}

sub retreivePass #($Key,$passEncrFile)
{
    my($Key,$passEncrFile)= @_;
    my($cr,$myPassword);

    $cr=`crypt -d $Key < $passEncrFile`;
    $myPassword=trim($cr);

return $myPassword;
}
[download]