| Consolidate. Modernize. Create added value. |
| |
| Short Description |
| |
| With SmartDCI®, Adabas C applications can be quickly and securely migrated to RDBMS – without having to make any modifi cations to the source code. |
| |
| All access to Adabas is made by SmartDCI® in runtime and transmitted to the Oracle database in the background – totally unnoticed by the applications. |
| |
Data from the relational database are then returned to the application(s) in Adabas format.
In doing so, all Adabas specifi cs (ISN, multiple fi elds, period groups, super descriptors, etc.) are
migrated and supported. |
| |
| Because the applications themselves remain unchanged and only the system gateways to Adabas (the so-called ADALNK) are replaced by SmartDCI®, it doesn’t matter what language the applications were written in – they can all be migrated from Adabas C to Oracle whether they were coded in COBOL, PLI, Natural or Assembler. |
| |
| The Situation - Arguments: |
| |
 A number of different in-house database systems, therefore different production environments
 (JCL, backup recovery, etc.) |
| |
| High degree of effort needed for data exchange, integration and syncing of data |
| |
| Proprietary interface for access to Adabas C |
| |
Insuffi cient support available on the market for Adabas C (BI tools, reporting tools,
personnel, etc.) |
| |
| Heavy costs for maintenance and upgrades to the Adabas C database |
| |
| High degree of dependency on Software AG and its technologies |
| |
| Questions: |
| |
How high is your fi xed budget for running production processes, maintenance and, in
particular, upgrades for the Adabas database? |
| |
How much time and how many employees do you have to sync and integrate your Adabas
database with other databases? |
| |
How many gateways between the apps have to currently be manually and thus elaborately
main tained due to the Adabas database? |
| |
How much time and how many employees do you have to generate data analyses and reports
from the Adabas databases? |
| |
Can you fulfi ll all of the specialized and technical demands with your Adabas database within
your required timeframe, without any additional products from Software AG? |
| |
| How do you ensure an upgrade to state-of-the-art, standardized technologies with Adabas? |
| |
| How dependent do you think you are on Software AG and its technology? |
| |
| Uses and Key Features of the Migration with SmartDCI® |
| |
Consolidation of in-house databases – a strategic database, production environment, no repeat
licensing and maintenance costs |
| |
| Integration of applications through commonly used database |
| |
| Independence from Software AG’s licensing and maintenance policies |
| |
| Adabas applications are run in an unmodifi ed state in RDBMS |
| |
| No modifi cation of the source code; applications continue to run in an unmodifi ed state |
| |
| Independent of the respective programming language |
| |
| Support of Adabas specifi cs like ISN, multiple fi elds, period groups, super descriptors, etc. |
| |
| Little testing effort needed for migration |
| |
| Automated test procedure based on Adabas command logs |
| |
| Fully relational database scheme in RDBMS |
| |
| Simple use of BI tools or reporting tools thanks to SQL standard |
| |
| Target Group |
| |
| Any company that has developed proprietary applications based on Adabas C, regardless of its line of trade. The applications’ programming language is irrelevant. Risk awareness and demands on the applications’ performance is very high. |
| |
| Distinguishing Features |
| |
The Gartner Group also advises users of so-called pre-relational mainframe databases (e.g. Adabas C) to develop some migration plans within the next few years.
Migration to RDBMS without any changes to the applications themselves is only possible with SmartDCI®; there is no other product in the world that is based on a transparency gateway.
The risks of migrating are also signifi cantly lower than with any other available technology. And testing efforts are only a fraction of those needed with other strategies because the business process logic does not need to be checked, only the parity of data between Adabas and RDBMS. This is why calculations for such a migration plan will be much lower than for any other method (manual, semiautomatic, new development, standard software). |
| |
| A Selection of Our References |
| |
TMD Friction
Steinbruchs-Berufsgenossenschaft (worker’s compensation)
GEMA (collecting society)
NUR DIE (hosiery manufacturer)
Unicef |
| |
| Further Information |
| |
Supported Platforms:
Mainframe: zOS, BS2000, (VSE)
Unix: AIX, HP-UX, Linux, Solaris
Windows: Server platforms
Databases: Oracle, DB2 |
| |
| Pricing: |
| |
No users or MSUs are licensed, only the one-time degree of utilization of SmartDCI®.
Prices are based on the size and complexity of the database to be migrated (number of fi les, number of multiple fields and period groups).
A database report from the Adabas databases is all that it takes to get a binding licensing quote.
A fl at rate for the migration project is calculated after an analysis of the application and database is conducted. Maintenance is calculated according to your specifi c demands on response time and support availability. |
| |
| Contact: |
| |
PKS Software GmbH
Georgstr. 15
88214 Ravensburg
Germany |
Mathias Jacobi
+49 751 56140-236
 Contact |
