DSXchange

Import warning at record 0 can also mean you forgot to set the "first line is column names" property to True.

The ^M character is probably being interpreted as a line terminator. Can you successfully extract data directly (not using FTP background)?

No problem whatsoever. The training class uses flat file exclusively (for portability reasons).

Just be connected to any network that can serve you an address. Then it all works happily. I don't know the cause, but I have to use this technique way too often!

Welcome aboard. :D

As you can see, this error has been reported by the DB2 client, if not from the database itself, rather than DataStage. Enlist the help of your DBA to trace it.

Not that I'm aware of. Pretty any other product, but no mention of DS.

You should be able to adapt the following code to your requirements. It reports the name of the job itself if it has no controller. FUNCTION UltimateController(JobName) $IFNDEF JOBCONTROL.H $INCLUDE DSINCLUDE JOBCONTROL.H $ENDIF Controller = "" TempJobName = JobName PrevController ...

Of course you can, how else could you determine its running status to be "running"?!

For parallel jobs there are some known issues with the Oracle OCI in importing table definitions. Prefer to import the table definitions using Orchestrate schema (dbutil).

Probably the overwriting of the job handle. Definitely the illegal comparison with @NULL (you must use the IsNull() function to test for null). Failure to detach jobs when done with them probably doesn't help either. A possiblity would be re-cast this routine so that it could call itself recursively...

But it's a one-off. Why not just search and replace using your favourite editor?

Of course it will! There's no such thing as a free lunch. You can't have your cake and eat it too. <<Insert favourite cliche here>>. It's a fundamental fact of performance monitoring that you want to impact the object being measured as little as possible. But your original question did not pose any ...

Can you garner any more information from the generated OSH? It appears to be complaining about a link - are you certain it's the XML input link? Can you post the exact and complete text of this error message? I presume that the job compiles without error.

As Arnd suggests, there's not sufficient information to get "the point at which a job failed" through the API. For a severe enough failure, the job will not have been able to record the fact that it failed! The best you can do is grab the log for the current run of that job, using DSGetLogSummary() ...

Would it work better if you invoked your map from within a DataStage server job (through a DataStage TX stage) and exposed the server job as the web service? Just a thought - I have no experience with DataStage TX whatsoever.