Using the Rebind Package tool, you can selectively rebind packages within the database. Processing may be initiated for immediate execution (PF key 10) or scheduled execution (PF key 6) using the Job Scheduling tool.
The Rebind Package tool uses the Database Services (DBS) Utility command REBIND PACKAGE described in the DB2 Server for VSE & VM Database Services Utility manual.
Below is an example of the Package Rebind Utility Screen.
Figure 209. Rebind Package Tool Entry Panel
+--------------------------------------------------------------------------------+ | ******* SQLRBIND V7.1 **** PACKAGE REBIND UTILITY ************* | | | | DATABASE ==> SQLDBA | | -------- | | | | | | ----------------------------- Options ------------------------------ | | | | PACKAGE CREATOR ==> ALL ( ALL, creator, use % for wildcard ) | | ------------------ | | PACKAGE NAME ==> ( blank for ALL, use % for wildcard ) | | ------------------ | | INVALID ==> YES ( YES or NO, rebind only if INVALID ) | | --- | | PAUSE ==> NO ( YES or NO, pause after DBSU creation ) | | --- | | | | | | | | | | | | | | PF: 1 HELP 3 QUIT 4 EXIT 5 Main Menu 6 SCHEDULE 10 PROCESS NOW | | | +--------------------------------------------------------------------------------+
The name of the target database where maintenance will be performed. Enter either the machine name or dbname.
Only packages having a specified PACKAGE CREATOR will be considered for rebinding. You may use a percent sign (%) at the beginning or end of your entry to represent zero or more characters. This allows you to select packages when only knowing a portion of the value or to select packages having similar values. Enter 'ALL' to rebind packages regardless of PACKAGE CREATOR.
Only packages having a specified PACKAGE NAME will be considered for rebinding. You may use a percent sign (%) at the beginning or end of your entry to represent zero or more characters, allowing you to select packages when only knowing a portion of the name or to select packages having similar names. Enter 'ALL' (or leave blank) to rebind packages regardless of PACKAGE NAME.
Enter 'YES' to rebind only those packages that are currently invalid. Enter 'NO' to rebind packages regardless of whether they are currently invalid.
Enter 'YES' to have the Rebind Package tool generate and capture all REBIND PACKAGE commands as specified without executing. The output is saved in Database Services Utility (DBSU) command file 'creator SQLDBSU A' (see Figure 210) where creator equals the PACKAGE CREATOR entry without the optional leading and trailing percent signs (%). You may execute the DBSU file at a later date and time using the DBS Utility external to the product.
| Note: | If file 'creator SQLDBSU A' already exists, then a backup copy is made before the new file is created. The name of the backup file is generated by taking the original name, switching the file name and file type, then reversing the order of the characters. For example, if the original file is named ALL SQLDBSU A, then the backup file will be named USBDLQS LLA A. If the backup file already exists, it will be overwritten without warning. |
Figure 210. Example SQLDBSU File Generated by Rebind Package Tool
SET AUTOCOMMIT (ON) SET ERRORMODE (CONTINUE) REBIND PACKAGE ("SQLDBA1"."ARIDSQL"); REBIND PACKAGE ("SQLDBA1"."ARIFCRD"); REBIND PACKAGE ("SQLDBA1"."ARIISQL"); REBIND PACKAGE ("SQLDBA2"."ETCATPHD"); REBIND PACKAGE ("SQLDBA3"."ETCATPHI"); REBIND PACKAGE ("SQLDBA4"."ETCATPHM"); |
Figure 211. Example DBSU Message File Output Generated During Processing
ARI0801I DBS Utility started: 05/13/97 15:37:21.
AUTOCOMMIT = OFF ERRORMODE = OFF
ISOLATION LEVEL = REPEATABLE READ
------> SET AUTOCOMMIT (ON)
ARI0815I ...AUTOCOMMIT Processing Mode = ON
ARI8997I ...Begin COMMIT processing.
ARI0811I ...COMMIT of any database changes successful.
------> SET ERRORMODE (CONTINUE)
ARI0827I ...Begin command execution: ERRORMODE = CONTINUE
------> REBIND PACKAGE ("SQLDBA1"."ARIDSQL");
ARI0852I REBIND PACKAGE processing started.
ARI0855I REBIND PACKAGE processing successful.
ARI8997I ...Begin COMMIT processing.
ARI0811I ...COMMIT of any database changes successful.
------> REBIND PACKAGE ("SQLDBA1"."ARIFCRD");
ARI0852I REBIND PACKAGE processing started.
ARI0855I REBIND PACKAGE processing successful.
ARI8997I ...Begin COMMIT processing.
ARI0811I ...COMMIT of any database changes successful.
------> REBIND PACKAGE ("SQLDBA1"."ARIISQL");
ARI0852I REBIND PACKAGE processing started.
ARI0855I REBIND PACKAGE processing successful.
ARI8997I ...Begin COMMIT processing.
ARI0811I ...COMMIT of any database changes successful.
------> REBIND PACKAGE ("SQLDBA2"."ETCATPHD");
ARI0852I REBIND PACKAGE processing started.
ARI0855I REBIND PACKAGE processing successful.
ARI8997I ...Begin COMMIT processing.
ARI0811I ...COMMIT of any database changes successful.
------> REBIND PACKAGE ("SQLDBA3"."ETCATPHI");
ARI0852I REBIND PACKAGE processing started.
ARI0855I REBIND PACKAGE processing successful.
ARI8997I ...Begin COMMIT processing.
ARI0811I ...COMMIT of any database changes successful.
------> REBIND PACKAGE ("SQLDBA3"."ETCATPHM");
ARI0852I REBIND PACKAGE processing started.
ARI0855I REBIND PACKAGE processing successful.
ARI8997I ...Begin COMMIT processing.
ARI0811I ...COMMIT of any database changes successful.
ARI0802I End of command file input.
ARI0809I ...No errors occurred during command processing.
ARI0808I DBS processing completed: 05/13/97 15:37:26.
|