DSXchange

Well, then it sounds like you are doomed.

does this logical partition funtion as an entirely independant machine? with it's own configuration/IP and so on? can anything on that logical partition not use more CPUs? if so I think my words still stand. Yes. Yes. No. Exactly. In essence, they look like individual machines - IP, config, CPU, RA...

Sure, if you can manage that it would be fine. As long as you are constraining it so that DataStage only has access to the number of CPUs you are licensed, for the warnings will stop. For example, we all live on a HP Superdome. (man, I really wanted to put 'yellow' in there. ). It has umpty CPUs but...

Assuming it's ok for the output to be one big file on the other end.

Luk, this is what the MERGE stage does, it will merge your two data streams into one. Just for the record, this is a PX answer. The confusion comes from having two stages, performing two different (yet somewhat similiar) functions, with the same name - MERGE. The Merge in PX is similar to the Link ...

The FTP stage doesn't support wildcards or sending more than one file at a time. Go back to good 'ol command line ftp if you really need to do that.

Sorry, Michael is right - that's what I get when I don't look all that closely at something and get sidetracked by the filenames. Try something more this instead: filename = "/xyz.txt" Call DSExecute("UNIX","sort -u /xyz.txt > /xyz1.txt", Output, SystemReturnCode...

That's... close. As a bare-bones-no-checking-for-errors-or-using-parameters routine it should be fine. Fix the file names so it looks like this: filename = "/xyz.txt" Call DSExecute("UNIX","sort -u /xyz.txt > /xyz1.txt", Output, SystemReturnCode) a = DSExecute&#...

All you did was copy xyz.txt to xyz1.txt. Then the "sort -u", with any redirection, simply sends the output to standard out - so you are basically throwing it away. Skip the copy and do the sort like this instead: Call DSExecute("UNIX","sort -u /xyz.txt > /xyz1.txt", Output, ...

Have you even tried to use the stage yet? It's pretty obvious how to set the time (ie, number of hours to wait) if you look at it. Like any of the Sequencer stages, you use 'triggers' to control what happens next. An 'OK' trigger will fire when the file arrives, link that to the job that should proc...

Let me put my requirement in this format. I have seq file with 2 columns SEQNO and SECNO. For One SEQNO We can have multiple SECNO'S. But not same SECNO.If I get the file like below i need to reject the file. Why not do something simple and leverage your operating system? Take the file and create a...

Or you can create the link in the Project directory, pointing back to your 'real' scripts directory. This is the route we chose to go with, but either way should work fine.

Whether the job would accept this would depend to some extent on the parameter type, but it serves as an example of what can go wrong, perhaps without even being noticed, if adequate care is not taken. Or it might be yet another example of a poster that typed in some of their code by hand rather th...

In otherwords, when you initialized jobs for the first time, you got version 1.1 on everything. If you then connect to the dev project and initialize some of the jobs again, they will be version 1.2 in the repository unless you override the numbering schema during the import.

Yup, simplest thing is to have your own job control code where you can do pretty much anything you need to. That was the third option I listed.

Glad you found a solution that works for you.