We have a generic w/ multiple lengths, defined by dash number, and the issue we are running into is when we release the generic and all existing dash numbers, w/ assoc. .drw, additional dash numbers can not be checked in unless the entire dataset is in an uncontrolled state. Thus, a change notice must be written against the entire package in order to add new dash numbers. As opposed to just releasing the new dash numbers via a Release Notice. Apparently, this is due to model check. In other words, if new instances are to be added to the generic family table, ALL instances must be in an unreleased/unlocked state so that modelcheck may run. Is our only option advancing the revision of the entire dataset? Or are there any other suggestions?
↧