DSXchange

Don't see how there could be a join issue unless it is one of your own making. Hashed reference lookups are inner by nature, either an exact match or there's no match at all. Provide a detailed description of your job design, please.

Use your first query to populate a hashed file keyed on pcode. Use your second to stream rows in and lookup the description from that same hashed file using pcode. Send the combination of the two out as the result.

Or simply join the two tables in your source query.

What "settings"? You said earlier that the Sequence job was not multi-instance, has that assertion changed? You only use the "jobname dot invocation_id" form at the command line to run jobs that are actually multi-instance, not 'normal' jobs. And please tell me you are using something meaningful for...

Enlist the help of your DBA. Have them verify if that is indeed the issue.

Ugh... why insert all records and then update them afterwards to set the timestamp? Set the timestamp in the transformer and use it in your DML. Biggest question to me is should each record have a 'current' timestamp, as in one that changes over the course of the job run? Or should each record in th...

There's only one job, even if it is 'multi-instance'. However, you can run multiple copies of it at the same time, as long as the Invocation Ids in use at any given time are unique. The 'main' job will always show as 'Compiled' in the Director while any invoked instance will be where it shows 'Runni...

Never had to do it, but if I had to I would go to the online help Index and type byte to see what turned up.

Doesn't really get any simpler. Don't you have the Convert function in PX? Or EReplace? While I agree it would be best to generate it the way you want it, but failing that it is easy enough to swap the delimiters: Convert(":",".",YourTimestamp) Perhaps another function wo...

I doubt you're "going wrong" anywhere. Just seems like you need to translate the colons into periods after you've gotten the timestamp, if you really need it in that format.

VCInDSX wrote:Is XML Reader/Writer a deprecated pair?

Yes.

Is that a supported compiler for PX on AIX?

I'm sure it would. However, I don't know DB2 and don't have access to it in my environment. What did your DSLogInfo message show?

In a nutshell - speed.

Look closer. Don't assume the exact name of the section, you're in the right place. I can't check right now, but it's not that hard to find.

Just use the type that is appropriate for the file. I don't seen the need to convert everything one way or the other, per se. And it's easy to check.

Open the file in vi. Look at the end of each record. Does it have a "^M" at the end? Yes = DOS file, no = UNIX file. Easy Peasy.