DSXchange

Though you can ask, there are no 'free trial' versions of any of this software. And if this helps your search, DataStage TX (like PX) was acquired from another company, rebranded and merged into the product line. Used to be called Mercator btw.

The output link going from nested condition sequence to the first job is blue and the rest of the links are black. Is that a sign of error? Does anyone have any idea what should I check? Sequence jobs don't color links like a job with active stages does, they just indicate the type of trigger on th...

ray.wurlod wrote:Using these would make the meaning in your expression pellucid.

As noted, substring was just one way... these are another. To be transparently clear.

You could also go Old Skool and export the jobs to a .dsx file and then use an editor to search the export.

Why is that so??? Not much of an answer other than - that's How It Works. You need to become familiar with where the surrounding markers are required and where they are not when using Job Parameters. If you are unsure, best to use the ellipses (...) to build the expression rather than typing it by ...

If 'batch job' means those 'Batch::' job control collections created via the Director (or Designer with no objects on the canvas) - yes.

If you mean something else, let us know..

So... you didn't notice any difference between the two examples?

Sounds like a daily challenge.

When you say 'this is what I have' does that mean you are currently generating that output? If so, it should be fairly simple to add a couple of stage variables to check for a Header record and increment a counter each time one is encountered.

Yes, Sequence jobs can be 'called just like a job' from a Sequence job. So, except for this separation and triggering days apart that you've mentioned, you could have put all three in a 'Master' Sequence job.

I've never seen XML 'Reader' or 'Writer' stages - perhaps they are synonyms for the XML Input and XML Output stages. Where did you encounter these terms?

Not any more. You'll need to find out where it lives on IBM's site... if it exists there at all. You may need to contact support to acquire it.

It just means that line-feeds - hex 0A which are record terminators in UNIX - are treated as data instead if found in a column with that option enabled. Which is pretty much exactly what you quoted from the manual.

If InputColumn = 'begin' Or InputColumn = 'end' Then Expression1 Else Expression2 Um... that doesn't check that the field starts with those values, that checks if they are equal to those values. Substring would be one way: If InputColumn[1,5] = 'begin' Or InputColumn[1,3] = 'end' Then Expression1 E...

From searching the forum, this looks like it can happen by checking the 'Omit' option when logging in - are you doing that?