Technical Specifications
  Operating System Version Support
NOMAD is supported when installed with any currently supported versions of VM/ESA.
Communication between virtual machines is handled via IUCV. NOMAD uses the documented IUCV interface including CMSIUCV so TSAF works between systems. NOMAD can be converted to use VMCF by changing one installation option and re-installing. No application level code needs to change.
Disk Storage
Since NOMAD uses standard CMS MACROs and functions to perform disk I/O, NOMAD supports all disk that CMS supports. Database blocksizes are determined by the disk blocksize. However, NOMAD I/O can be optimized by specifying how many blocks are read at one time and/or by specifying the logical blocksize. In XA and XC virtual machines, most I/O is done above 16M.
Virtual Machine Storage
NOMAD requires a minimum of a 1 megabyte virtual machine. It will use as much storage as needed and is available within the virtual machine. A run-time option is available to reserve storage for CMS or called application use. In addition to the virtual machine storage, an installation can choose to set up special "expansion" segments that are attached in exclusive writable mode as NOMAD needs additional storage. This allows normally small virtual machines to obtain additional storage only when needed. Any attached "expansion" segments are detached upon exit from NOMAD.
Memory Usage
NOMAD uses storage above the 16 megabyte line when it is available. This can be virtual machine storage or "expansion" segments as described above. The NOMAD shared segment can be either above the 16 megabyte line or below. If below, NOMAD dynamically decides whether it is running in a 370 virtual machine or an XA virtual machine.
Foreign Language Support
NOMAD "knows" certain different foreign languages and provides error messages, date formats and number formats as appropriate. The installation can choose to install any or all of the languages, and can choose to have them available in the shared segment or on a shared disk.
NOMAD allows several different levels of security. System profiles, database profiles and user profiles enable restriction of NOMAD commands and data access. Database passwords are provided to allow additional security. System profiles and database profiles can be scrambled or pre-scanned. If desired, the disk containing the system profile will be dynamically linked and accessed by NOMAD before the user ever gets a chance to execute anything. After use, the system profile disk can optionally be detached by NOMAD. User exits are available for database access to provide additional security.
Optimal Resource Utilization
NOMAD was specifically developed to run in the virtual machine environment. It is written in Assembler and C, and is completely re-entrant. Furthermore, NOMAD takes advantage of VM's Extended Architecture operating system and runs in exploitation mode, above the 16 megabyte line, with most temporary storage obtained above the line. In addition, NOMAD is fully tested and operable in the VM/ESA environment.
Since NOMAD was designed from the beginning as a user-level interface, it requires no operating system modifications for either CP or CMS. It has one optional module that runs in a separate, privileged virtual machine to allow automatic logon of shared database servers and to provide access to the system account information for applications.
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