I have a job which uses the 'KeyMgtGetNextValue' built-In routine. It has been working fine for a few months until now.
The jobs appears to hang in a constant state of 'running'. I have pin-pointed the problem down to a particular sequence I am accessing via 'KeyMgtGetNextValue'.
If I change the sequence the job works fine.
However I noticed a very odd thing when I looked in the hashed file called SDKSequnces (which holds the actual sequences used by KeyMgtGetNextValue).
The bad sequence appears to be constantly incrementing even though there are NO jobs running. So, could there be a rogue process running in the background which is constantly incremanting it?
Has anybody experianced this type of thing before?
Also, if I create a new sequence (which KeyMgtGetNextValue does on the fly) is there anyway I can start the count at a number other than 1? Suppose I could update the actual SDKSequences hashed file....but whats the best way of doing this?
Thanks
Manny
![Question :?:](./images/smilies/icon_question.gif)