DSXchange

ray.wurlod wrote:It's "hashed" file, not hash file.

You refuse to give up don't you

Wait a sec, there is a bug in my code. The design is fine, only the derivations. Change it to the following. In Agg1, group by all your fields and specify MAX for date2 In Agg2, group by all your fields and specify MAX for date1 and LAST for date2 In Agg4, group by all your fields and speicfy MAX fo...

Dont use stage variables. Use aggregator stage. Work your way from the bottom up. Your design will look something like this FILE --> XFM --->Agg1--->Agg2--->Agg3--->File | | | Reject Reject the records that have NULL values in column Add. In Agg1, group by all your fields and specify MAX for date2 I...

No. Multiple assignments are not allowed. As Ken pointed out, use stage variables. Feel free to use as many for as many assignments.

Nothing out of the box but you can use the LEFT() function.

Ops, but not my fault, really, i got the impression that its something that the OP wanted to set up dynamically at a regular basis.

LIST.DICT just displays the dictionary items not the contents. Plus DS_JOBS just has info about the jobs, not the stages. I say stick to DS functions to retrieve job meta data and stage info. Also, search for kduke's ETLStats.

Refere to this post.

If you can do it from outside datastage then you do have Truncate permissions. Thats not it. Also make sure your using the same id to access the database within datastage.
You said that DELETE FROM TABLE works, you meant the delete command works in the OPEN command option? Please confirm.

You sure you have truncate permissions ?

So, you have to pass encrypted pass word if the parameter is specified as encrypted. Go the the job log, click on the first entry, see what it has for your password parameter, copy paste that string in your parameter file. Then run the job.

For some reason, i always suggest the Field() method and Craig, you always suggest the easy method on similiar issues in the past. I, should really start registering

No constraint disabling is needed/advised. These constraints are there for a reason. Instead of a workaround, lets stick to what the guide says.

You are on the right track. Read it as one huge column and inside the transformer, split it using the Field() function.

Its a known bug with windows xp. You need a patch. Refer here