DSXchange

Sounds like your target database, or the network connectivity to it, is down. In other words, not a DataStage problem.

Read it with the Folder stage.

So, your DataStage server is installed on Linux rather than Windows? That OS: prompt where you put 'Windows' as the answer is meant to be for your Server as we know all clients are Windows clients. In any case, there were ways to fix the "schema" issue you have now in the past with earlier...

I'm curious why you have code to do inserts into your target hashed file and am wondering if simply turning that into a job using a hashed file stage would solve your problem. Any reason this couldn't be a job?

Please don't post the same question multiple times. Answered here - more than once.

Again, there's no "coversion" needed here, just a substring to remove the time portion.

And you would use "D-YMD[4,2,2]" for "yyyy-mm-dd". Note the dash between the "D" and the "M" to match the delimiter needed/used.

Sure, you've made the process harder as there's lots of little fiddly bits to bring over but the backups don't really come into play as there isn't that remote danger of destruction of the 'old' server. That and you'll need to install the Multi-Client Manager and both clients in separate directories...

There's not a lot of true 'converting' in Server, it is very forgiving. Here, since your format is correct, you can either substring the date portion or use Field() to get it:

If 'DSnum' is the internal job number used in all on the control structures names (like the 'nnn' in RT_LOGnnn) then you can query that from DS_JOBS: SELECT NAME, CATEGORY FROM DS_JOBS WHERE JOBNO = 'nnn'; Going back to it from the PID is another kettle of fish, not sure off the top of my head and n...

No issues that I recall seeing. There's no "special" precautions, just all of the usual ones, primary revolving around backups and making sure you have them. And make sure you upgrade all of the clients as well. Will this be an "upgrade in place" or will you be building a new ser...

Please start your own post and include your own relevant details.

So the 'this' from IBM was to make sure you include the domain in the dsjob command line?

Involve your DBA, have them monitor the database process and ensure there's no locking problems either with your own job or with some other processing.

Toad <> DataStage. While a query is a query they execute in quite different environments between the two tools. Toad is all about returning you the first few rows while OE will need to process all. What you should be worried about is the explain plan which is not something anyone here can check for ...

No, just like it says it means you can only use that option from DataStage installed on a Windows server, not a UNIX one... it being a Microsoft product and all. :wink: Your only other option is to ftp the file to the database server and then remote execute a scripted bulk load on that server. From ...