Version 6.3.13 for Windows
 —  Release Notes for Natural Version 6.3 for Windows  —

Release Information for Natural Version 6.3.13

This document covers the following topics:


New Features

Parameters

The following new Natural parameter is provided in this version:

Parameter Description
DBGAT This Natural profile parameter is intended for use with NaturalONE. It can be used to activate the debug attach mechanism of NaturalONE, to define the name and port of the debug attach server, and to define a client ID which identifies the NaturalONE project to be debugged.

System Variables

The following new Natural system variable is provided in this version:

System Variable Description
*REINPUT-TYPE Indicates whether the application is in a state allowing to execute a REINPUT or PROCESS PAGE UPDATE statement.

Top of page

Changes and Enhancements

Local Versioning

Local Versioning now supports the new library structure of a Subversion 1.7 workspace. Note, that a workspace with the old library structure has either to be upgraded using the svn upgrade command of version 1.7, or that you have to create a new workspace by checking out the repository with Subversion 1.7. If you use the Subversion client svn.exe in version 1.7 and workspace still has the old Subversion format (or if you are using an older client and the workspace already has the new format), the Local Versioning commands will be disabled.

See also Local Versioning in the Natural Studio Extensions documentation.

Configuration Utility

The new profile parameter DBGAT can be specified. See Debug Attach Settings in the Configuration Utility documentation.

SYSEXT Utility

Enhanced USR* Text Objects

The USRnnnnT text objects have been enhanced:

New List of Natural APIs in the Documentation

The documentation for the SYSEXT utility now contains the new section List of Natural APIs.

For further information, see SYSEXT Utility in the Tools and Utilities documentation.

Natural Web I/O Interface Client

The Natural Web I/O Interface client is now delivered in the Version 1.3.11. This version now also supports Google Chrome.

Note:
The Google Chrome support is based on Google Chrome Version 19. Due to frequent version upgrades of Google Chrome, compatibility of the Natural Web I/O Interface client Version 1.3.11 with future versions of Google Chrome cannot be fully guaranteed. Possible incompatibilities will be removed during the regular maintenance process of the Natural Web I/O Interface client.

The following keys can now be simulated for all platforms (see also Differences between the Natural Web I/O Interface Client and Terminal Emulation in the Natural Web I/O Interface documentation):

As of this version, Microsoft Internet Information Services (IIS) is no longer supported. All information on how to install and configure IIS has been removed from the Natural Web I/O Interface documentation.

If you are currently using the Natural Web I/O Interface client on IIS, you have to move to another supported server platform. This may be JBoss Application Server, Oracle GlassFish Server or Apache Tomcat. The most simple solution is to migrate the Natural Web I/O Interface client from IIS to Apache Tomcat. For detailed information, see Migrating the Natural Web I/O Interface Client from IIS to Apache Tomcat in the Natural Web I/O Interface documentation.

Top of page

Natural Remote Procedure Call (RPC)

Natural Remote Procedure Call (RPC) is available as a separate subcomponent of Natural. It has its own version number. This measure takes into account that Natural RPC is a cross-platform component and makes it possible to provide new Natural RPC versions independent of new Natural versions for the various platforms supported.

With Natural Version 6.3.13, an enhanced Natural Remote Procedure Call Version 6.3.4.6 is delivered that replaces the existing Natural RPC Version 6.3.4.5.

The following changes and enhancements are available.

NATRPC99 Used for All Normal Server Terminations

The Natural RPC server termination exit NATRPC99 is now called for all kinds of normal Natural RPC server terminations. It is not called in the case of abnormal terminations. See also User Exit NATRPC99 in the Natural Remote Procedure Call (RPC) documentation.

Top of page

Natural Security

The following enhancements are provided with Natural Security Version 6.3.13:

Administrator Services - Authentication Options

The Administrator Services subsystem of Natural Security provides a new function Authentication Options (invoked with function code "B" on the Administrator Services Menu 1). It is used to define security profiles for IAF servers and LDAP (see below). The functionality for the definition of IAF server profiles, which with previous versions used to be invoked with PF10 on the Administrator Services > General Options screen, has also been incorporated in this new function.

Administrator Services - Logon Records

The Administrator Services function Logon Records has been enhanced to facilitate the page-by-page deletion of logon records as performed by the functions Delete Logon Records and Delete Logon Records But Last. Instead of invoking these functions from the Logon Records Menu with ENTER, you can invoke them with PF4 (Del+): Pressing PF4 on the logon records list itself will then delete the current page of logon records and immediately scroll to the next page, without your having to press PF8. This reduction of keystrokes will be helpful when you delete a large number of logon records.

Library Profiles - Statement Restrictions

The Statement Restrictions section of library security profiles has been revised and the layout of the corresponding screen has been made more consistent. In addition, it is now possible to allow or disallow individual clauses of the PROCESS statement.

Utility Profiles - NATLOAD, NATUNLD and SYSTRANS

This is the last Natural Security version to support utility profiles for the obsolete Natural utilities NATLOAD, NATUNLD and SYSTRANS. These utilities are no longer supported. Their utility profiles have continued to be available for compatibility reasons only. If you still have utility profiles for these utilities, you have to convert them into corresponding SYSOBJH utility profiles before the next release of Natural Security. For detailed instructions, see Conversion of Utility Profiles in the Natural Security documentation.

Support for LDAP

It is now possible to perform user authentication via an LDAP server (that is, a server which uses the Light Directory Authentication Protocol) instead of via Natural Security itself. This is possible for online and batch sessions which are started with the Natural profile parameter AUTO=OFF being set. To define the LDAP to Natural Security, you use the new function Authentication Options (see above). For more information, see Authentication Options in the Natural Security documentation.

For the use with the authentication type LDAP, a new logon-related user exit routine LOGONSX1 is provided which is invoked instead of LOGONEX1. In conjunction with this user exit routine, a different logon screen is also available. For more information, see the following sections in the Natural Security documentation:

Top of page

Documentation

Event-Driven Programming Techniques

It is now documented that the names of the alphanumeric attributes can be suffixed with a "-U" to support characters that are not available in the active code page. See Attributes in the Dialog Component Reference.

In addition, the section How To Manipulate Dialog Elements in the Programming Guide has been expanded to cover Unicode support for dialog and dialog component attributes. See Querying and Modifying Unicode Attribute Values.

Top of page

Notice of Future Changes

The following changes are planned for future versions of Natural.

Natural Buffer Pool

With a future version of Natural, the maximum size of a Natural buffer pool will be increased from 512 MB to 1024 MB, and the maximum number of directory entries will be increased from 51200 to 102400.

Natural Development Server

The file NDVSERVER.LOG (located in ..\Software AG\Natural\<version>\Prof), which is used to terminate the started Natural development servers, will be renamed to NDVSERVER.PRU. Existing entries inside the NDVSERVER.LOG file will not be migrated to NDVSERVER.PRU.

Top of page