´╗┐Release Notes
ASNA Mobile RPG®
Version: 10.0.89.0
Release date: 2023-12-06


Important notices

See the Software Requirements section below for platform support.

If you are upgrading from an earlier version of AVR, you may be effected by the changes to the ASNA Runtime (see ASNA Runtime Changes below).

Be sure to read about the IBM i System Value requirements below.

What's New in Mobile RPG®

DataGate Studio & DataGate Monitor

DataGate Client

Web Controls

Known Issues

DataGate Client * 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.

DataGate Studio

Web Controls

Secure Sockets Layer (SSL)

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.

More information here

Other DataGate SSL Options

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.

Configuring DataGate Connections Programmatically

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 Name Migration From Non-SSL Releases

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.

Installation Notes

Only one installation of Visual RPG, Windows Deployment, or DataGate WebPak may be installed on a single machine. The Windows Deployment and WebPak components are subsets of what is contained in the AVR installation package. If you have one of these products installed currently on your machine, please uninstall it before installing another.

ASNA Mobile RPG is composed of several items, some of them are used exclusively at design time, others at design and run time, there are items installed on the Windows machines and there are others installed on the System i.

These are the ASNA components used at design time:

For run time, the ASNA components needed are:

The download packages on this page include the components for MDA, Monarch Collector and WebPak. The downloadable package for DataGate 16.0 for IBM i can be found here.

IE/Edge/Windows Installation note

If this software is downloaded via Microsoft Internet Explorer or Edge you may receive a message stating that this file "is not commonly downloaded" when attempting to install it. In this event click the View Downloads button, select the ASNA product to install from that list, and confirm that you'd like to install it.

Similarly, attempting to install the software directly through Microsoft Windows may cause a "Windows protected your PC" message to appear. In this event click the small More Info prompt on the left, and click Run Anyway on the following window.

Silent Installation Process

Wings supports silent installations. See the Installation section of the Readme file for more detail.

Local Help Support

Visual Studio 2019 treats local (offline) as an optional component. As such installing it requires some additional steps:

When installing Visual Studio 2019:

  1. Under the Individual Components tab.
  2. On the Code Tools section.
  3. Enable the Help Viewer component.

To verify the Help Viewer is installed, look at the top of the Help Menu in Visual Studio. The following three options should be visible at the top of the menu:

  1. View Help
  2. Add and Remove Help Content
  3. Set Help Preferences

ASNA Runtime Changes

The version 15.0 of the ASNA family of .NET products introduces two changes in some ASNA DLLs.

1. ASNA.VisualRPG.Runtime.DLL expands into three new DLLs

The first change is that ASNA.VisualRPG.Runtime.DLL expands into three new DLLS: * ASNA.Runtime.DLL * ASNA.Runtime.Support.DLL * ASNA.Runtime.Monarch.DLL

This increased granularity was made to better match library improvements and DLL changes to the various ASNA products that use them. The details of this three-way split are shown below in Figure 1.

Figure 1. Version 15.0's new DLL structure

In Figure 1 above the namespaces each DLL provides is shown prefixed with {}. You can see that although ASNA.VisualRPG.Runtime.dll has been split into three DLLs the same namespaces are provided in the new DLLs. The version 15.x DLLs also provided a few new additional namespaces beyond what's shown in Figure 1.

To maintain backwards compatibility of version 15.0 with previous versions we ship an ASNA.VisualRPG.Runtime.dll library which forwards requests for any of the four original namespaces that where in that DLL to the corresponding new DLL. We will stop shipping the ASNA.VisualRPG.Runtime.dll with the next major version of ASNA .NET products. This forwarding version of this DLL will be available as a separate download.

2. ASNA.VisualRPG.Common.Sgml.dll has been deprecated.

The second change is that ASNA.VisualRPG.Common.Sgml.dll has been deprecated and its code has been moved to ASNA.Runtime.dll. This change mostly affects customers using Mobile RPG and Wings.

Changes you need to make because of these DLL changes

There are no coding changes you need to make in your projects because of these changes. The only changes you need to make is adding and/or deleting references. For new 15.x projects the correct project references will already exist.

In addition to removing that reference:

The ASNA.Runtime.* DLLS are located at:

C:\Program Files (x86)\Common Files\ASNA Shared\Client\16

For more details on the runtime changes click here.

Microsoft Product Recommendations

Installing Microsoft's latest service packs, high priority and optional software updates for Windows, the .NET Framework, and Visual Studio 2019 is highly recommended.

Windows optional update KB3118401 is required for correct operation of version 16.0. See https://support.microsoft.com/en-us/kb/3118401 for more detail.

Caution: Ensure neither Visual Studio, its installation, nor any Visual Studio update is running at the time of Mobile RPG installation, as it may cause conflicts.

Software Requirements

Mobile RPG Design Aid requires the following software:

Visual Studio Editions

Platform support and product requirements, including Visual Studio, are detailed on our Product Requirements page

Platform support/product requirements

Platform support and product requirements are detailed on our Product Requirements page

Supported Web browsers, smartphones, and tablets

Licenses Needed for ASNA Mobile RPG

ASNA Mobile RPG requires license keys on the Windows and IBM i machines.

On the development Windows machine apply these license keys (Using the Registration Assistant):

On the IBM i apply these license keys:

Required IBM i SYSVAL and User Profile setting required for Mobile RPG 10.0.

The following System Values are required:

Limitations of IBM Rational Open Access - RPG Edition

For more details, please see Chapter 6 in the document link below:

https://www.ibm.com/developerworks/mydeveloperworks/wikis/form/anonymous/api/library/01071083a0-b012-4248-10d0c-33ef810a6c3dd/document/88ce10ecc-1e14-4044-10c50-fc107700371d7/attachment/18aba10c1-7253-4de4-a534-f28e486de2e3/media/open_access_rpg_edition_5733OAR_2010_08_23.pdf

´╗┐

Changes Since Version: 10.0.88.0

Clients - DataGate Explorer