DSXchange

The routines commonly used for (1), (2), (3), (4) are:
DSAttachJob(), DSDetachJob(), DSGetJobInfo(), DSGetStageInfo(), DSGetLinkInfo().
I don't know what (5) and (6) mean, so cannot answer that.

Is this a protected project or a system routine? If so, it is best not to try to rename it. If you export this routine, then edit the .dsx export file and change the readonly attribute and then re-import it you will have effectively changed the status and can then rename it.

This would be an ideal place to use the type of functionality implemented in such stages as "Change Capture", "difference", or "Slowly Changing Dimension".

sreedharmsc - Your query is so susupiciously like an interview question that you will most likely not get any responses. If you illustrate what you are looking for in more detail then someone will certainly answer.

Are you on a MPP or grid or on a single machine? If you are in a distributed environment then you are correct in your restriction. I don't know the c++ function akin to ByteLen(), I think I couldn't find one and then decided to do the whole think in a BASIC transform stage.

Attu - now you have proven that the DataStage error was, in fact, correct. But your file inconsistancy still exists. Clearing the log file (from the director, not from the TCL prompt) should do the trick for you.

The BASIC transform stage will suit you just fine, it will run on as many nodes as your job does. We recently had to do something similar and instead of writing a buildop we used a BASIC stage and ByteLen() to determine actual string sizes with multibyte characters.

Parameter sets can be tricky to work with. In our current project we've seen such value propagation problems and seen that there are known issues, but if I recall correctly we encountered issues when using parameter set values in shared and local containers, not from a sequence calling a job. How ar...

Here's one approach of many. Call your PX job from a sequence, in the sequence have a transformer which has a constraint on an output link to only output when the value exceeds your limit and write this to a sequential file. Then, in the calling sequence check to see if the file has a length longer ...

Is the dataset always being opened in "append" mode?

Generally PX jobs run with more throughput but take more time to develop. Let's take an example job that takes 3 days to develop in PX and runs in 10 minutes and the same job would take 1 days to develop in Server but runs for 60 minutes. Which is better? If the job runs 10x a day and is part of a c...

The most likely reason is that the job log is corrupted. If you don't need the information a "clear log" might fix the error.

What happens if you enter the command as "dsjob" and parameters as "-run -mode NORMAL -param paramRecLmt = 10 DEV TestdsjobExecute
"

as user "dsadm", go to your $DSHOME, source the dsenv file and enter "bin/dssh". You will get a ">" prompt, enter "LOGTO vodafone". What happens? (You exit out of TCL with the "QUIT" command).

Too add some detail to what Craig has illustrated, you can convert a timestamp into a number of seconds by using (ICONV(In.Timestamp[1,11],'D4-DMY[2,3,4]')*24*60*60)+(ICONV(In.Timestamp[13,8],'MTS'))+(In.Timestamp[22,3]/1000) Do this for the other timestamp, s...