Name column in director contains prompt info from designer

elliferg · Post by **elliferg** » Mon Sep 11, 2006 12:48 pm

Is anyone else seeing the data from the prompt column (from Designer) in the name column when you hit the run button (in Director)? This seemed to start when we upgraded to 7.5.2 .

kcbland · Post by **kcbland** » Mon Sep 11, 2006 12:56 pm

Wow! Waiting for the right moment for your first post? :lol:

I've never seen this problem with 7.5.2 on AIX and Solaris. But, my prompts are usually the same as the parameter name so I haven't exactly been trying to test this.

elliferg · Post by **elliferg** » Mon Sep 11, 2006 1:50 pm

I swear I posted before I paid to join. I think my post bucket has a hole in it.

Anyway, most of our prompts match our parameter names, but some other people got in our code and made the prompts into actual prompts. Go figure.

ray.wurlod · Post by **ray.wurlod** » Mon Sep 11, 2006 4:10 pm

Job parameter names have to be legal variables names. The prompt text can be made more meaningful text, and in local language (for example Arabic or Korean). I advocate and counsel use of meaningful prompt text, and always supplying help text, for job parameters.

elliferg · Post by **elliferg** » Mon Sep 11, 2006 10:34 pm

That's all well and good, but now we can't see the variable names, which we have in our parameter files that we use to call dsjob. It seems pretty hokey to me.

ray.wurlod · Post by **ray.wurlod** » Mon Sep 11, 2006 11:47 pm

It is working as documented.

If you find that hokey, then so be it.

Change your prompt text to be the same as the parameter name if that's what you need. Why do you need to see the parameter name anyway? Generate job documentation; it's all in there.