What infrastructure is required?

NOMAD requires a mainframe environment running z/OS or z/VM. It also requires access to the data sources it will be reporting on, such as VSAM, DB2, IMS, Oracle, or SQL Server. The NOMAD Session Manager (NSM) can operate outside of TSO.

For mainframe products: Does this run in an LPAR?

NOMAD runs on z/OS and z/VM mainframe operating systems. It can run in an LPAR (Logical Partition) and may require specific subsystems depending on the data sources being accessed.

How do users interact with NOMAD?

NOMAD uses a command-driven interface. Common operations include defining data sources, writing reports, and executing queries. The syntax involves specifying data elements, selection criteria, and output formats.

How does NOMAD integrate with other systems?

NOMAD provides a JDBC interface for accessing relational databases. It also supports integration with CICS through the NSM/CICS component. The specific APIs and integration methods depend on the version and configuration of NOMAD.

What is the business value of using NOMAD?

NOMAD allows organizations to leverage their existing mainframe investments by providing a reporting and application development environment for legacy data. It can reduce the need to migrate data to newer systems, saving time and resources.

How does NOMAD improve data management?

By providing a single environment for accessing both legacy and relational data, NOMAD can improve data consistency and reduce data silos. This can lead to better decision-making and improved business insights.

How does NOMAD improve application performance?

NOMAD's performance optimization features, such as NOMAD One Pass, can improve the efficiency of applications and reduce resource consumption. This can lead to cost savings and improved system performance.

How does NOMAD handle security?

NOMAD's security features depend on the underlying mainframe security system, such as RACF or ACF2. It leverages these systems for authentication and access control.

What access control model is used?

NOMAD uses the access control mechanisms provided by the mainframe operating system to control access to data and resources. This includes defining user roles and permissions.

What audit/logging capabilities exist?

NOMAD's audit and logging capabilities depend on the configuration of the mainframe environment. It can generate logs of user activity and system events, which can be used for security monitoring and auditing.

What ongoing operational requirements exist?

NOMAD requires ongoing monitoring and maintenance to ensure optimal performance and availability. This includes monitoring system resources, applying patches, and managing user accounts.

What level of technical expertise is required to implement it?

Implementing NOMAD requires technical expertise in mainframe systems, data access methods, and reporting techniques. It also requires knowledge of the data sources being accessed, such as VSAM, DB2, and IMS.

What are common implementation challenges?

Common implementation challenges include configuring data access, optimizing performance, and integrating with existing security systems. It is important to plan the implementation carefully and involve experienced personnel.

Are You a Vendor? Claim Your Listing

Take control of your product listings. Add verified information, showcase updates, and unlock a Claimed Vendor badge across the directory.

Claim Your Listing Now

NOMAD

Name: NOMAD
Availability: InStock

Select Business Solutions Active z/OS z/VM

Report Generation and Management Programming Language Databases

Vendor

Select Business Solutions

Product Overview

NOMAD is a reporting language and application development tool designed to access data from legacy systems such as VSAM, DB2, and IMS, as well as relational databases like Oracle and SQL Server via JDBC. Its architecture comprises several key components: 1. **NOMAD Language Engine:** The core component that interprets and executes NOMAD code.

It handles data access, manipulation, and reporting logic. 2. **Data Source Adapters:** These components provide connectivity to various data sources, including VSAM, DB2, IMS, Oracle, and SQL Server.

The JDBC interface is a key adapter for relational databases. 3. **NOMAD Session Manager (NSM):** This component allows multiple NOMAD applications and users to operate in a single address space outside of TSO, improving performance and resource utilization.

NSM/CICS provides a CICS interface. 4. **NOMAD Application Performance Analyzer:** This tool monitors the resources used by NOMAD applications, helping to identify performance bottlenecks and optimize code.

5. **NOMAD One Pass:** A performance optimizer that improves the efficiency of data access and processing. These components communicate through internal APIs and protocols.

Data access typically involves the Data Source Adapters retrieving data from the underlying data sources, which is then processed by the NOMAD Language Engine. The NSM manages sessions and resource allocation. Security is handled by the underlying mainframe security system, such as RACF or ACF2.

NOMAD leverages these systems for authentication and access control.

Frequently Asked Questions

What does NOMAD do?

NOMAD is a reporting language and application development tool designed to access data from legacy systems like VSAM, DB2, and IMS. It also provides a JDBC interface for connecting to relational databases such as Oracle and SQL Server.

Is this a system, application, or tool?

NOMAD is a combination of a programming language, a report generation tool, and a database access system. It provides tools and utilities for application development, performance optimization, and session management.

What types of organizations use this?

Organizations that rely on mainframe systems and legacy data sources, such as VSAM, DB2, and IMS, can benefit from NOMAD. These organizations are often in industries like banking, insurance, and government.

When should we consider NOMAD?

A company should consider using NOMAD when they need to access and report on data stored in legacy systems alongside relational databases. It is useful for organizations that want to leverage their existing mainframe infrastructure while integrating with newer database technologies.

What are the alternatives to NOMAD?

Alternatives to NOMAD include other reporting languages and data access tools such as SAS, FOCUS, RAMIS, and Easytrieve. These tools also provide data extraction, transformation, and reporting capabilities.

Help Improve This Directory

Notice outdated information? Have insights about this product? Help the mainframe community stay informed with accurate, current data.

Report Issue Suggest Product Share Event

Share Your Product Experience

Help the community by sharing your experience with mainframe products. Your insights help others make informed decisions.

Share Your Experience

Are You a Vendor? Claim Your Listing

NOMAD

Product Overview

Frequently Asked Questions

What does NOMAD do?

Is this a system, application, or tool?

What types of organizations use this?

When should we consider NOMAD?

What are the alternatives to NOMAD?

What infrastructure is required?

For mainframe products: Does this run in an LPAR?

How do users interact with NOMAD?

How does NOMAD integrate with other systems?

What is the business value of using NOMAD?

How does NOMAD improve data management?

How does NOMAD improve application performance?

How does NOMAD handle security?

What access control model is used?

What audit/logging capabilities exist?

What ongoing operational requirements exist?

What level of technical expertise is required to implement it?

What are common implementation challenges?

Related Products

More from Select Business Solutions

Ultraquest Applications

Ultraquest Library

Ultraquest Reporter

Ultraquest Web Services

Similar Products

_beta access audit

_beta doc|z plus

_beta doc|z transform

$avers

AcceleREXX

Access Manager for CICS

Help Improve This Directory

Share Your Product Experience