ADABAS Database and Natural Programming Quiz

RCT expands to Resource Control Table in mainframe systems. It manages and controls system resources during job execution. Request control table and Region control table are incorrect expansions - RCT specifically deals with resource management.

JCT stands for Journal Control Table, which tracks transaction journals and recovery information in mainframe systems. Job control table and Job control time are incorrect - JCT is specifically about journaling for recovery purposes.

DCT expands to Destination Control Table, which manages destination information and routing in data processing systems. Data coverage table and Destination coverage table are incorrect - DCT specifically controls destination handling.

The query reads records with SUPER-ID-NAME-AGE starting from '1235' through '3457'. Records with IDs 2345 and 3456 fall within this range (1235 < 2345 < 3457 and 1235 < 3456 < 3457). Record 1234 is below the range, and records 4567 and 5678 are above it. Therefore, 2 records are displayed.

The query uses SUPER-NAME-ID-AGE starting from 'A', which sorts by IDENT-NAME first. All 5 names (AAAA, ACDB, ADSB, DADS, EDSC) start with letters A or E, which come after 'A' alphabetically, so all 5 records match and are displayed.

With null suppression and SUPER-ID-NAME-AGE starting from '1234', all 5 records match because 1234 is included in the range. Note that 'bbbb' represents a space value in null-suppressed fields, which still allows the record to be retrieved.

ADABAS allows multiple DDMs (Data Definition Modules) to be mapped to the same physical database, providing different logical views of the data. This is a standard feature for accessing the same database with different field selections and naming conventions. The statement is true.

When a record layout or DDM length mismatch occurs where the database contains data longer than the program's DDM definition (A4 vs A6), updating or reading may lead to mismatch behavior, but in Adabas/Natural, changing field length specifications or updating with mismatch formats can cause runtime errors (such as NAT3009 or type conflicts) during execution, leading to abnormal termination.

The read operation starts from 'A' through 'D', meaning names starting from A up to D are included. Looking at the records, 1234 (AAAA), 2345 (ACDB), 3456 (ADSB), and 4567 (DADS) fall within this range, while 5678 (EDSC) starts with E and is excluded. The final record displayed within that range is 4567 DADS 15.

The program attempts to STORE a record into IDENTIFICATION-TABLE, but the table is never defined in the DATA division - only a VIEW is defined. Without a table structure, STORE cannot execute and the program cannot create an executable object. This is a compilation error.

The FIND uses IDENT-ID EQ '1234', which is a non-unique descriptor (appears in 2 records: AAAA and ABCD). FIND on a non-unique descriptor returns all matching records in ISN (Internal Sequence Number) order, so 2 records are displayed.

SUPER-ID-NAME-AGE comprises IDENT-ID + IDENT-NAME + IDENT-AGE concatenated. The FIND looks for records where this superdescriptor EXACTLY equals '1234'. However, no record has this value - the superdescriptor values are much longer (e.g., '1234AAAA23'). So 0 records match.

When FIND uses a non-unique descriptor (IDENT-ID has 2 records with value '1234'), ADABAS returns all matching records in ISN (Internal Sequence Number) ascending order. This is standard behavior - records are sorted by their internal ISN, not physical storage order.

SUPER-ID-NAME-AGE comprises IDENT-ID, IDENT-NAME, IDENT-AGE in that order. The READ range '1235' THRU '3457' matches 2 records: 2345 BBBB 13 (starts with 2345) and 3456 CCCC 25 (starts with 3456). Record 1234 AAAA 23 is excluded (1234 < 1235), and 4567 DDDD 15 is excluded (4567 > 3457).

SUPER-NAME-ID-AGE comprises IDENT-NAME + IDENT-ID + IDENT-AGE. Starting from 'A' matches any record where IDENT-NAME starts with 'A'. All 5 names (AAAA, ACDB, ADSB, DDDD, EEEE) start with letters A through E, but since the STARTING point is 'A' and there's no THRU clause, it reads from the first matching record (AAAA) until end - all 5 records qualify.

The READ statement using the super descriptor SUPER-ID-NAME-AGE starting from '1234' will retrieve records in sequential order. With null-suppressed fields and 5 data rows, the READ operation processes all records and displays 4 of them based on the matching criteria defined by the super descriptor.

A single ADABAS database can be mapped by multiple Data Definition Modules (DDMs). This allows different applications or views to access the same physical database with different field definitions or access patterns.

The data was stored using IDENTIFICATION-TABLE-EXP with IDENT-NAME as A6 (6 bytes), but the READ uses IDENTIFICATION-TABLE where IDENT-NAME is defined as A4 (4 bytes). This field length mismatch causes a runtime error because the READ operation cannot properly interpret the 6-byte data using a 4-byte field definition, resulting in abnormal program termination.

The READ operation with SUPER-NAME-ID-AGE processes records sequentially. The LOOP displays each record read. The final record displayed (5678 EDSC 20) corresponds to the last record in the sequence that was read and processed through the loop before the read operation completed.

The STORE statement syntax 'STORE IDENT IN RECORD' is incorrect because RECORD is not a defined DDM name or valid storage target. In Natural/ADABAS, you store records directly into a DDM-defined file. This syntax error prevents the program from being compiled into an executable object.