DSXchange

No negative impact unless the system is already overloaded.

First you need to determine how that null gets there. When you write the file, what termination and attributes are you using and are they the same as when you read the file?

hint: If you don't know this already - you can greatly improve throughput if you make this file a fifo one

That is very odd. If you substitue your sequential file output with a peek stage does the error go away?

Run the job with $APT_DISABLE_COMBINATION set to true in order to localize which stage is causing the error. It is most likely the JOIN but you cannot be sure.

Convert your dates to internal format, then use OCONV(In.Date1,'DQ') to get the quarter number and OCONV(In.Date1,'DY') to get the year and then (Date1Q+(Date1Y*4))-(Date2Q+(Date2Y*4))

Ray - thanks; after I saw the post I realized that I snarfed a copy when he posted it. I thought you were referring to a built-in EReplace() call in PX.

We really should get a DSXchange toolbox put together.

Why not try setting the soft file limit to 2048 and checking to see if it makes a difference?

Ray, I used the search system but couldn't find a reference to a PX "ereplace" type function amongst the threads returned.

At version 8 you need to do this through the IIS administration client, usually through your web browser with address "http://{YourServer}:9080/"

Check your log auto-purge options, if you selected to keep only the last run then your log information is irretrievably gone. Sometimes the log information is still there, but your director client might have a filter condition set.

Does this thread apply to you?

if you limit the number of rows in the input do you get the same error?

Ken - do you have one of those? I never got one (I didn't even know such a certificate existed)

You cannot do this simply in a PX transform stage. You can write a BuildOP to do this, or perhaps use a UNIX program such as "sed" to do the conversion for you.

Have you spoken with your DBA to have him/her check for locked groups or records? This would explain the job just hanging around without doing any processing.

The debugger is explained in the documentation, the out-of-context message is perfectly OK in your situation.