DSXchange

You should have delete descriptor file whenever the mode in the Data Set stage is Overwrite, but not when it's Append. Can you please check this property?

Why not just script the commands that are currently being performed manually?

There's only one row to be processed by the job. Why start up a parallel job to process one row? Also, the interface to the user status area is much simpler in a server job.

PhilHibbs wrote: Which raises the question, how can it return a pointer that has been freed?

Perhaps THAT is the question you should be putting to IBM?

There is no limit. The GUI may limit the number you can enter. However there are stupid values (for example 4000000 readers for 2000000 rows). Think about the architecture. Sequential File stage uses the STREAMS I/O module under the cover so, even with only one reader per node, you are going to be r...

Use the pxEreplace() function you can find here on DSXchange.

So what's your question?

Theoretically yes. I'll have to give some thought to the next, "how", question!

What if you remove the quote characters? (The statement as it exists will encrypt the literal string.)

Do their Rules require a hammer to fasten a screw? The idea here is to use the right tool for the task. In this case it's a sequence (and, preferably a server job to read the file). You can update a values file of a parameter set directly, but you have to overwrite the entire file. You could do this...

You don't have a timestamp in your data. You have merely a year.

You ARE able to use sequences.

The rest of the message seems to be column headings. Is there an environment variable that can be set to suppress these from returned information from Sybase?

Think for a moment what the Merge stage is doing. This will provide some guidance about which columns need to be identically named and which ones do not.

I have done this in the past, but not all in one job. I had a server job build the custom SQL and place it into its user status area. A downstream parallel job receives the entire SQL statement as a job parameter from activity variable Job1.$UserStatus, and uses this in the appropriate stage in Job2...