compiled-in default vs. from value file

[bobyon]

We have a job that uses a paraemeter set value file which is being stubborn and refuses to pick up the values from the values file. When looking in the director log at parms the job is using ("double click Starting Job... entry) it shows [compiled-in default] rather than [from value file] as we have seen in other jobs.

Why?

what am I missing?

Thanks,
Bob

[ray.wurlod]

How are you running this job? Try some other method, such as dsjob command, to eliminate the invocation method. If, for example, it works from dsjob but not from Director (also try with a sequence), you can at least isolate the genesis of the problem.

[bobyon]

Thanks Ray.

We have been doing exactly as you recommend and have discovered that it does not seem to matter whether we submit from a sequencer or just submit the job from Director. We have submitted with dsjob and results are similar.

When submitting via the sequencer we see the following in the job jog.

Code: Select all

Starting Job RMKD910R.
ps_RMKD910R = (As pre-defined)
ps_RMKD910R.TD_USER =      (Compiled-in default)
ps_RMKD910R.TD_PASSWORD =      (Compiled-in default)

I'm fairly certain the problem is with the [as pre-defined] setting, but not sure how to get it to default to the name of the value file.

We also have a very similar job in production that is submitted via dsjob, it somehow runs with the value file name though it is not included as a parm on the dsjob statement. The job log for it is as follows:

Code: Select all

Starting Job P_RMK_TD_SuppressionInfo.
ps_RMKD405W = RMKD405W
ps_RMKD405W.TD_USER = xrmkd405w     (From value file)
ps_RMKD405W.TD_PASSWORD = "********"     (From value file)

What controls whether it runs with [as pre-defined] or the value file name?

Thanks,
Bob