Installing Natural Single Point of Development

This document summarizes the prerequisites and the installation steps that are necessary to create a Natural Single Point of Development environment that uses NaturalONE or Natural Studio as a development client and Natural Development Server running under the operating system z/OS (Batch or Com-plete), z/VSE, BS2000, Windows, UNIX or OpenVMS as a remote development server.

This document covers the following topics:

Prerequisites

Products Required or Involved

When using the Natural for Windows (Natural Studio) development client, see Prerequisites for Natural Single Point of Development at http://documentation.softwareag.com/natural/spod_prereq/prereq.htm (Empower login required) for detailed information on the supported products.

When using NaturalONE as the development client, see your NaturalONE documentation for detailed information on the supported products.

Technical Requirements

A wide-area network (WAN) environment is required with a minimum transmission rate of 100 Mbit or higher.

Installation Procedure

Installing the products that make up Natural Single Point of Development comprises the following general installation steps (as applicable):

Installing NaturalONE

Refer to the Installation documentation for NaturalONE.

Installing Natural for Windows (Natural Studio)

Refer to the Installation documentation for Natural for Windows.

Installing Natural for Mainframes

Refer to the relevant installation documentation for Natural for Mainframes:

  • Installation for z/OS

  • Installation for BS2000

  • Installation for z/VSE

For background information on the automated installation of Software AG products, see also Concepts of System Maintenance Aid in the System Maintenance Aid documentation.

Installing Natural for UNIX

Refer to the Installation documentation for Natural for UNIX.

Installing Natural for OpenVMS

Refer to the Installation documentation for Natural for OpenVMS.

Installing the Natural Development Server

Refer to the relevant section of the Natural Development Server installation instructions:

  • Installing the Natural Development Server on z/OS (Batch) and,

    • if CICS is used as TP monitor, Installing the Natural Development Server CICS Adapter

    • if IMS TM is used as TP monitor, Installing the Natural Development Server IMS Adapter

  • Installing the Natural Development Server on z/OS (Com-plete)

  • Installing the Natural Development Server under SMARTS on z/VSE and, if CICS is used as TP monitor, Installing the Natural Development Server CICS Adapter

  • Installing the Natural Development Server under SMARTS on BS2000

  • Installing the Natural Development Server under Windows

  • Installing the Natural Development Server under UNIX

  • Installing the Natural Development Server under OpenVMS

Defining a Natural Development Server File

The Natural Development Server File (FDIC) is used as a central dictionary file for storing Natural applications and the links to objects making up an application. It also holds object locking information. This information is not bound to certain groups of application developers, but has an impact on the entire application development of an enterprise. Therefore, this file should be available only once, to ensure that the application definitions and locking states are kept consistent.

The following information applies to mainframe environments only:

Start of instruction set To ensure the use of one single Natural development file

  1. Set the NTDYNP parameter in the default Natural parameter file NATPARM to OFF:

    • Specify NTDYNP OFF, if you want to disallow overwriting of all dynamic parameters

    • or specify NTDYNP OFF,FDIC, if you want to disallow overwriting of the Natural development server file only.

  2. Disallow any changes to profiles by the end user.