NOMAD Modernization Guide
NOMAD is a report generation and management product by Select Business Solutions. Explore technical details, modernization strategies, and migration paths below.
Product Overview
NOMAD is a reporting language and application development tool designed to access data from legacy systems such as VSAM, DB2, and IMS.
The NSM/CICS component provides a CICS interface.
Modernization Strategies
Rehost
- Timeline:
- 6-12 months
Lift-and-shift to cloud infrastructure with minimal code changes. Fast migration with lower risk.
Refactor (Recommended)
- Timeline:
- 18-24 months
Optimize application architecture for cloud while preserving business logic. Best ROI long-term.
Replatform
- Timeline:
- 3-5 years
Complete rewrite to cloud-native architecture with microservices and modern tech stack.
Frequently Asked Questions
General
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.
Technical
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.
Business Value
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.
Security
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.
Operations
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.
Ready to Start Your Migration?
Download our comprehensive migration guide for NOMAD or calculate your ROI.