NOMAD Teradata Interface

The NOMAD Interface for Teradata provides the full functionality of NOMAD for application development and end-user computing to maximize your investment in the Teradata DBC/1012 and NCR 5100.

Offers full functionality for application development and reporting with NOMAD and Teradata databases.

Designed for optimum efficiency with the Teradata engine.

Provides additional relational features not found in the DBC/1012.

Simplifies data loading and editing with automated commands.

The NOMAD Interface for Teradata is a solution to the problems associated with managing very large shared databases, coupled with the benefits of a fourth-generation language for end-user access and application development. The Teradata DBC/1012 machine provides the power to manage trillion-byte databases by harnessing the cost-effective power of microprocessors. This approach achieves the performance levels required to support concurrent end users and production systems activity.

Users quickly benefit from NOMAD's complete non-procedural language for fast prototyping, its built-in decision-support functions and its fully integrated programming language with functionality comparable to PL/I and COBOL. In addition, the product offers an array of tools and templates for quickly generating report requests, forms, menus and maintenance procedures.

Features of the NOMAD Interface for Teradata

Read/write access to data stored in the DBC/1012 or NCR 5100 system.

Database-sharing across hosts and operating systems. Users running on the VM/CMS and MVS environments can access the same NOMAD database residing on the Teradata machine. Since all of the NOMAD facilities for reporting and maintenance are available, the end user does not need to know where the data actually resides.

Efficient handling of very large shared database applications. All concurrency and data sharing is done by the Teradata Machine. There is no need to use NOMAD's shared database facility for data stored on the Teradata Machine.

Fault tolerance. All hardware, software, power supply and data files (optionally) are intentionally duplicated to provide a reliable, fail-safe environment. To provide data duplication the user only need specify FALLBACK on the MASTER statement.

Integration with the Teradata Engine

The NOMAD Interface for Teradata translates NOMAD commands into DBC/SQL statements sending as much of the work as possible to the Teradata Machine. Sorting and aggregation triggered by NOMAD's LIST command for reporting are performed on the Teradata Machine, with only the requested information shipped back to NOMAD.

The NOMAD Interface for Teradata supports the use of the DBC/SQL LONG VARCHAR data type, enabling you to maintain, manipulate and report long strings of textual data.

NOMAD's Interface handles requests to the Teradata Machine using the following techniques:


Only needed columns (data fields) are requested for processing.


All of NOMAD's reporting functions (except MEDIAN) are passed, in addition to the five basic SQL functions of MIN, MAX, SUM, AVG and COUNT.


Data is requested in the proper sorted sequence; ascending or descending.

Selective Data Listing

Selective Data Listing: NOMAD's LOCATE and LIST WHERE commands are passed. SELECT expressions containing boolean expressions, as well as AMONG and CONTAINS are also passed. DATE data items are also passed to the DBC/1012, a very useful feature for users accessing time-series data.

Data Maintenance

Global data maintenance is performed by sending set calls for CHANGE and DELETE as a single transaction, rather than processing a single record at a time. NOMAD performs global data maintenance through single commands such as CHANGE WITHIN DATABASE, DELETE WITHIN DATABASE and CHANGE WHERE, while other fourth-generation languages typically require dozens of lines of code to perform the same processing.

Relational Enhancements

The NOMAD Interface for Teradata extends DBC/SQL's handling of the relational model by providing:

Complete Outer Join Support NOMAD's MERGE MATCHING for outer joins and EXTRACT ALL MATCHING for left-hand outer joins provide this support with no limit on the number of tables that can be joined. Further, any two tables can be joined on any two columns - predefined indexes are not necessary.

Complete Referential Integrity Support User-defined compensating actions such as cascading deletes and updates are defined through RULEs in the central Schema, NOMAD's data-definition facility. The RULEs also determine whether or not user approval is requested before the action takes place. The MEMBER designation on an item limits the assignment of a value to only those found in the specified master.

Null Support NOMAD supports null values by handling missing values in a column differently from values of zeros or blanks. Nulls are disallowed for any item by specifying NOTNAV in the Schema. Additionally, NOMAD always disallows nulls for primary keys.

Extended Data Type Support NOMAD has additional data types for time, datetime, fixed and varying arrays, and time-series data.

Using the NOMAD Interface for Teradata

Accessing the Data

With the NOMAD Interface for Teradata a database can include not only data stored in Teradata but data stored in DB2 and SQL tables, NOMAD's native relational database and in external files such as ISAM, VSAM and QSAM. (With additional NOMAD interfaces, it can also include data in other DBMSs.)

The TYPE parameter on the MASTER statement indicates how data is stored. Teradata tables can be maintained using all of NOMAD's navigation and maintenance commands. Data stored in multiple files can be drawn together using NOMAD's relational facilities such as DEFINE EXTRACT and MERGE MATCHING.

NOMAD reporting and file creation work exactly as if the data were stored in NOMAD. NOMAD retains its concept of position, despite the fact that Teradata does not support such a concept. Thus, you have the ability to move backward and forward through the data.

Moving the Data

Moving data from a NOMAD database to Teradata is accomplished simply by adding the TYPE TERADATA parameter to the Schema (NOMAD's data-definition facility), and issuing the SCHEMA REORG command. There is no need to worry about dumping and reloading data. The NOMAD Interface for Teradata does the work of creating a new table on the Teradata Machine for you.

Using the Data

To use NOMAD with existing Teradata tables, you use SCHEMGEN, a menu-assisted Schema generator, which produces a basic NOMAD Schema from selected tables. This Schema can be edited to take advantage of NOMAD's extensive data-definition language to add headings, masks, limits, member checks, defined items, passwords and multiple data types. In addition to fixed and varying arrays and time series, NOMAD data types include DATE, TIME, DATETIME and TEXT. Additional display formats include NAME, FORMAT and PICTURE. After the Schema is compiled, all of NOMAD's command language is available for application development, reporting and analysis.

NOMAD for Application Development and Reporting

View features in application development and reporting. Additional features for Teradata:

Database Loading

The Teradata FASTLOAD utility is a powerful tool for inserting large volumes of clean data into DBC/SQL tables. However, if your data needs to be verified first, or if you are also changing or deleting rows, NOMAD's LOAD command easily loads the data into the DBC/1012 system.

DBC/SQL Commands

All commands are issued within NOMAD's single environment. DBC/SQL commands can be issued interactively by prefacing them with "TQL."

Supported Environments

NOMAD facilities look and function consistently in all its environments, which include:




Interactive System Productivity Facility (ISPF)

MVS Batch Facility (Native or TSO Batch)

NOMAD MVS Session Manager (for access via TSO, CICS or VTAM)

Learn More
To find out more about how Select Business Solutions can help you either Contact Us, or visit our Product Resources area for all the latest related downloads.


NOMAD (1.2mb)

NOMAD Reporting

NOMAD Interface for DB2

NOMAD Interface for VSAM

Useful Links

IBM Mainframe servers