DSXchange

The first argument is the return value. Then there are five input arguments. Total = six. Can't load subroutine errors usually result from their not having been compiled and cataloged. Use the multi-compile tool to compile all the routines in the project. Or at least all the ones in the "Kim" catego...

Your first post stated "override". If it's the PAT file, you need to check that you have not allowed the previous pattern handler to fall through into yours, or yours to fall through into the subsequent pattern handler.

Sort by Inv and Rec Type. The rest follows easily, particularly if you have the Sort stage generate Key Change column.

Write a little test bed in C (C++) to invoke your routine.

Try it. Let us know.

In a fixed-width format file any representation of NULL must have the same number of characters as the field in which it occurs. Your Null Field Value property is set to "" for a Char(13) field. What you actually require is a value with 13 characters in it ro represent NULL - perhaps 13 space charac...

The Change Capture stage (which is what I must assume CC_delta to be, since you omitted to provide this information) requires its inputs to be sorted by the Change Key columns. Does your upstream sort provide this? The message suggests not. Put explicit Sort stage into your job design, on the inputs...

With File Pattern try using a job parameter for the directory part of the pathname, for example #jpFileDir#/*.txt

The behaviour of the File Name Column property (to return the complete pathname of the file) is as documented.

Build some benchmark tests. For example,

Use this to time how long you need to read the file with and without multiple readers per node.
Then experiment with Data Set. Experiment with Lookup vs Join vs Change Capture stages.

Job Categories are separate records in DS_JOBS beginning with \\\. For example, to delete the category MyJobs\LoadHash you could execute DELETE FROM DS_JOBS WHERE NAME = '\\\MyJobs\LoadHash\'; It might be worth while to check first that the category is empty. SELECT CATEGORY, COUNT(*) AS ITE...

Of course you can. The value from -jobinfo is only where -logsum starts; specify a later end timestamp with -logsum, then parse off the first entry.

Welcome aboard. You really do need to be more precise. "Not working properly" is not enough information for diagnosis. What method is used to create the new project? Does this complete successfully? What is in the &COMO& directory in the new project's directory? When job's don't run, is anyt...