Parameter for Input Value on General Tab of Job Properties

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
roman_l
Premium Member
Premium Member
Posts: 3
Joined: Thu May 01, 2008 1:30 pm

Parameter for Input Value on General Tab of Job Properties

Post by roman_l »

Hi All,
When I specify an after-job subroutine on General tab of Job Properties page, there is an option to provide an argument(s) for that subroutine in "Input Value" field;
The problem is that it only accepts hard coded values and I could not find any way to use either job parameter or environment variable as it's probably treated as something completely outside of the job itself.
So, when I migrate my project from dev. to test/prod. I'll need to manually change data in "Input Value" which I'm trying to avoid.

As an example, I call DSJobReport as my after-job subroutine and provide path for output status report in "Input Value" field in form of env. var.; Here is the error message:
AfterJob (DoJobReport): Failed to open directory $AGH_OUTPUT_DIR

Is there any known workaround?

Thanks,
Roman L.
There are 10 kinds of people in the world: those who understands binary and those who do not.
ray.wurlod
Participant
Posts: 54595
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Welcome aboard.

Surround your job parameter reference with "#" characters, for example

Code: Select all

#$AGH_OUTPUT_DIR#
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
roman_l
Premium Member
Premium Member
Posts: 3
Joined: Thu May 01, 2008 1:30 pm

Post by roman_l »

Thanks Ray,
I've just tried that, but it still produces the same result:

Code: Select all

AfterJob (DoJobReport): Failed to open directory #$AGH_LOG_DIR#


It seems that if it is before- or after-job (i.e. outside the job), then there is no way to apply anything what is available in the job environment...

Do you have any similar cases when you use before- or after-job routines and are able to provide env. var-s or parms for Input Value?

Thank you again,
Roman L.
ray.wurlod
Participant
Posts: 54595
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Have you added the environment variable to the job as a job parameter? Usually when the unresolved reference appears in an error message like that, it means that the job parameter does not exist or has been mis-spelled.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
roman_l
Premium Member
Premium Member
Posts: 3
Joined: Thu May 01, 2008 1:30 pm

Parm. for Inp. Val. on Gen. Tab/Job Properties - RESOLVED!

Post by roman_l »

Yes, you're right, this env. var. was not added to the job parameters page(there was another one that I tried first but it wasn't enclosed in #..#, what a shame..);
So, once I've added it to parameters it worked perfect.
Truly appreciate your help and fast turnaround.

Thank you again,
Roman L.
Post Reply