Home > Articles > Home & Office Computing > Mac OS X

z/OS® Version 8 DBA Certification Guide: DB2 Environment

Jan 28, 2005

📄 Contents

␡

⎙ Print

< Back Page 11 of 15 Next >

This chapter is from the book 

DB2 for z/OS Version 8 DBA Certification Guide

Learn More Buy

Catalog and Directory

The DB2 catalog and directory act as central repositories for all information about the support and operations of DB2 objects, authorizations, and communications. The catalog comprises several DB2 tables and can be accessed via SQL. The catalog contains details about DB2 objects obtained from the DDL (Data Definition Language) when an object is created or altered or from DCL (Data Control Language) when an authorization is granted on an object or a group of objects. The DB2 catalog also contains information about communications with other DB2 and non-DB2 databases through the use of the communications database (CDB), which contains information about VTAM and TCP/IP addresses.

Table 2-4 lists the DB2 catalog tables and the types of information in each. (Descriptions of all the columns in the DB2 catalog tables can be found in detail in Appendix D of the IBM DB2 for z/OS Version 8 SQL Reference Manual.)

Table 2-4. DB2 Catalog Tables

*Table Name (`SYSIBM.``table`***)	Information Contents
`IPLIST`	Allows multiple IP addresses to be specified for a given `LOCATION`. Insert rows into this table when you want to define a remote DB2 data sharing group. Rows can be inserted, updated, and deleted.
`IPNAMES`	Defines the remote DRDA servers DB2 can access using TCP/IP. Rows in this table can be inserted, updated, and deleted.
`LOCATIONS`	Contains a row for every accessible remote server. The row associates a `LOCATION` name with the TCP/IP or SNA network attributes for the remote server. Requesters are not defined in this table. Rows in this table can be inserted, updated, and deleted.
`LULIST`	Allows multiple LU (Logical Unit) names to be specified for a given `LOCATION`. Insert rows into this table when you want to define a remote DB2 data sharing group. The same value for the `LUNAME` column cannot appear in both the `SYSIBM.LUNAMES` table and the `SYSIBM.LULIST` table. Rows in this table can be inserted, updated, and deleted.
`LUMODES`	Each row of the table provides VTAM with conversation limits for a specific combination of `LUNAME` and `MODENAME`. The table is accessed only during the initial conversation-limit negotiation between DB2 and a remote LU. This negotiation is called change-number-of-sessions (CNOS) processing. Rows in this table can be inserted, updated, and deleted.
`LUNAMES`	The table must contain a row for each remote SNA client or server that communicates with DB2. Rows can be inserted, updated, or deleted.
`MODESELECT`	Associates a mode name with any conversation created to support an outgoing SQL request. Each row represents one or more combinations of `LUNAME`, authorization ID, and application plan name. Rows in this table can be inserted, updated, and deleted.
`SYSAUXRELS`	Contains one row for each auxiliary table created for a LOB column. A base table space that is partitioned must have one auxiliary table for each partition of each LOB column.
`SYSCHECKDEP`	Contains one row for each reference to a column in a table check constraint.
`SYSCHECKS`	Contains one row for each table-check constraint.
`SYSCHECKS2`	Contains one row for each table-check constraint created in or after version 7.
`SYSCOLAUTH`	Records the `UPDATE` or `REFERENCES` privileges that are held by users on individual columns of a table or view.
`SYSCOLDIST`	Contains one or more rows for the first key column of an index key. Rows in this table can be inserted, updated, and deleted.
`SYSCOLDIST_HIST`	Contains rows from `SYSCOLDIST`. Whenever rows are added or changed in `SYSCOLDIST`, the rows are also written to the new history table. Rows in this table can be inserted, updated, and deleted.
`SYSCOLDISTSTATS`	Contains zero or more rows per partition for the first key column of a partitioning index or DPSI (Data Partitioned Secondary Index). Rows are inserted when `RUNSTATS` scans index partitions of the partitioning index. No row is inserted if the index is nonpartitioning. Rows in this table can be inserted, updated, and deleted.
`SYSCOLSTATS`	Contains partition statistics for selected columns. For each column, a row exists for each partition in the table. Rows are inserted when `RUNSTATS` collects either indexed column statistics or nonindexed column statistics for a partitioned table space. No row is inserted if the table space is nonpartitioned. Rows in this table can be inserted, updated, and deleted.
`SYSCOLUMNS`	Contains one row for every column of each table and view.
`SYSCOLUMNS_HIST`	Contains rows from `SYSCOLUMNS`. Whenever rows are added or changed in `SYSCOLUMNS`, the rows are also written to the new history table. Rows in this table can be inserted, updated, and deleted.
`SYSCONSTDEP`	Records dependencies on check constraints or user-defined defaults for a column.
`SYSCOPY`	Contains information needed for recovery.
`SYSDATABASE`	Contains one row for each database, except for database DSNDB01.
`SYSDATATYPES`	Contains one row for each distinct type defined to the system.
`SYSDBAUTH`	Records the privileges held by users over databases.
`SYSDBRM`	Contains one row for each DBRM of each application plan.
`SYSDUMMY1`	Contains one row. The table is used for SQL statements in which a table reference is required, but the contents of the table are not important.
`SYSFIELDS`	Contains one row for every column that has a field procedure.
`SYSFOREIGNKEYS`	Contains one row for every column of every foreign key.
`SYSINDEXES`	Contains one row for every index.
`SYSINDEXES_HIST`	Contains rows from `SYSINDEXES`. Whenever rows are added or changed in `SYSINDEXES`, they are also written to the new history table. Rows in this table can be inserted, updated, and deleted.
`SYSINDEXPART`	Contains one row for each nonpartitioning index and one row for each partition of a partitioning index or a DPSI.
`SYSINDEXPART_HIST`	Contains rows from `SYSINDEXPART`. Whenever rows are added or changed in `SYSINDEXPART`, they are also written to the new history table. Rows in this table can be inserted, updated, and deleted.
`SYSINDEXSTATS`	Contains one row for each partition of a partitioning index. Rows in this table can be inserted, updated, and deleted.
`SYSINDEXSTATS_HIST`	Contains rows from `SYSINDEXSTATS`. Whenever rows are added or changed in `SYSINDEXSTATS`, they are also written to the new history table. Rows in this table can be inserted, updated, and deleted.
`SYSJARCLASS_SOURCE`	Auxiliary table for `SYSIBMSYSCONTENTS`.
`SYSJARCONTENTS`	Contains Java class source for installed JAR (Java Archive).
`SYSJARDATA`	Auxiliary table for `SYSIBMSYSOBJECTS`.
`SYSJAROBJECTS`	Contains binary large object representing the installed JAR.
`SYSJAVAOPTS`	Contains build options used during `INSTALL_JAR`.
`SYSKEYCOLUSE`	Contains a row for every column in a unique constraint—primary key or unique key—from the `SYSIBM.SYSTABCONST` table.
`SYSKEYS`	Contains one row for each column of an index key.
`SYSLOBSTATS`	Contains one row for each LOB table space.
`SYSLOBSTATS_HIST`	Contains rows from `SYSLOBSTATS`. Whenever rows are added or changed in `SYSLOBSTATS`, they are also written to the new history table. Rows in this table can be inserted, updated, and deleted.
`SYSPACKAGE`	Contains a row for every package.
`SYSPACKAUTH`	Records the privileges that users hold over packages.
`SYSPACKDEP`	Records the dependencies of packages on local tables, views, synonyms, table spaces, indexes and aliases, functions, and stored procedures.
`SYSPACKLIST`	Contains one or more rows for every local application plan bound with a package list. Each row represents a unique entry in the plan's package list.
`SYSPACKSTMT`	Contains one or more rows for each statement in a package.
`SYSPARMS`	Contains one row for each parameter of a routine or multiple rows for table parameters—one for each column of the table.
`SYSPKSYSTEM`	Contains zero or more rows for every package. Each row for a given package represents one or more connections to an environment in which the package could be executed.
`SYSPLAN`	Contains one row for each application plan.
`SYSPLANAUTH`	Records the privileges that users hold over application plans.
`SYSPLANDEP`	Records the dependencies of plans on tables, views, aliases, synonyms, table spaces, indexes, functions, and stored procedures.
`SYSPLSYSTEM`	Contains zero or more rows for every plan. Each row for a given plan represents one or more connections to an environment in which the plan could be used.
`SYSRELS`	Contains one row for every referential constraint.
`SYSRESAUTH`	Records `CREATE IN` and `PACKADM ON` privileges for collections, `USAGE` privileges for distinct types, and `USE` privileges for buffer pools, storage groups, and table spaces.
`SYSROUTINEAUTH`	Records the privileges that users hold on routines. (A routine can be a user-defined function, a cast function, or a stored procedure.)
`SYSROUTINES`	Contains one row for every routine. (A routine can be a user-defined function, a cast function, or a stored procedure.)
`SYSROUTINES_OPTS`	Contains one row for each generated routine, such as one created by the DB2 Development Center tool, that records the build options for the routine. Rows in this table can be inserted, updated, and deleted.
`SYSSCHEMAAUTH`	Contains one or more rows for each user granted a privilege on a particular schema in the database.
`SYSSEQUENCEAUTH`	Records the privileges that users hold over sequences.
`SYSSEQUENCES`	Contains one row for each identity column.
`SYSSEQUENCESDEP`	Records the dependencies of identity columns on tables.
`SYSSTMT`	Contains one or more rows for each SQL statement of each DBRM.
`SYSSTOGROUP`	Contains one row for each storage group.
`SYSSTRINGS`	Contains information about character conversion. Each row describes a conversion from one coded character set to another.
`SYSSYNONYMS`	Contains one row for each synonym of a table or a view.
`SYSTABAUTH`	Records the privileges that users hold on tables and views.
`SYSTABCONST`	Contains one row for each unique constraint—primary key or unique key—created in DB2 for OS/390 version 7 or later.
`SYSTABLEPART`	Contains one row for each nonpartitioned table space and one row for each partition of a partitioned table space.
`SYSTABLEPART_HIST`	Contains rows from `SYSTABLEPART`. Rows are added or changed when `RUNSTATS` collects history statistics. Rows in this table can be inserted, updated, and deleted.
`SYSTABLES`	Contains one row for each table, view, or alias.
`SYSTABLES_HIST`	Contains rows from `SYSTABLES`. Rows are added or changed when `RUNSTATS` collects history statistics. Rows in this table can be inserted, updated, and deleted.
`SYSTABLESPACE`	Contains one row for each table space.
`SYSTABSTATS`	Contains one row for each partition of a partitioned table space. Rows in this table can be inserted, updated, and deleted.
`SYSTABSTATS_HIST`	Contains rows from `SYSTABSTATS`. Rows are added or changed when `RUNSTATS` collects history statistics. Rows in this table can be inserted, updated, and deleted.
`SYSTRIGGERS`	Contains one row for each trigger.
`SYSUSERAUTH`	Records the system privileges that users hold.
`SYSVIEWDEP`	Records the dependencies of views on tables, functions, and other views.
`SYSVIEWS`	Contains one or more rows for each view.
`SYSVOLUMES`	Contains one row for each volume of each storage group.
`USERNAMES`	Uses each row in the table to carry out one of the following operations: Outbound ID translation Inbound ID translation and "come from" checking Rows in this table can be inserted, updated, and deleted.

Catalog Consistency Queries

Consistency queries can be executed as part of the migration process to ensure that the data in the catalog is correct. These queries are found in the data set prefix.SDSNSAMP(DSNTESQ). These queries test such logical relationships as ensuring that all indexes are created on tables that exist.

The SQL statements can be executed from SPUFI or from a dynamic SQL program, such as DSNTEP2. The queries can be executed on the catalog tables or on copies of the catalog. RUNSTATS should be run on the catalog or the copies to ensure the best performance. In some cases, the queries will perform better when executed on the copies, using the extra indexes as defined for some of the tables.

Following is an example of a catalog consistency query that checks whether all table spaces belong to a defined database. This query will find all the SYSTABLESPACE databases that do not have corresponding rows in SYSDATABASE. The desired—expected—result is to have no rows returned.

SELECT DBNAME, NAME
   FROM SYSIBM.SYSTABLESPACE TS
   WHERE NOT EXISTS
     (SELECT *
        FROM SYSIBM.SYSDATABASE DB
        WHERE DB.NAME = TS.DBNAME);

DB2 Directory

The DB2 directory is used to store information about the operation and housekeeping of the DB2 environment. This directory, unlike the DB2 catalog, cannot be accessed by using SQL. The DB2 directory contains information required to start DB2; activities and utilities in the DB2 environment do the updating and deleting of table entries in the DB2 directory. The DB2 directory contains five tables: a description of each is given in Table 2-5.

Table 2-5. DB2 Directory Tables

Directory Table	Information Contents
`SPT01`	Referred to as the skeleton package table (SKPT), this table contains information about the access paths and the internal form of the SQL for a package at bind time. Entries are made into this table during bind time (`BIND PACKAGE`), and entries are deleted when a package is freed (`FREE PACKAGE`). This table is loaded into memory at execution time, along with the `SCT02` table described next.
`SCT02`	Referred to as the skeleton cursor table (SKCT), this table contains information about access paths and the internal form of the SQL for an application plan. Entries in this table are made when a plan is bound (`BIND PLAN`) and deleted when a plan is freed (`FREE PLAN`). This table is also loaded into memory at execution time.
`DBD01`	Information about DBDs (database descriptors), which are internal control blocks, is kept in this table. Each DB2 database has one DBD for its objects: table spaces, indexes, tables, referential integrity constraints, and check constraints. Updates to this table are made when a database is created or updated. This information is accessed by DB2 in place of continually using the DB2 catalog, permitting faster, more efficient access to this information. The information in the `DBD01` directory table is also contained in the DB2 catalog.
`SYSLGRNX`	Referred to as the log range table, this table contains information from the DB2 logs about the RBA (relative byte address) range for updates. This allows DB2 to efficiently find the RBAs needed from the DB2 logs for recovery purposes. A row is inserted every time a table space or a partition is opened or updated and is updated when the object is closed.
`SYSUTILX`	This system utilities table stores information about the execution of DB2 utilities, including the status and the steps during execution. This information is used when a utility needs to be restarted. Information in this table is added when a utility is started, and the entry is removed when the execution has ended.

< Back Page 11 of 15 Next >

🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Privacy Notice

Overview

Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security

Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children

This site is not directed to children under the age of 13.

Marketing

Pearson may send or direct marketing communications to users, provided that

Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
Such marketing is consistent with applicable law and Pearson's legal obligations.
Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out

Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

As required by law.
With the consent of the individual (or their parent, if the individual is a minor)
In response to a subpoena, court order or legal process, to the extent permitted or required by law
To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
To investigate or address actual or suspected fraud or other illegal activities
To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links

This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020

Email Address