ASNA Wings® 9.0 for Microsoft� Visual Studio�

Installation Notes

Software Requirements

Supported Web Browsers

Licenses Needed for ASNA Wings

Limitations of 9.0
Required IBM i SYSVAL and User Profile
Limitations of IBM Rational Open Access - RPG Edition
Differences in Format Level Identifiers

Installation Notes

If you have installed a previous release, please uninstall it before installing this release.

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. Attempting to install Visual RPG (the development package) onto a machine where the Deployment package is already installed (or vice-versa) will result in neither package working.

ASNA Wings 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 IBM 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 WDA, Monarch Collector and WebPak. The downloadable package for DataGate 15.0 for IBM i can be found here.

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

Silent Installation

To set up a silent installation, you must download the Wings package or otherwise have it available on your Windows machine or network.

Then, in a command prompt, enter the path to the folder where the Wings installation package is saved followed by Setup.exe, using the following syntax:

ASNA.Setup.exe [options] 

The following options are required for silent installation:

-s       Run the installation with no user interface.
-a       Accept the ASNA Software License Agreement (required to run in silent mode)

Other available installation options are:

-?       Displays the command line usage dialog.
-f       Full: Install all components.

-c       Core: Install required components.
-o       Optional: Install required and optional components.
-h       Help: Install required and help components.
-netfx35 .NET Fx 3.5: Install .NET Framework 3.5 Support if present on machine.
-np      Do not prompt the user to reboot if reboot is required.

Note: Multiple installation options may be used.

Ex. \"ASNA.Setup.exe -s -a -o -netfx35\" will install the required components, optional components, and .NET 3.5 Support.

To repair an installation from the command line:

-r       Repair the installation.
Will repair all features that are installed and have not previously been upgraded by another product.

To uninstall from the command line:

-u       Uninstall the product.
Will remove all features that are part of the product package, are not permanent (ASNA Services for example is permanent, so will not be uninstalled), and are not shared with other ASNA products that are currently installed on the machine.

WDA has been tested on the following operating systems:

Software Requirements

Before installing WDA, please ensure the Windows machine is equipped with the following:

On the IBM i, you will need the following:

Supported Web Browsers

ASNA Wings may be used with many different browsers. However only the versions listed on our Supported browsers page have been tested and are officially supported

Licenses Needed for ASNA Wings

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

Limitations of 9.0

This build (9.0) of Wings has the following limitations:

Required IBM i SYSVAL and User Profile:

ASNA's browser-based emulator requires the above as it runs in Interactive mode on the IBM i. Modernized Wings pages run in Batch mode, and do not require any specialized SYSVALS.

Limitations of IBM Rational Open Access - RPG Edition

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

Differences in Format Level Identifiers

There are several display file features that are handled differently in Wings than on the IBM i with respect to the layout of certain fields in record formats, these differences cause the Format Level Identifiers used in Level Checks to be different for files exported by Wings and those created directly from pure DDS. The normal development cycle for Wings ensures that this differences do not cause any problem. This cycle follows these steps:

  1. Import Display File DDS into Visual Studio
  2. Optionally make modifications to the ASPX file created
  3. Export the ASPX back to the IBM i onto a library for Wings exported Display Files
  4. Add the HANDLER keyword to the RPG ILE program that will use the new ASPX as a workstation file
  5. Compile the RPG ILE program ensuring the exported Display Files library is found first in the library list by the RPG compiler

Some of the DDS features that cause Wings to generate different Format Level Identifiers are:

Note - If this software is downloaded via Microsoft Internet Explorer 9 or above 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 8 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.

   June 14, 2017       � 2007-2017  ASNA. All rights reserved.