DSXchange

The User Guide does a good job of describing what's in a rule set. Start by reading that, in conjunction with inspecting the files associated with an existing rule set (which you can do from the Designer). DSXchange Learning Center is currently developing some materials relating to QualityStage rule...

It's a value mark, its ASCII code point is 253 (decimal). You can use tr to convert it to some other character, such as a comma. \375 is the octal equivalent. \xFD is the hexadecimal equivalent.

How about a shell script that loops through the file names generated by the regular expression and issues the orchadmin against each? (Yes, I know you're on Windows, and I also know that MKS Toolkit installs with version 8.0 on Windows, so you can use a shell script.) for filename in /IS_Projects/DS...

DataStage can handle valid scientific notation numbers provided that the exponent is not more than 38.

That's Windows, not DataStage or Oracle.

It won't really help unless we know the provenance of DStageWrapper. Does it come with DataStage, does it come from IBM, does it come from your particular reseller, was it written in-house? What's in it?

Or port #31538 is blocked by firewall software.

Your reviewer is basing these calls on outdated knowledge.

Demand proof that the Transformer stage is more burdensome that the other stage types. In 7.5 they did a lot of work on the Transformer stage; under some circumstances it can be more lightweight than other stage types.

Yes but you have to write your own after-job subroutine that encapsulates both. Use DSExecute() to invoke the shell script.

The aborted job is "attach locked". You need to detach then re-attach it before you can reset it.

Would it not be easier to call DSPrepareJob() before attempting to run the job? This is the function behind the "reset if required, then run" functionality in job sequences.

Have you tried to start DataStage on the DR server? Does dsrpcd start then stop, or not start at all? Try starting dsrpcd in debug mode.

SLEEP seconds

SLEEP hh:mm

NAP milliseconds

Each of these is a statement, not a function. The hh:mm format for SLEEP uses a 24-hour clock, and causes the process to sleep until that time, or not to sleep at all if that time has already passed.

myukassign wrote:Can I pass job parameters as the parameter value in this function?

No.

You can pass the value of a job parameter, but you can not pass a reference to a job parameter.

You're all crazy! Use an Aggregator stage to sum the column. Specify no grouping columns. It will use no memory (apart from the actual running sum) and be very fast. And it will require no "programming".