NIGERIAN DEFENCE ACADEMY

DEPRATMENT OF COMPUTER SCIENCE

CS 911 – ADVANCED DATABASE TECHNOLOGY &

APPLICATIONS

BY

ANAS ABDUSSALAM (NDAPGS/FMSIS/COM012024/3918)

YAKUBU ERNEST NWUKU (NDAPGS/FMSIS/COM012024/5184)

PhD COMPUTER SCIENCE

1
Integrated Data Store (IDS)

The Integrated Data Store (IDS) was developed by Charles Bachman at General Electric in 1964.
It was designed to It was the first commercial DBMS to use the network data model, which
allowed for more complex data relationships than the hierarchical model. IDS played a crucial
role in the development of the CODASYL DBTG (Conference on Data Systems Languages Data
Base Task Group) model, which became a standard for network databases.

Features

 Network Data Model: Uses a graph-like structure to represent many-to-many relationships,

providing more flexibility than the hierarchical model.
 Efficient Data Retrieval: Optimized for efficient navigation and retrieval of interconnected
records.
 Data Integrity: Ensures data integrity through defined relationships and constraints between
records.
 High Flexibility: Capable of modeling complex relationships that are difficult to represent in
hierarchical systems.
 Concurrent Access: Supports concurrent access by multiple users, ensuring data consistency and
integrity.

Design Issues

 Complexity: The network model can be complex to design, understand, and navigate,
particularly for large datasets.
 Standardization: Early versions of IDS lacked standardized query languages, making it more
challenging to use and learn.
 Maintenance: Maintaining and updating the network structure can be labor-intensive, especially
as data relationships grow more intricate.
 Limited Scalability: While IDS was designed to handle large volumes of data, the system's
architecture and network model were not easily scalable for very large databases or high
transaction environments.
 Performance Overhead: The pointer-based navigation and complex relationships in the network
model could introduce significant performance overhead, particularly for large databases with
many interrelated records.

2
Sample Program

IDENTIFICATION DIVISION.

PROGRAM-ID. SAMPLE-IDS.

DATA DIVISION.

WORKING-STORAGE SECTION.

01 EMP-RECORD.

05 EMP-ID PIC X(5).

05 EMP-NAME PIC X(30).

05 EMP-DEPT PIC X(10).

PROCEDURE DIVISION.

* Connecting to the database

CALL 'IDS_CONNECT' USING EMP-RECORD.

* Retrieving an employee record

CALL 'IDS_RETRIEVE' USING

BY CONTENT EMP-ID

RETURNING EMP-RECORD.

DISPLAY 'Employee ID: ' EMP-ID.

DISPLAY 'Employee Name: ' EMP-NAME.

DISPLAY 'Employee Department: ' EMP-DEPT.

* Closing the database

CALL 'IDS_DISCONNECT'.

STOP RUN.
3
IBM Information Management System (IMS)

History of DBMS

IMS is a comprehensive database management and transaction processing system developed by IBM. It
was created in 1966 in collaboration with North American Rockwell (now part of Boeing) and
Caterpillar. It was initially designed to manage the complex manufacturing processes and vast
inventories required for the Apollo space missions. IMS became commercially available in 1968
and quickly gained popularity for its ability to handle large volumes of data with high reliability.

Features

 Hierarchical Database Model: IMS organizes data in a tree-like structure where each
parent node can have multiple children, but each child node has only one parent.
 High Performance: Optimized for transaction processing, IMS provides quick data
retrieval and updates.
 Data Integrity: Ensures consistency and integrity of data through its strict hierarchical
model and built-in validation rules.
 Batch and Online Processing: Supports both batch processing for large volumes of data
and online transaction processing (OLTP) for real-time operations.
 High Availability: Designed for high availability and reliability, making it suitable for
mission-critical applications.

Design Issues

 Inflexibility: The hierarchical model can be rigid and difficult to adapt to changing
business requirements.
 Complex Queries: Navigating the hierarchical structure can be complex, especially for
queries involving multiple levels of the hierarchy.
 Scalability: While IMS can handle large amounts of data, the hierarchical model can
become cumbersome as the database grows in complexity.
 High Maintenance and Operational Costs: The complexity of IMS, coupled with its
specialized nature, often results in high maintenance and operational costs. This includes costs
related to system upgrades, schema changes, performance tuning, and staff training.
 Integration with Modern Systems: While IMS has been updated to support integration with
modern technologies (such as XML, Java, and web services), its core architecture remains rooted
in legacy design principles.

4
Sample Program
IDENTIFICATION DIVISION.

PROGRAM-ID. SAMPLE-IDS.

DATA DIVISION.

WORKING-STORAGE SECTION.

01 EMP-RECORD.

05 EMP-ID PIC X(5).

05 EMP-NAME PIC X(30).

05 EMP-DEPT PIC X(10).

PROCEDURE DIVISION.

* Connecting to the database

CALL 'IDS_CONNECT' USING EMP-RECORD.

* Retrieving an employee record

CALL 'IDS_RETRIEVE' USING

BY CONTENT EMP-ID

RETURNING EMP-RECORD.

DISPLAY 'Employee ID: ' EMP-ID.

DISPLAY 'Employee Name: ' EMP-NAME.

DISPLAY 'Employee Department: ' EMP-DEPT.

* Closing the database

CALL 'IDS_DISCONNECT'.

STOP RUN.

5
References
1. IBM IMS Overview
 IBM. (n.d.). IMS: An Overview
2. Historical Development of IMS
 IBM. (2016). IMS: 50 Years of Innovation
3. IMS in the Apollo Program
 Northrop Grumman. (n.d.). How IBM's IMS Helped Put a Man on the Moon
4. Integrated Data Store (IDS)
Historical Background of IDS
 Computer History Museum. (n.d.). Charles W. Bachman - Oral History
5. Development and Impact of IDS
1. Bachman, C. W. (1973). The Programmer as Navigator. Communications of the ACM,
16(11), 653-658.
6. CODASYL DBTG and IDS
1. CODASYL Data Base Task Group. (1971). Report of the CODASYL Data Base Task
Group
2. This report outlines the network database model developed by the CODASYL DBTG,
heavily influenced by IDS.