DSXchange

Yes, you can do that; but the way you declare it and the way it is called from another routine will change. I think it is best to keep it the way it is - it is called as a function.

I wish I understood the question. The normal custom routines in DS server are written in DS/BASIC and are internal to the package, so .net doesn't play a role. External routines can (with some difficulty) be bound into the package, but they too are unaffected by .net. Are you referring to custom wri...

Let us assume you wrote a routine called MyRoutine and it has two arguments, A and B . You would declare a line DEFFUN MyRoutine(A,B) CALLING 'DSU.MyRoutine' MyRoutineAnswer = MyRoutine(Param1,Param2) The two parameter variables are placeholders and don't need to match the declaratio...

You can run any BASIC routine or function from a before/after subroutine. You will need to declare it and then call it correctly. Which routine do you wish to call? If it is a function type call (which is what the "routines" in the manager tend to be) then you need to declare it with a DEFFUN statem...

I'm fairly certain that this script gets generated at compile-time; so it should not sometimes be available and at other runs not be found. That is why I was wondering what your date/time stamp for that file is.

The DataStage engine runs as services on Windows; so you can use the "net stop {service}" to stop DataStage. net stop "DataStage Engine Resource Service" net stop "DataStage Telnet Service" net stop "DSRPC Service" There might be a way to call the control panel applet directly as well, but I don't k...

Thanks for that info; I'll keep that in mind next time I play on HP-UX.

meena wrote:...If OutTX1.P1=OutTX1.P1 and OutTX1.P2=OutTX1.P2 or IsNull(RefT2.P1) then @flase else @true...

If you cut-and-pasted that text then look into the mnemonic "@flase" as it doesn't exist.

Craig - do you remember offhand which won't work? I tried it on AIX and it did work, and know I've done it successfully on Windoze in the past.

I think that @INROWNUM and @OUTROWNUM are case sensitive. Also, inrownum > 2000 and @outrownum <= 2000 , should be corrected to "@INROWNUM > 2000 AND @OUTROWNUM <= 2000" Each run will start off with @INROWNUM and @OUTROWNUM being 0, so you will need to pass your start row number into the job as a pa...

Yes you can. The command line needs to be an executable and not contain any parameters, but I've done something like make the command line "sh -c " and the command line options then contain "#JobParameterWithUNIXCommand#"

I'm not at a PX station right now, but I find it odd that in two cases you don't have a valid path to the file (missing "/"),

internal error-missing script file RT_SC8741 oshExecute.sh

The answer to "can we use these stages" is yes. What you are really asking is "should we use these stages in a production environment" and the answer to that is not always straightforward. In most of the cases you will not want to add any non-essential overhead to a job in production so you should r...

Does the error always refer to the same file and have you checked to make sure that the file is actually there (if yes, what is the date/time stamp on it - i.e. has it just recently been created or is it from days ago?). Does it always abort on the same or similar parameter values? Is there any rule...

You've just said "the code doesn't work" without telling anyone what happened. You also stated that you've put in a sort but the data you posted isn't sorted so none of the example or suggestions can work. Try doing the sort first to a sequential file to ensure that this is working. Then use the tra...