DSXchange

You need quotes surrounding the literal values in the trigger expressions. Otherwise, the single letters are treated as variable names when the job sequence is compiled.

It's the usual Windows thing. There are new DLLs being emplaced. Re-booting is the only way Windows can guarantee that the new ones will be loaded when called. Otherwise there's no guarantee that the old ones won't still be resident. It may work without re-booting, but there are no guarantees.

Please post the complete error message.

What evidence do you have for making that statement?!! None, as far as I can see.

Convert the number to a string, add a day number (such as "01") in the appropriate location for your date format, then use a string to date conversion function.

What's different on the different days? (Note: "nothing" is not the correct answer.)

Clearly, if your job design has not changed and not been recompiled, then the problem does not exist within DataStage, at least not within that DataStage job.

What other jobs are running on each day?

Use an Aggregator stage. That's its function. Use the right tool for the job.

Somewhere you've specified the execution mode as Sequential. Track this down. Use the words in the error message to help.

See response in ProfileStage forum. It's the same problem here.

Some ODBC drivers for Excel don't like worksheet names that contain spaces or are otherwise non-conforming to ODBC naming rules. The worksheets themselves must be in strict columnar format with the first line containing column headings that also conform to ODBC naming standards. If any of these cond...

Check spelling. Check casing. Check that routine is compiled.

Unless you do something to it, it is not possible for the row counter to be in anything but its generated order. What are you expecting, what are you getting, and what is your job design?

That message (dimensioned array not found) typically means that the routine has not been compiled/cataloged, or that you have mis-spelled or mis-cased its name where you have used it. Or, if you have used it in a routine, that you have omitted the DEFFUN declaration for it.

There is no simple command. The export MUST be performed from the Manager client. It is a non-trivial exercise to unpack the nested structures used within the Repository into a normalized structure as used in the Reporting Assistant.

Provide an explicit trigger from your Routine activity that handles all expected return values, so that the default behaviour (of treating any non-zero return value as a failure) is pre-empted.