This document covers the following topics:
We would like to inform you that, after a detailed analysis & assessment, Software AG has decided to adjust its strategy regarding the Legacy-Unix platforms HP-UX®, AIX® and Solaris®. With many of our customers already departed from or soon planning to depart their Legacy-Unix platforms due to cost and technical reasons, Software AG has decided Linux x86 will be its strategic open systems platform for Adabas & Natural 2050+ going forward. This will allow Software AG to focus more resources on this platform and maximize the overall value to our customer base.
The end-of-maintenance date (EOM) for Software AG support of the Legacy-Unix platforms is December 31, 2024. For the period from December 31, 2024 to December 31, 2025 Software AG will offer options for non-standard sustained support on the Legacy-Unix platforms for customers who are unable to rehost by the regular EOM date. Both dates apply to all Software AG A&N products (excluding CONNX, which will still be available on Legacy-Unix).
This will provide you sufficient time to rehost your Software AG applications from the Legacy-Unix platform to your preferred Linux x86 platform(s). Software AG recommends one of the following rehosting options:
RedHat Enterprise Linux®
SUSE Linux Enterprise
Please be assured that Software AG is prepared to offer assistance in planning and executing your rehosting from the Legacy-Unix platform to an alternative platform.
Following the principles of our "A&N 2050+ Initiative", your rehosting project will be a high priority to Software AG. Our local Software AG teams will be happy to discuss any rehosting topic with you.
If you have any questions regarding the Adabas & Natural platform roadmap, please do not hesitate to contact Adabas & Natural Product Management (e-mail: AskANProdMgt@softwareag.com).
For the Adabas & Natural products on the Legacy-Unix platforms HP-UX®, AIX® and Solaris® we currently plan the following final versions:
| Final Version (GA) | EOM | EOSS | |
|---|---|---|---|
| Adabas HP-UX® | 6.7.0, October 2018 | 31.12.2024 | 31.12.2025 |
| Adabas AIX® and Solaris® | 7.0, October 2020 | 31.12.2024 | 31.12.2025 |
| Natural HP-UX® | 9.1.1, October 2018 | 31.12.2024 | 31.12.2025 |
| Natural AIX® and Solaris® | 9.1.3, April 2021 | 31.12.2024 | 31.12.2025 |
The read/write buffer pool can now be used on its own in performance-critical environments.
For details about the buffer pool with enhanced performance, see Operations > Natural Buffer Pool > Buffer Pool with Enhanced Performance.
The new application programming interface NSCSSXMN allows you to archive and revive LDAP security profiles.
For details, see Natural Security > Application Programming Interfaces.
You can now start the debug attach server with SSL/TLS security. You can configure the
SSL/TLS security with the DBGAT parameter.
For more information about debugging an external Natural application with NaturalONE, see Parameter Reference > DBGAT - Debug Attach Server for NaturalONE.
For detailed information on how to debug external Natural applications, see the NaturalONE documentation.
The following Natural application programming interfaces (APIs) are new in the
SYSEXT system library:
| API | Task | Enhancement |
|---|---|---|
USR2071N |
Support EntireX Security on client side |
The example program |
When a parameter provided in an INPUT USING MAP, CALLNAT,
or PERFORM external subroutine does not correspond to a parameter in the
called object, an error with the position number of the parameter in error shows.
The error text now also includes the field name of the parameter variable. The
variable name is only available at compile time when the PCHECK compiler
option is set to ON. If the external subroutine is received at runtime,
the error text does not include the field name.
This change affects the first insert position in the following error messages: NAT0936, NAT0937, NAT0938, NAT0648, NAT0965, NAT0966, NAT0969.
The Natural compiler has been improved to generate an internal hash signature for Natural objects instead of the former timestamp value. The hash signature is generated based on the Natural object structure and remains the same for Natural objects of the same structure whenever compiled.
With this enhancement, the GDA's signature remains the same throughout multiple compiles, provided no structural changes were done in a GDA. As a result, Natural objects using GDA's only need to be re-compiled if there is a change in GDA signature due to a GDA structure change.
The new behavior is more consistent with the documented behavior and has the advantage for developers that fewer object compilations are required. This change also results in error message "NAT0925: GDA signature conflict" being returned, instead of "NAT0933: GDA time-stamp conflict."
The Natural compiler has been improved to also display mismatching field names of a MOVE BY NAME or MOVE BY POSITION statement. The new error message NAT0321 has been introduced:
NAT0321 Error :1: in :2: processing fields :3:.
Parameter :1: is filled with the underlying error (e.g. 300 for “Operands are not data transfer compatible.”)
Parameter :2: is filled with statement MOVE BY NAME or MOVE BY POSITION
Parameter :3: is filled with the field name or pair of fields causing the error
Error finding in large structures will be speed up with the additional information.
The new PARSE JSON statement allows you to parse JSON documents from a
Natural program. For more information, see PARSE JSON in
Statements.
The NATBPMON administrator can now always invoke the utility. If the
maximum buffer pool user limit is reached, the administrator accesses the utility as
an emergency user.
The Data area format of the Transfer options is enhanced with the value ‘D’ to
convert data areas to the DEFINE DATA format. For more information, see
the enhanced DA-FORMAT of the Keyword
Explanation of transfer-options described in option-setting.
