DSXchange

So, what actually fixed it for you? The switch to single quotes? Were you still able to levelage your file path parameters?

Parameter set yes, parameter file no.

Again, best if you post your actual syntax. There should be no issues calling any operating system command but seeing your syntax and any errors generated would be helpful in figuring out what is going on.

Explain what you mean by 'through a network' - by definition the client connects via your network. Do you actually mean a WAN? If you are not local to the network DataStage is on, it will be slow. That's the nature of the beast and there really aren't any 'tunings' or setting you can use to help out...

Probably the same issue as your 'cannot save a job' issue - permissions or space.

Pretty much what I thought, this wasn't going to solve your problem just create oodles of new ones. Please mark this thread as Resolved and add your latest explanation / questions to the original thread so we can continue the conversation over there, not here.

Disk space?

What is "not working" about it? The syntax is available directly from the command itself, in the documentation and regurgitated here so many times that I don't see why we should type that all up again. 1. Type 'dsjob' and press return. Or look it up in the Server Job Delevoper's Guide. 2. Nope. If y...

Your query will need to be complete and thus include the table name. Not sure what exactly you are having a problem with, can you be more specific?

To me, it looks to be as Kim mentioned - a bunch of parameter values in a file and an attempt to simply pass the filename to the job in the hope that somehow it will magically know what to do with them all. The syntax used was perfectly valid, it just was saying that there is no parameter who's name...

Or declare the pipe and then 'manually' split the date field in the job.

I can't imagine any reason why you'd need to worry about a ".trx" file. Your solution lies elsewhere. Did you recompile after making the change?

lfong wrote:The derivation for target column is:
if StgBranch = @False then 'XXXXXXX'

System Variables must be all upper case. @False does not exist, but @FALSE does and should work more better.

I get the same 'error' trying to run that query.