As you've no doubt deduced, sequences do not persist across jobs. At the start of the job, you would need to query the table for the last ID, increment by 1, and put that value into a variable. Use the variable as the start value for your sequence instead of 1000.
Your answer is informative.
But don't we have any component which stores the last sequence value generated and increment by 1. Similar to Sequence Generator transformation in Informatica.
You can get the last value of id by having as a lookup table and in the input component in the limit column have 1 as the value and use sort by desc by this way u can get the maxvalue and in the numericsequence("s1",id_column+1,1) will get you the sequence which you want
Thanks for your response.
But it degrades the performance if I do lookup on the table to fetch max value.
Also I want to generate the sequence id for same target table from multiple jobs which might also run in parallel.
Eg: In informatica, we can have reusable SequenceGenerator which can be called from different mappings at a time to generate SEQID for same target and still generates unique values.