DSXchange

Welcome Aboard
Confirm this for me, does the data get loaded or not? Also, the control files will be created in the directory you provided in "Control File Directory" property. Also, what is the file name that you are providing, if you are not providing any name it will default to table_name.tmu

I rest my case

And now you can mark your post as Resolved. Make it a practice.

You can rename the file in the after job subroutine using the unix date function as part of the file name.

Switch the conditional check for more efficiancy. As your @INROWNUM = 1; condition will only be true once. If you have millions of records, it will make a difference.

You guys still in a tag-o-war on which one is better. geez...

-lparam will give you a list of all the parameters. So paraminfo is what you want now? You are seriously confusing. IF you want to do this at the OS level, create a dos batch job that reads from a list, loops through the dsjob -paraminfo command and passes the parameter read from the list one by one...

Hi, If lets say there are 5 jobs that are required to be run but in a specific sequence, can we control that too, I am looking in to the UtilityRunJob, but trying to understand the design to in corporate the job dependencies. Thanks ! Yes it can be controlled. Depends upon what sequence fed to the ...

UtilityRunJob() is just present in server i believe, not too sure, dont have access to DS right now so cannot validate that. Populate the table into a flat file, have a small shell script read that file line by line and pass the jobname to dsjob command. You can control this in a sequence job.

Let wikipedia throw some light on sixes/sixer.

And who in the world told you that it will not work in the before sql tab. Never 'assume'. Test it out yourself first before confirming any one else's notion. Anyways, thanks for the info, you can now mark your post as resolved.

Do an exact search on keywords "Add block to queue failed". See if the search comes back with any useful hits.

Yea but it should still work in a sequence job. Try it, if it doesnt, o bugger. Plus Whale's code wont give you the franction seconds part. Are you talking about current date and timestamp to be concatenated to the target file? I am still confused on that part.

If you cleared it then its gone. Re-run the same job with warning limit set to maybe 2 or 3. This way you can view the log in the director and see why those warning messages were created. It will also keep the log file size in check.

Or if this completely falls on your shoulders then you can incorporate this logic is a small script. The script will take the current date and check if its first saturday, second, third or fourth. Depending upon that it will assign the parameters via the dsjob command and run the job. You can also i...