Database Management Systems

GNP (Get Next Parent) requires that the parent segment be established in the PCB before the call can be issued. Without a parent position established, DL/I cannot determine which parent's children to retrieve next. Option C correctly identifies this prerequisite.

IMS (Information Management System) uses a hierarchical database model where data is organized in a tree structure with parent-child relationships. This is distinct from network (many-to-many), relational (tables), or object-oriented models.

When the current version of a document in a version tree is deleted, the Documentum Content Server automatically promotes the version with the highest r_modify_date to be the new current version.

Connection strings vary significantly between different database systems and providers. Each database requires specific connection string parameters like provider name, data source path, authentication mode, and other database-specific settings.

The Recovery Scenario wizard in QuickTest Professional follows a specific sequence: first you define what triggers the recovery (trigger event), then define what recovery operations to perform (steps to recover), and finally define post-recovery operations (what to do after recovery completes). This logical flow ensures the test knows when to activate recovery, what actions to take, and how to resume.

A data warehouse architecture consists of three core components: metadata (technical and business definitions about the data), summary data (aggregated facts and metrics pre-calculated for query performance), and raw data (detailed transaction records from source systems). Metadata includes schemas, transformation rules, and data lineage; summary data contains pre-aggregated metrics like monthly sales totals; raw data holds the granular source records that enable drill-down analysis.

The two primary schema types for data warehouse dimensional modeling are star schema and snowflake schema. Star schema has a central fact table connected directly to dimension tables (denormalized dimensions), while snowflake schema further normalizes dimension tables into sub-dimensions. Snowflake reduces redundancy but adds join complexity; star schema is simpler for queries but has some dimension data duplication.

SCD stands for Slowly Changing Dimension - a dimension in a data warehouse that evolves over time but not with every transaction. Common examples include customer address changes, product price updates, or employee role changes. Different SCD types (1-6) handle these changes differently: Type 1 overwrites old values, Type 2 maintains history with effective dates, Type 3 adds new columns for previous values, and so on.

Same partitioning means data maintains its existing partition arrangement from the input link - no repartitioning occurs. This is efficient when data is already properly distributed. Entire would broadcast to all nodes, Hash uses key-based distribution, and DB2 uses DB2's algorithm.

Entire partitioning sends every row to every partition/node. This is used when all nodes need complete data, such as creating reference lookup files or when every row must be processed everywhere. Same keeps existing partitions, Hash distributes by key, DB2 uses database partitioning.

Range partitioning groups related records together based on key value ranges, ensuring data with similar keys lands in the same partition. Same maintains existing partitions, Entire broadcasts to all, Hash uses hash algorithm. Range is ideal for maintaining data locality.

DB2 partitioning uses the same partitioning algorithm as IBM DB2 database, allowing DataStage to align with DB2's data distribution. This is useful when data comes from or goes to DB2 tables. Same maintains partitions, Entire broadcasts all rows, Hash uses hash function.

Ordered collection reads all records from the first partition completely before moving to the second, and so on sequentially. Same and Entire are partitioning methods. Hash is a partitioning method. Ordered is specifically a collection strategy.

Database stages (Oracle, DB2, etc.) in DataStage are used for reading from or writing to database tables as sources or targets. They are not used as intermediate stages for data passing within a job. For intermediate data processing, use transformer stages, aggregators, or other processing stages.