DSXchange

Hmmm... on the Server side, there is an option to "Ignore row truncation warnings" which would give you that very behaviour - read the first x columns as defined in the stage and ignore the fact that there are more in the file. Is there an equivalent on the PX side?

You'd have to fully spell that out on the command line - server, user, password, etc. or take advantage of the -file option. Come to think of it, I don't believe I've ever actually tried to run a job from my PC but have scripted it into things to list project and job names, for instance.

No need, just use the parameter(s) directly in the stage.

Right, missed that. INSTANCE not INTERFACE.

Of course you did.

I wonder what in the heck I was thinking of. I distinctly remember having to 'borrow' something from another colleague who's server was on Windows, I'll need to go back thru my email archives. :? I'm wondering if I'm thinking of older versions of the client, 6.x perhaps. I believe the inclusion of d...

I'm using a Trillian Pro plugin called Good News.

Separately, inter-process row buffering can have a positive performance impact on "some" Jobs..... but apply sparingly and carefully. I would never use it as a default at the Project level. :!: Heed these words, children. And in my own personal experience, I've found "some" to m...

You removed (or did not add) the "ON MODS" part of my posted sql, hence the error.

You could use the Execute Command stage to do (off the top of my head) a "test -f filename" on the file and then conditionally run the job based on the result. Or perhaps "-s" if you need to check if it exists and is not empty as well.

Try...
Not sure why there was a second 'where' in there.

As noted, there isn't one. The only "override" setting is done at the client (individual PC) level as an option in the Director. There is no project level equivalent.

ps. Didn't really answer my tangential question as to exactly what you're doing in this script, but that's ok.

There isn't one... but that doesn't mean you can't create one for that purpose, I suppose. I'm curious, what 'project setting values' are you fetching in your script and how are you using them? Seeing as how they are project level environment variables, those variables are automatically created in e...

You really need to try it from your DataStage server, not your local PC. And was this an ASCII or binary transfer?