DSXchange

Irrespective of the users, dsadm will have the full control of that.

ds_team wrote:I inserted a transformer stage and still it is giving that random error.

Have you tried the other approaches suggested?

Why need to convert into numrical representation, if so need use use another funcition of SecondsSinceFromTimestamp()

StringToTimestamp().

Yea, so you can call one of the three jobs which loads the table, again after the three jobs finished in Batch. Alternatively, you can use command line functions called in Routine or script.
Or use After SQL of the third job to Truncate the table.

Hi,
You are using DSExecute("UNIX",Command, Result, SystemReturnCode), Aren't you?
Use DSLogInfo to see what is the Result and SystemReturnCode, and change your code accordingly.

If you need to output in this format,
a,b,3
m,n,2
x,y,1
The better way is to group by from you soruce SQL. If key1 and key2 are indexed, SQL should me much more effecient.

Can your other team mate able to make it up with your datastage use id/pwd?
Same way, what happens if you try with the other members login in you PC?

You can alternatively limit the row from the source of the exisining job design through a parameter. If the source is from DB and if you have a Userdefined SQL, have a extra condition in WHERE class as 1=2 for no rows to extract and 1=1 for normal cases. Or if you have transformer, use @INROWNUM =0 ...

It will hurt if you overwrite the existing DSParam file, if that is under use.

Alternativley you can 'Abort' the routine based on the ReturnCode as well.

What is the job desing? May be the operator combination might screwed up your function. Try with Combinable operator to false. If you have parallel version, I dont think transformer is a plugin to upgrade. you should be having the stage, may be you may need to customize your pallet to get the stage ...

If mark the topic, it avoids others to revisit it.

Create Round Robin partition and use the logic that you are using (as specified in your other post). Again it will minimize the so called hole, but not all.
If you are more concern about sequence number, run the job in Sequential mode, atleast the Transformer and use simply @INROWNUM.

Hi, You can refer the FAQ related to this sequence number generation. This has been discussed earliar. Since the number been generated in different partition, you cannot expect the nubmers to be gererated in a sequence order. It depends on the number of records that flows in each partition. If your ...