mainframe Online Quiz - 18

ADABAS stores data hierarchically: fields group into records, records into files, and files into a database. This is FIELD -> RECORD -> FILE -> DATABASE, which is the inverted-list structure ADABAS uses.

ADABAS uses natural language commands for data access: Find (search), Read (retrieve), Histogram (data distribution analysis), Get, Store, etc. 'Select' is SQL terminology, not part of ADABAS's native command set. ADABAS predates SQL and has its own access language.

For a single alphanumeric character 'M' in a variable field (#VAR), Fixed Format storage is preferable. Fixed storage is predictable and efficient for short values. Default Compression and Normal Suppression are variable-length techniques that add overhead for single characters. Fixed format avoids the length byte overhead.

ILB (Inclusive Length Byte) is a feature of Default Compression in ADABAS. When using default compression, ADABAS stores a length byte before compressed data to indicate the actual length. This is not part of Null Suppression (A), Fixed Format (C), or Variable Suppression (D).

ADABAS stores a single space character in an alphanumeric 20 field using 1 byte - the space itself. Even though the field is defined as 20 characters, a single space only needs 1 byte of storage (assuming no compression that would expand it). It's not 0 bytes (data exists), not 2 bytes (no length prefix for a single char), and not 20 bytes (only one character stored).

ADABAS's unique and distinguishing feature is multivalued fields - the ability to store multiple values within a single field occurrence without child tables. Different views (A), data storage (B), and security (D) are common to most database systems and not unique to ADABAS. Multivalued fields were revolutionary in pre-relational systems.

ADABAS provides both Sequential (reading records in order) and Random (direct access by descriptor value) access methods. This dual capability is fundamental to ADABAS architecture - you can scan sequentially or jump directly to specific records. It's not just one or the other.

In ADABAS, Read logical uses descriptors (inverted indexes) to find records based on field values, while Read physical and Read by ISN access records directly by their ISN without using descriptors.

ADABAS supports multiple descriptor types: super descriptors (combinations of multiple fields), sub descriptors (portions of a field), phonetic descriptors (for sound-based searching), and regular descriptors.

In COBOL, when moving PIC 9(6) VALUE 000178 to PIC 9(3)V9(3), the decimal is inserted after 3 digits from the right: 178.000. When moving PIC 9(3)V9(3) VALUE 123.456 to PIC 9(6), the decimal portion is truncated (not rounded): 000123. Option B correctly shows both transformations.

The STRING statement moves WS-VALUE (ABCD) into WS-OUT-MSG starting at position 1 (from WS-OUT-LEN). Since WS-OUT-MSG is 5 bytes and WS-VALUE is 4 bytes, the result is 'ABCD ' with a trailing space. WS-OUT-LEN is updated to 5 (1 + length of data). WS-VALUE remains unchanged at 'ABCD'. Option A correctly shows all three values.

The COPY statement in COBOL uses REPLACING with the syntax '==pseudo-text== BY ==pseudo-text=='. Option B incorrectly uses 'XYZ TO 120' which doesn't match the required pseudo-text format with == delimiters. Options A, C, and D show valid COPY syntax.

COBOL programs must have four divisions in a specific order: IDENTIFICATION DIVISION (program identification), ENVIRONMENT DIVISION (external environment configuration), DATA DIVISION (data definitions), and PROCEDURE DIVISION (executable logic). Option C shows the correct sequence. Options A and B misorder the divisions, and option D incorrectly substitutes Working-Storage (a section within Data Division) for a full division.

In COBOL, tables (arrays) can have up to 7 dimensions. This is a standard COBOL limitation - the OCCURS clause can be nested up to 7 levels deep to create multi-dimensional tables. Each dimension is defined using nested OCCURS clauses in the data division.

The SET statement assigns the first value in the range defined by the level-88 condition, which is 10, to the elementary data item Data.

In COBOL report writing, the three primary verbs are INITIATE (starts the report processing), GENERATE (produces report lines based on report groups), and TERMINATE (ends report processing and produces final totals). These verbs control the complete lifecycle of a report. Option D incorrectly uses 'Initialize' and 'End', while Option B incorrectly uses 'Write' instead of 'Generate'.

In COBOL, the MERGE verb combines multiple pre-sorted input files into a single sorted output file. Unlike the SORT verb, MERGE does not support INPUT PROCEDURE because the input files must already be sorted - MERGE only merges existing sorted files. OUTPUT PROCEDURE is supported to process the merged output. Option A is incorrect because KEY data items with OCCURS clause are not allowed. Option B is incorrect because MERGE implicitly opens files. Option C is incorrect because OUTPUT PROCEDURE cannot contain SORT or MERGE statements.

IBM's Information Management System (IMS), one of the first hierarchical database management systems, was developed in 1966-1968. It was initially developed for the Apollo space program and became one of IBM's most important software products. 1968 is the correct answer among the options provided.

In DL/I (Data Language/I), which is the data manipulation language for IMS databases, the segment is the smallest unit of data that can be retrieved or stored. Fields exist within segments but are not independently addressable by DL/I calls - you always work with entire segments. Therefore, 'SEGMENT, FIELD' correctly identifies the hierarchical relationship where segment is the smallest fetchable unit and field is within it.

In IMS terminology, a segment type is like a template or structure definition (similar to a class in programming), while a segment occurrence is a specific instance of that type with actual data values (similar to an object). For example, 'CUSTOMER' might be a segment type, while a specific customer's data record would be a segment occurrence. Therefore, segment occurrence is an instance of segment type, not the reverse.