DSXchange

The code compiles perfectly well on my machine too (I changed dukOpenFile references to OpenSequentialFile, since that's obviously what it's based on - I do trust that you kept my copyright notice intact as instructed in the original code!). Try copying and pasting the code from this thread into a n...

Can you prove that the project was created successfully? A partially-created project will probably not allow creation of jobs. The next thing to look for might be permissions. What user created the project? Is the user trying unsuccessfully to create a job the same user? What is each of those users'...

Can you connect to the server? If you can ping the server, then the server is back up, but not necessarily all the required components. To find out if the WebSphere Application Server is up, there is a command serverStatus.sh that can be executed. You need to know the name of the default profile ser...

Hmm...

Not to mention "erk!"

Nice catch. Lucky you have a slow system (or super fast vision)!

I expect you will end up setting the Record Delimiter String property to "DOS style".

Look at the incoming date/time at around record # 400,000. Report if there's anything different about it.

The ODBC stage has a property for quote character on the Stage properties. Click "Get SQL Info" to have this populated with the correct value from the database. You could also apply double quotes around the table name in the Table Name property.

There's never time to do it right, so they have to take more time to do it again some time in the future.

You can't do it that way. DSLogFatal() only ever aborts the job from which it was invoked. Therefore you need to do something like detect the failure of S2 in S1 and react accordingly, or not fail S2 at all and detect the job failure in S1.

There's already an open thread on this question. Opening a second thread won't help.

Can you create a Routine activity on an output link from the End Loop activity - call UtilityMessageToLog() to report anything you like, but also perhaps the value of the loop $Counter activity variable.

Does the name of the fifo file include just the job name, or does it include the invocation ID as well? If it's only the job name, then you've bumped up against a limitation of multi-instance running.

But it's not certified for the server components and therefore IBM would be within their rights to refuse support for that combination.

The fifo files are named pipes used (probably) for inter-process communication. Perhaps there are left-over fifo files from an earlier aborted job? Could it be that two concurrent jobs are trying to use the same fifo file?

Craig has it. Search for Local.msh unless you're using named message handlers, which are stored "globally" in a MessageHandlers directory. They still have the ".msh" suffix, though.