DSXchange

skadiam wrote:I know this is not related to the current topic discussed but felt that someone can suggest a solution.

If you are not contributing to the current topic, start a new one. Someone will still be able to 'suggest a solution' without the hijack.

For the record, split from here.

You'd have to start by explaining to us what "not good" means. Examples would be nice, too.

What version of Windows is your client installed on? Are you certain the client installed correctly?

Or manage it via a Sequence job, via the Execute Command or User Variables stages. Or use a Routine Activity stage if you are more comfortable coding up the process in BASIC.

Headers are still an issue for multiple files read using a file pattern, but I don't believe they would have an adverse effect on multiple readers on a single file, however.

I went down the "why is it a dollar sign" path, this rather than @ or % or something else entirely...

There's nothing stopping someone from using a file pattern to read a single file. And I believe you may find that the 'only for fixed-width files' mulitple readers advise is for older versions and that restriction was lifted in newer versions. Hopefully someone can confirm / deny...

Well... I assumed that by "directly" you meant a single something, a stage that reads in a COBOL file and spits out XML, which is why I answered in the negative and I don't see that changing in future versions. However, I don't see any particular issues with using DataStage and the two sta...

You'd probably need a time machine and a trip back to the 60's to find out the reasons behind fundamental things like this. Before UNIX were fun things like Multics and RUNCOM. Some history here including the interesting note that "Unix" was a joke name someone made up that stuck.

Not much of a resolution.

I've seen the same issue in the past and a simple rerun always "fixed" the problem so our Operators knew to do that if that was the error they saw. We weren't doing anything fancy and our DBAs could never explain what the issue was.

This is bog standard command line stuff and I'm sure an exact search here for "command not found" will turn up all of the lectures on the subject. It's a pity that people nowadays are so entrenched in a GUI mouse-driven world that simple stuff like this trips them up. Makes old farts like ...

Not "directly", no. It certainly supports reading the COBOL file and it supports creating XML from any input stream. How familiar are you with either? Meaning, have you used the CFF stage before? Have you done anything with XML in DataStage? Outside of DataStage?

Which is just basically the long official version of what Ray posted.

u can use "KeyMgtGetNextValue('xyz')" in the transfer stage James has posted the correct parallel function to use when generating surrogate keys in the Transformer (not transfer) stage, you've just mentioned the Server / BASIC equivalent. ps. People don't really need to ask for their answ...

As noted, there is no DataStage limit to speak of... but you always have to consider the underlying resource availability.