DSXchange

Bad advice in this case. What Mandy seeks to do it to find out why SIGINT signals are being generated (they cause jobs to abort) and to prevent them from occurring. The first step would be to determine what is causing the interrupt signals. Fatal errors can not be modified using message handlers.

Use sorted data, and stage variables in a Transformer stage to detect duplicates. Search the forum - this technique has been described before.

Please ignore the advice from sreddy; it is too narrowly focussed. For example there is no guarantee that the source is a database table.

How, in your locale, do you know when daylight saving time toggles? (It's different, and indeed variable, in some parts of the world while other places simply don't use it.) Once you have these rules documented you can readily incorporate them into a routine.

Microsoft knows far better than you do what your requirements are, and therefore you clearly need these quote characters.

(No, I don't know any way to strip them.)

About the only way you could effect this level of control would be to intercept the commands that start jobs and use a script of some kind to detect the user ID to deny access where necessary. The particular combination you specified can not be effected using DataStage roles or file system permissio...

Welcome aboard. :D

The best kind of design document for ETL is a target-from-source mapping. Investigate the FastTrack product which gives a spreadsheet-like interface to doing just that and can then generate DataStage jobs at the click of a command button.

Reposting the same message after an interval serves only to clutter the server. Please don't do it.

Looks like the license date is corrupted. Visit the Administrator client or use uvregen to re-license DataStage.

When you did a Search on DSXchange, what did you find about this particular property?

The QualityStage plug-in stage has two parts (as do most plug-in stages): a server part, installed on the DataStage server machine, and a custom GUI, installed on the client machine(s).

I don't believe so.

What does the incoming value look like?

What did you find when you did a Search for this error?

Never "I am sure". Always check.

No. Excel formats each cell (by default) as Microsoft thinks fit. You have to apply a General format (or something else) to the cells. This is not a DataStage issue.

Good catch! Please mark the thread as Resolved if you believe it is.