You could capture it using an Execute Command stage and 'echo'. Or add it as a job parameter to the sequence and set it to $PROJDEF. Depends on what 'based on an input parameter' means.
-craig
"You can never have too many knives" -- Logan Nine Fingers
input parameter to sequence name will be a database name.
Based on database name i need to fetch the username and pwd which is set as used defined environment variable
Two Execute Command stages or a custom routine called in two Routine Activity stages. I'd probably prefer the latter as you have more control over the string building and error handling, plus you can strip any extra who-ha (like Field Marks) from the result before passing it back. Either way could be made to work, however.
-craig
"You can never have too many knives" -- Logan Nine Fingers
If the parameter is a parameter of the job sequence itself, then you can simply use it directly to supply the parameter value in any Job activity. Just use the "insert parameter value" tool. Encrypted or not, it will work.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
But it could be. The job sequence itself could have a parent sequence. However, encrypted parameters are still an issue - can you use $ENV to pick these up?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
$ENV didn't work.
How can assign the value of environment variable to a job parameter from command line
e.g.
DBPWD -- job parameter
$DBPWD -- environment variable
how can i assign DBPWD with the value of $DBPWD (DBPWD=$DBPWD)