Natural Development Server Version 8.2.5 for BS2000/OSD
 —  Natural Development Server for BS2000/OSD  —

Natural Development Server Frequently Asked Questions

This document contains frequently asked questions concerning the Natural Development Server (NDV) under SMARTS on BS2000/OSD.

The following topics are covered:

Natural Development Server starts and terminates immediately

At server initialization, the Natural Development Server

If one of these steps fails, the server will not be able to continue and will terminate immediately.

Analyze the trace output or the error output in the logical system file SYSOUT to find out the problem.

STGTRACE, STGSTDO, STGSTDE are synonyms for serveridE, serveridO and serveridT.

Top of page

Which dataset should I analyze to get error information?

SYSOUT The central logical system file SYSOUT of the FSIO task contains the error and trace output and the content of the configuration file.

Top of page

Trace output shows: Cannot load Natural front-end ...

The Natural front-end specified by the NDV configuration parameter FRONTEND_NAME was not found in the load library concatenation.

Top of page

Trace output shows: Transport initialization failed, EDC8115I address already in use

The TCP/IP port number specified by the NDV configuration parameter PORT_NUMBER is already in use by another process.

Top of page

Trace output shows: Error at: Template runtime connect

When a Natural Development Server initializes, it starts a Natural session using the session parameter(s) defined by the NDV configuration parameter SESSION_PARAMETER. The profile definition of the NDV configuration parameter DEFAULT_PROFILE is appended. If the initialization of the template session fails, the server terminates immediately. The original error can be found below the message Error at:Template runtime connect.

Typical error situations could be:

Top of page

Definitions required in Natural Security

Top of page

I do not get a NAT0954 even if I specify DU=OFF

SMARTS encountered an irrecoverable error and terminates a worker-task without recovery processing.

Top of page

Map Environment fails with a NAT3048

Specify session parameter ETID=' '. If you are using Natural Security, clear the ETID (Adabas User Identification) definition for that user.

Top of page

Map Environment fails with Stub RCnn

Stub return codes are raised by the NDV front-end stub, if it detects a logical processing error when dispatching the NDV request. The NDV trace output contains detailed information about the reason for the error.

The following stub return codes are possible:

Code Meaning, Reason, Action

Error during session reconnect (for future use).


Cannot create new session directory entry or subtask.

When Natural Studio executes a Map Environment command, the Natural Development Server allocates an entry in its session directory and creates a new subtask. If one of these actions fails, the Stub RC 2 is raised.

  • Maximum workload of parallel processes exceeded.


Increase the value of the SMARTS parameters WORKLOAD_MAXIMUM and/or WORKLOAD_AVERAGE.


Cannot initialize new session.

This error occurs if a storage allocation for internal NDV control buffers fails due to a lack of virtual memory above 16 MB.


Virtual memory above 16 MB too small.


Increase the virtual memory above 16 MB by increasing the value of the SMARTS parameter DATA_MAXIMUM, decrease the number of physical storage threads, distribute the clients to several Natural Development Servers.


Session execution failed.

Internal error. Natural Studio uses an invalid session identifier to process a request.

  • When a Map Environment command is issued, the session ID already exists.

  • The Natural session with the specified ID is not initialized.


Locate the defective session ID in the server trace file and cancel it using the monitor task, or restart your Natural Studio session.


I/O execution not allowed.

In some situations, a Natural I/O is prohibited at the Natural Development Server.

  • I/O execution during LOGON request.

  • I/O execution while a transaction processor is executing.


Locate the I/O buffer in the server trace file to find out which I/O should be processed. Check for any startup program specified for the library you want to logon to.

6 Not applicable.

Error during I/O execution.

The Natural Development Server cannot finish a terminal I/O.

  • Virtual memory above 16 MB too small.

  • I/O reply buffer sent by Natural Studio is invalid.


Increase the virtual memory above 16 MB by increasing the value of the SMARTS parameter DATA_MAXIMUM. If the I/O reply buffer is invalid, contact Software AG support.


Protocol element missing.

Internal error, contact Software AG support.


NDV not installed on Natural system file.

Natural Development Server cannot execute the Natural module TRPRO located on library SYSLIB.

  • The NDV modules were not loaded on the system file FNAT.


Use the Natural utility INPL to load the NDV modules.


LOGON command required.

If you execute a program on the Natural Development Server that executes a LOGOFF (or a RETURN when no SETUP record is available), the logon library is undefined.

In an online environment, the Natural Security logon screen is displayed in this situation. Under NDV, the Natural session rejects all requests except a LOGON command. This applies only if Natural Security is installed. You can issue a LOGON command either via the command line or by clicking on any library in your tree view.

Top of page

Special characters are not translated correctly

The ASCII-to-EBCDIC translation for NDV uses the Natural translation tables TABA1/TABA2. These tables are automatically or manually adapted at the customer's site.

Automatic Adaptation of Translation Tables

Automatic adaptation of the Natural translation tables TABA1/TABA2 takes place if the following Natural profile parameters are set:

For further information on possible settings, see the corresponding profile parameter descriptions in the Natural Parameter Reference documentation.

At session initialization (when you map to the NDV server) Natural automatically adapts its conversion tables TABA1/TABA2 according to the CP parameter definition and the code page used at the client. To verify if the conversion tables have been adapted, set NDV TRACE_LEVEL=31, connect to the NDV host via Natural Studio, and review the NDV trace file.

Each Map Environment starts with:

11 07:58:02 00000003 Got new connection

some lines down you find:

11 07:58:02 00000005 Client codepage: windows-1252
11 07:58:02 00000005 Client operation = 18

and again some lines down you find:

11 07:58:03 00000005 TABA1/TABA2 adapted according CP definitions

which indicates that the table has been adapted.

Manual Adaptation of Translation Tables

The translate tables can be modified as follows:

  1. Modify source member NTTABA1/NTTABA2 on the Natural distribution library. Reassemble NATCONFG and relink the Natural nucleus.

  2. Specify the Natural session parameter TABA1/TABA2.

Manual adaptation requires setting CP=OFF. It also requires that TERMINAL_EMULATION=WEBIO be off. As a result, you cannot use the statements REQUEST DOCUMENT and PARSE.

Automatic and manual adaptation are mutually exclusive. If the automatic adaptation is effective, any TABA1/TABA2 definitions are discarded. You can use either the automatic or the manual update but not a mix of both.

Do not use Natural Studio session parameters as an approach to permanently implementing these changes. You run the risk that different clients may use different translations, and this could corrupt source code the clients share. It is better to maintain the translation centrally. You can do this in two different ways:

  1. Maintain the Natural parameter module, or

  2. Use the NDV configuration parameter SESSION_PARAMETER.

    This affects the SPoD users only.

For NDV under BS2000/OSD, the translation tables have to be adapted as follows:


Position Value Character
E4 FB ä
F6 4F ö


Position Value Character
4F F6 ö
FB E4 ä

Top of page

Characters are not displayed correctly in the terminal emulation of Natural Studio

In Natural Studio, see also Tools / Options / Workspace / Terminal emulation setting in Natural Studio. The default (Latin) may not be the correct choice. For instance, in the US, you probably want to select "United States".

A simple Natural program on the mainframe can reveal the EBCDIC representation of a character which is not converting correctly:

#A(A1) = '{'

If none of the available code pages applies to your needs, it is possible to adapt one of the N3270_USER 3270 translation tables in the etc directory. Details are in the Natural for Windows product documentation.

The web-site is a good resource for finding valid EBCDIC and ASCII values for a given character (glyph) in various code pages.

Top of page

How do I find out which hexadecimal value must be specified for TABA1/TABA2?

Run the following program on your Natural for Windows locally.

#A(A1) = '{'

Output is 7B.

Run the program on a mainframe (edit the program with the Natural mainframe editor). Output is 75, assuming that you use a German EBCDIC table. If you use a US EBCDIC table, the output will be C0.

Start your Natural Development Server session with TABA1=(75,7B) and TABA2=(7B,75).

Top of page

The modifications of TABA1/TABA2 do not apply to sources listed in the remote debugger

Specify the NDV configuration parameter DBG_CODEPAGE=USER.

Top of page

Are there any Natural profile parameter settings required for NDV?

The following Natural profile parameter values are required for NDV:

Top of page

NAT9915 GETMAIN for thread storage failed

The Natural front-end cannot allocate the Natural thread. Increase the SMARTS SYSPARM parameter THSIZEABOVE.

Top of page

The NDV server consumes a lot of CPU time even if only a few clients are using it

If you run your NDV server without a CPU time limit on session level, a Natural program might run into an endless loop. Issue a server command list sessions and examine whether any of the listed sessions has the status code "IO" (under the column header St. in the list output). The character I means that the client owns an initialized session, and the O flags mean that the client occupies a thread and is currently executing.

If a second list sessions command results in an "IO" for the same client with an unaltered Last Activity, it is probably a stuck or looping client. You can try to cancel the session using a CANCEL SESSION server command. If the cancelation fails, a restart of the NDV server is required.

If the list sessions function does not show a stuck or looping client, cancel the NDV server by using the DUMP option, and consult Software AG support.

Top of page