IBM Db2 stored procedures used by Catalog Manager
Procedure | Description |
|---|---|
SYSPROC.ACCEL_ADD_TABLES | If you are using the IDAA Accelerator for Db2, Catalog Manager uses these stored procedures to communicate commands to the accelerator when you use the ACCEL command. |
SYSPROC.ADMIN_COMMAND_DSN | Catalog Manager uses this stored procedure to run DSN commands when connected to a remote Db2 subsystem. If the user option Run DSN commands using CLIST is set to N, Catalog Manager uses this stored procedure when attached to a local Db2 subsystem. |
SYSPROC.ADMIN_COMMAND_DB2 | Catalog Manager uses this stored procedure to run Db2 commands when connected to a remote Db2 subsystem. |
SYSPROC.ADMIN_DS_LIST | Catalog Manager uses this stored procedure to generate a data set (DS) list. If the stored procedure exists, the DS list displays data set information on a remote Db2 subsystem. If the stored procedure does not exist or returns an error, Catalog Manager generates the DS list by using LOCATE calls but returns only the DSNAME and VOLUME. |
SYSPROC.ADMIN_INFO_SYSPARM | When Catalog Manager attaches or connects to a Db2 subsystem, it uses this stored procedure to look up various Db2 system parameters. Catalog Manager also uses this stored procedure to build a DSNZPARM list. This IBM stored procedure requires an active WLM environment. All users require MONITOR1 authority because Catalog Manager calls either the SYSPROC.ADMIN_INFO_SYSPARM or SYSPROC.DSNWZP stored procedure at startup. |
SYSPROC.DSNWZP (Db2 V11 or earlier) | When Catalog Manager attaches or connects to a Db2 subsystem, it uses this stored procedure to look up various Db2 system parameters. Catalog Manager also uses this stored procedure to build a DSNZPARM list. All users require MONITOR1 authority because Catalog Manager calls either the SYSPROC.ADMIN_INFO_SYSPARM or SYSPROC.DSNWZP stored procedure at startup. |