DSXchange

A little confused... the metadata in the job still declares these fields as Char(30) or you reimported from Oracle and they now show as Char(90)?

It has a tendency to do that. You just need to reset the size if that's the case.

Yes, you can.

Suggest you actually read the thread you decided to drop into. The first reply waaaaay back up there tells you what you should be doing.

Sorry, this is a hijack plain and simple and you should have just started a new post for your issue. And FYI, there's no way to prevent creating a flat file when no records are processed. None.

What kind of routine, BASIC or C++? For use where? What have you tried so far?

Your LD_LIBRARY_PATH is set in the dsenv file in $DSHOME. You need to edit it to include the folder where the ".so" file mentioned lives and then stop/restart DataStage.

Not exactly a beginner's task you've taken on. What exactly do you mean by what you posted? You will be doing this "passing" from the command line using dsjob, or inside a Sequence job to a Job Activity stage or what? Do these files have a single record in them or multiple records? Do you ...

OK. There are ways to automate that list so you don't need to paste it in like that but if that's working for you then good. Let us know if you want to discuss the "not as expected but fine" part.

It's important to understand that the status of a job is basically just a 'flag', something that gets set when the job starts and adjusted when the job finishes. So server crashes or unusual situations where a job may just core dump and fall over dead can leave it stuck forever in a 'Running' status...

Sure, from the online help switch to the Index tab and look for 'server job, reject links' and 'reject rows' - both are good places to start.

What "files in the job" would you be referring to? How did you imagine that simply copying the job would allow that to happen?

Yes, of course. Unlike the PX product which defines rejects from the DB stage itself, for Server you would create a Reject link from the transformer feeding the database and use it to check for and write out anything 'rejected' by the database.

Your 'best practice' is specific to the PX product and the OE stage, so not applicable to the Server product whatsoever.

It's an Oracle setting you would have DataStage provide. There's a place in the stage for 'load options' I do believe, can't check right now however.

Without getting into why you felt the need to copy it, perhaps your user doesn't have the permissions it needs?