Install Uniface on iSeries

If you are using a DLM license, ensure that you have installed DLM, the Uniface Distributed License Manager, before installing Uniface. See Install DLM on iSeries .

Always install a new version of Uniface into a different library or remove the old installation first. If you need to repair an existing installation, see Install Over an Existing Installation.

AS400INS is a wizard-like installer that takes you from screen to screen during the installation process. Press Enter to proceed to the next screen, F12 to go to the previous screen, or F3 to stop the installer immediately without installing anything.

  1. In the Welcome screen, press Enter to continue.
  2. Specify the library into which you want to install the Uniface product, and the IFS directory into which other files will be installed.

    Accept the default values by pressing Enter, or change the values here.

    If the directory name is not absolute (that is, it does not start with a slash /), pressing Enter causes the installer to display the same screen again, with the same directory prefixed with the current directory. (The current directory is usually your home directory, as specified in your user profile. If no home directory is specified, the root directory / is usually the current directory.)

  3. Press Enter again to go to the next screen.

    The installer attempts to create the library and the directory. If one of these fails, you are returned to the previous screen and an error message is displayed in the status line at the bottom. You can then change the values and try again.

  4. Select the components to be installed.

    The only component available is Uniface which is selected with a 1 in front of it. Press Enter to install it.

  5. Select the character set appropriate for your language by entering a 1 in front of it, then press Enter.

    The screen displays a list of the code pages supported by Uniface. Using the page-down and page-up keys (or roll-up and roll-down) you can scroll to the languages that are not visible.

    If the coded character set identifier (CCSID) of the job in which you are running is among the supported code pages, the installer will have placed a 1 in front of it already.

    The selected character set will be reflected in the assignment files generated by the installer, and will also be the CCSID of the UROUTER and USERVER jobs.

    If no character set is selected, or more than one is selected, or anything other than a 1 is filled in, an error message is issued, and the screen remains displayed.

  6. Specify the TCP/IP port number to which the Uniface Router should listen when you start the subsystem or run STARTUP.

    The default value is 13001, which causes the UROUTER to start listening at port 13001.

    Press Enter when you are finished editing this parameter.

  7. Specify the name of the subsystem and job queue and press Enter.

    Default names are filled in. The library name previously specified is displayed as the library where the subsystem description and the job queue will be created.

    It is recommended that you do not change the library names. The name of the subsystem can be anything you want, as long as it does not conflict with existing subsystems on your system, and follows the normal file-naming conventions.

    If you do not want to create a subsystem, but instead just use QBATCH or another existing subsystem, press F2.

  8. Specify the job description the installer will create and the profile name of the user that will be the owner of the UROUTER job, then press Enter.

    The current user name is filled in by default. However, it is recommended that you use UNIFSID as the owner of the UROUTER job. A subsystem will be created, which will have an autostart job that starts the UROUTER; the user name you fill in here will own this job; it must already exist.

    The job queue field is the same as in the previous screen, unless you pressed F2. If you pressed F2 instead of Enter, then the screen is slightly different—the default values are QBATCH and *LIBL, which already exist on most iSeries systems. No subsystem will be created, but the job queue and job description you fill in here, which must already exist, will be used instead.

    Note:  The out-of-the-box subsystem QBATCH allows only one batch job at a time. If you plan to use the QBATCH subsystem you must make sure that you set this to *NOMAX, otherwise the Uniface Router will not be able to start any Uniface Servers.

  9. Specify the type of license you will be using. You have the option of:
    • Sentinel Network Licensing using an RMS Server
    • Sentinel On-premises Served Standalone Licensing using a local license file
    • Skip to configure your licensing manually, or use DLM

    Enter a 1 in front of your chosen license type, then press Enter.

    The installer prompts you to enter the network name of the RMS server or the location of the license file, based on your selection. An error message is returned if the server or the license file cannot be found. You may proceed if you will configure this manually later.

    Note: The Sentinel RMS Server cannot be run on iSeries. To use this option, run the RMS Server remotely on another platform accessible via the network.

  10. In the next screen, review and confirm the information you have provided thus far.

    You can scroll down using the page-down (or roll-up) key.

    Up to this point, only the installation library and directory have been created; nothing has been installed yet. Press F3 to stop immediately, or press Enter to proceed with the installation.

    The installation program creates and copies the required files, and creates default assignment files. As it runs, the installer displays progress messages on the screen and also writes messages to the file install.err in the current IFS directory.

    Note:  Despite its name, the install.err file is a log file that contains progress messages as well as error messages, if any.

    The Copy files stage takes the most time—on a busy machine or slow machine, it can take up to 10 minutes. When the installation is completed successfully, you should see the word Done after each of the installer’s progress steps. If there was a problem at any stage, look in the install.err file for details.

For more information, see Installation Contents .

Related Topics