DSXchange

Through the use of permissions are noted in this FAQ posting. Adjust as necessary for use in a Windows environment as it is UNIX specific, but the concept holds true regardless.

If you're sure no-one is monitoring it, have you tried using Cleanup Resources from the Director? Look for both the job name or files with the job number (RT_LOGnnnn, for instance) to find the culprit.

:? Still confused. Projects cannot "run 24x7" so what exactly does that mean? "RTI Enabled" jobs can be set to be "always on" and thus run constantly as a web service, is that what you are doing? It doesn't sound like it, since there seems to be a script involved. What ...

Do you not have the pdf mentioned? Check the link I posted? Both places show the syntax.

No such thing.

Assuming you meant CR/LF and that it can occur as 'data' inside a text field, yes? Is the string field quoted in the file? Search here (PX forum) for 'contains terminators' for other discussions on the subject.

Except isn't the error coming from the DB2 database, so perhaps... temp space? Is there an order by in your sql?

A couple of things... one is that you don't need multiple processors to "use the parallel configuration capabilities". Node <> cpu.

The other is you have a Windows version of the tool, so no UNIX anything for you. Not without a license purchase for your flavor of UNIX, that is.

Right, the "current value" we talked about in the other threads is the next value that will be used. Not the last one used. Sorry, didn't realize there was a confusion there or that that was why you wanted to fetch it.

Hopefully it's not, seeing as how they marked their Release as 7x in the opening post. I know where you're going, though...

sarjushah wrote:Let me search the forum but if you have it handy please pass it on.

It, what "it"? The link to Ken's post I already provided to you?

You might want to explain what you mean by 'the recovery of the data' here.

I've used the technique and routines Ken discusses here and it worked out well for me.

You cannot.

They mention those two stages together - UV/OBDC - as they are the only two stages that allow you to return 'multiple row' results rather than a singelton row. And the performance comments were related to direct database reference lookups.

Sure, "officially", but I would still think that you could be successful using an older client to connect to it. Worked well with 9i to 10g, for example.