DSXchange

Server jobs don't have a timestamp data type, so you would need to separate the date and time portions of the string, then use ICONV to convert the two parts, perform the delta math, the use OCONV again to build the timestamp.

Cheru,

the answer supplied (almost) solves the problem as you described it.

svFoundStar IF(svFoundStar=0) THEN IF (In.ValRecd = '*') THEN 1 ELSE 0 ELSE 1

Then the constraint svFoundStar = 0

The column you titled "Output Records" is the output count from the sequential file stage, correct? The number of records output from the sequential file stage should be the same, regardless of how many readers. Can you confirm that this is, or isn't, the case?

If you have MS-Office installed you've probably also got "msquery" installed, which will let you test the ODBC connection to see if the problem lies in the ODBC connectivity or in DataStage. What sort of storage lies behind the ODBC connection? If it is an Excel document then I've seen str...

Compute the YYYY and the MM from a date and compute X as ((YYYY*12)+MM). Do the same for the other date and subtract the larger from the smaller. This returns 0 for (2012-08-31::2012-08-31) and 1 for (2012-08-31::2012-09-01) and would be the number of calendar months between the two dates and might ...

I hope you realize that you cannot TRIM a CHAR() field. A CHAR(6) filled with spaces is 6 spaces long after a TRIM. I don'T see a stage variable in the IF clause. I assume the COLLTN_APPL_ID and COLLTN_APPL_ID_REF are both Char(9) and COLLTN_APP_TYPE_NM and COLLTN_APPL_TYPE_NM_REF are char(6). If Ma...

The first error points to "strcopy" and I would check the changes from varchar to char first (make a copy of the job, remove those derivations and see if it compiles). Often with big transform stages I give up trying to find the cause in the compiler output but just remove columns until th...

The "UV" commands are for hashed files and server jobs. Unfortunately you cannot modify existing dataset contents (although you can add extra records)

Phil - in the last post the OP stated that the problem remains even with a 1-node configuration so the issue of hashing is a moot point (for the moment); while you are spot on regarding the cardinality of the hash keys I believe that the problems here are much more basic.

This sounds rather strange indeed. If you run your job with 1-reader-per-node from the designer with a 1-node $APT_CONFIG_FILE configuration then write down the number of records shown as coming out of the files 1, 2 and 3. Then change the number of readers per node and re-run the job. Are the numbe...

You need to add the system parameter $APT_CONFIG_FILE, I'm sorry if I confused you by not putting the leading "$" sign in. In the Designer parameter selection, you need to specify "Add environment variable" and then choose $APT_CONFIG_FILE.

Which UNIX variant are you using?

See http://www.unix.com/shell-programming-s ... cript.html

Yes, you should be able to add the parameter APT_CONFIG_FILE to your job and point it at a 1-node configuration at runtime.

To expand on the previous answer: there are several hardcoded time limits within DataStage that, when they are passed, trigger jobs to fail. The more things you run in parallel in a timesharing operatings system such as UNIX or Windows, the less time each process gets and therefore the slower proces...

I can't check but seem to recall having to use '0001-01-01' as low-date in DataStage in a project. Months 0 and Day 0 don't exist in any case, so '0000000' is not a legal date in any case.