DSXchange

Tell me about the log that the shell script creates. When the shell doesnt execute, or you think it does not execute, is there any entry in the unix shell's log? If there is nothing, what does the director's log say.

Does the script run from command line? May i ask why are you executing the script in "Telnet Before Command" and why not in the before job subroutine "ExecSH"?

So that means the job was created on a windows server and is now being used on a unix server.

I was gonna, but you beat me to it

Yes. You are correct. Its just a function. You can have a main and do the testing from command line, but once all the testing is done, you need to remove the main() function. Also make sure that no input arguments of the C function are defined as const. It does not work with datastage.

Ask her to ndm the file (ftp the file) in ascii mode to you. That can be done.

Or if you are using an enterprise scheduler like Control-M or Tivoli, they have a file watcher in place. You can utilize that as well.

Check out this post. In this post Craig elaborates a method thats taught by IBM to capture duplicates.

Does the script execute from command line ? Try giving

Welcome Aboard
Most of the errors that developers encounter have been covered here before. This site has a search facility which is very robust and helpful. Do an exact search on keywords 'Mismatch in number of column'.

OR

Pay close attention to Ray's comment. Just because you have it, does'nt mean you 'have to have to' use it. Just source the odbc, do a lookup on the hashed file using the conventional design via transformer

It wont work Whale. A job parameter cannot be set within the job. It needs to be set before the job is fired. It can definately be done before starting the job. The OP is sitting on unix, so the special character can be read and stored in a file, the contents of that file can be passed as a paramete...

Can be done in two jobs. Find and store that special character, in a file or UerSatus. In your second job, define a parameter, while defining the parameter, the default value will be a routine which will make a call to the user status or read it from whereever you stored it. Tie the jobs together vi...

Did you compile your routine. Did you test it out before using it in the job?