DSXchange

In many years using datastage I've never seen something like that ... It's a new "feature" of the 8.x architecture and not something that was possible in earlier versions. As to the other issues, I'd fix the first one first and see what happens with them. However, I'd be curious if they a...

Unfortunately, I don't have any way to check this and provide more details, hopefully someone else can.

What exactly does "fails to pick up the parameter from sequencer" mean? What are you seeing when this happens - something set wrong, a specific error? Need more details...

Your repositories are out of sync, contact your official support provider for help getting that corrected.

Or we could wait for an example of the input and desired output so we have a better idea what "count" means in this context...

ODBC isn't the performance evil that it used to be. Only way to know, however, is to try it and see. Have you contacted Vertica on this issue?

Do keep in mind the fact that (as best as we can tell) they already have a DataStage job that does all this. They are looking for an alternative for some reason.

vamsi.4a6 wrote:Could anyone explain description about following format specifiers?

jwiles wrote:You may have to play around with the format specifiers a little bit...they are documented in the Parallel Job Developer Guide.

Oddly enough, in a section titled "Date and time formats".

Not really clear yet, I'm afraid. Can you post an example or twelve? What the selected data looks like and what your counted output from that input would be? That would be a good and much less ambiguous start.

Is there something else going on? Another message you're not showing us? That message is mentioned many many times here if you search for it, and it is always listed as a Warning, not an Error. For example: ##W IIS-DSEE-TOSH-00049 01:44:08(005) <main_program> Parameter specified but not used in flow...

Stick with the DataStage job. Any straight 'conversion' of the entire file will corrupt the packed fields and it's more trouble than it is worth to try to parse out the different record types, converting the individual string fields and unpacking the others using a script. Of course, you could fall ...

Parallel Job Developer's Guide, Chapter 2, Partitioning, repartitioning, and collecting data, Hash partitioner.

There's no guarantee that they will partion across all three nodes. All you are guaranteeing is that records with the same deptno will be on the same partition as they will generate the same hash key. Which is the whole point, and you shouldn't really care which one goes where.

In other words, the standard cron entry that DataStage creates. Still think you're going to need to involve your official support provider on this.

If you haven't already, try unscheduling it and then adding it back to the schedule, see if that helps.

Actually, it is something better suited for a Teradata support forum since it is specific to their client tool. However, I would go along with Paul and your default Windows characterset being the issue.