DSXchange

Nothing specific, but the example for the Loop stage shows one that goes through 1440 iterations, so... "never mind".

Right... from a job control or scripted standpoint, I'm good. Warning limits are throttled down appropriately and I can handle the default of 50 from the Director. Specifically wondering how to change the seeming default of Unlimited warnings to something more... limiting... when running a job from ...

Isn't 256 an awfully coincidental number? 256 good, 257 bad? Silly, I know, but any chance that's the maximum number of iterations it can handle?

Ok... where in the heck does one change the default 'Abort job after X Warnings' limit in the Designer? I hate the fact that it defaults to Unlimited and it keeps becoming an issue because people don't seem to remember it works that way. The 'Tools/Options' setting for the Director only works for jo...

220 gigabytes? That seems excessively large somehow. I don't recall any upgrade I've done taking 1 hour let alone 10+ but then I've never added the wrinkle of including NLS in the picture, nor had that much... baggage. Are you counting hashed files in the Projects in those 220GB? Perhaps that comes ...

ray.wurlod wrote:DataStage 7.5 is (remains) a 32-bit application.

From what I recall, depends on your platform. DataStage on Tru64 is 64-bit, I do believe.

Between "THE" and "NETHERLANDS".

I really think you need to have an underscore there. Other than that, I'll have to defer to one of the NLS experts on the forum here.

Either fully path it or specifically 'cd' to the directory you want to create the file in before you do the concatenation. When you use a relative file path from a DataStage job, that is relative to the Project the job is running in as that is the 'current working directory'.

Well... what kind of 'Java function' and where do you want to call it? We're doing it 'outside' of DataStage from the O/S to leverage Java functions that accept streams of data from standard in and output streams to standard out. If you mean row by row inline... The official answer will be to purcha...

Don't believe that's the case. I seem to recall it always concatenating all columns together.

Checked the docs and they don't mention anything special about the key fields, but it would be simple enough to test and see.

Use the : operator.

No, you won't lose anything. In the past, that was the only way to change or upgrade the license information. From what I recall, it's not until 7.5.x that we were given a way to just update the license information...

Are you trying to do it as the dsadm user?

At worst case, you can do a 'reinstall' of the server with the new auth code.

From the help: Validate input XML. Select to validate the input XML against the XML schema that is referenced in the XML document. If not selected, XML Input checks only for well-formed XML. Validation against an XML schema is required when you want default values for elements and attributes that ar...

Are you sure it is even finding the xsd? I'd try a full path to it to remove any ambiguities about where it lives.