DSXchange

What's the resolution?

Set the commit interval to 0 rows. (0 = all)

Placate your DBA.

Was the file created on Windows? My guess is that it has CRLF line terminators but you are specifying UNIX style in your Format properties.

Look in the log to learn what's wrong.

Did you make it a protected project?

Make very sure that your hashed file metadata are 100% correct. Hashed files are navigated by position of the field in the record, not by column name. Examine the Position field in the Columns grid.

Set the Hashed File stages to "clear before writing".

Why do you want to clear them otherwise? It does not give back any disk space.

Please be more careful with your spelling.

Use a lookup from one table to the other. Perform whatever comparisons you need in the Transformer stage.

The ALLOWNFS parameter in uvconfig must also be set.

&PH& automatically has a VOC entry. How are you determining its size? &PH& is a sub-directory in the project directory.

That's totally unrelated. Please begin a new thread for it.

Make the first (or an early) activity in the sequence a Job activity that fetches the maximum value and loads it into its own user status area. A server job is always recommended for processing just one row. The job activity's $UserStatus activity variable is available anywhere downstream of the act...

There are basically two approaches. One is to perform arithmetic on the individual components, the other is to use something like DateFromDaysSince() function with an offset of -183 days (a close approximation to six months).

I don't think this is related to the node agents. Another site where I worked recently had the same java.lang.NullPointerException issue (on AIX) and received a patch from IBM to fix it. There are scripts - from memory NodeAgentsStart.sh and NodeAgentsStop.sh - for starting and stopping the node age...

Try using a Merge stage, which consumes rows loaded from the Update input. However, your "restart from the top" requirement can not be implemented using this stage type. That would call for some kind of circularity for which, I suspect, you will need a Build stage (or a routine that loads ...