Natural Development Server Version 8.2.5 for z/VSE
 —  Natural Development Server for z/VSE (SMARTS/Com-plete)  —

Natural Development Server on Mainframes

This document describes the concept and the architecture of the Natural Development Server (product code NDV) which is designed for use under SMARTS or Com-plete on z/VSE.

In addition, an optional Natural Development Server CICS Adapter is available that enables Natural Development Servers for z/OS or SMARTS/VSE to be used with a CICS TP monitor.

The following topics are covered:

Development Server Concept

A Natural Development Server is a multi-user, multi-tasking application. It can host Natural sessions for multiple users and execute their requests concurrently.

The concept is based on the "serverized" Natural runtime system. Its architecture comprises a server front-end stub (development server stub NATRDEVS) that uses the Natural front-end to dispatch Natural sessions and to execute functionality within these sessions.

The Natural remote development server architecture basically consists of:

Top of page

Front-End Stub NATRDEVS

The multi-user, multi-tasking, front-end stub NATRDEVS is launched to initialize a Natural Development Server.

The following topics are covered below:

Stub Description

The task executing the server initialization (TMain) basically is the main listener which waits for incoming requests from the remote development client (Natural Studio). It owns a session directory to manage multiple clients (users) and their corresponding remote Natural sessions. TMain has the task to accept all incoming requests and to dispatch them to other subtasks (TWork). The process is as follows:

That is, each client owns one subtask TWork on the Natural Development Server and multiple remote Natural sessions (one for each mapped environment). This subtask remains active as long as the mapped environment on Natural Studio is the currently active environment. Each remote Natural session remains active until the user disconnects/unmaps the corresponding environment on the client side. Consequently, a Natural session can be executed under different subtasks if the user switches among multiple environments.

Natural System Variables Used

Within a Natural Development Server session, the following Natural system variables are used:

Natural I/O Handling

The Natural runtime system allows I/O execution in the same way as in an online environment:

Top of page


The Natural front-end required for a Natural Development Server is the Natural Com-plete driver NCFNUC that is delivered with the corresponding Natural Version for Mainframes.

The Natural front-end required for executing the Natural sessions under control of CICS is the Natural remote front-end NATCSRFE that is delivered with the Natural Development Server. For further information, refer to Introducing the Natural Development Server CICS Adapter in the Natural Development Server CICS Adapter documentation.

Top of page

Transaction Processors

The transaction processors are Natural programs in the library SYSLIB that process transactions (for example, "save source", "get library list") requested by the remote development client. The transaction processors are invoked by the front-end stub.

Top of page

Gateway Module

The gateway module NATGWSTG is already included in the Natural nucleus.

For CICS support, the Natural Development Server distribution medium in addition contains the remote gateway modules NATSRGND/NATLRGND. Theses modules are responsible for transmitting the NDV-relevant data between a Natural Development Server and the Natural session running in CICS.

For more information, refer to the Natural Development Server CICS Adapter documentation.

Top of page

Server Monitor

To enable the administrator to monitor the status of the Natural Development Server, a monitor task is provided which is initialized automatically at server startup. Using the monitor commands, the administrator can control the server activities, cancel particular user sessions, terminate the entire server, etc. See Operating the Development Server.

Top of page

Product Interaction

The following figure illustrates the interaction of Natural Studio used as a remote development client with a Natural Development Server.


  1. Natural Studio (the client) sends a remote development request to the Natural Development Server (NDV) using the port number specified with the NDV configuration parameter PORT_NUMBER.

  2. The Natural Development Server dispatches the Natural session using the Natural front-end you have specified with the NDV configuration parameter FRONTEND_NAME (NCFSERV in this example).

Top of page