DSXchange

Keep the solution you have.

If you're not using a correlated subquery which I assume you don't - for a fixed value per job - then that piece of SQL code gets only executed once.

Ogmios

Where do you find DSWaitForJobList in the documentation? I find DSWaitForJob but not the one you use. From the error message I would think DataStage does not think the DSWaitForJobList exists as well.

Ogmios

Has been handled pretty recently at:

viewtopic.php?t=86538

Ogmios

When generating it from DataStage you don't get the microseconds. You should be lucky to be able to get seconds as smallest measurement in DataStage.

Ogmios

The easiest solution if you want to use the "current timestamp" on the DB2 side is to: * not include the timestamp column in datastage at all * for inserts: have your DBA make the timestamp column: "generated by default as current timestamp" in the DDL (or generated always whatev...

Try executing your SQL query in the database's own "tool", it may give you a better indication of the error. I don't see anything wrong with it a first sight (it may just be a typo in the column names).

Ogmios

Solaris 8/Sunfire (with a big number :) ). The pictures in the presentation don't look like a representation of the standard DataStage edition: e.g. haven't seen a "player" mentioned elsewhere in the documentation I have (will check with Ascential). Right now I was thinking of rolling our ...

As high available as possible. We already have "high availability" on hardware level, every component is duplicated: when a disk crashes its mirror is automatically used, when a backplane gets broken the machine reboots and automatically switches to a backup backplane. Now customers want t...

Does anyone have experiences with DataStage High Availability on Solaris UNIX Machines? Has anyone already implemented the failover scripts that are shown in the "DataStage Operator Tips Tricks Final Version Customers.ppt" in the files section of http://developernet.ascential.com ? And do ...

Aaaaaah, so what you try to do is to launch queries via DataStage but for the rest don't use DataStage. It would work but it's not really the way to use DataStage. You won't be able to see e.g. from the log files how many real rows were processed. It should work and since the insert and delete are n...

Hi Folks, I need to move records from temp table to the final table. Can you suggest a good approach so that I can move data from temp table to warehouse and then delete from the temp table. I would prefer not to pull the records into ascential's memory and at the same time would need to keep the i...

Look whether you have a link called .dslibs in the / on your system, it should be there.

This should point to the /"..."/Ascential/DataStage/branded_odbc/lib directory where "..." is wherever you installed DataStage to. It should not point to a dummy directory.

Regards,
Ogmios

ALWAYS use root to install DataStage (on UNIX). When using root it will put some suid bits on the binaries which allow Datastage to switch the user ids of the DataStage jobs that it executes to the user id you run the job with. It will also allow the engine to run with a little bit of extra privileg...

Have a look at a previous discussion: viewtopic.php?t=84050

The quick solution is to do a "Clear Statusfile".

Regards,
Ogmios

Strange, normally either the "Do not timeout" is switched on (and the "seconds" are greyed out) or the "Do not timeout" is switched off (and the "seconds" are changeable). Are you sure you're logged on as DataStage administrator? Were you in the meantime alrea...