DSXchange

This isn't an issue I'd worry too much about 'fixing' but I would imagine the solution you found earlier is still viable if they really bother you.

As Ray would say, the issue of Premium Content is easily solved.

It really is as simple as the links are completely processed in order, so the first one must go to the target and its fate determined before the second one is... released. Now, array and transaction sizes can complicate error reporting and may affect how it works depending on the relationship betwee...

You need to switch from Delimiter to Delimiter String to see the Windows option, since it is two characters.

Pretty much except Ray threw in a little bit of high-level hoodoo to implement the DIGITS transform at the same time.

dxk9 wrote:Will the 1st record sent to Link 1 gets processed before its being sent to link 2 ??

This.

Hmmm... don't recall an ftp issue in 7.5.1a and I spent many moons working with that product version. But I'll be the first to admit that doing multiple ftps wasn't high on the 'to do' list.

Have you involved your official support provider yet?

Ah... thanks for the clarification.

I was under the impression that ZIP+4 would actually be enough to get a unique city / state value. At least the vast majority of the time. :wink: When I needed to do something like this many (many) moons ago, I recall being told that each ZIP code will have a 'preferred' city/state with any other po...

... and nothing about that is DataStage specific, that is just the nature of buffers.

What kind of routines? All of the above mentioned ones are BASIC routines for Server and Sequence jobs and their source code is visible. Do you mean parallel routines? Those are written in C++ and are a wee bit more complicated...

At first you said globally within 'this' job but now it is across multiple jobs? Complicates it a little but you should still be able to capture it in a routine in your Sequence job and then pass it as a job parameter to all downstream jobs.

I would imagine it's an all-or-nothing proposition. Any chance you are clearing the logs of running jobs?

Sorry, back to the Server forum you go.

Have you tried using the extract() function to read the XMLTYPE field? I'm assuming you want XML back rather than pulling a specific string value.

You don't need to populate the SMTP server property.