DSXchange

You may need to have your DBA clear pending changes if you have not managed successfully to roll back any transactions that you may have started.

You simply schedule the run JCL that was generated by DataStage.

Assuming, of course, that you have already successfully executed the compile JCL.

Done. You only missed one word!

If month might be one or two digits, the Field() function is more appropriate.

Adapt as required for different delimiter character.

Enabling the write cache will improve load performance (elapsed time) if the hashed file will fit into your cache. Size of the cache can be set using the Administrator client, but to no more than 999MB. This is probably enough for two million short rows. Not loading any column or row you don't need ...

I'm sure someone posted this link recently, to the eServices web site. Try a Search.

Inspect the generated osh for the job, look for any occurrence of FILLER. Working backwards, determine in which link (or, perhaps, schema file) it appears and make appropriate adjustment.

If you find none, and the problem is reproducible, log a support call. You may have uncovered a bug.

All complaints to billg@microsoft.com

The Cartesian product "solution" proposed by a couple of posters will be very long-running if both tables have large row counts.

sud wrote:I have used direct path in the location property and it works (cant access DS right now hence cant tell u the exact name of the property). In my case i put a path like /home/<name>/<folder>

Was this in an FTP Enterprise stage?

You don't really need to back up the whole installation (though it's not a bad idea) - simply reinstalling the server would have a similar effect except you'd need to reconfigure .odbc.ini etc. You can back up your design components (the DS_... hashed files) any time, even if jobs are running, provi...

I believe only single-character delimiters are handled. Have you tried a non-printing delimiter, such as Ctrl-Y (025)?

What looks suspicious? There are not error/warning messages, though it appears you have tracing enabled. Have you created user IDs for qsserv and qsrtmngr and, if so, are these also in the dstage group? Have you checked that you (or someone) actually deployed the SCVSTAN job? All QualityStage jobs m...

Please explain exactly what you did and why you believe it did not work. What is the nature of the "script" in which parameter values are to be found? Do you have code in your job control to read that file?

A project can certainly be exported just after installation and subsequently, and in the event of disaster a new project created and the export imported into it. That's possibly easier.

Never, ever, say "doesn't need backup"!