The DB2® catalog tables relating to the bind contain the actual data set location of the DBRM that was used to perform that specific bind. However, when the code is promoted to the next level of the hierarchy, the information in the DB2 Catalog is now technically incorrect as the DBRM no longer resides in the location specified. This may cause problems if the DB2 REBIND option is used.

Once a DBRM is promoted to the next level of the hierarchy it is good practice not only to bind at the To Group level, but to issue a "back-bind" that also binds the package or plan at the From Group level. To ensure that this back-bind is executed correctly, the From Group DBRM library should be concatenated in front of the To Group DBRM library just in case the program has already been changed in the From Group. Of course this may not be necessary as the SQL that is executed by the package or plan is correct, it is just the DBRM member location that is now out of date.