DSXchange

I once had the DataStage client break on every desktop in a training room halfway through a training course due to a dll file pushed onto the computers overnight. Had to reinstall the client on all machines. After that we shut down the machines at the end of each day instead of leaving them on but l...

I thought it was theoretically possible to implement server jobs on an MPP by using the SOA edition. Your large server jobs would be turned into real time jobs but called up via a standard batch scheduler, the SOA agents would then decide which server to run it on. Sorry I'm a bit vague on the detai...

The sequence job will run for any user who has a Director since it runs on the server. Compilation however occurs on the client. Therefore a sequence that has run successfully for weeks but wont compile indicates a problem on your client machine, ie no write access to the DataStage client directory.

There is a thread in the FAQ forum on DataStage job reporting options.

I think that's an argument for doing testing and training rather then for writing your own restart checkpointing. Checkpoint can very easily be cleared out, if someone resets the sequence job or recompiles the sequence job. Perhaps the drawback of sequence job restart is that you cannot manually set...

Any reason why you are upgrading to 7.1 and not the newer 7.5.1?

It is as simple as checking the check box! The main considerations - you need to make sure you restart with the same job parameters as the failed sequence. You need to consider whether you should should be restarting jobs that update aggregate database tables or perform database inserts. Your suppor...

You need write access to your c:\Program Files\Ascential\DataStage directory (or whatever equivelent directory your DataStage Client is installed to). Do a search through the archives for other threads on this error.

I am going to resurrect this old thread because we are also getting this error and we have opened a case with Ascential support. There are two Lookup stage errors that abort a job even with a perfectly valid lookup stage. Both errors happen if you have column propogation turned on and make changes t...

I assume you want to replace your old DataStage BASIC routines with C functions. These functions can be called directly from a parallel transformer and the sample functions are a good place to start. It is written in a C language so you should find a good C reference book, I don't think Ascential ha...

Read the chapter on Custom Stages in the Parallel Job Developer's Guide . Correction, look in the Parallel Job Advanced Developer's Guide. Going to add this thread to my favourites. You can also look in the old Orchestrate Guides as they have some more sample C code and are sometimes more complete ...

Have you tried recompiling the job?

Server jobs are easier then parallel jobs, a hash file stage and transformer stage is easier to learn then lookup + join + merge + change data capture + filter + modify + transformer + change data apply + dataset + fileset. Especially since the change capture stage produces a mountain of warning mes...

For DB2 SQL State is the correct error message identifier, not SQL code. You will find this field on the right mouse click menu within the Transformer - set up an output to the DB2 stage and an output to a reject file. Create an output field for your reject link called SQLSTATE as an integer field. ...

Normally DataStage interacts with a database by reading and writing against tables. The enterprise PACK gives you an intelligent layer between the Oracle database and DataStage making it easier to import metadata and interface with Oracle application databases. Impossible to tell from the web site w...