DSXchange

I would bet on somebody from that other team writing your sequential file either during your run or between your runs.

Get on your unix box and note the exact size and time of your source file.

Run job --> check file size and time --> then repeat.

Mike

I believe a default installation of version 9 has DSODB turned on (it was new in version 8.7, but off in a default installation of 8.7).

You'll want to verify the details with whomever did your installation.

You'll find sample queries and configuration details in the IBM Knowledge Center.

Mike

Version 9x. No need to waste application cycles doing that sort of thing.

Everything you need is already sitting in a nice DataStage Operations Database (DSODB).

Mike

The join operator is not going to be your problem here. It will be the sort operator that gets inserted because the join requires sorted inputs. Sort is a blocking operator, so it won't emit any output rows until it has consumed all of its input rows. I think your temp table idea with doing the join...

My memory could be off a bit, but I don't think version 8.1 supported null in a stage variable. I think that might've been introduced in version 8.5.

Mike

The backslash is a typical unix escape character used to treat the escaped (i.e. following) character as just a normal character.

To get 2 backslashes, give \\\\ a try (i.e. 2 "escaped" backslashes).

Mike

One last thought...

Since the long startup time is not consistent from run to run, it is probably not directly related to something that your job is doing; but rather, to something that is happening in your environment.

Mike

And, of course, it includes the "real" startup time of waiting for computing resources to become available.

Since you're using Teradata, any chance that you may be waiting for a utility slot to free up?

Mike

It's not just before SQL that appears to get captured as Startup time. From what I've observed, it appears to be a catch-all bucket for any time not specifically measured elsewhere. Overhead would probably be a better name for it. Before SQL, after SQL, time spent computing database statistics are a...

Many of the database connectors support multiple input links now. See if that will meet your needs.

What is your target database?

Mike

You can build as many levels into your job sequences as you'd like. It's not uncommon to have child job sequences , grandchild job sequences, etc. If designed properly, the restart is just as simple as cramming everything into a single master sequence.

Mike

I'm not sure if I understand...

but, no...

a parameter can not reference another parameter.

Mike

When the documentation says 2 datasets, it doesn't mean 2 dataset "stages". It is talking about virtual datasets. The link from the DB2 connector stage to the change capture stage represents a virtual dataset.

Mike

A little more context please...

I should've said it wasn't an out-of-the-box DataStage function.

I assumed it to be a SQL function, while Craig guessed that it might possibly be a custom server routine.

Mike

That's not a DataStage function.

Since it's a new server, that probably means you have a new database client installation.

You'll need to check your database client configuration settings for differences. Enlist the help of your DBA if necessary.

Mike