DSXchange

You bet. Or from a 6.x job or a 5.x job or...

I don't think there's anything major to worry about. The readme should include any points of interest, things that have been changed in the new release.

If that's the case I'd say that's a new bug, not something corrected, and it should definitely get presented to IBM/Ascential support.

I'm curious, though - not only should it not be sorted but that last constraint (And CT.CASE_REPORTED_SFX > ' ') should also not be happening. Is that true?

Sometimes it is trivial. Back in my Informix days, a SERIAL column would generate a new unique identifier upon insert (if you fed it a zero) and then a check of a specific field in the SQLCA record would retrieve the inserted value. Not sure how you would manage that in DB2 or DataStage for that mat...

Not really. As long as there's a return at the end of the commented string, the comment should end there. In any tool, I would think. If it's really the case that everything from there down is now commented out in 7.5.1A, alot of the jobs that other people have written here will break as well when w...

Umm... that's not hex, that's EBCDIC.

Lance - If you're on 7.5 you can use that spanky 'message handler' functionality thingy. I think you may be able to suppress specific messages, or at the very least 'promote' or 'demote' its severity level, changing it from a Warning to an Info message. From what I recall in our class, all you need ...

Well, that's too darn bad.

I was speaking from my Oracle experience, should have figured SQL Server would work differently...

It's not about the links, it's about the stages. Two links into two stages = possible locks. Two links into one stage = no locks.

mhester wrote:Craig - maybe it's time I write that FAQ?????

Perhaps... perhaps...

Sorry, not off the top of my head. My DOS days were long ago and far away.

Yah, it's been posted here more than once that the DB2 plugin is different from any other DB plugin in that it wants dates in internal rather than external format for some reason. As to the reason, you'd have to ask whomever wrote the darn thing.

Sorry you had to go through all that.

You could work this out after the Aggregator by building a 'single' record with all of your desired fields in it, formatted as shown but with a record terminator between each 'record'. For UNIX that would be a line feed, for Windows a CR/LF pair. It would then be three records when read by a subsequ...

When ever you run the dsjob command it only echos the job status not job return code. Not really, the behaviour depends on the command line options you choose. Assuming you are wanting to wait for the job to actually finish before moving on to the next step in your script, it works one of two ways:...

You run this on every row? So for the first row it counts from 1 thru 1, the second row 1 thru 2, then 1 thru 3, etc? Is that really what you want? For example, the Amount passed in on row 3 gets added to intTotAmount three times, does it not? Why not just write this information out to a flat file a...

Not that I'm aware of.