How to upgrade ASNA DataGate WebPak
The ASNA WebPak is the DataGate client for Windows Servers. It is to Windows servers what the Client Deployment binary is to Windows clients. The WebPak should be installed on any Web server on which you’ve deployed an AVR ASP.NET Website/Web services or Monarch migrations. Installing WebPak is very simple; you just run the WebPak’s executable to install it. Previously-created database names continue to work with a new WebPak install. A Web server does not need multiple versions of WebPak. Windows policies ensures that the highest installed version is always used at runtime–and installing a newer WebPak deletes the previously installed version. End DataGate IBM i end user jobs first […]
Using IBM’s Open Query File with ASNA Visual RPG
Finding records where a field contains a given value is an awkward thing to do with RPG’s record-level access. In either green-screen RPG or ASNA Visual RPG (AVR), the ugly solution is simple, loop over every record in the file checking each field as you go. This works, but have something nearby to keep you occupied while you wait. This article provides an alterative to that record level access using AVR for .NET’s Open Query File.
Installing a second instance of DataGate for IBM i
Please read these instructions completely to ensure a successful co-existing install of ASNA DataGate for IBM i. If you have any questions, please contact us at info@asna.com or give us a call before you start your installation. It is very important to end all existing versions of DataGate that are running before installing a new instance. Starting with DataGate 16.x, the installation procedure ends all exisiting instances of DataGate and starts the one you just installed. See this article for how to end DataGate. During installation, be sure to vary these configuration values: Service table entry name . Be sure to provide service table entry name that is not currently in […]
Running Multiple versions of DataGate
Question Can I run more than one instance of DataGate on my IBM i? Answer Yes. You can run multiple versions of DataGate on the IBM i. The only constraint is that each instance must be assigned to a unique TCP/IP address during installation. While it isn’t absolutely necessary, it’s generally best to install a second instance while no other instances of DataGate are running. In a related footnote, all versions of DataGate on the IBM i use the same caching library, DG8_VCAT72. See this article for more information on DG8_VCAT72. Question Can I run more than one instance of the ASNA WebPak on my Windows Web Server? Answer No–but the answer isn’t as […]
How to change the TCP/IP port that DataGate for IBM i uses
This article explains how to change the TCP/IP port that DataGate uses. See this article for a list of other articles that may be helpful for this task Why would you ever want to change the TCP/IP port? In normal circumstances, you’d generally not ever need to do this. However, consider the scenario of updating from DatGate 15.x to DataGate 16.x. To test DataGate 16.x before you use it in production, install it alongside the existing DataGate 15.x instance, being sure to assign the DataGate 16.x a different TCP/IP port number than what DataGate 15.x is using. Use a special-case ASNA Database Name (created with the DataGate Studio in Visual […]
Monitoring Wings and Mobile RPG end-user licensing
ASNA Wings and ASNA Mobile are licensed per end-user on your IBM i server. Your license can be either an unlimited site license or licensed to a specific number of users (sold in blocks of 5, 10, 15, 20, 50, 100, 200 users, etc). This article is primarily for those customers licensed with a fixed number of users. It shows how to determine how many licenses you currently have and how many licenses are currently active. To see your Wings or Mobile RPG license information, use the DSPRRR (Display Registar) command. This command is in your DataGate library. For example, if you’re using the default DataGate library for DataGate 16.x on […]
How to start, stop, and confirm ASNA DataGate on the IBM i
This article shows how to start and stop ASNA DataGate on the IBM i.
Confirm DataGate for IBM i IP address and port are working
When you install DataGate for the IBM i you select a TCP/IP port over which DataGate connects to the IBM i. DataGate’s default port is 5042 but you may have changed that at installation. See this article if you need to know what TCP/IP port your DataGate instance uses. A common problem with DataGate for IBM i connectivity is for its TCP/IP port to be blocked or otherwise not available at runtime. While you can use ping to check the IP connection to the server you cannot use \\ping check whether the DataGate port is available. You need to use telnet` to confirm that connectivity through a specific TCP/IP port is available. This […]
How to uninstall DataGate for the IBM i
This article explains how to uninstall one or all instances of ASNA DataGate for IBM i. Please read it carefully before starting the uninstall process. Important notices If you are running multiple instances or versions of DataGate and want to uninstall a single DataGate instance, do not delete or rename the ASNA_DG8 library or the DG8SVCPRF user profile. These are required for all installed instances of DataGate. Deleting these objects will render all installations of DataGate on the machine inoperable . If you are running multiple instances or versions of DataGate, we strongly recommend that you ensure that there are no active jobs for any of these instances/versions before removing a […]
How to end DataGate for the IBM i
Do not attempt to end DataGate on the IBM i until all end-user jobs have been ended. Trying to end DataGate while end-user jobs will leave you will a hodge-podge of object locks that requires lots of manual clean-up (or perhaps even an IPL) before you can stop and restart DataGate. Ensure that no end-user DataGate DG8_NET end-user jobs are running for the instance of DataGate you want to stop. This article explains how to identify end-user DataGate jobs. If any DG8_NET are running under the instance of DatGate you want to stop, they must be ended before stopping the DataGate server. Ideally, have end-users bring their jobs to a natural end; but if necessary, manually […]
