ASNA DataGate 11.0 for IBM i


System Requirements

IBM i Configurations
Windows Configurations

Installation Notes

What the Installation Will Do
Transferring and Installing DataGate for IBM i
Installing DataGate for IBM i onto the IBM i from Windows
Installing DataGate for IBM i onto the IBM i from the IBM i
Installing DataGate for IBM i using a IBM i CD-ROM drive
Changing the Default DataGate TCP Port
Licensing DataGate for IBM i
Entering the License Code on the IBM i
Authority of the User Profile used to Register DataGate
Configuring DataGate for IBM i
Verifying that TCP/IP is Installed Correctly
Configuring Support for Terminal Emulation
Naming a IBM i Database
Configuring Multiple Versions of DataGate for IBM i Using TCP/IP
Troubleshooting
Troubleshooting DataGate Service
Troubleshooting a DataGate Job that is Not Terminating
Setting up a Subsystem
Troubleshooting Manually Ending Users Jobs
Finding a  IBM i IP address
Upgrading OS/400
Uninstalling DataGate

Release Notes


System Requirements

IBM i Configurations

DataGate 11.0 for System i is fully supported for the following i5/OS releases:

Please also consult the release notes for information regarding DataGate for IBM i interoperabilty with DataGate Client.

Back to Top

Windows Configurations

Windows is not required for installation of DataGate for IBM i, but may be used if desired. The installation notes in this document refer to procedures available in the following Windows releases:

Please consult the installation notes for further details regarding the configuration requirements for installing DataGate for IBM i.

Back to Top

Installation Notes

DataGate for IBM i Installation Instructions

You will achieve fast, record-level DB2/400 database access from Windows with DataGate for IBM i. Whether you are developing your client applications in Visual Basic.NET, C#, Visual RPG.NET, or Visual RPG Classic, DataGate for IBM i provides the direct file access needed for efficient Client/Server processing - without SQL and ODBC.

IBM i connectivity is supported for TCP/IP.

DataGate for IBM i retains all IBM i object authority and object locking. Its Remote Program Call support features automatic program initiation and activation, and allows character, numeric and indicator (Boolean) parameter data types.

DataGate for IBM i provides full object control for the IBM i including: creating files; accessing file definitions; adding, deleting and initializing file members; renaming and copying files. It provides full access to CL commands and data areas, and it utilizes all IBM i CPF error messaging.

Note: The user installing DataGate on the IBM i must have *SECOFR authority.

What the Installation Will Do

On the IBM i

On Windows

Back to Top

Transferring and Installing DataGate for IBM i

The procedure to install DataGate for IBM i on the IBM i consists of 2 parts. The first is to transfer the DataGate software to the IBM i, either from Windows or the IBM i CD drive, and the second is to actually install DataGate into the specified IBM i library.

There is one way in which you can transfer DataGate for IBM i to the IBM i from Windows

There is one way in which you can transfer DataGate for IBM i to the IBM i from another IBM i

Refer to the appropriate installation procedure below for the desired transfer method. Each procedure will have a subheading noting whether the steps are done on the IBM i or Windows.

The last step in each procedure will be to run the command that actually installs DataGate for IBM i onto the IBM i.

Back to Top

Installing DataGate for IBM i onto the IBM i from Windows

Note: The user installing DataGate on the IBM i must have *SECOFR authority.

Prior to installation, DO NOT DELETE or RENAME the ASNA_DG8 library. It is required for all versions of DataGate, even though you may be installing into a library with a different name. Also, if you are installing to an existing subsystem, please be sure that the subsystem has been started prior to the installation.

Installing DataGate for IBM i using FTP

In order to install DataGate for IBM i on the IBM i from a Save file (obtained from the Installation CD), you must have TCP/IP installed on both Windows and on the IBM i . (You must also have FTP installed on your IBM i).

Installing TCP/IP and FTP on the IBM i is beyond the scope of this document. If you do not know whether your IBM i has TCP/IP and/or FTP, please check with your network manager or system provider.

On the IBM i
  1. Sign onto the IBM i using the QSECOFR account.
  2. Create a Save file in QGPL by entering the following command:
On Windows
  1. To upload the Save file from the CD via Windows, an FTP session must be started to the IBM i.

    From Windows, click on the Start button, select Run and enter the following command:

    FTP tcpipaddress

    �tcpipaddress� is either the IBM i�s TCP/IP address such as 199.076.129.35, or a machine name that is registered either in a DNS or a HOSTS file.

  2. When prompted for a user name and password, enter the appropriate information that will give you privileges to upload data to the IBM i.
  3. Once FTP has been started, upload the Save file to the IBM i by entering the following commands:
    1. binary
    2. put x:\Datagate\FTP\ASNAINST QGPL/ASNAINST

      where x is the Windows CD-ROM drive.

    3. quit
On the IBM i
  1. Restore the library called ASNAINST from the Save file by entering the following command:

    RSTLIB ASNAINST DEV(*SAVF) SAVF(QGPL/ASNAINST)

  2. To install DataGate for IBM i, execute the following command:

    ASNAINST/DG8LOAD

    When DataGate for IBM i is installed, it is automatically authorized for one user license. If you wish to authorize more than one licensed use of DataGate for IBM i, obtain a license code from ASNA and then enter InstallLib/REGISTER from IBM i command line.

  3. The installation program will display the ASNA Software License Agreement. If you agree with the terms of the license, press the F8 key to continue with the installation. If you do not agree, press the F3 key and the installation will be cancelled.

    Next, the installation program displays the installation options. The installation can be cancelled at any time by pressing the F3 key.

    Installation Library Option:

    Select a library where DataGate for IBM i will be installed. If the library does not exist, it will be automatically created during the installation. The following libraries are not allowed for the installation: QSYS, QGPL, QSPL, QTEMP, VCAT_72 and the distribution library. Libraries called ASNA_DG8 and VCAT_72 are always created.

    Subsystem Options:

    Select a subsystem where DataGate for IBM i will run. You must also specify the library where the subsystem description is located or where it will be created during the installation. This is required so that the installation program can determine whether the specified subsystem exists or must be created. If the subsystem does not exist, it will be automatically created in the specified library during the installation. If you are installing to an existing subsystem, please be sure that the subsystem has been started prior to the installation.

    Service Table Entry Options:

    Select the name of the service table entry and the port that DataGate for IBM i will use. The default values are recommended.

    Start DataGate Option:

    Enter �Y� to have DataGate for IBM i started as soon as the installation has completed. If you select not to start DataGate, you will have to start it manually with the STRDG8SVR command by entering:

    InstallLib/STRDG8SVR

    Where InstallLib is the library into which DataGate for IBM i was installed.

    Clear Cache Library Option:

    Enter �Y� to clear the DataGate for IBM i cache library. This is recommended. Make sure that there are no active DataGate for IBM i jobs if you select this option.

  4. When all options have been selected, press the F6 key to display a verification screen for each of the above options. As you review each option, press Enter if you are satisfied with your selection, otherwise press the F12 key to redisplay the options screen and enter your changes. When all options have been verified, the installation will start.
  5. The installation program will stop the version of DataGate for IBM i that is running out of the specified installation library � if there is one. If there are multiple versions of DataGate for IBM i running, those other versions will not be stopped.
  6. Once the installation has completed, the ASNAINST Save file is no longer needed, and may be deleted. The ASNAINST library is automatically deleted.
  7. You must name the IBM i Database in DataGate Database Manager using Work with Database Names. See Naming an IBM i Database for more information.

Back to Top

Installing DataGate for IBM i onto the IBM i from the IBM i

Note: The user installing DataGate on the IBM i must have *SECOFR authority.

The following installation processes have two steps.

Back to Top

Installing DataGate for IBM i using a IBM i CD-ROM drive

Note: The user installing DataGate on the IBM i must have *SECOFR authority.

To install from IBM i CD_Rom Drive

  1. To restore the installation library, load the CD, then enter the following command:

    RSTLIB ASNAINST OPT01 OPTFILE('DATAGATE/RSTLIB/ASNAINST')

    Where OPT01 is the device name from which the library will be restored.

  2. See the above section titled Installing DataGate for IBM i with FTP, starting with step 8, for detailed instructions and information about the various installation options.

    Once the installation is completed, the ASNAINST Save file is no longer needed, and may be deleted. The ASNAINST library is automatically deleted.

    When DataGate for IBM i is installed, it is automatically authorized for one user license. If you wish to authorize more than one licensed use of DataGate for IBM i, obtain a code from ASNA and then InstallLib/REGISTER from IBM i command line.

Back to Top

Changing the Default DataGate TCP Port

To modify the installed (default) TCP/IP port 5042 to another port:

  1. Enter the command WRKSRVTBLE (Work with service table entries) to verify the name of the DataGate service. On the prompt screen, press <enter> and list of table entries is displayed; the entry list is typically in arrival sequence, so this entry should be at or near the bottom of the list. Scroll down the list of entries until you see port 5042. The default DataGate Service name is "Acceler8DBServer". Write down the Service name and then press the F3 key.
  2. The entry for port 5042 must first be removed. On the command line, enter RMVSRVTBLE and press <enter>. In the Service prompt field, enter the name of the DataGate service from the Service Table entry; in the Port prompt field enter "5042"; and in the Protocol prompt field prompt enter "tcp". Press <enter> and the entry will be removed from the Service Table.
  3. To add the entry for the port you wish to use, on the command line, enter ADDSRVTBLE and press <enter>. In the Service field prompt enter "Acceler8DBServer"; in the Port prompt field enter the port number you want to use; in the Protocol prompt field enter "tcp" (this must be lower-case); and in the Text prompt field enter "DataGate/400 Service Table Entry" and then press <enter>.

    The name that you entered for the service on the ADDSRVTBLE command must match the name in the TCPSERVICE data area in the DataGate library (by default it is "Acceler8DBServer").

Back to Top

Licensing DataGate for IBM i

Before DataGate for IBM i may be used on any IBM i, a valid license code, issued by ASNA, must be entered. For new trials, this code will be sent with the product if the machine serial number and model type are known at the time of shipping.

The code issued with a trial of DataGate for IBM i will license, or register the product to be used on a specified machine up to a specified date. If it is required to move the product onto another machine, upgrade the model type, or extend the trial period, please contact your Distributor or ASNA for a new license code.

Once the product has been purchased, a new license code will be issued to register the product on a permanent basis. This code will be based either on unlimited users, or on a per-user basis.

Back to Top

Entering the License Code on the IBM i

A new license code is entered, or a current license can be viewed or changed by using the product�s Registration Assistant program.

When installing the product for the first time, or when an upgrade is installed, the Registration Assistant screen is displayed with the bottom of the screen displaying whether the current License Code is valid or not. If the License Code is valid, press F3 to continue. If not, call ASNA or your Distributor to get a new License Code.

Note: You cannot use the product without a proper License Code.

To Enter, Display, or Change a License Code on the IBM i

  1. If you are not already at the Registration Assistant Screen, enter the following:
    InstallLib/REGISTER
    Where InstallLib is the library into which DataGate for IBM i was installed.

  2. Enter or verify the information to the display, as detailed below.

    System Name
    The name of the IBM i will automatically display.

    Model
    The model of the IBM i will automatically display.

    Serial Number
    The serial number of the IBM i will automatically display.

    License Key
    For a new license, enter the 16-digit license code acquired from ASNA exactly as it is given.

    License Type
    License Type specifies if the licensing is for an individual machine, or for the entire company.



    Customer Name
    The name of the user that was entered when the product was installed will automatically display. However, you can change this name as needed.

    Company Name
    The name of the company that was entered when the product was installed will automatically display. However, you can change this name as needed.

    If you are entering a Site License, the name of the company must be spelled exactly as determined by you and ASNA. This name is also case-sensitive, so capitalization must match exactly.

    Start Date
    The Start Date specifies if the product has been purchased, in which you have a Permanent code, or if the product is a �Trial�, which is only valid for a specified period.

    Expiration Date
    The Expiration Date indicates the date on which the license code will expire.

    User Count
    User Count specifies the number of concurrent users that can access the product, as a per-user-basis, or as unlimited.

  3. Acceptance of a valid licensing code is confirmed at the bottom of the screen. Press F3 to continue.

    If the message �The License is Invalid� displays, recheck all entries. If no errors were made in any of the entries, call ASNA or your National Distributor for further assistance.

    If the message �Couldn't create license data area, check authority and try again" displays, you do not have the proper authority to register DataGate for IBM i. See Authority of the User Profile used to Register DataGate for more information.

Back to Top

Authority of the User Profile used to Register DataGate

The user profile used to register DataGate software must have *CHANGE authority to the ASNA_DG8 library. Additionally, it must have *ALL authority to the DGPCODE4 data area in ASNA_DG8, if it already exists (say, from a previous registration of the product).

The user profile must have these authorities regardless of the method used to register the program.

As an example, suppose user profile ADBUSER is to be used to register DataGate. The successful execution of the following two IBM i commands prior to registration will insure that the required object authorities will be available to ADBUSER:

GRTOBJAUT OBJ(QSYS/ASNA_DG8) OBJTYPE(*LIB) USER(ADBUSER) AUT(*CHANGE)

GRTOBJAUT OBJ(ASNA_DG8/DGPCODE4) OBJTYPE(*DTAARA) USER(ADBUSER) AUT(*ALL)

Remember that the DGPCODE4 data area may not exist yet if DataGate has never been registered on the machine. If so, the second command is not necessary.

Back to Top

Configuring DataGate for IBM i

Configuring TCP/IP on Supported Windows Platforms

This process assumes that your machine is on a TCP/IP Network. If you are unsure of the type of Network, or do not understand any of the steps, please contact your Network Administrator.

You should use automated IP settings (DHCP) whenever possible, for the following reasons:

To Configure TCP/IP on Windows Platforms

  1. Open Control Panel (in Windows XP, by selecting Start � Control Panel).
  2. Double-click the Network Connections Icon to open the Network settings.
  3. Click the connection you want to configure, and then, under Network Tasks, click Change settings of this connection.
  4. Do one of the following:
  5. Do one of the following:
  6. To configure DNS, WINS, and IP Settings, click Advanced.
    If these differ from your configuration or you are not sure of the network configuration, please contact your Network administrator!
  7. Follow the procedure to verify that TCP/IP is installed correctly.

Back to Top

Verifying that TCP/IP is Installed Correctly

To verify that TCP/IP is installed correctly and can communicate with the IBM i, you will need to know the IBM i�s TCP/IP address and Full domain name. If you do not know, please contact your Network Administrator!

To Verify that TCP/IP is Installed Correctly

  1. Open a Command Prompt (in Windows 7  or 8 by typing CMD into the Start Menu search bar).
  2. Type the command ping followed by the TCP/IP address of the IBM i.
  3. If TCP/IP is functioning correctly, you should receive four replies.

Back to Top

Configuring Support for Terminal Emulation

DataGate 10.2 introduced support for the execution of interactive programs via a DataGate connection, the actual handling of the 5250 data stream is part of Monarch and Wings in the form of a browser based terminal emulator. In order for this support to be enabled, the following configuration parameters must be established on the IBM i, these parameters do not affect non Monarch/Wings installations where terminal emulation is not needed.

Back to Top

Naming a IBM i Database

To Name a IBM i Database For TCP/IP Connectivity

  1. Select DataGate Explorer from the DataGate menu. The DataGate Explorer tool window will display.
  2. Click the Add New Database Name button on the right side of the toolbar at the top of DataGate Explorer window (or alternately, right-click the Local Database Names node and select Add New New Database name on the context menu). The New Database Name dialog is displayed, as shown below.
  3. Select primary parameters for the database name, as explained in the DataGate Studio Help, Database Name Parameters topic.
  4. After clicking OK, the dialog will close and the identifier of the new database name will be selected in edit-mode, under Local Database Names in DataGate Explorer. Change the default, �New Database Name�, to the identifier you wish to refer to the database name with.

    Enter a "Name" to call the database on your computer. This is the identifier you will use to refer to the database in your applications.

    Alternatively, selecting the Database Wizard from the the DataGate menu will begin a series of prompts that will guide you through creating a database name.

Back to Top

Configuring Multiple Versions of DataGate for IBM i Using TCP/IP

To Configure an Additional DataGate for IBM i on the same IBM i using TCP/IP

  1. Create a new installation library.
  2. Install DataGate into the newly created library by following the steps found in the Installation Notes in the sections entitled Installing DataGate for IBM i using FTP or Installing DataGate for IBM i using a IBM i CD-ROM drive.

    Note: Make sure to specify an unused port, a new TCP Service Table Name, and the new Library specified in Step 1.

Back to Top

Troubleshooting

Troubleshooting IBM i TCP/IP Connectivity

If you are unable to connect to the IBM i database from ASNA�s DataGate Database Manager, the following information may help identify possible incorrect setups on the IBM i.

It is assumed that TCP/IP configuration has been completed correctly in Windows. If you are unsure whether TCP/IP is installed or correctly configured in Windows, contact your network administrator for assistance.

TCP/IP names are a combination of host names (machine names) and domain names. A machine name for TCP/IP does not have to match the IBM i machine name; however, it will be a unique name - and it can be the same as the IBM i machine name.

Throughout this example, the machine name used is �machine�, and the IBM i name is actually �S1037242�. The domain name used throughout this example is �domain.com�. Together the machine name and the domain name make a �complete� TCP/IP name - �machine.domain.com�. At your site, you should use your own domain name and own machine name.

  1. First check to see if you are able to ping the IBM i by name from Windows. For example, if the TCP/IP name of the IBM i is �machine.domain.com�, then the following command should be issued from your machine from a Command Prompt:

    ping machine.domain.com

  2. From the Configure TCP/IP menu screen that appears, select the Work with TCP/IP Interfaces (option 1).
  3. The following menu screen will appear.

    You should see something similar to this screen. If you do not, then TCP/IP is probably not configured on the IBM i properly, or it may not be completely installed. Check with your IBM i administrator to make sure the IBM i has TCP/IP installed.
  4. If there is an internet address other than 127.0.0.1 listed, select that address and enter an option 5 command to display the setting for that IP address.


  5. If you reach this point and are still having problems accessing the IBM i via TCP/IP, then F12 back to the main configuration screen for TCP/IP (Configure TCP/IP) and enter option 21 (Configure Related Tables) from the main TCP/IP configuration menu.


    Note:The protocol listed in the service table entry for the �DataGateServer� service should be �tcp�. It is case sensitive, so if the letters are uppercase, you will need to remove the service and re-add the service with lower case letters.

Back to Top

Troubleshooting DataGate Service

If you are unable to start the DataGate Service, the following steps will assist in trouble shooting the possible causes.

When the DataGate service job is submitted for execution, the job is submitted under the user profile of DG8SVCPRF. This user profile is created during the installation and the system value for the Printer option will be assigned to this user profile. If the DataGate service job has trouble starting, a one page report outlining the possible cause of the problem will be generated for the user DG8SVCPRF and printed to the assigned printer. This report will not print unless the Output Queue associated with this printer automatically prints the generated reports. Otherwise, to view the list of reports that have not printed for this user, enter the following command:

WRKSPLF SELECT(DG8SVCPRF)

At this point you will need to contact ASNA for further assistance.

The most probable cause for the DataGate service job not starting is that the current DataGate service job is terminated with an ENDJOB command, so subsequent attempts to start the service will not be successful.

  1. If the DataGate service job is not currently running and it won't start by issuing the STRDG8SVR command, enter the following command:
     NETSTAT 
  2. Select Option 3. Work with TCP/IP Connection Status.
  3. Select F14 to Display Port Numbers In the Local Port column, locate the Port Number you assigned as the Port for the DataGate Service (The default Port Number is 5042).
  4. You will need to end this connection by selecting Option 4.
  5. When this connection is ended successfully, you may now execute the STRDG8SVR command.

Back to Top

Troubleshooting a DataGate Job that is Not Terminating

If you notice that a DataGate Job is still running after a client connection is lost, this is due to a TCP/IP feature called "Keep-Alive". Refer to the following to change the system's default Keep-Alive value.

Keep-Alive packets are used to probe a connection that has been inactive for a long time. The server initiates a disconnect when the probes do not get through.  This means that if the client connection is lost for a prescribed length of time, the server sends a disconnect message to its server job (usually the result of a system crash or power-down).

The default Keep-Alive setting for Windows and IBM i is two hours, meaning that a DataGate thread or DataGate job would remain active for 2 hours after connection was lost with the client. The 2-hour default may be an unsatisfactory period of time for you, as files would continue to remain open, etc. on an abnormal disconnection until the Keep-Alive time had elapsed.

Refer to the following to modify the server machines' respective Keep-Alive period.

IBM i

  1. Request the Configure TCP/IP menu by executing the command: cfgtcp
  2. Select menu item 3 - Change TCP/IP Attributes.
  3. Set TCP/IP Keep-Alive to the number of minutes desired. (Note: 2 to 5 minutes should work well in most cases).

Windows

WARNING: Using Registry Editor incorrectly can cause serious, system-wide problems that may require you to reinstall Windows to correct them. Microsoft cannot guarantee that any problems resulting from the use of Registry Editor can be solved. Use this tool at your own risk. The following was derived from Article ID Q120642.

To Change these parameters, use the following procedure:

  1. Run Registry Editor (REGEDT32.EXE or REGEDIT.EXE).
  2. From the HKEY_LOCAL_MACHINE subtree, go to the following key:
    \SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

  3. The Value is " KeepAliveTime". If present (usually not), double click on it to edit in milliseconds. Otherwise, continue with Step 4.
  4. Select "Edit -> Add Value".
  5. For Value name, enter KeepAliveTime.
  6. From the Data Type drop down list, select REG_DWORD
  7. Press OK
  8. In the DWORD Editor dialog, enter the number of milliseconds. Select the Radix Decimal option.
  9. Select OK.
  10. Enter the Keep-Alive value in milliseconds; e.g. 5 minutes = 300000 msec.

    Valid Range: 1 - 0xFFFFFFFF
    Default: 7,200,000 (two hours)

    The parameter controls how often TCP attempts to verify that an idle connection is still intact by sending a Keep-Alive packet. If the remote system is still reachable and functioning, it will acknowledge the Keep-Alive transmission. Keep-Alive packets are not sent by default. This feature may be enabled on a connection by an application.
  11. After typing in the value, use the "Data Type" checkbox to set the value type.
  12. Select OK.
  13. Exit the Registry Editor.
  14. Reboot the system to make the change take effect.

Back to Top

Setting up a Subsystem

Basically, to set up a subsystem, you need to have a routing entry with a compare value of �QCMDB� that runs the program QCMD in QSYS.

The subsystem that is used for the job queries must be set up with a proper routing entry in order for DataGate service to start. This routing entry must run the program QCMD in Library QSYS and have the compare value of �QCMDB� or �*ANY�. If the subsystem has one of these routing entries, it may be used for DataGate.

Back to Top

Troubleshooting Manually Ending Users Jobs

If DataGate is shut down and there are users connected, their jobs will still be out there and you have to manually end them. However, after manually ending the users� jobs, DataGate may not start for about 5 minutes. It will start the first DG8SVC job and then end it until the 5 minutes (or so) is up.

It is likely that OS/400 is not reclaiming the DataGate TCP/IP port (5042) in a timely manner when the service and connection jobs are ended. When you "manually end" connections to DataGate, it may not have a chance to properly shut down TCP/IP resources. The system typically does not realize that those resources are no longer in use for some quantum.

The best way to avoid this is to let the connections and service end normally, though in abnormal situations this isn't always possible.

When you must use ENDJOB, etc., to end the connections and/or the service, you can sometimes use the WRKTCPSTS command to view the outstanding socket connections and end them. In such a case, if you find a socket in the "listening" state using the DataGate port, you can end this connection (but only if you are absolutely sure the service isn't running) using WRKTCPSTS. Likewise, if you find sockets connected to the DataGate port from external ports, you can end those (if you are sure that there are no jobs using the connection). The system will then reclaim the port, and a new instance of the DataGate service can use it immediately.

Back to Top

Finding a IBM i IP address

If the user does not know the IP address of the IBM i to which they are trying to Name a database, do the following. Note however, that most users should never have to do this, and you may want to "call your Network Manager� instead of performing the steps below.

  1. In Windows, open a Command Prompt window and enter:
    arp -a
    Note the IP addresses that appear. You will compare this list with the list generated in step 4. (Normally, there will be only one difference, and it will be the addition of the IBM i's IP address).
  2. For Windows: At a Command Prompt, enter:

    IPCONFIG

    The IP address of Windows will display. Note this IP address, since you will use it in step 3.

  3. On the IBM i on a command line enter:

    PING 'xxx.xxx.xxx.xxx'

    where xxx.xxx.xxx.xxx is the IP address of Windows noted in step 2.

    In the Configuration dialog, there's a drop down list box of adapters. Note that in most cases you will only have one Ethernet adapter, so the only challenge is to distinguish the Ethernet adapter from a dial-up adapter. This is usually easy, because dial-up adapters usually have a name like "NdisWan4".


    It is also wise to NOT attempt to ping a Windows computer that is also running 5250 emulation, etc., to the object IBM i. That's because that IBM i will already be in the arp sorted "list", so one would not be able to tell which is the target IBM i because the list would be the same in steps 1 and 4.

  4. On Windows in the Command Prompt window, enter:

    arp -a

    The IP addresses are sorted. Compare the list with the list in step 1 and note the new IP address, this is the IBM i's IP address.

Back to Top

Upgrading OS/400

If you are upgrading IBM i's OS/400 to a new level, please contact ASNA to ensure you have a compatible version of DataGate.

Note that you will also need to reconfigure DataGate for TCP/IP access (i.e., the ADDJOBQE and ADDSRVTBLE commands).

Back to Top

Uninstalling DataGate

If you are running multiple instances or versions of DataGate and wish to uninstall a single version; please note the following:

DO NOT delete or rename the ASNA_DG8 library or the DG8SVCPRF user profile. these are required for all versions of DataGate even though you may be installing into different library names Deleting these objects will render ALL installations of DataGate on the machine INOPERABLE. 

For TCPIP access, you will need to remove the service table entry for the instance of DataGate that you wish to uninstall. To verify the Service Table entry, display data area TCPSERVICE in the library that you are uninstalling. This data area contains the name of the Service Table entry that you will remove.

To uninstall an instance of DataGate that was not installed in the default installation library ASNA_DG8, follow the steps below.

To Uninstall a DataGate Instance

  1. Remove the job queue entries for the Jobq Datagate and the Jobq DG8_SVC using the RMVJOBQE command. These Job Queues reside in the installation library. (Most commonly called ASNA_DG8).

    If you have installed DataGate into a library other than ASNA_DG8, your job queues will reside in the library where DataGate is installed.
  2. Delete the Job Queues Datagate and DG8_SVC using the DLTJOBQ command.
  3. Remove Service Table Entry for TCPIP access using the following command.

    RMVSRVTBLE SERVICE('DataGate400') PORT(5042) PROTOCOL('tcp')
  4. Delete the DataGate installation library using the DLTLIB command.

    DataGate is now uninstalled.

Back to Top

Release Notes

DataGate Client Compatibility

Character Data Translation

Back to Top

   October 5, 2012        � 2007-2012 ASNA. All rights reserved.