Do their Rules require a hammer to fasten a screw? The idea here is to use the right tool for the task. In this case it's a sequence (and, preferably a server job to read the file).
You can update a values file of a parameter set directly, but you have to overwrite the entire file. You could do this with a job design that read from a values file, only changed it where the parameter name was the one you wanted to change, and wrote back to a file. Use before- and after-job subroutines to fiddle about with file names.
Dynamic Insert SQL Statement
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 298
- Joined: Tue Aug 26, 2008 12:17 pm
Hi everybody.ray.wurlod wrote:Do their Rules require a hammer to fasten a screw? The idea here is to use the right tool for the task. In this case it's a sequence (and, preferably a server job to read the file).
You can update a values file of a parameter set directly, but you have to overwrite the entire file. You could do this with a job design that read from a values file, only changed it where the parameter name was the one you wanted to change, and wrote back to a file. Use before- and after-job subroutines to fiddle about with file names.
It looks great! I'll try this solution!!!
![Wink ;-)](./images/smilies/icon_wink.gif)
I have a doubt about your comment above. Why is it preferable to use Server job than Parallel for this solution?
Tk you so much.
Best Regards,
Joyce A. Recacho
São Paulo/SP
Brazil
São Paulo/SP
Brazil
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
There's only one row to be processed by the job. Why start up a parallel job to process one row? Also, the interface to the user status area is much simpler in a server job.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.