DSXchange

Sounds like you don't actually have decimal values you're working with.

The dummy file gives you something to check for, as Arnd noted. Think of it like a flag or semaphore - your Sequence job checks for the existence of the file and only if found allow the processing job to run. And there are several ways you can 'check', one way is by using a simple UNIX test function...

ps. "I increase it to 2500 in Director" just means you have changed the default value for you on your PC when you manually launch the job from the Director. Now, if you run the Sequence job with that warning higher level, it is supposed to pass it down to all Job Activity stages automatica...

Thanks for coming back and posting that, especially the specific patch number.

I helped build a clustered installation of the Server product on Compaq Tru64 Alpha boxes many moons ago. However, as noted, I wouldn't consider it true "high availability" as there was no notion of what was called TAF at the time: Transparent Application Fail-over. Running jobs would all ...

I know, it was just a friendly poke in the kidneys for Petty Officer Wussing.

Exactly - logical rather than physical rejects. No job should ever knowingly violate a constraint on a table and thus should not only be aware of them all but attempt to ensure compliance with them before sending the record to the database.

Just to expand on (3) - they are like "include files", the code they contain is added to the job at compile time as if it had always been there. It's not like a discrete object that is also shared at runtime.

As a guess, some sort of tracing option was turned on.

They're rejected for a reason and that reason is logged, regardless. A 'cheat' would be to demote what you don't want, better to fix the job and (gasp) not violate the constraint. Any reason you can't do that?

The default format is "plain csv". Since I don't have access at the moment to get all of the exact specific settings, I suggest you remove the stage then add it back in again. Add any lost metadata - filename, first line is columns, etc and then define your one string column. That should w...

Remember that without code tags the forum software removes all of that nasty extra white-space you accidentally put in there.

Is there any reason to believe that this internal IBM part number is even stored in the engine / software somewhere? I can't see why it would be.

Tried changing that "select *" to a specific list of fields? One that exactly matches your columns in the stage?

Another option - open any job in the Designer and switch to the Job Control tab under the Job Properties. Use the 'Add to job' option and pick one or two jobs at random that have job parameters defined. Answer the questions that come up and then examine the code it generates to run and monitor the j...