Lets reverse the coupling here. Put the status bit in the individual enum, and then this method doesn't need to know about DUMMY specifically, it can just check the bit for each value, instead of this function having to have specific knowledge of the DUMMY value. Since it's the only one though, you can create two constructors to make the "autoIncrement" field default to true, and only DUMMY has to use the more complicated constructor.

This paradigm btw is referred to [loose coupling](http://en.wikipedia.org/wiki/Loose_coupling). Inside a single enum, this isn't that important, but the concept in general is, and it's important to use in more complex cases.