This is simply functioning as designed, Stephen. When you allocate a chunk and it is taken, the nextId variable is reset at that time to N + <chunk size>. When the server restarts, that's the next ticket number, regardless of what happened to those preceding it. Plus, how would it know whether the Entry IDs allocated were never used, or were used and then deleted? Rick _____
From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Heider, Stephen Sent: Friday, February 09, 2007 5:40 AM To: [email protected] Subject: Re: Next-ID-Block-Size - Skipping Numbers ** Wow. I am curious as to how this is a benefit. Does anyone know why BMC designed it this way [that each time you restart the server it skips Request ID numbers]? There must be some benefit, I just can't see it. Stephen _____ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Hugo Visser Sent: Friday, February 09, 2007 5:04 AM To: [email protected] Subject: Re: Next-ID-Block-Size ** There's one thing that you have to know when working with this feature. If you restart the server the "reserved" block gets lost for ever. So when you start with a fresh form, and have reserved 1000 entry id's, the first entry id will be 000...1. If you restart the server 999 entry id's ar e "lost" so the new next entry id (the second ticket in the form) would be entry id 000001000 and not 00000..2. Hugo it___ __20060125_______________________This posting was submitted with HTML in it___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
