DSXchange

Good. I seemed to recall you stating this in the past but wanted to double-check. Thanks! :D

Just wondering if I should be concerned about something. I'm taking a routine that passes in as one of its arguments a dynamic array of indeterminate size and modifying it to take three arrays. I really can't say how large is 'large' as they will change in size from run to run and call to call but I...

I would think that's really a question for IBM, but perhaps someone here knows as well.

No time to speak of. It basically deletes what's there and recreates it empty, from what I've seen.

Not sure there is a 'best' way. Command line ftp is a way, as well as scp. Many shops have 3rd party utilities they've purchase to transfer files. Ask your Admins there how you should be transferring your file.

You'd need to 'attach' to the job first to establish the handle. How about posting the relevant chunk of your job control code?

Ah... sorry - the DEFFUN is not needed for internal functions, but for other routines, yes. And depending on the function, you may or may not need to 'include' anything.

Pretty much exactly what Ray told you when you asked this same question in your other thread.

If your hashed file needs to grow beyond the well-documented 2GB size barrier with the default 32bit addressing, you'll need to create it as a -64BIT hashed file then.

AHA! There's the secret.

Isn't there more to this in the 8.x release now? The issue could be in the relational repository, yes? Or would that generate a different error, I wonder...

Line 676 is not from the job, it's from the program noted in the log message - an internal DataStage program called DSD.StageRun, of which we don't have access to the source. So... Doing anything... strange... in the transformer in your derivations? Using stage variables? Etc. If you rerun the jobs ...

That's true... if you are producing this for consumption elsewhere (like a mainframe) then you may be able to write it out as normal ASCII and then have the transfer mechanism do the EBCDIC conversion. May be complicated if you have any packed fields, however.

The host or even the network. You'll need to involve your network and/or system support people to figure it out.

Actually, AFAIK you *should* be able to 'just send it' but honestly never had a need to try. Do you have NLS enabled?

Also, what are you using to view the file after it is created?