ADABAS/Natural Utilities

Field definitions are automatically extracted directly from the backup or database, so the selection process can be configured without maintaining a separate definition set. In a single pass of the input file, ADASTRIP can extract all required data from an application for further processing.

Simple parameters specify field and data-selection criteria. The utility can work from ADABAS databases or backups created by ADASAV or CCA Software’s QDUMP, giving teams a practical way to create subsets of data for reporting, testing, migration, conversion and downstream integration.

eSTRIP creates the primary-key extract file and then runs as a special ADASTRIP user exit to undertake the selection process. A set of useful ADASTRIP exits is associated with eSTRIP, with those exits available separately where specialist selection is required.

Related records can therefore be kept together when creating subsets from high-performance transaction ADABAS databases. The output is suitable for test databases or for publishing related data to a data warehouse or RDBMS.

STRIPZIP converts variable-record ADASTRIP output into compressed ASCII data, reducing dataset size and transmission time for distributed processing.

ADAREORG enables DBAs to insert or delete fields anywhere in a file, including within a Periodic Group, create subsets based on comparisons of specified fields, and convert data formats. It supports field-type conversions, changes in length, and moving fields into or out of periodic groups or multi-valued fields.

It can reorder fields within a record, manipulate data at sub-field level, join two files whether compressed or decompressed, and undertake specialised conversions through field-level user exits. These functions let teams respond quickly to changes in application requirements with minimal effort, risk and resource usage.

ADAMAGIC is the server-oriented counterpart to the mainframe ADASTRIP utility. It can migrate mainframe ADABAS databases to ADABAS under UNIX, Linux or Windows, and can convert mainframe data to ASCII flat files, CSV files or normalised files suitable for RDBMS applications.

The utility can process mainframe files while extracting them to the required format, use comprehensive selection criteria to extract exactly the required data, and access raw mainframe historical data on a server platform. It can also be used to populate test databases and make application data available outside the original mainframe environment.

DBAUDIT scans a nominated ADASAV backup, avoiding any impact upon production databases, and applies user-supplied verification criteria. Its simple but powerful SQL-like command language allows a DBA or developer to specify verification rules without writing programs.

Output can be reports or files containing full details of database-integrity violations, together with optional control totals and counts. DBAUDIT provides a flexible and efficient way to search for application integrity issues and verify the logical relationships and contents of ADABAS data.

The display is divided into screens and pages, with one record per screen line. PF7/PF8 provide vertical navigation while PF9/PF10 reveal additional fields horizontally. This makes it possible to inspect data in virtually any sequence with only a keystroke or two, directly from the NATURAL Editor.

The PF6 detail screen shows all data from a single record, including PE and MU occurrences, and supports adding, modifying, copying and deleting records. PEEK gives developers and DBAs a direct, practical view of ADABAS file contents without the need to create a separate browsing program.

NIM establishes a new OS subtask for each user and allocates a unique address range in its virtual address space. Each user sub-task is independent and isolated from other users, while the system uses documented z/OS interfaces so it remains transportable through operating-system upgrades.

NIM uses only a minimum of activity between NATURAL, VTAM and ADABAS and does not need to run as an authorised program, although it can. Its DBA interface supports simple installation, minimum training, environment monitoring, system tuning and the potential to improve resource utilisation and response times.

For suitable environments, NIM can reduce resource overhead, minimise dedicated support requirements and provide a stable, low-maintenance system-management architecture.

ADABAS data may be modified by programs written in NATURAL, COBOL or other languages. Regardless of the program used, changes are automatically recorded on the ADABAS Protection Log, making it a reliable centralised source of information and an ideal input for AUDITRE.

AUDITRE supports extensive selection criteria so teams can retrieve changes for specific files, fields or time frames instead of reviewing millions of log records. It can produce summary reports showing adds, deletes and updates, as well as detail reports showing before-and-after values.

Output datasets can support reporting, analysis, update propagation and decision-making. Multiple reports and output datasets may be produced in a single pass, and AUDITRE does not require ADABAS to be active while the log is being processed.

The TRIM Real-Time Monitor provides hundreds of performance statistics online, showing ADABAS activity for recent time periods, session statistics, warnings about queue and table fill-up conditions, traces of performance problems and ADABAS calls by user, job and program, and database information.

TRIM includes Batch Slowdown to reduce the impact of prime-time batch runs on online response. Its Dynamic Control and Security facility can disallow inefficient commands, lock out file access, protect ADABAS passwords and perform security checks before performance problems occur.

TRIM also provides batch facilities for processing ADABAS Command and Protection Logs, assisting performance tuning, chargeback and capacity planning. Dynamic Logging reduces command-log volume by retaining only the detailed records or buffers a site actually needs.

N2O addresses the practical challenges of managing applications containing hundreds of objects changed by many programmers. It helps control migrations into production, avoid program overwrites, track the current location of a program, verify changes, change related objects, archive and recover content, and maintain complete audit trails.

N2O/3GL extends the workflow to non-NATURAL components such as ASSEMBLER, COBOL, FORTRAN, PL/I and RPG source, as well as JCL and other data types. It supports batch migration, check-out/check-in and audit trails for objects stored in partitioned datasets, PANVALET libraries, LIBRARIAN master files or ENDEVOR stages.

N2O follows a site’s repository and naming conventions, helping teams automate change-management tasks without abandoning the established development environment.