DSXchange

The Modify stage KEEP specification can (and should in your case) be a job parameter.

2016-01-18T12:34:56.123445 is a valid timestamp. Will your tests handle it? How about "2016.01.18 12.34.56,123445" (which you are unlikely to encounter in Australia)?

I note that you have marked this as Resolved. I assume that you are only validating a single, very specific timestamp format.

The "Where Clause" property of the Filter stage can be a job parameter.

In your examples, this would need to be the entire Where Clause. It could be built dynamically in a sequence job, for example by invoking a routine or by doing something with user variable and loop.

As noted, MATCHES_REGEX is your friend. Time validation requires a very straightforward regular expression. Design it yourself, or find one on the internet. Two scenarios only are needed. First digit is 0 or 1, second digit is 0-9, third character is ":", fourth character is 0-5, fifth cha...

In Information Analyzer I prefer to use MATCHES_REGEX as it's more flexible handing variable numbers of fractional seconds. You can also handle variations such as a "T" rather than a space between the date and time components. Google regular expressions that match timestamps. There are sho...

Welcome aboard. Become familiar with the date functions in the parallel environment. For example MonthFromDate() gives you the month number, from which you can obtain the quarter number and, by inference, the beginning and end month of the quarter. The day number of the beginning of the quarter is a...

I recently posted a routine for "looking up" the jobs called from a sequence. The logic of that may help.

What (precisely) do you mean by "event" here?

We prefer to group by neither source nor target but, instead, by major subject area and then by job type (update, insert, recovery, sequence, etc.) For example, the Allowances subject area will have sub-folders Update Jobs, Insert Jobs, Recovery Jobs, Sequence Jobs.

Perhaps it's the buttons in the tools. Try running from the menu. If this works, close the Designer and Director windows (ideally re-boot the client machine) and start with newly-opened clients.

Welcome aboard. Which stage type(s)? What have you tried?

My solution does not involve @INROWNUM. If you use @INROWNUM it increments on each node, though that would work OK in a two node configuration using Round Robin partitioning if your data were sorted by the integer value to which you referred. But you described your requirement in terms of pairs of r...