Release date: 2023-12-06
If upgrading from an earlier version please obtain a new license code from ASNA after installation.
Visual Studio Editions
Platform support and product requirements, including Visual Studio, are detailed on our Product Requirements page
Enhanced support for Free Format RPG
Procedure-scoped field and DS declaration.
Enhanced Embedded SQL Support
INCLUDE CL command
Ability to Rename Fields and Subroutines (including converting procedures that are not external to simplified subroutines)
INFDS "status" support.
Optimized Data Agent, including enhanced support for multi-member files.
Support runtime elimination of clear-text passwords via .NET SecureString.
Encrypted local storage of Database Name connection details.
*DOMAIN authentication enhancements ("Negotiate" protocol support, to eliminate "NTLM" from Active Directory networks).
IPV6 support (server-only enhancement, all past & present .NET DG clients can take advantage of this).
* DataGate 16 features secure database name storage using Windows DPAPI. ASNA has always recommended using PUBLIC database names for websites.
In v16, we further recommend always using the "Public/" prefix explicitly when referencing database names in website applications, including Monarch.
Otherwise, applications may encounter run-time exceptions that include phrases such as "user profile not loaded" when Windows DPAPI is used in IIS sessions running with anonymous or impersonated credentials.
For example, an AVR-based website might have code similar to the following, which references a DG database name in a DCLDB statement as follows:
DclDB Name(MyDatabase) DBName("IBMSERVER") Access(*Public)
We strongly recommend changing this statement as shown below:
DclDB Name(MyDatabase) DBName("*Public/IBMSERVER") Access(*Public)
If changing existing code is impractical, the only way to avoid errors is to ensure that the configuration of the IIS application pool in which the
website runs includes the setting "Load User Profile = True".
Note that this setting may reduce the performance of large-scale website applications. Configuring IIS is Windows- and version-dependent, but
generally follows this set of steps:
1. Open IIS Manager.
2. Under the Application Pools node, select the Application Pool that the website runs under.
3. On the right-hand panel, select "Advanced Settings...". A property dialog appears.
4. Scroll to the Load User Profile setting, and ensure that it is set to True.
5. Restart IIS.
The DataGate client software contained in this release significantly changes the way Secure Sockets Layer (SSL) connections are configured. DataGate SSL support was introduced in Version 15 as an option for secure network communications between DataGate clients and servers.
In prior releases, DataGate client connection configurations, by default, specified an SSL-enabled connection. This allowed many users to enhance the security of their applications by simply installing the new, SSL supporting DataGate release. Unfortunately, other customers experienced connection and security issues due to shifting standards and evolving platform infrastructure supporting SSL, as offered by Windows and IBM i.
In this release, DataGate client users must now "opt-in" when configuring new connections secured with SSL. When a new connection configuration is created, the default setting is to specify a non-SSL, or "clear-text" connection to the server.
DataGate connections are typically configured as "database names". A database name is a collection of properties defining all the information needed to connect to a DataGate server from the client computer. Existing database names are not affected by this change, but new database names are affected:
Database names created by prior releases retain the same SSL configuration as they had when created or modified. The default configuration of new database names will specify non-SSL connections. Creating SSL-Enabled Database Names
Online documentation linked below fully details the process of creating an SSL-enabled database name configuration using DataGate Studio. The process is very similar for users of DataGate Monitor.
DataGate offers many options for enhancing the security of its client/server connection with SSL. For full details of options available for both the client and server, please consult the online documentation.
Connection configurations are represented in DataGate as instances of the SourceProfile class in the DataGate .NET API. While most users and applications will configure connections via database names, some programs use the DataGate API directly.
Users of the SourceProfile class are advised that the changes in this release may represent a breaking change to the behavior of your programs. The default value of the SourceProfile.SslOptions property is now SslOptions.None; in previous releases the default value was SslOptions.Request. If your program does not explicitly set this property, connections made with the SourceProfile instances you create will be clear-text, rather than SSL-enabled.
If you directly create and use SourceProfile instances in your programs, ASNA highly recommends modifying them to explicitly set SourceProfile.SslOptions before deploying this DataGate release.
Database names created by DataGate releases prior to Version 15 do not contain SSL-related configuration information. When these database names are read by Version 15 software, the configuration is migrated to include SSL configuration options. Prior to this release, those migrations would enable SSL connections, unless otherwise explicitly changed by the user. Henceforth, automatic database name migrations will disable SSL in the connections they represent.
Users who deploy applications using the database names contained in configuration files created with prior, non-SSL supported DataGate releases are advised that changes in this release may represent a breaking change in this deployment strategy, for reasons outlined in the previous paragraph.
ASNA Monarch requires the following software:
Platform support/product requirements
Platform support and product requirements are detailed on our Product Requirements page
ASNA Monarch 10.0, ASNA Wings 10.0 and ASNA Mobile RPG 10.0 share some components to produce their user interface. These components are distributed with AVR and WebPak 16.0. The shared components are:
Supported Web browsers, smartphones, and tablets
Monarch 10.0 can be installed on a machine with the previous version (Monarch 9.0) if so desired. Any earlier products may cause conflicts if you have installed other ASNA products from our 14.0 and 8.0 product families (e.g. Visual RPG 14.0, Wings 8.0), please remove them prior to installation, or upgrade them before or after upgrading to Monarch 10.0.
ASNA Monarch 10.0 may be installed as a stand-alone product, or it may be installed along side ASNA Visual RPG 16.0. ASNA Monarch 10.0 is not compatible with ASNA Visual RPG 14.0 or earlier. Please consider upgrading to ASNA Visual RPG 16.0 before installing ASNA Monarch 10.0.
Installing Microsoft's latest service packs, high priority and optional software updates for Windows and the .NET Framework is highly recommended.
Silent installations are now supported by Monarch Cocoon. See the Installation section of the readme for more details.