IBM Network Station

Full-Screen Solutions

Full-Screen Solutions

17 Jul 1998


http://www.ibm.com/nc/pubs

Table of Contents

Introduction

Release 2.5 Solutions

  • 3270 Emulator
  • 5250 Emulator
  • PC Desktop
  • UNIX Common Desktop Environment

    • Release 3 Solutions

  • 3270 Emulator
  • 5250 Emulator
  • PC Desktop
  • UNIX Common Desktop Environment
  • NC Navigator
  • Suppressed Login

    • Migrating Release 2.5 to Release 3

    Introduction

    When an IBM Network Station is replacing a certain type of terminal or environment, it may be desirable to override the default behavior of the IBM Network Station to behave like the terminal it is intended to replace. This document describes some solutions to configure the IBM Network Stations for some typical environments. The solutions shown in the Release 2.5 section apply to all Network Stations. The solutions shown in the Release 3 section apply to a specific user (except where indicated).

    IBM provides program support for configuration files automatically edited through the ordinary use of the IBM Network Station Manager program, and the files manually edited in accordance with the full-screen solutions in this document.

    Refer to Editing Configuration Files for information on what editor to use and tips on how to edit the configuration files.

    Release 2.5 Solutions

    These solutions show IBM supported changes that you can make by hand editing certain configuration files. The changes shown in this section apply to all IBM Network Stations.

    In this section we refer to placeholders for path names. When you see the following placeholders in the example files, replace them with the directory paths that are shown in the tables below:

    		BOOTPATH/
    AS/400 /QIBM/ProdData/NetworkStation/
    OS/390 /usr/lpp/tcpip/nstation/standard/
    PC Server /nstation/
    RS/6000 /usr/netstation/
    VM/ESA /QIBM/ProdData/NetworkStation/


    		DBOOTPATH/
    AS/400 /QIBM/ProdData/NetworkStation/
    OS/390 /usr/lpp/tcpip/nstation/standard/
    PC Server c:\nstation\ (where c:\ is the default installation drive and path)
    RS/6000 /usr/netstation/
    VM/ESA /QIBM/ProdData/NetworkStation/


    		MODS/
    AS/400 /QIBM/ProdData/NetworkStation/mods/
    OS/390 /usr/lpp/tcpip/nstation/standard/mods/
    PC Server /nstation/mods/
    RS/6000 /usr/netstation/mods/
    VM/ESA /QIBM/ProdData/NetworkStation/mods/


    		DMODS/
    AS/400 /QIBM/ProdData/NetworkStation/mods/
    OS/390 /usr/lpp/tcpip/nstation/standard/mods/
    PC Server c:\nstation\mods\ (where c:\ is the default installation drive and path)
    RS/6000 /usr/netstation/mods/
    VM/ESA /QIBM/ProdData/NetworkStation/mods/


    		NSM_PROD_SYSDEFAULTS/
    AS/400 /QIBM/ProdData/NetworkStation/SysDefaults/
    OS/390 /usr/lpp/tcpip/nstation/standard/SysDefaults/
    PC Server /nstation/ProdData/SysDef/
    RS/6000 /usr/netstation/SysDefaults/
    VM/ESA /QIBM/ProdData/NetworkStation/SysDefaults/


    		NSM_ADMIN_SYSDEFAULTS/
    AS/400 /QIBM/UserData/NetworkStation/SysDefaults/
    OS/390 /etc/nstation/system/SysDefaults/
    PC Server /nstation/UserData/SysDef/
    RS/6000 /usr/netstation/nsm/SysDefaults/
    VM/ESA /QIBM/UserData/NetworkStation/SysDefaults/


    		DNSM_ADMIN_SYSDEFAULTS/
    AS/400 /QIBM/UserData/NetworkStation/SysDefaults/
    OS/390 /etc/nstation/system/SysDefaults/
    PC Server c:\nstation\UserData\SysDef\ (where c:\ is the default installation drive and path)
    RS/6000 /usr/netstation/nsm/SysDefaults/
    VM/ESA /QIBM/UserData/NetworkStation/SysDefaults/


    		CONFIGPATH/
    AS/400 /QIBM/UserData/NetworkStation/StationConfig/
    OS/390 /etc/nstation/system/StationConfig/
    PC Server c:\nstation\configs\ (where c:\ is the default installation drive and path)
    RS/6000 /usr/netstation/configs/
    VM/ESA /QIBM/UserData/NetworkStation/StationConfig/

    Some general notes about the configuration file templates in this section:

    Notes:

    1. The pound sign # placed at the beginning of the line indicates that this line is a comment line.

    2. In the TCP/IP settings in the defaults.dft file, you can use one of two methods to resolve host names:

    3. After changing the configuration files, the Network Station must be re-started for the changes to take effect.

    3270 Emulator

    This solution allows all Network Stations to display a full screen 3270 emulator session without a login dialog.

    In this solution:

    1. Use the example below to create a defaults.dft file in the CONFIGPATH/ directory. 
      #################### 3270 full screen template ###########################################
## START CONFIGPATH/defaults.dft
## 3270 template definition
##
## START TCPIP configuration ##
## Either use name-local-cache stanza or other three lines
## Comment out one of the choices below
set tcpip-name-server-protocol = dns
set tcpip-name-servers[-1] = {"10.2.3.2"}
set tcpip-dns-default-domain = mydomain.com
set tcpip-name-local-cache = {
#       { bigsmile 10.2.3.232 }
#       { bigeasy 10.2.3.248 }
       { localhost 127.0.0.1 }
#       { sorry 10.2.3.211 }
}
## END TCPIP configuration ##
##
## START environment variables configuration ##
## Have to set these since Login is not being used
## The PATH for these values may be different between platforms
##
set pref-environment = {
	{"PATH" "MODS/"}
	{"HOME" "BOOTPATH/"}
	{"BOOTPATH" "BOOTPATH/"}
	{"LANGID" "ENU" }
	{"MRIPATH" "MRI2924"}
	{"NSM_PROD_SYSDEFAULTS" "NSM_PROD_SYSDEFAULTS/"}
	{"NSM_ADMIN_SYSDEFAULTS" "NSM_ADMIN_SYSDEFAULTS/"}
}
## END environment variables configuration ##
##
## START modules configuration ##
## set these to avoid loading unneeded modules to conserve memory
##
set modules-load-policy = {{ }}
## END modules configuration ##
##
## START screen background configuration ##
## Set this to cover any non-fit of the emulator screen
##
set pref-screen-background-type=solid-color
set pref-screen-background-color=black
## END screen background configuration ##
##
set exec-startup-commands = {
  {"ns3270 -fn 8x13,9x15,10x20,fixedR28 -LANGID ENU <Host> "}
}
## END CONFIGPATH/defaults.dft
##########################################################################################

      Notes:

      1. If TCP/IP is already working properly, remove the TCP/IP section.

      2. The LANGID value can be any value that is found in DMODS/NS3270/nls on the boot server.

      3. Use the following table to construct the set exec-startup-commands.


        Display Resolution set exec-startup-commands =
        640x480 "ns3270 -fn 8x13 -LANGID ENU <Host>"
        800x600 "ns3270 -fn 9x15 -LANGID ENU <Host>"
        800x600* "ns3270 -fn 9x15,8x13 -LANGID ENU <Host>"
        1024x768 "ns3270 -fn 10x20 -LANGID ENU <Host>"
        1024x768* "ns3270 -fn 10x20,9x15,8x13 -LANGID ENU <Host>"
        1280x1024 "ns3270 -fn fixedR28 -LANGID ENU <Host>"
        1280x1024* "ns3270 -fn fixedR28,10x20,9x15,8x13 -LANGID ENU <Host>"

        Notes:

        1. * This entry allows the user to scale down the window and font. The first font in the list (-fn) is used at startup. The other fonts are available through the Options-> Fonts pulldown menu (if the screen resolution allows).

        2. The fonts you pick must exist in one of the font directories DBOOTPATH/fonts/pcf/... Not all fonts are available on all platforms.

        3. The LANGID value can be any value that is found in DMODS/NS3270/nls on the boot server.

        4. Replace <Host> with the name or IP address of the host.

      4. If you want to run the integrated window manager, add {wm} as the first clause in the exec-startup-commands. For example: 
          set exec-startup-commands = {
  {wm}
  {"ns3270 -fn 8x13,9x15,10x20,fixedR28 -LANGID ENU <Host> "}
  }

    2. Use the example below to create a pref file in the DNSM_ADMIN_SYSDEFAULTS/ directory.
      Note:This file is normally created and edited by the IBM Network Station Manager program. If this file does not exist, you must create the file and directory. 
      ##########################################################################################
## START 3270 preferences file
## DNSM_ADMIN_SYSDEFAULTS/NS3270/pref
NS3270*KeyRemap: disable
NS3270*Keymap101Path: 0
NS3270*Keymap102Path: 0
NS3270*ColorMap: basic
NS3270*ColorMapPath: 0
NS3270*rows: 32
NS3270*cols: 80
NS3270*autoAction: false
NS3270*buttonBox: false
NS3270*Speckey: false
NS3270*Port: 23
NS3270*Graphics: false
NS3270*DefaultColorMapPath: 0
## END 3270 preferences file
##########################################################################################

    5250 Emulator

    This solution allows all Network Stations to display a full screen 5250 emulator session without a login dialog.

    In this solution:

    1. Use the example below to create a defaults.dft file in the CONFIGPATH/ directory. 
      #################### 5250 full screen template ################################################
## START CONFIGPATH/defaults.dft
## 5250 template definition
##
## START TCPIP configuration ##
## Either use name-local-cache stanza or other three lines
## Comment out one of the choices below
set tcpip-name-server-protocol = dns
set tcpip-name-servers[-1] = {"10.2.3.2"}
set tcpip-dns-default-domain = mydomain.com
set tcpip-name-local-cache = {
#       { bigsmile 10.2.3.232 }
#       { bigeasy 10.2.3.248 }
        { localhost 127.0.0.1 }
#       { sorry 10.2.3.211 }
}
## END TCPIP configuration ##
##
## START environment variables configuration ##
## Have to set these since Login is not being used
## The PATH for these values may be different between platforms
##
set pref-environment = {
	{"PATH" "MODS/"}
	{"HOME" "BOOTPATH/"}
	{"BOOTPATH" "BOOTPATH/"}
	{"LANGID" "ENU" }
	{"MRIPATH" "MRI2924"}
	{"NSM_PROD_SYSDEFAULTS" "NSM_PROD_SYSDEFAULTS/"}
	{"NSM_ADMIN_SYSDEFAULTS" "NSM_ADMIN_SYSDEFAULTS/"}
}
## END environment variables configuration ##
##
## START modules configuration ##
## set these to avoid loading unneeded modules to conserve memory
##
set modules-load-policy = {{ }}
## END modules configuration ##
##
## START screen background configuration ##
## Set this to cover any non-fit of the emulator screen
##
set pref-screen-background-type=solid-color
set pref-screen-background-color=black
## END screen background configuration ##
##
set exec-startup-commands = {{"ns5250 -geometry 9999x9999+0+0 <Host> "}}
## END CONFIGPATH/defaults.dft
##########################################################################################

      Notes:

      1. If TCP/IP is already working properly, remove the TCP/IP section.

      2. The -geometry option set to 9999x9999 works with the common 640x480, 800x600, 1024x768, and 1280x1024 monitor resolutions.

      3. Replace <Host> with the name or IP address of the host.

      4. If you want to run the integrated window manager, add {wm} as the first clause in the exec-startup-commands. For example: 
          set exec-startup-commands = {
  {wm}
  {"ns5250 -geometry 9999x9999+0+0 <Host> "}
  }

    2. Use the example below to create a pref file in the DNSM_ADMIN_SYSDEFAULTS/ directory.
      Note:This file is normally created and edited by the IBM Network Station Manager program. If this file does not exist, you must create the file and directory. 

      ##########################################################################################
## START 5250 preferences file
## DNSM_ADMIN_SYSDEFAULTS/NS5250/pref
NS5250*27x132: enable
NS5250*ImageView: disable
NS5250*ColumnSeparator: disable
NS5250*KeyRemap: disable
NS5250*ColorMap: basic
NS5250*KeyPad: disable_and_hide
NS5250*PlayBack: enable
NS5250*Control: enable
NS5250*Edit: enable
NS5250*LocalPrint: enable
NS5250*ChangeIPAddress: enable
NS5250*Command: enable
NS5250*Keymap101Path: 0
NS5250*Keymap102Path: 0
NS5250*Keymap122Path: 0
NS5250*ColorMapPath: 0
NS5250*PlayBackPath: 0
NS5250*DefaultColorMapPath: 0
## END 5250 preferences file
##########################################################################################

    PC Desktop

    This solution allows a Network Stations to display a full screen Windows desktop without a login dialog.

    In this solution:

    Use the example below to create a defaults.dft file in the CONFIGPATH/ directory. 

    #################### WinCenter full screen template ###########################################
## START CONFIGPATH/defaults.dft
## WinCenter template definition
##
## START TCPIP configuration ##
## Either use name-local-cache stanza or other three lines
## Comment out one of the choices below
set tcpip-name-server-protocol = dns
set tcpip-name-servers[-1] = {"10.2.3.2"}
set tcpip-dns-default-domain = mydomain.com
set tcpip-name-local-cache = {
#       { bigsmile 10.2.3.232 }
#       { bigeasy 10.2.3.248 }
        { localhost 127.0.0.1 }
#       { sorry 10.2.3.211 }
}
## END TCPIP configuration ##
##
## START environment variables configuration ##
## Have to set these since Login is not being used
## The PATH for these values may be different between platforms
##
set pref-environment = {
	{"PATH" "MODS/"}
	{"HOME" "BOOTPATH/"}
	{"BOOTPATH" "BOOTPATH/"}
	{"LANGID" "ENU" }
	{"MRIPATH" "MRI2924"}
	{"NSM_PROD_SYSDEFAULTS" "NSM_PROD_SYSDEFAULTS/"}
	{"NSM_ADMIN_SYSDEFAULTS" "NSM_ADMIN_SYSDEFAULTS/"}
}
## END environment variables configuration ##
##
## START xserver configuration ##
## these lines guarantee that the WinCenter server 
## will be able to display on the Network Station
set xserver-access-control-enabled = false
set xserver-access-control-enabled-default = false
## END xserver configuration ##
##
## START modules configuration ##
## set this to be empty avoid loading unneeded modules to conserve memory
##
set modules-load-policy = {{  }}
## END modules configuration ##
##
## START screen background configuration ##
## Set this to cover any non-fit of the screen
##
set pref-screen-background-type=solid-color
set pref-screen-background-color=black
## END screen background configuration ##
##
##START command to execute configuration ##
set exec-startup-commands = {
    {"wincenter <Host> -resolution fullscreen -noaudio " }
}
##
## END command to execute configuration ##
## END CONFIGPATH/defaults.dft
##########################################################################################

    Notes:

    1. If TCP/IP is already working properly, remove the TCP/IP section.

    2. Replace <Host> with the name or IP address of the host.

    UNIX Common Desktop Environment

    This solution allows all Network Stations to display a full screen UNIX common desktop environment without a login dialog.

    In this solution:

    Use the example below to create a defaults.dft file in the CONFIGPATH/ directory. 

    #################### UNIX Login full screen template ###########################################
## START CONFIGPATH/defaults.dft
## UNIX Login template definition
##
## START TCPIP configuration ##
## Either use name-local-cache stanza or other three lines
## Comment out one of the choices below
set tcpip-name-server-protocol = dns
set tcpip-name-servers[-1] = {"10.2.3.2"}
set tcpip-dns-default-domain = mydomain.com
set tcpip-name-local-cache = {
#       { bigsmile 10.2.3.232 }
#       { bigeasy 10.2.3.248 }
        { localhost 127.0.0.1 }
#       { sorry 10.2.3.211 }
}
## END TCPIP configuration ##
##
## START environment variables configuration ##
## Have to set these since Login is not being used
## The PATH for these values may be different between platforms
##
set pref-environment = {
	{"PATH" "MODS/"}
	{"HOME" "BOOTPATH/"}
	{"BOOTPATH" "BOOTPATH/"}
	{"LANGID" "ENU" }
	{"MRIPATH" "MRI2924"}
	{"NSM_PROD_SYSDEFAULTS" "NSM_PROD_SYSDEFAULTS/"}
	{"NSM_ADMIN_SYSDEFAULTS" "NSM_ADMIN_SYSDEFAULTS/"}
}
## END environment variables configuration ##
##
## START modules configuration ##
## set this to be empty avoid loading unneeded modules to conserve memory
##
set modules-load-policy = {{ }}
## END modules configuration ##
##
## START screen background configuration ##
## Set this to cover any non-fit of the screen
##
set pref-screen-background-type=solid-color
set pref-screen-background-color=black
## END screen background configuration ##
##
## START command to execute configuration ##
set exec-disabled-commands = {{ }}
set exec-startup-commands = {{ "login <Host>" }}
## END command to execute configuration ##
## END CONFIGPATH/defaults.dft
##########################################################################################

    Notes:

    1. If TCP/IP is already working properly, remove the TCP/IP section.

    2. Replace <Host> with the name or IP address of the host. The solution assumes that the target host is running a window manager such as CDE or Motif.

    Release 3 Solutions

    The following solutions provide a way to:

    The Release 2.5 solutions bypass the Network Station login. This prevents many setup functions from taking place. In Release 3, the login can be suppressed, rather than bypassed. This allows the required setup functions to take place.

    Suppression of the Network Station login means that the Network Station automatically logs itself in under a special userid. The login screen is not shown to the user. We refer to the userid that is used by the Network Station as the kiosk userid.

    In order to suppress the login, a special kiosk userid must be created on your server. For each particular appearance of a full screen application, you must create a userid. Use the Network Station Manager program to configure the full screen application for that userid. If you have more than one userid, you may want to create a user group for these userids. Each Network Station that you associate with the userid can login and automatically start a full screen application. These special kiosk userids and passwords (along with the Network Station host name or IP address that you want to associate) must be added to a special kiosk file that is encoded and saved on your server.

    If the session hangs or the configuration changes, the Network Station must be re-booted to restart the session.

    If name resolution and TCP/IP are not working properly, use the IBM Network Station Manager program to configure this information. Go to Hardware->Workstations to configure the Network Station's Hosts table and domain name server.

    In this section we refer to PRODBASE/ and USERBASE/. These are placeholders for path names. The path names for these placeholders are shown below:

    		PRODBASE/
    AS/400 /QIBM/ProdData/NetworkStation/
    OS/390 /usr/lpp/nstation/standard/
    PC Server c:\nstation\prodbase\ (where c:\ is the default installation directory and path)
    RS/6000 /usr/netstation/
    VM/ESA /QIBM/ProdData/NetworkStation/


    		USERBASE/
    AS/400 /QIBM/UserData/NetworkStation/
    OS/390 /etc/nstation/
    PC Server c:\nstation\userbase\ (where c:\ is the default installation directory and path)
    RS/6000 /usr/netstation/nsm/
    VM/ESA /QIBM/UserData/NetworkStation/

    3270 Emulator

    This solution allows a Network Station to behave like a 3270 terminal.

    __  1.

    Create a userid on your server that can be used for the kiosk userid.

    __  2.

    Use the IBM Network Station Manager to configure the kiosk userid for the following:

    __  a.

    Disable the window manager. Select Startup->Environment Variables->User defaults. Set RUNWM to NO.

    __  b.

    Remove the menu bar. Select Startup->Menus->User defaults. Select Standard desktop without menu bar.

    __  c.

    Autostart a 3270 session. Select Startup->Programs->User defaults. Under 3270 Sessions to AutoStart:

    __  1)

    Enter the name or address of the System/390 server. Use ${BOOTHOST} if you want to connect to the boot server.

    __  2)

    Set the Width and Height to match the monitor resolution of the Network Station. If your Network Stations have different monitor resolutions, you need to create at least one kiosk userid for each monitor resolution.

    __  3)

    Set the Horizontal and Vertical offsets to 0.

    __  4)

    All other fields may be left as defaults. Make sure that no other programs are configured to autostart for this user on the user, group, or system levels.

    __  d.

    Set the background color to black. Select Hardware->Workstations->User defaults. Set the Desktop background color to black.

    __  3.

    You may want to set other options for the kiosk userid. For example:

    • Remove 3270 dropdown menus. Select 3270->User defaults.

    • Set language. Select Languages->User defaults.

    __  4.

    Create the kiosks.nsl file. See Suppressed Login.

    5250 Emulator

    This solution allows a Network Station to behave like a 5250 terminal.

    __  1.

    Create a userid on your server that can be used for the kiosk userid.

    __  2.

    Use the IBM Network Station Manager to configure the kiosk userid for the following:

    __  a.

    Disable the window manager. Select Startup->Environment Variables->User defaults. Set RUNWM to NO.

    __  b.

    Remove the menu bar. Select Startup->Menus->User defaults. Select Standard desktop without menu bar.

    __  c.

    Autostart a 5250 session. Select Startup->Programs->User defaults. Under 5250 Sessions to AutoStart:

    __  1)

    Enter the name or address of the AS/400 system. Use ${BOOTHOST} if you want to connect to the boot server.

    __  2)

    Set the Width and Height to match the monitor resolution of the Network Station. If your Network Stations have different monitor resolutions, you need to create at least one kiosk userid for each monitor resolution.

    __  3)

    Set the Horizontal and Vertical offsets to 0.

    __  4)

    All other fields may be left as defaults. Make sure that no other programs are configured to autostart for this user on the user, group, or system levels.

    __  d.

    Set the background color to black. Select Hardware->Workstations->User defaults. Set the Desktop background color to black.

    __  3.

    You may want to set other options for the kiosk userid. For example:

    • Remove 5250 dropdown menus. Select 5250->User defaults.

    • Set language. Select Languages->User defaults.

    __  4.

    Create the kiosks.nsl file. See Suppressed Login.

    PC Desktop

    This solution allows a Network Station to behave like a Windows PC desktop.

    __  1.

    Create a userid on your server that can be used for the kiosk userid.

    __  2.

    Use the IBM Network Station Manager to configure the kiosk userid for the following:

    __  a.

    Disable the window manager. Select Startup->Environment Variables->User defaults. Set RUNWM to NO.

    __  b.

    Remove the menu bar. Select Startup->Menus->User defaults. Select Standard desktop without menu bar.

    __  c.

    Do one of the following:

    • To autostart a session to a WinCenter server using X protocol, select Startup->Programs->User defaults. Under Remote Programs to AutoStart:

      __  1)

      Enter the name or address of the Remote host (WinCenter server).

      __  2)

      Set the Program to run to wincenter.

      __  3)

      Set the Optional parameters to -display ${IP}:0 -resolution fullscreen -noaudio.

      __  4)

      Make sure that no other programs are configured to autostart for this user on the user, group, or system levels.

    • To autostart a session using ICA protocol, select Startup->Programs->User defaults. Under Local Programs to AutoStart:

      __  1)

      Set the Program to run to icaclnt.

      __  2)

      Set Parameters to -host MYHOST -geometry fullscreen. Where MYHOST is the name or IP address of the ICA server.

      __  3)

      Make sure that no other programs are configured to autostart for this user on the user, group, or system levels.

    __  d.

    Set the background color to black. Select Hardware->Workstations->User defaults. Set the Desktop background color to black.

    __  3.

    Create the kiosks.nsl file. See Suppressed Login.

    UNIX Common Desktop Environment

    This solution allows a Network Station to behave like an X-terminal.

    __  1.

    Create a userid on your server that can be used for the kiosk userid.

    __  2.

    Use the IBM Network Station Manager to configure the kiosk userid for the following:

    __  a.

    Disable the window manager. Select Startup->Environment Variables->User defaults. Set RUNWM to NO.

    This solution assumes that the target host is running a window manager such as CDE or Motif.

    __  b.

    Remove the menu bar. Select Startup->Menus->User defaults. Select Standard desktop without menu bar.

    __  c.

    Autostart an X session. Select Startup->Programs->User defaults. Under Local Programs to AutoStart:

    __  1)

    Enter the Program to run as login.

    __  2)

    Enter the Parameters as the name or IP address of the X session server.

    __  3)

    Make sure that no other programs are configured to autostart for this user on the user, group, or system levels.

    __  d.

    Set the background color to black. Select Hardware->Workstations->User defaults. Set the Desktop background color to black.

    __  3.

    Edit the USERBASE/StationConfig/defaults.dft file.

    This file can be created if it does not exist. Add the following line to the file: 

    set exec-disabled-commands = {{ }}

    This line guarantees that the X login program is allowed to run on all the Network Stations. This line applies to all Network Stations.

    __  4.

    Create the kiosks.nsl file. See Suppressed Login.

    NC Navigator

    This solution allows a Network Station to display a full screen NC Navigator session.

    __  1.

    Create a userid on your server that can be used for the kiosk userid.

    __  2.

    Use the IBM Network Station Manager to configure the kiosk userid for the following:

    __  a.

    Remove the menu bar. Select Startup->Menus->User defaults. Select Standard desktop without menu bar.

    __  b.

    Autostart a NC Navigator session. Select Startup->Programs->User defaults. Under NC Navigator Sessions to AutoStart:

    __  1)

    Enter the URL that you want to be the home page.

    __  2)

    Set the Width and Height to match the monitor resolution of the Network Station.

    __  3)

    Set the Horizontal and Vertical offsets to 0.

    __  4)

    All other fields may be left as defaults. Make sure that no other programs are configured to autostart for this user on the user, group, or system levels.

    __  c.

    Set the background color to black. Select Hardware->Workstations->User defaults. Set the Desktop background color to black.

    __  3.

    You may want to set other options for the kiosk id. For example:

    • Set preferences for NC Navigator, such as enabling Java. Select Internet->NC Navigator.

    • Set network parameters, such as manual proxies. Select Internet->Network.

    __  4.

    Create the kiosks.nsl file. See Suppressed Login.

    __  5.

    If you want to customize the window manager, create and edit the USERBASE/SysDef/pref.dft file. Use the example statements below when you do not want the kiosk users to be able close or minimize the NC Navigator Window. Note that these statements will affect all Network Stations (not just kiosks) that run NC Navigator. 

    ! This statement controls the window manager functions that are available for the NC Navigator window.
! This statement tells the window manager to allow no window functions.
! If a plus sign precedes the first function, then the window manager starts with no function and adds functions.
! If a minus sign preceeds the first function, then the window manager starts with all functions and starts subtracting functions.
! The function values that are available are: all, none, resize, move, minimize, and close.
mwm*Navio.clientFunctions: none
 
! This statement controls the window decorations that are around the NC Navigator window.
! This statement tells the window manager to show the title and border.
! If a plus sign precedes the first decoration, then the window manager starts
with no decorations and adds decorations.
! If a minus sign preceeds the first decoration, then the window manager starts
with all decorations and starts subtracting decorations.
! The decorations values that are available are: all, maximize, minimize, none, resizeh (resize handles), menu, border, and title.
mwm*Navio.clientDecoration: +border +title

    Suppressed Login

    In order to keep the login window from being displayed, do the following:

    __  1.

    Ensure that the following PTFs are applied for your platform:

    • AS/400 - SF49127 (5648-C05)

    • VM/ESA - UA00045 (APAR SA74942)

    __  2.

    Attention: Review the following security considerations:
    All Platforms

    • The unencoded file contains the unencoded passwords of the kiosk userids. It should only be accessible by the system administrator.

    • The encoding program should only be accessible by the system administrator.

    • The kiosk userids associated with suppression of login should have very limited authority. Userids should be created similar to guest userids.

    • The kiosks.nsl file should only be writeable by a system administrator.

    • If the file system cannot prevent a general user from creating the file, an empty file should be created and protected by the system administrator.

    AS/400

    • User profiles associated with suppression of login should have initial menu = *SIGNOFF, initial program = *NONE, limit capabilities = *YES, special authorities = *NONE, and group profile = *NONE.

    • Change the authority of the encoded file so that public is excluded from reading or writing, QTFTP has read access only, and the system administrator has write access. Write access is needed by the system administrator when using the encoding utility. The following commands could be used to restrict access to the encoded file: 
      CHGAUT OBJ('/qibm/prodata/networkstation/configs/kiosks.nsl')
USER (*PUBLIC) DTAAUT(*EXCLUDE) OBJAUT(*NONE)
 
CHGAUT OBJ('/qibm/prodata/networkstation/configs/kiosks.nsl')
USER (*QTFTP) DTAAUT(*R) OBJAUT(*NONE)
 
CHGAUT OBJ('/qibm/prodata/networkstation/configs/kiosks.nsl')
USER (sysadmin) DTAAUT(*W) OBJAUT(*NONE)

      Where sysadmin is the userid of the system administrator.

    • You may want to use the QTFTP user profile as a kiosk id. This special case user profile does not require a password to login.

    PC Server

    • The unencoded file should NOT be kept in any subdirectory of \nstation\, since clients have NFS and TFTP read access to the entire \nstation\ tree.

    • If the unencoded file is kept on the server, it should be placed in a directory with appropriate NTFS access control. For example, all access control entries except for the Administrators group could be removed from the file.

    • Consider keeping the unencoded file on a diskette and stored in a secure location.

    • Remember that the kiosk userids associated with suppression of login must be added to the NSMUser group through the User Manager.

    __  3.

    Review these DHCP considerations:

    • Suppression of login relies on the Network Station being associated with an IP address or IP host name that can be matched to an IP address or IP host name in the kiosks file. DHCP needs to be configured so that the Network Station is assigned a fixed address or an address in a designated range.

    • Wildcards are allowed in the kiosks file. This allows a match to an address in a designated address range.

    • The userid and password for the first IP address or IP host name match that is found in the kiosks file is used for authentication. Searching the file stops after the first match is found.

    __  4.

    Create a file using the security consideration mentioned above. Use any file name other than kiosks.nsl. For EBCDIC platforms (AS/400, VM/ESA, or OS/390), the unencoded file must be created in EBCDIC format, not ASCII format. If the unencoded file is created in ASCII format on these platforms, unpredictable results may occur.

    __  5.

    Edit the file to add the Network Station IP address or host name, kiosk userid, and password. The values should be separated by one or more spaces. For example: 

    10.9.99.99 kioskid1 password1
kiosk      kioskid2 password2

    In this example, the IP address 10.9.99.99 is associated with kioskid1. The Network Station at 10.9.99.99 will auto-login under the userid of kioskid1 and use the preferences of kioskid1.

    You can use wildcards (that match patterns) to specify the IP address or hostname. Wildcard usage is in regular expression notation.
    Pattern Description
    string String (no special characters) - a string with no special characters matches the first IP address or host name that contains the string.
    [set] Set - matches a single character specified by the set of single characters within the square brackets.
    ^ Caret - signifies the characters following the ^ are the beginning of the IP address or IP host name.
    $ Dollar - signifies the characters preceding the $ are the end of the IP address or IP host name.
    . Period - signifies any one character. The period means match any character, not just the period in an IP address.
    * Asterisk - signifies zero or more of preceding character.
    \ Backslash - signifies an escape character. When preceding any of the characters that have special meaning, the escape character removes any special meaning from the character. The backslash is useful to remove special meaning from a period in an IP address.

    For example:
    Pattern Examples of IP addresses or IP host names that match
    10.2.1.9 10.2.1.9, 10.2.139.6, 10.231.98.6
    ^10\.2\.1\.9$ 10.2.1.9
    ^10\.2\.1\.1[0-5]$ 10.2.1.10, 10.2.1.11, 10.2.1.12, 10.2.1.13, 10.2.1.14, 10.2.1.15
    kiosk kiosk01, mykiosk, akioskbc
    ^kiosk$ kiosk
    ^kiosk0[0-4][0-9]$ kiosk000 through kiosk049
    kiosk[3-8] kiosk3, mykiosk4, akiosk5b
    ^kiosk kiosk01, kiosk
    kiosk$ mykiosk, kiosk, 3kiosk
    kiosk... kiosk123, mykioskabc, akiosk09bcd
    kiosk*1 kiosk1, mykios1, akiosk1abc, kioskkkkkk12
    ^kiosk0.. kiosk001, kiosk099, kiosk0abcd
    ^kiosk0..$ kiosk001, kiosk099

    __  6.

    Run the program to encode the file. The program creates the kiosks.nsl file and places it in theUSERBASE/Station Config/ directory (PRODBASE/configs\ for PC Server).
    Platform Program Syntax
    AS/400 
    CALL PGM(QYTC/QYTCMTKS)
PARM('/QSYS.LIB/MYLIB.LIB/MYFILE.FILE/KIOSKS.MBR' '37')

    Where:

    • '/QSYS.LIB/MYLIB.LIB/MYFILE.FILE/KIOSKS.MBR' is the full path and name of the unencoded file.

    • '37' is the CCSID value. This parameter is optional and defaults to CCSID 37 if omitted.

    PC Server 
    d:\nstation\servbase\bin\nsmkiosk x:\myDir\kiosk.source

    Where:

    • d:\ is the default installation drive and path.

    • x:\myDir\kiosk.source is the full path and name of the unencoded file.

    VM/ESA 
    MOUNT /../VMBFS:VMSYS:ROOT/ / GLOBAL LOADLIB SCEERUN NSMKIOSK fn.ft.fm

    Where:

    • fn is the filename of the unencoded file.

    • ft is the filetype of the unencoded file.

    • fm is the filemode of the unencoded file.

    If an error code is returned by the program, use the following table for an explanation:
    Error code Description Action
    1 The unencoded filename parameter is not specified. Make sure that you specified a parameter with the name of the unencoded file.
    2 The CCSID parameter is not valid. Make sure that you specified a valid CCSID.
    3, x The unencoded file cannot be opened or read. Make sure that you have specifed the correct full path and name of the unencoded file. Make sure that the user running the encoding program has the correct authority to read the unencoded file.
    4, x The encoded file cannot be created or written. Make sure that the user running the encoding program has the correct authority to create or write the encoded file.
    5 An internal codepage conversion error has occured. Contact IBM service.
    6 There is invalid data in the unencoded file. Make sure that the unencoded file is created following the instuctions in step 5. If you specified a CCSID as an input parameter, make sure that it matches the CCSID with which the file was created.

    Migrating Release 2.5 to Release 3

    If you created full screen sessions by using any of the Release 2.5 solutions, you need to do the following before you install Release 3:

    __  1.

    Remove all lines that have been added to defaults.dft. If you added lines to allow TCP/IP name resolution (DNS or name cache) to work, then you can leave these lines in the file.

    __  2.

    If you edited DNSM_ADMIN_SYSDEFAULTS/NS3270/pref, note that, with the exception of the NS3270*autoAction line, all lines are now configurable through the Release 3 Network Station Manager program. You should do the following:

    __  a.

    Delete the NS3270*autoAction line from DNSM_ADMIN_SYSDEFAULTS/NS3270/pref.

    __  b.

    Use the IBM Network Station Manager program to change 3270 preferences.

    __  3.

    Install IBM Network Station Manager Release 3.

    __  4.

    Add the NS3270*autoAction line to USERBASE/SysDef/pref.dft.

    Notes:

    1. If you edited DNSM_ADMIN_SYSDEFAULTS/NS5250/pref, note that all lines are now configurable through the Release 3 Network Station Manager program. For Release 3, do not edit DNSM_ADMIN_SYSDEFAULTS/NS5250/pref. This file is Unicode format in Release 3. Use the IBM Network Station Manager program to change 5250 preferences.

    2. For Release 3, do not edit DNSM_ADMIN_SYSDEFAULTS/NS3270/pref. This file is Unicode format in Release 3. Use the IBM Network Station Manager program to change 3270 preferences.

    NC Home
    IBM HomeOrderSearchContact IBMPrivacyLegal