DSXchange

Read the error message carefully. There is some problem executing the fifo command in UNIX to create a named pipe. Track it down.

It's in the DX334 (DataStage Essentials) class from IBM also.

Job type is irrelevant here. 20000000 can not be a valid date. There is no month zero, no day zero, in the year 2000 (unless I missed something - I was up all night in case of Y2K problems occurring).

You will not be able to get it to work in one Modify stage for reasons already stated. The Modify stage does not support nested functions.

ELF is an optionally installed Linux component. The message suggests that you need to install something that you haven't yet installed. You really shouldn't source dssh. You should source dsenv, but execute dssh directly. And you must be attached to a DataStage "account" in order to do so, not to th...

Says a lot for the "S" ("standard") in ASCII, doesn't it?

It's usually started automatically by the init process (user id 1) when the UNIX system is booted. It does need to run with superuser privilege, so that it can authenticate logins. Check out its parent process ID in your ps -ef | grep dsrpcd | grep -v grep report.

Can you leave the map set to NONE and process the hex data with to see what you get?

The message is telling you that you have not imported the Stored Procedure definition. DataStage requires that you import Stored Procedure definitions so that it can verify the number of arguments.

My choice would be MatchField(). "P/N " : MatchField(InLink.Description,"0X'P/N '0X' '0X",3) The MatchField() function here returns everything between "P/N " (with trailing space) and the next space character. It will return "" if "P/N " does not occur in the string, or i...

Even a validation run must start within 60 seconds.

Make sure there is no space between any function name and its opening (left) parenthesis. DataStage BASIC can be finicky about this. There is no limit to the length of a string variable in DataStage BASIC until you run out of virtual memory. By assembling the entire log into a single string to be wr...

Try to use generated SQL wherever possible. Everything in the table name field becomes the FROM clause. So what you put in the table name field is all of: table1 LEFT OUTER JOIN table2 ON table1.key = table2.key (Adjust as required. Make sure any ambiguous column names are fully qualified in the Der...

Diagnostician Note Don't be in too much of a hurry to attribute blame to a particular stage type. Here the subject line suggests a problem with the Sort stage, which may mislead future searchers. The problem wasn't. DataStage did exactly what it was programmed to do - via the pad character property...

Why a routine? Can't you use a job? What do you want to do with the result? Clearly you are unfamiliar with DataStage routines. You can use the supplied before/after routine ExecUV to execute COUNT #HashedFile# command, but what do you want to do with the result?