Operating the Natural Development Server

This document describes how to operate a Natural Development Server in a SMARTS on BS2000 environment.

The following topics are covered:

• Starting the Natural Development Server

• Terminating the Natural Development Server

• Changing the SYSOUT File Assignment of the FSIO Task

• Monitoring the Natural Development Server

• Runtime Trace Facility

• Trace Filter

• Support of NATRJE Functionality

Starting the Natural Development Server

Start the Natural Development Server with the SDF command:

/Enter-Proc *LIB(NDVvrs.JOBS,START-NDV)

The SDF procedure START-NDV has to be supplied with the following parameters:

For the currently applicable versions refer to Empower https://empower.softwareag.com/.

Caution:
Do not modify the variable names and parameter names that are used in the procedure START_NDV. This procedure is called recursively to attach the worker-tasks. For this purpose, the ENTERPARM string is internally executed and several variables are read from the system, using the GETVAR function of SDF-P.

Terminating the Natural Development Server

The Natural Development Server can be terminated with the console command:

/INTR <TSN smarts-main-task>,EOJ

Changing the SYSOUT File Assignment of the FSIO Task

The central logical system file SYSOUT written by the FSIO task can be reassigned at SMARTS server execution time, using the SDF procedure SHOW-SYSOUT.

Thus it is possible to look up trace outputs, error reports, etc., without having to terminate the server.

The procedure SHOW-SYSOUT has to be called with the following parameters:

As a result of the SHOW-SYSOUT execution, the logical system file SYSOUT of the FSIO task will be reassigned to a new file and the previous one will be opened with the SHOW-FILE command. The new logical system file SYSOUT is built by appending a numerical suffix to the file name. The value of the suffix is incremented by 1, each time SHOW-SYSOUT is executed.

Example:

/Call-Proc *LIB(NDVvrs.JOBS,SHOW-SYSOUT), <SMARTS-tsn>

where SMARTS-tsn is the TSN of your SMARTS main task.

Monitoring the Natural Development Server

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 described below, the administrator can control the server activities, cancel particular user sessions, terminate the entire server, etc.

The following topics are covered below:

• Monitor Communication

• Monitor Commands

Monitor Communication

To communicate with the monitor, you can use the monitor client NATMOPI; see Monitor Client NATMOPI. Or you can use the HTML Monitor Client that supports standard web browser; see HTML Monitor Client.

Monitor Commands

The Natural Development Server supports the following monitor commands:

I'm still up

set TRACE_LEVEL 0x00000012

Runtime Trace Facility

For debugging purposes, the server code has a built-in trace facility which can be switched on, if desired.

The following topics are covered below:

• Trace Medium

• Trace Configuration

• Trace Level

Trace Medium

A remote development server writes its runtime trace to the logical system file SYSOUT of the FSIO task.

Trace Configuration

The trace is configured by a trace level which defines the details of the trace. Once a trace is switched on, it can be restricted to particular clients or client requests by specifying a trace filter, see also NDV configuration parameter TRACE_FILTER.

Every Natural session is provided with a 32-bit trace status word (TSW) which defines the trace level for this session. The value of the TSW is set in the NDV configuration parameter TRACE_LEVEL. A value of zero means that the trace is switched off.

Trace Level

Each bit of the TSW is responsible for certain trace information. Starting with the rightmost bit:

Trace Filter

It is possible to restrict the trace by a logical filter in order to reduce the volume of the server trace output.

• The filter can be set with the configuration parameter TRACE_FILTER.

• The filter may consist of multiple keyword=filtervalue assignments separated by spaces.

• To activate the filter definition, the trace bit 14 in the trace status word (see Trace Level) must be set.

The filter keyword is:

The following rules apply:

• If a keyword is defined multiple times, the values are cumulated.

• The value must be enclosed in braces and can be a list of filter values separated by spaces.

• The values are not case sensitive.

• Asterisk notation is possible.

Example:

TRACE_FILTER="Client=(KSP P*)"

Each request of the user ID KSP and each request of the user IDs starting with a P are traced.

Support of NATRJE Functionality

Calls to the NATRJE utility (Natural Remote Job Entry) are supported. For technical reasons, however, the file name of the job to be submitted is created in a way which is different from batch operation in a TIAM or openUTM environment. The file name has the following structure:

E.DDMMYYYY.XXXXXXXX.program-name.terminal-id

Where: