DSXchange

Which rule set uses these literals (I am not in the USA)? The names suggest "mixed numeric", "mixed alpha" and "mixed something beginning with R" - possibly very mixed tokens such as R2D2.

Not directly within IA but, if you create an appropriate view in the source, then you can profile the view.

I don't see why this couldn't be written to handle execution on multiple machines, whether in a cluster or a grid, though the information would have to be collected (and maybe reported) per-node, just as row counts currently are. One of the additional items of information might be the number of rows...

What is your specified delimiter. The stage has read the four characters indicated. Could there be line terminators in your data?

Go for it.

Same as the Sort stage. The tsort operator is used in both cases. It will attempt to do the entire sort in memory until allocated memory is exhausted, then spill to scratchdisk.

Put a DSLogInfo() call into your routine to report what pathname it received. Put DSLogInfo() calls into all four clauses of the OpenSeq statement to report which is taken. Put a DSLogInfo() call into the Then and Else clauses of the ReadSeq statement to report what happened and what was read.

What if you use two Lookup stages, so that you're not mixing lookup types? A range lookup compiles to a transform operator whereas a normal lookup compiles to a composite (LUT_CreateOp/LUT_ProcessOp) operator.

Or quantum physical data!

Does the executing user have INSERT privilege to the table in question?

(If you don't tell us, we have to ask.)

Might have a REALLY FAST processor!

Please mark thread as Resolved using green button at top. Well done for finding the solution.

You can use an after-job routine quite happily. It should use the log interrogation functions DSGetNewestLogId(), DSGetLogEvent() and/or DSGetLogSummary().

When you switch to LDAP, assuming it's done properly, all of the internal user registry users are eliminated. The new administrator is the LDAP server user name. You need to open web console for Information Server logging in with this ID, allocate the Suite Administrator role to one or two LDAP user...

Message handlers are based on the Message ID.

Only that particular message ID will be masked. And only in jobs for which the message handler is loaded.