DB2 Database and ISPF Mainframe Quiz

To split a line in certain text editors, you can use the TS command either as a line command or prefix it on the command line, then position the cursor at the desired split point and press Enter. Options B and D (SPLIT, Break) are not the correct commands for this operation.

Entering '10000' on the command line and pressing F8 attempts to scroll, but 10000 exceeds the valid scroll amount limit for this specific editor/system, resulting in an 'Invalid Scroll Amount' error. The scroll commands typically have maximum limits (often much smaller than 10000 lines or columns). Option D is incorrect because the command can be issued, it just fails at validation.

UR (Uncommitted Read) isolation level provides maximum data concurrency while preventing access to uncommitted data. This is achieved by allowing transactions to read data that other transactions have modified but not yet committed, while still protecting against reading uncommitted changes. RS (Read Stability), CS (Cursor Stability), and RR (Repeatable Read) are more restrictive levels that reduce concurrency to prevent various types of phenomena like non-repeatable reads and phantom reads.

In relational databases like DB2, when a parent view is dropped, any views that depend on it are not automatically deleted but are instead marked as "inoperative" (or invalid), meaning they cannot be used until they are recreated or regenerated.

The RESTRICT referential integrity rule prevents the deletion of a row in the parent table if any dependent rows exist in the child table. CASCADE would delete the child rows, SET NULL would set the foreign keys to null, and DELETE is not a standard delete rule.

The REORG utility is specifically designed to reorganize table data, reclaiming space from deleted rows and improving access patterns by physically reordering data on disk. db2look is for DDL extraction, db2move is for data movement/export/import, and runstats is for updating table statistics used by the query optimizer. REORG is the correct tool for the stated purpose of space reclamation through data reorganization.

In SQL, a SELECT query without an ORDER BY clause returns rows in an ambiguous, non-guaranteed order. The database is free to return rows in whatever order is most efficient, which depends on the access path chosen by the optimizer. This order is not based on primary key, insertion order, or any specific column value unless explicitly specified. Option A is correct because relational databases make no guarantees about row order without ORDER BY.

Repeatable Read (RR) isolation level is designed to prevent phantom reads, which during an index scan requires acquiring a table-level lock to prevent other transactions from inserting or modifying rows that would affect the scan results. Read Stability (RS) and Cursor Stability (CS) use less restrictive locking at the row or page level. Uncommitted Read (UR) acquires minimal locks. The table-level lock in RR ensures that the set of rows matching a query remains consistent throughout the transaction.

The Client Configuration Assistant (CCA) is a DB2 tool used to catalog databases, which involves registering database connection information in the client's configuration. Journal, Alert Center, and License Center are not tools for cataloging databases - they serve different administrative or monitoring purposes. Cataloging is essential for clients to locate and connect to databases on the network.

SYSCTRL authority has the privilege to create databases in DB2. SYSMAINT can perform maintenance operations but cannot create databases. DBCTRL is not a standard DB2 authority level. While SYSADM (System Administrator) has all privileges including database creation, the question specifically asks for which authority CAN create a database, and SYSCTRL is the minimal authority with this privilege. The answer key is correct.

Database locking mechanisms can be applied at row level, table level, and index key level, but NOT at individual column level. Column-level locking would be extremely granular and inefficient - most database systems lock at the row or page level instead. When you need to prevent concurrent access to specific columns, you use row-level locks which protect the entire row including all its columns. This is a fundamental design decision in database concurrency control.

X locks (exclusive locks) provide the most restrictive locking mode in DB2. An X lock allows only the lock owner to access the table - all other applications are blocked from any access. The UR (Uncommitted Read) isolation level allows dirty reads, but even UR applications cannot read a table locked exclusively by another transaction. The question specifically identifies X lock as preventing concurrent access while making a narrow exception for UR-level readers.

DB2 AVI Extenders is the IBM product specifically designed for storing and managing image data within DB2 databases. It provides specialized data types and functions for image storage, retrieval, and manipulation. Net.Data is a web development environment, Net Search is not a DB2 storage product, and XML Extenders and Text Extenders handle their respective data types rather than image data.

The SELECT DISTINCT clause eliminates duplicate rows from a result set, returning only one instance of each unique row. The DISTINCT keyword is applied to the entire row (all columns), so rows must match in every column to be considered duplicates. The UNIQUE keyword and parentheses syntaxes are not valid SQL - the correct form is DISTINCT without parentheses around the asterisk.

Views are virtual tables that enhance data security and access control by limiting what data users can see or modify. By creating a view on a table, administrators can grant users access only to specific rows or columns, effectively increasing control over data access. Views do not reduce memory usage (they store no data), do not reduce compilation time (queries are still compiled), and do not increase data access time (access is similar to the base table).

The statement is false because IMS GSAM supports checkpoint and restart operations. By using symbolic checkpoint (CHKP) and restart (XRST) calls, a program loading or processing a GSAM database can indeed be restarted from the last saved checkpoint in the event of a failure, making the "True" option incorrect.

In DL/I database systems, RSA stands for Record Segment Argument. It specifies the segment type to operate on within a hierarchical database call. The other options are incorrect expansions of this acronym.