DSXchange

But you do have at least one timestamp in the data stream?

What you have NOW is irrelevant. What you have when the job is running is what's important. And the error message suggests that what you have now is insufficient for what you need then.

Within a job? No.

Check your work, double check, and have a colleague check it. I can't see how this could happen. What exact version of DataStage?

Maybe have the janitor look at it as well (old joke, but a good one).

One of the tools in the Designer toolbar is Resource Estimator. It will do all that and more. You can also set the environment variable that causes player processes to dump their PID into the job log at startup and monitor those processes' memory consumption.

Get the syntax correct by selecting activity variables and DS Constants from the Expression Editor operand menu.

The easiest solution to this is to use DataStage BASIC's innate ability to treat a file as a record in a database table, where the table is the file's parent directory, the name of the file is the "record key" and the data in the file the "record contents". This is achieved simpl...

Very urgent? We don't do "urgent". DSXchange is an all-volunteer forum whose members post as and when they can. If you want urgent help sign up for premium service from your official support provider, and learn just how much "urgent" costs. Meanwhile, have you attempted to write ...

You're thinking of Execute Command activity. One ought not to get line terminators in output of routines.

Moderator: please move to parallel forum

Server jobs do not have a funnel stage.

They do (post correctly) if you wrap them in Code tags! PARAMS = '' ; * this initializes the array variable ArgString = DSGetJobInfo(DSJ.ME, DSJ.PARAMLIST) for i=1 To NbArgument ; PARAMS<i> = Field(ArgString,",",i,1)) Next i Don't use the DIM function - read about Dynamic arrays Next you n...

Welcome aboard. One of the things we can't deal with is "it doesn't work". You need to be more specific. For example, are any warnings/errors logged? Please report these fully and accurately. You ought not to need an alias, particularly if SQL Server is otherwise visible from your DataStag...

Only that something, somewhere HAS changed, and you're going to have to track it down. Good detective work so far, you might also question anything "I'm told" and check.

If you're sorting using the sort command as a filter in the Sequential File stage, why not just add the "unique" (-u) option to that command?

One of the upcoming Tips and Tricks papers at DSXchange Learning Center deals with pattern matching (including the MatchField() function) in DataStage.