DSXchange

Nice.

We have, right here and just yesterday.

Thank you for posting this.

I'm curious if they included an explanation of how that fixes anything or what exactly it does when set to true...

I have executed .\dssh in DSEngine directory.. while executing :UPDATE SDKSequences USING DICT VOC SET F1 = '192' WHERE @ID = 'E_OPER_UNIT_TBL' got error: DataStage/SQL: table sdksequence doesn't exist. As stated before, if you launch from DSEngine you must LOGTO the Project you want to work with f...

They've been posted here before and a search should turn them up. One example is here. Hopefully the links are still valid.

Script the report generation and save the output to a tmp file. Collect the information you need for each column via standard UNIX functions like grep and cut. You can then echo them out with your delimiter of choice to a flat file.

You could install the client.

Windows 7 XP Mode.

Keep in mind the fact that for 7.x the Client is supported on Windows XP and the Server on Windows Server 2003 or a flavor of UNIX.

Neither the client nor the server side of the 7.x product are supported on Windows 7.

Since we're talking XML consumption here, I'm assuming the goal is to collect the various filenames so the file path can be passed to an XML Input stage where it will do the actual reading of the contents. Yes, no, maybe so? If that's the case then off the top of my head I'd say perhaps a "find...

Of course, just offering an alternative. Perhaps an EmptyToNull() wrapper around the whole thing?

... unless you want the result to be an empty string in that case. If so, stick with just the "else" portion.

And you'll need to leverage the various "DSGet" functions, depending on exactly what you need to do. Speaking of which, can you expand a teeny bit on what "output its log" means? For example - outputs in what format, to where? To what purpose?

Define 'not working'. It is a perfectly valid function in the 7.x version of the product, one that I made extensive use of back in the day, doing exactly the kind of things you've asked about here.

From what we've seen here over the years it is a known "issue" with datasets, kind of surprised it is still an issue. I would think it would be worth asking your official support provider about.