9a Run the CBRPBIND SAMPLIB job.
You must perform this step both for migration and at initial installation.
CBRPBIND performs a DB2 BIND of DBRMs to create the packages needed to access the OAM Object storage group tables. The use of the DB2 packages allows user defined qualifiers for the object storage groups table definitions. CBRPBIND must be modified and run prior to running the CBRABIND, CBRHBIND, or CBRIBIND jobs. It is currently written for the existing 100 Object storage groups with high-level qualifiers of GROUP00–GROUP99, so it needs to be modified for your installation requirements.
CBRPBIND now uses the VALIDATE(RUN) instead of the VALIDATE(BIND) statement. For VALIDATE(BIND), DB2 verifies the authorization at bind time. For VALIDATE(RUN), DB2 verifies the authorization initially at bind time, but if the authorization check fails, DB2 rechecks it at run time.
Statements embedded within various OSR and OSMC packages now reference the V_OSM_LOB_BASE_TBL view. However, these views might not be known to DB2 if either LOB support is disabled (default, LOB=N in IEFSSNxx Parmlib member) or LOB support is only partially enabled (LOB=P in IEFSSNxx Parmlib member). Each storage group that does not have the V_OSM_LOB_BASE_TBL created must use VALIDATE(RUN); otherwise, bind authorization occurs at bind time and the bind fails.
However, it might be desirable to use the VALIDATE(BIND) statement for each object storage group that you want to VERIFY that a V_OSM_LOB_BASE_TBL view has indeed been created. This is not required and should only be used as a precautionary measure to ensure that the LOB view has been created. The bind fails if the LOB view is not created.
Related reading: For more information on the CBRPBIND SAMPLIB job, see CBRPBIND.