DSXchange

Ah... that makes sense.

Yes, thanks. I'm sure someone will be along shortly with some help for your problem.

Why not switch Putty to emulate a VT100 and see if that helps? It's under Connection / Data / Terminal-type string.

First off, a caveat: I think the SQL Builder tool sucks and is totally unneeded, except on paper so you have it as part of your feature set. I wouldn't touch it with a ten foot pole. There, with that out of the way... I don't believe you can parameterize the schema with the SQL Builder. I use the 'G...

Loop? Failure trigger perpetuates the loop, success exits? Hmmm... not sure how that would solve a deadlock, however.

It would probably help if you mentioned the database in question... Oracle?

I thought this was your fourth post but it's actually your first as you've posted this in four different forums. Please don't do that, it doesn't help get you an answer faster and just causes problems maintaining a coherent conversation. I can't help other than to strongly suggest you delete the oth...

Yes. Once set in the Administrator, it will automatically be included in the environment of every job in the project. Include it as a parameter to override that value.

Silly, perhaps, but you *did* notice the dots in "SET.TERM.TYPE", yes?

From the FAQ: "By default, PuTTY announces its terminal type to the server as xterm." Give that a shot. You should also be able to override that to whatever you like, I would think.

Perl itself is required. Obviously.

You don't have to worry about any compiler / interpreter silliness, it's all handled for you automagically. Thought this might help:

http://www.perl.com/doc/FMTEYEWTK/comp-vs-interp.html

Not his thread, or I woulda asked the same.

Perhaps I am in the wrong direction trying to solve this by altering Oracle parameters. You are. Your best solution is to craft a methodology that doesn't rely on any particular 'NLS' parameter setting, something that will work regardless of them. This is typically done using generated sql and matc...

leeb wrote:and have created the symbolic links to append a "." on the end of some files.

I'm curious why this step? And which 'some files'? I don't know beans about Solaris or what extra who-ha it may require, it was just that this struck me as odd and something that could cause the install script to fail.

Probably an issue because you are still running 7.1.

Since you can't do this directly in the Sequence job, you'll need to do all of this work inside a routine and make sure what you pass back as the 'Ans' has been properly cleansed there.

And on the off chance you mean every 10th record, then a MOD() could be used... assuming that is available in PX.