DSXchange

So, you need to do this in a SQL query? And you need all data in this date range or you need a list of the Year/Month values between them? Examples would be nice, btw.

Details, please. How exactly are you 'executing' it?

Seeing as how it's a sqlldr message, I'd see if your DBA could help with it.

asorrell wrote:I'm not certain if you can get it to work from the admin console, but you can try it.

Works fine from there. There are also posts here showing how to launch a dssh session from the command line, run a sql and redirect the output to a file that a search should turn up.

Note to self.

Please mark your post as Resolved using the button at the top of the page.

In COBOL it would involve a REDEFINES and you'd end up with a number like 202020.20 or some such. Or 404040.40, depending on the ascii versus ebcdicness of it, from what I recall.

That's not anything I've ever seen documented... is this something that works in 7.x or was it added in the 8.x release?

Store them as 'chunks' with the client-id as a separate key field to facilitate the lookup. The chunk becomes just another lookup data field.

The command line only supports the dsx format. Out of curiousity, why xml?

Not that I'm aware of. Perhaps there's something in the registry that controls that?

An extra space at the end of the file's name caused all that ruckus? Good catch, I'll have to remember that for next time.

I'm not sure either how a simple export/import will reduce the number of directories needed. The other issue you're going to have is you will not have a working VC project after you do that. Simply bringing over the jobs is not enough, there are five magical hashed files (which an export does not in...

Yes, of course. I haven't had access to an AIX system for more years than I'd care to admit, so specific advice will need to come from other folks like Arnd who seems to be on it right now. I remember there are games you can play to convert the internal hashed files from Type 30 to some other type t...

No worries. :D

To use the stage, you'd first need to parse the one column up into multiple columns and you could use the Field() function or the Column Import stage for that.

Search for 'Rocket Software' here, they own the software now and the first post that comes up should contain a link to the manuals.