DSXchange

The short answer is that UniVerse (the original underlying engine) was out and about well before Windows appeared. It's originally a UNIX-only application, where case-sensitivity is assured. The only "fix" you're likely to get is a documentation fix extending the prohibition on duplicate routine nam...

I don't propose to transcribe the DataStage BASIC manual here. This is the ultimate source for questions about the language, and installs with every DataStage client. For REMOVE to make sense you first need to get your head around dynamic arrays.

Turn Write cache off. This hashed file (14GB if no overflow) will never fit even in the maximum possible write cache (999MB).

The message is simply alerting you to this fact.

Tell the Win Admin nowhere

DataStage is a 32-bit application. It uses malloc() to request only the memory it requires.

Why is that a problem?

If your Win Admin can't understand that, a job with Micro$oft is probably beckoning.

All of the DataStage API functions only operate in the current project. To work with a separate project you will need to use dsjob (which has to be told which project to attach itself to). You can, of course, invoke dsjob through DSExecute(), etc.

Welcome aboard. :D

That's a useful tip - we usually assume everything we need is ready and waiting. Did not the UNIX Administrator notice that not all the mounts had succeeded?

Derivate?!!

But my DB is huge. So, I can't use the Lookup stage unless I make it a Sparse Lookup. I have done that. Since my input file also has a large amount of data, I was just wondering if we had any other way to implement this. But you asserted that this is a server job. If it is, then an ODBC stage with ...

Are you surfing away to other web sites? That's been known to do it. Send an email to the webmaster explaining precisely what you are doing when you get logged out, for example trying to send a post, open a post, open a different forum. Also advise what anti-virus software you have running. DSXchang...

Premium membership is only a few cents per day (corporate discounts are available - see link from home page) and helps to fund the bandwidth charges that DSXchange incurs. Read my previous post again. This is the answer you will get from support. Then get yourself a less flaky operating system (any...

Not enough information.

For example, how can you assert that "The above fatal error is occuring in Transformer (both Transformer and basic Transformer)."? What proof do you have of this? What other error/warning messages were there that you have elected not to post?

To quote the Sergeant-Major from "It Ain't 'alf Hot Mum":

Sergeant-Major Tudor Bryn 'SHUT UP!' Williams wrote:Oh dear. How sad. Never mind.

Don't worry about .| at the end - the "." is the end of the sentence and the | seems to be a newline or something - I've often seen it. I'd be checking that F:\ is not full, and that you have access and write permission to all the folders in the path F:\DataStage\ProjData\PMIERP\LEDAR_D1WorkFiles\Ha...

You know the job name. You can attach that job and use the requisite functions to interrogate its log. Don't forget to detach the job before exiting from your routine.

All you need to know is here

OK, so maybe there's more we need to do.