DSXchange

No. Simply create the reject link FROM THE ODBC ENTERPRISE STAGE.

How have you set the "Lookup Failed" rule in your Lookup stage? By default this is set to abort the job as soon as the first lookup failure occurs. Change the rule to Continue (or to Output if the Lookup stage is to have a reject-handling output link).

The command to run each may vary, but will be given to you in the documentation that accompanies the software. Typically it involves executing a supplied shell script.

There's no auto-arrange functionality and, as far as I can determine, none planned. If you think it's a good idea, add it to the enhancement requests forum (farther down the Index page).

There is no "troubleshooting the score" command in AIX or any other operating system.

The only thing you can do with a score is to inspect it, and that's done from Director log view (which does have a Print option).

Any troubleshooting is done with the brain.

Get in touch with membershipdirector@dsxchange.com They usually get it done within 24 hours of application, provided there's no problem with the credit card information. Of course, lots of servers went into meltdown on January 20 because very many people were watching the inauguration of the US Pres...

So, we're not permitted to sleep?

Given that the job parameter error_code is populated as you say:
Field(error_cod, "|", 1, 1) will return error_cod=----
Field(error_cod, "|", 2, 1) will return FILENAME= Test_20080801.dat

What are you doing with the stage variable COD_ERROR ?

Look carefully. The Sequential File stage is the one that has generated the error message. This stage type does not generate sqlcode - after all, it doesn't use SQL. My guess is that you have tried to propagate sqlcode column through your job design. Get rid of it. If you create a proper reject link...

Define "special characters".

I'm guessing yours is not an NLS issue.

Have you tried creating a synonym for the column name (in the database's table definition) and using that?

You use it to read or write complex flat files, the kind that are typically created or consumed by COBOL applications.

There's a terminator (";") missing from the SQL. Apart from that the SQL looks OK. Is there a VOC pointer to the hashed file, and is the hashed file name being resolved correctly from the job parameters? (Look in the job log for the answer to this question.) The commit is managed automatic...

Definitely not, since server jobs do not generate a Score.

chulett wrote:And not marked your "job type" as Server.

Alas there's no choice on that; TX is not one of the options.