DSXchange

Do you not realize that saying "special characters" is pretty much meaningless? Most of the time what people think are "special" or "junk" are just characterset conversion errors or perhaps ones they've never seen before and "cleaning" (as in removing/strippin...

Permissions.

Who all has this problem? Everyone? Just you?

Search again because this has been posted before... unless "no luck" means something other than you couldn't find anything. I know because I've seen the same message and posted about it here.

Parallel routines are written externally in C++ and (from what I recall) all the 'routine' entry turns out to be is an interlude / pointer to it. Not my area of expertise by any stretch, however, but the process should be documented. Somewhere.

Assuming that's not a disk space issue, then it would be (as noted) permissions.

I assume it's the one on his website's Tips page. Also see if this helps:

viewtopic.php?t=114828

Not that I've seen. People with that requirement seem to export the whole thing and then hack it up afterwards - a search for "dsx cutter" should bring up some old conversations and perhaps even a perl script to do that. Others have done as you've noted - create a control list of the compo...

Even more reason to be puzzled as to the reason you are having issues with the approach. Ah well, at least you found something that works for you.

I'd be surprised if that part makes them "huge" or adds a great deal of time to the process but who knows. If you really need them gone, you might want to consider a post process (script, Perl, ds job, etc) to remove that section from the export before you version it.

You'd have to identify the character first. Any way to get the hex/decimal equivalent of this "square"? Oracle has a DUMP() function but no clue what DB2 has. That or write it to a flat file and then check it with a hex editor / viewer.

OK, that makes more sense.

No idea why the issues, however, unless it's got something to do with leveraging it in a Server Shared Container in a PX job... or is this a Server job now? Lost track.

just4geeks wrote:

ArndW wrote:"Pathed" filenames use OPENPATH while VOC filenames use OPEN. Which is being used in your routine?

The pathed version uses OPEN and it now works in the job. The unpathed version uses OPENPATH and it fails to run in the job.

That sounds completely... backwards.

The whole point behind creating a 'pathed' version of the routine was so there would be no need for a VOC record. It's always worked fine for me, I would verify you're always passing the full path correctly to the routine.

And?

ArndW wrote:blah-blah homologated blah-blah

Jeez, had to look that one up.