I'm working with a client to cleanup your huge numbers of models in test and production environment. We checked each utility model, is it used also today, how can we customize it to use in production and test the same model. Today, we checked the BIND/REBIND and find the %OPTION symbol, which is an automatic symbol and cannot changed by the user. On the other hand, if we create a BIND/REBIND, we see, that are about 5 - 6 DB2 BIND/REBIND parms inserted. It are not BIND/REBIND values, because they will defined automatically from the REBIND execution:
A default of existing value for REBIND PLAN or REBIND PACKAGE means that the default is the value that was determined during the previous bind or rebind of the plan or package that you are rebinding.
For example at a BIND, RCM generates in the %OPTION: QUALIFIER(EWH) ISOLATION(CS) CURRENTDATA(NO) DEGREE(1 ) DBPROTOCOL(DRDA)
at a REBIND i get:
QUALIFIER(EWH) ISOLATION(CS) DEGREE(1 ) DBPROTOCOL(DRDA)
Ok, the QUALIFIER may make sense, but the other ones are the regular defaults for the parms. So, its not necessary to add this parms to the BIND/REBIND statements.
They are only confusing for users and increase the length of the analysis output a log. BIND/REBIND statements are doubled in their length.
Or am i wrong?