DSXchange

You can always reset the value of your key. So you can set any value you want, you can go back to one as well.

Simplest thing to do, is to have a process, which will find out the Max value of ID column. This value then in turn can be used to reset the SK.

IHTH.

Thank You Ken, that help. So in brief can I say : Depending on the number of jobs and complexity involved in trigerring the job one can opt for Sequencer or Scheduling Tool. The way we do it here is, before any development work, we come up with one common parameter list, which is used for all the jo...

Two issues I always face with Lookup Fileset: 1. How to view the data, that is loaded in the Lkp File Set. 2. You can not append data Secondly, unlike Hash File Lookup..the lookup stage lacks the capability of showing only the number of records that found match with the source, not sure if anything ...

Hello Ken, Just wanted to understand more on the point 'schedule a controlling Batch or Sequence job and let that manage the load effort '. What I have seen and I prefer is giving control to the Scheduling tool, that way it has control over all the jobs and easy to maintain. I do ot have to worry ab...

It means that you have less columns in your file then what you have defined in the metadata. Please cheeck that record

It depends on your tables.. Out of two tables can we say that one will have all the records for that key ? Or Keys are divided among two tables ? If its the first case, then you can use Inner Join or Even lookup stage, but if its the second scenario than you will have to do left or Right outer join....

Dsguru,

You need to have some kind of FMT applied to your input, DS by itself won't know whether to take 01 or 11..unless and until you specify.

You either format your input using substring ...

Or the other alternative and preferred one is to use Iconv/Oconv functions. There are lots of posts for these, please use search feature.

You can do it by formating yuor string to the timpstamp format..

Or the alternative and preferred one is to use Iconv/Oconv functions. There are lots of posts for these, please use search feature.

Two ways you can avoid this warnings:

1. Use Message handler and suppress this warning to Information

2. If you are very sure that the column won't contain NULL then change it to NOT NULLABLE in your table definition.

If the warning are handled, using message Handler in One Environment will it create warnings in the new environment when you move your jobs?

I tried once, and I got the warnings in the new environment..is there anything specific one needs to do ?

Can you please provide some more information ? What exactly you are doing in the job..and if you got any other error apart from what you have mentioned ?

On the sameline, how easy it is to move hash files not created under project, from one server to another ?

Is it just moving it from one box to another..or you need to do anything special ?

Vincent Thank You For the information related to lookup performance. The Lookup fileset performance wise looks most of the time best option.. Few places where I struggle in using lookup fileset is, no ability to view the data and no option to append the data. Is there anything done regarding these i...

Somehow its not identifying the Col names..? It gived the error if I try CREATE>INDEX HF A,B,C