dssetparm apt_config_file
Moderators: chulett, rschirm, roy
dssetparm apt_config_file
so sad I search in the forum so long time but cannot find any post.
I use a routine to run the DS job, now I want to specify the different APT fot different job, eg. file1.apt for job1, file2.apt for job2.
I hope I can set this by DSSETPARM like the user defined params but failed.
paramerr = DSSetParam (job2 , "$APT_CONFIG_FILE", '/sysp/DataStage81/InformationServer/Server/Configurations/file1.apt')
It still uses the default apt to run.
do I use the incorrect function to run?
I use a routine to run the DS job, now I want to specify the different APT fot different job, eg. file1.apt for job1, file2.apt for job2.
I hope I can set this by DSSETPARM like the user defined params but failed.
paramerr = DSSetParam (job2 , "$APT_CONFIG_FILE", '/sysp/DataStage81/InformationServer/Server/Configurations/file1.apt')
It still uses the default apt to run.
do I use the incorrect function to run?
wuruimao
Did you check 'paramerr' after the function call? What is 'job2'? It needs to be a handle to a job, not an actual job name, obtained using DSAttachJob.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
Did you actually declare the APT_CONFIG_FILE parameter explicitly in your job?
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
Yes, it is both possible and you are using the correct function. As noted, you need to declare it as a job parameter in the job (this is one of several that should be in every job) to allow it to be overridden on a run-by-run basis as needed.
I also found this 'remark' in the latest documentation as shown here.
Remarks
The job specified by JobHandle must be locked, using DSLockJob, before the DSSetParam function is called.
That's a new one on me as I don't remember ever having to do that or even seeing that function before.
Please use the Reply to topic button to reply unless you really need to quote something... which is hardly ever the case. Saves me having to clean up all the over-quoting. Thanks.
I also found this 'remark' in the latest documentation as shown here.
Remarks
The job specified by JobHandle must be locked, using DSLockJob, before the DSSetParam function is called.
That's a new one on me as I don't remember ever having to do that or even seeing that function before.
Please use the Reply to topic button to reply unless you really need to quote something... which is hardly ever the case. Saves me having to clean up all the over-quoting. Thanks.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
I believe that the DSLockJob() is when using the c interface, I can't see it mentioned for the BASIC calls documentation (11.3) and it isn't even defined - I get a compile error when I try to use it.
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Are you 100% certain that you defined this parameter in the job (case sensitive)? Could you also post your DSAttachJob() call?
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>