LIBERATE ADABAS DATA CLEVERLY, INNOVATIVELY, SUSTAINABLY

HOW YOU BRING THE PROPRIETARY DATABASE ADABAS C TRANSPARENTLY AND

FULLY AUTOMATICALLY INTO THE OPEN WORLD
VON HEIDI SCHMIDT

www.pks.de

HIERARCHICAL OR RELATIONAL PREFERABLY BOTH?

A hierarchical database such as Adabas C offers lightning
speed, high availability and high-performance handling of large
quantities of data. The thing about the hierarchical concept is
that it is based on the NF database model.
NF stands for NFNF = non first normal form.
This refers to the fact that Adabas C, to use relational theory
terminology, does not save the data in the first normal form.
Instead, the data is saved in a packaged format that also allows
period groups and multiple fields.
First invented by Peter Schnell in 1971 as a high-performance
database for mainframes, Adabas C also became available over
the years for Unix, Linux and even Windows.
Over the last 40 years, large and complex core systems were
developed on this database platform, systems which make the
most of the particular functions of Adabas C, for example index
processing, handling of large numbers of data records, or the
use of access authorisations down to the field level.

Adabas C is often used in combination with the development

environment and programming language Natural. Both products
were developed by Software AG in Darmstadt. Cobol, Assembler
and PL/I applications were developed based on an Adabas C
database, as well.
The relational model was suggested for the first time in 1970 by
Edgar F. Codd, and is still an established standard for databases. The foundation of the concept of relational databases
is the relation. It represents a mathematical description of a
table. Operations on these relations are specified by relational
algebra. Relational algebra therefore forms the theoretical basis
of SQL. For querying and changing the data, the standardised
database language SQL (Structured Query Language) is used.

Since the 80s, following the move of open platforms such as Unix, Linux or Windows into data centre operations, relational
database systems (such as Oracle, DB2, SQL Server) have been more and more in use. Due to the swift availability of SQL-based
application software, many companies decide to run both database concepts: Adabas C, and also relational databases and
corresponding applications.

BUT THIS PARALLEL RUNNING OF HIERARCHICAL AND

RELATIONAL DATABASES HAS MANY DISADVANTAGES.
DISADVANTAGE: SPECIAL ADAPTER COSTS OF SEVERAL HUNDRED THOUSAND EUROS MOUNT UP AND TAKE
THEIR TOLL ON THE IT BUDGET.
Adabas C data cannot be accessed from the open database and programming language world using standard (SQL)
procedures.
DISADVANTAGE: AS A CUSTOMER YOU FEEL TRAPPED IN THE ADABAS C WORLD.
Large applications running on an Adabas C database cannot be replaced by SQL-based procedures from one day to
the next, or rewritten in a few months.
DISADVANTAGE: PERSONNEL AND TRAINING COSTS ARE INCURRED TWICE.
Database administrators and developers must be familiar with both philosophies, NF and relational databases.
DISADVANTAGE: STAGNATION IN THE DEVELOPMENT OF ADABAS C BLOCKS THE OVERALL
ARCHITECTURE OF YOUR APPLICATIONS.
Hierarchical database concepts play only a minimal role in software strategy today.
DISADVANTAGE: HIGH ADDITIONAL COSTS ARE INCURRED FOR ADABAS C LICENCES IN THE CASE OF
INFRASTRUCTURAL CHANGES.
Licence and maintenance charges for Adabas C are usually tied to CPU ressources machine (capacity) and location.

THE EXCITING QUESTIONS ARE:

How do you move from Adabas C to an SQL database with minimal risk?
How do you consolidate the IT landscape and reduce maintenance and operational costs?
How do you achieve an application architecture that is sustainable in the long term, and
attractive to developers and users as a basic foundation for growth and enterprise success?

AND THE ANSWER IS:

SmartDCI transforms Adabas C transparently and fully automatically into DB2 or Oracle.
SmartDCI opens the door to a future-oriented architecture and makes you independent
of the implemented programming language for your application development.
Transparently, powerfully and fully automatically, SmartDCI decouples your applications
from the corresponding Adabas C databases.

The SmartDCI approach is to replace the central Adabas C database interface (ADALNK, ADALNC, ADALNU depending on the
environment) below the application level. Facing up, towards the applications, is the Adabas C schema, as before. Facing
down, towards the database, all accesses are transformed, optimised and executed fully automated by SmartDCI into SQL.
In this way, database calls can be executed against any SQL target system:

ADALINK

The SmartDCI architecture also allows you to run a combination of Adabas C and a relational database for the same
application, as well as a hybrid architecture in which, for example, the application stays on the mainframe and the database
runs on Unix, Linux or Windows.

Combination of Adabas and Relational Database

Hybrid Execution

The translation of NF to SQL is performed automatically at runtime, and the applications remain unaffected. The translation of
the data, its structure and its formats is controlled by an internal database repository. When you create the SmartDCI
repository, you can decide for each individual multiple field (MU) and each period group (PE) how it is to be depicted in the
relational target schema. This allows case-specific normalisation, for example using index columns, as well as the moving of
fields to separate tables with primary/foreign key relationships (column compression). Selection criteria for each depiction are
the performance requirements and the technical use of the data.
Due to the separation of the database and the application layer, it is also possible to develop new applications natively, based
on the now SQL-based database schema. SmartDCI therefore also acts as agent and translator between the database
philosophies of the past (hierarchical) and those of the future (relational).

Step-by-Step New Development

Complete Separation from Adabas and Natural

In addition, SmartDCI supports the remodelling of the database schema, so that optimised structures can be provided for new
applications without you needing to change anything in the old applications. Access via database frameworks such as Hibernate
is also supported. This means that the future application and database landscape comes into being step by step, at a speed that
suits your enterprise. In the end, SmartDCI can be deactivated since all applications access the new database system natively.
Which means that after about 3-5 years, SmartDCI is no longer required.

WHAT ARE THE ADVANTAGES OF SmartDCI

FOR YOUR ENTERPRISE?
ADVANTAGE: TAKES PRESSURE OF YOUR IT BUDGET
At the latest when you start running SmartDCI, you can simply cancel your Adabas licences and maintenance contracts. When
you transfer to your strategic database system of choice, there are then, ideally, no extra costs for the additional database load
of the migrated applications. So you simplify your database landscape greatly, while avoiding the expensive and error-prone
database replication procedures that were necessary before.
ADVANTAGE: WORKS SECURELY AND ERROR-FREE
With SmartDCI, youre choosing a technology that is and has been used by customers worldwide for many years. What you get
is a sophisticated, flexible migration concept that is tailored to the individual needs of your enterprise in terms of optimized
project timing, secure and intelligent fall-back scenarios, and self-verifying test procedures to take the pressure off your end
users. PKS ensures a successful project execution by deploying experienced teams that have been in place for many years.
All work takes place exclusively at your site, or at our company headquarters in Ravensburg neither near shore nor offshore
capacity is used.

ADVANTAGE: SIMPLIFIES EMPLOYEE SELECTION

After the move with SmartDCI, your database team no longer needs any expert knowledge of Adabas. As the next generation
comes in, you save the cost of training new Adabas administrators. At the same time, SmartDCI means that your experienced
Adabas experts will be able to work in the relational environment without additional training.
ADVANTAGE: MAKES YOU FLEXIBLE AND AGILE
Thanks to SmartDCI, new software projects can directly access database systems from the old world that have grown
organically and are still relevant for future core applications. The mapping between the old and the new database can be
modelled in a flexible way. Nevertheless, everything stays as it is for the Natural applications until you have successfully
completed your transfer from Adabas C. You specify the rate of innovation for your application architecture, and at the end
you are completely free from proprietary components.

HOW CAN THE IMPLEMENTATION OF SmartDCI LOOK

IN YOUR ENTERPRISE?
With you and for you, and starting with static and dynamic analyses of your Adabas C databases as well as your
application sources; we take a few days to create a robust roadmap for the smart transformation of your core
applications into a future-proof system architecture.
The first step towards the smart transformation and liberation of your data from the Adabas C prison:
You call us and we set up an individual consultation day at your site:

We show you how other customers have been successful with the SmartDCI concept
and were able to drastically reduce their IT costs.
You understand how you can migrate your Adabas C databases to SQL standards
securely and with high-performance.
You see how users, developers, and your management will love the idea
of an Adabas-C-free zone.

Send us an ADAREP of your systems and we guarantee that well provide the answers
to all your migration questions.
Feel free to contact us. We look forward to hearing from you.

Heidi Schmidt
CEO
Tel.:
+49 751 56140-229
Mobile: +49 173 5661443
e-mail: schmidt@pks.de
Bernd Butscher
Software Architect und Project Lead
Tel.:
+49 751 56140-257
e-mail: butscher@pks.de
Tobias Braun
Technical Consultant
Tel.:
+49 751 56140-241
e-mail: braun@pks.de
PKS Software GmbH
Georgstr. 15
88214 Ravensburg