If a unix script is called from an execute command activity, is there any way to not display the password in the director log?
My script is
sh /data/basel2dev/integration/scripts/displaysysdate.sh #Integration.$PrmDBIntgUser# "File Validation Script" "E004" "Unmatched file count with trailer record" "testfile" #Integration.$PrmDBIntgPwd# #Integration.$PrmDBIntgSchema#
the value of #Integration.$PrmDBIntgPwd# should not be displayed as clear text in the director log
How to keep password out of the log?
Moderators: chulett, rschirm, roy
Note: split from this topic.
Last edited by chulett on Mon Jan 09, 2012 7:44 am, edited 1 time in total.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
You'd have to write your own routine, as noted in the linked post, that did not log that information. Note, however, that since you are passing the password to the script on the command line, it will still be visible to anything looking at the running process.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
The first time I saw it was on dsxchange
Then I found it in a pdf, but I can't recall its name (one about job sequence).
You can find more info on IBM' website
Regards,
Eric
Then I found it in a pdf, but I can't recall its name (one about job sequence).
You can find more info on IBM' website
Regards,
Eric