Configuration Files
Configuration Files
9 Nov 1998
http://www.ibm.com/nc/pubs
Release 2.5 Configuration Files
Release 3 Configuration Files
Introduction
IBM Network Station Manager Program Setup Tasks
Server Directory Structure
Hardware Files
Shipped Configuration Files
System-Wide Configuration Files
Individual IBM Network Station Configuration Files
Group Configuration Files
Individual User Configuration Files
Application Files
Product Configuration Files
Shipped Configuration Files
System-Wide Configuration Files
Group Configuration Files
Individual User Configuration Files
Startup Files
Shipped Startup Files
System-Wide Startup Files
Group Startup Files
Individual User Startup Files
How the Network Station Reads Configuration Files
Configuration File Download Sequence
Access to Server Directories
Migrating to Release 3
Editing Configuration Files
Attention: This information is intended for advanced
users that understand the consequences of directly editing configuration
files. The IBM Network Station Manager program is the preferred method
to change configuration parameters. These parameters are subject to
change at any time. IBM provides program support for configuration
files that are automatically edited through ordinary use of the IBM Network
Station Manager program, and the files that are manually edited in accordance
with the
full-screen solutions
.
The IBM Network Station network computer (hereafter referred to as
Network Station) configuration files contain parameters (or settings) that set
the configuration of the IBM Network Station. Most frequently used
parameters can be set through the IBM Network Station Manager program.
Other parameters can only be set through the use of editable configuration
files. A description of these parameters can be found in NCDware's
Remote Configuration Parameter Quick Reference. You can
obtain this document from Network Computing Devices, Inc. (the US
telephone number is 650-694-0650). This information is also available
on some platforms in the following files:
- RS/6000 - /usr/netstation/configs/configd.doc
- OS/390 - /usr/lpp/tcpip/nstation/standard/StationConfig/configd.doc
- PC Server - d:\nstation\configd2.doc where d: is a
drive letter
Note: | The files described in this section contain hardware settings. Do not
confuse hardware settings with application settings and startup
settings.
|
The following tables list the configuration files that are shipped with
the IBM Network Station Manager program. The tables indicate which
files can be edited and which files should not be edited.
Attention: Do not edit any files that are marked No in the
Edit column of the following tables. If you edit these files, your
changes may be overwritten by the IBM Network Station Manager program, and
they may not be migrated in future releases.
The settings in these files are the basic system-wide settings.
These settings apply to all IBM Network Stations.
File Name
| Edit
| Description
|
standard.nsm
| No
| This is the master file that controls the other configuration files
downloaded by the IBM Network Station.
|
required.nsm
| No
| This file contains the settings for base IBM Network Station
functions. These settings are not configurable through the IBM Network
Station Manager program.
|
control.nsm
| No
| This file contains the default settings in the IBM Network Station
Manager program.
|
hosts.nsm
| No
| This file contains TCP/IP settings set through the IBM Network Station
Manager program.
|
defaults.nsm
| No
| This file contains the settings set through the IBM Network Station
Manager program.
|
defaults.dft
| Yes
| This file may be created if it does not exist. Configuration
settings added to this file take precedence over settings in
required.nsm, control.nsm, and defaults.nsm. IBM
Network Station Manager program does not read or write this file.
|
local.nsm
| Yes
| Found on the RS/6000 platform only. This file is created during
RS/6000 installation with settings specific to the system where the IBM
Network Station Manager program is being installed. This file may be
edited by customers and changes are migrated on the next installation.
|
The defaults.dft file is in the following directory:
AS/400
| /QIBM/UserData/NetworkStation/StationConfig/
|
PC Server
| d:\nstation\configs\ (where d: is a drive letter)
|
OS/390
| /etc/nstation/system/StationConfig/
|
RS/6000
| /usr/netstation/configs/
|
VM/ESA
| /QIBM/UserData/NetworkStation/StationConfig/
|
The local.nsm file is in the following directory:
/usr/netstation/configs/.
These files are specific to a particular IBM Network Station.
The settings in these files take precedence over the system-wide files.
File Name
| Edit
| Description
|
"name"
| No
| This is the master file that controls the other configuration files
called "name". Where "name" is the TCP/IP host name of the IBM Network
Station.
|
"name".nst
| No
| This file contains the settings that are set through the IBM Network
Station Manager program for the IBM Network Station called "name".
|
"name".trm
| Yes
| This file cannot be edited until it is created by the IBM Network Station
Manager program. The IBM Network Station Manager program creates this
file when the IBM Network Station is configured. Settings added to this
file take precedence over settings in the "name".nst. The IBM
Network Station Manager program does not read or write this file.
|
The "name".trm files are in the following directory:
AS/400
| /QIBM/UserData/NetworkStation/StationConfig/
|
PC Server
| d:\nstation\configs\ (where d: is a drive letter)
|
OS/390
| /etc/nstation/system/StationConfig/
|
RS/6000
| /usr/netstation/configs/
|
VM/ESA
| /QIBM/UserData/NetworkStation/StationConfig/
|
These files are specific to a particular IBM Network Station
user. The settings in these files take precedence over the system-wide
files and individual Network Station files.
File Name
| Edit
| Description
|
"username".nsu
| No
| This file contains the settings that are set through the IBM Network
Station Manager program for the IBM Network Station user called
"username". Where "username" is the name of the user.
|
"username".usr
| Yes
| This file cannot be edited until it is created by the IBM Network Station
Manager program. The IBM Network Station Manager program creates this
file when the IBM Network Station user is configured. Settings added to
this file take precedence over settings in the "username".nsu.
The IBM Network Station Manager program does not read or write this
file.
|
The "username".usr files are in the following directory:
AS/400
| /QIBM/UserData/NetworkStation/"username"/
|
PC Server
| d:\nstation\userdata\"username"\ (where d: is a drive letter)
|
OS/390
| /etc/nstation/user/"username"/nsm/
|
RS/6000
| /usr/netstation/nsm/"username"/
|
VM/ESA
| /QIBM/UserData/NetworkStation/"username"/
|
The sequence that the configuration files are downloaded is
important. In the case of conflicting parameters appearing in two
files, the last file that is downloaded sets the parameter. The
configuration files are downloaded from the server to the IBM Network Station
in the following order:
__ 1.
| During boot (pre-login):
__ a.
| Download system-wide files (apply to all IBM Network Stations):
__ 1)
| standard.nsm
| __ 2)
| required.nsm
| __ 3)
| control.nsm
| __ 4)
| local.nsm (editable, RS/6000 only)
| __ 5)
| hosts.nsm
| __ 6)
| defaults.nsm
| __ 7)
| defaults.dft (editable)
|
| __ b.
| Download files associated with a particular IBM Network Station:
__ 1)
| "name"
| __ 2)
| "name".nst
| __ 3)
| "name".trm (editable)
|
|
| __ 2.
| During login
- Download files associated with the user
__ a.
| "username".nsu
| __ b.
| "username".usr (editable)
|
|
If you have already changed one or more of the files
that should not be edited, you need to do the following steps. If you
do not make these changes, your settings will be lost when you install Release
3.
- If you changed standard.nsm, required.nsm,
control.nsm, hosts.nsm, or defaults.nsm, move the added
or changed statements in those files to the defaults.dft file.
- If you changed any "name" or "name".nst files, move the added or
changed statements in those files to "name".trm files.
- If you changed any "username".nsu files, move the added or changed
statements in those files to "username".usr files.
- If you changed any other Network Station Manager file, see Migrating to Release 3 for instructions on how to keep these changes in Release
3.
- If you created a new file and changed standard.nsm to include the
new file, move the statements in the new file to the defaults.dft
file.
Attention: Do not simply copy the contents of the changed
files to the editable files. This may cause unpredictable
results. Move only the new or changed information to the editable
files.
Attention: This information is intended for advanced
users that understand the consequences of directly editing configuration
files. The IBM Network Station Manager program is the preferred method
to change configuration parameters. These parameters are subject to
change at any time. IBM provides program support for configuration
files that are automatically edited through ordinary use of the IBM Network
Station Manager program, and the files that are manually edited in accordance
with the
full-screen solutions
.
If you decide to hand edit configuration files, the changes that you make
may conflict with IBM's default parameter settings, causing errors on the
Network Station. Your changes may conflict with configuration changes
made through the IBM Network Station Manager program.
The information in this section applies to Version 1 Release 3 of the IBM
Network Station Manager licenced program.
IBM Network Station configuration files contain parameters (or
settings) that set the configuration of the IBM Network Station. Most
frequently used parameters can be set through the IBM Network Station Manager
program. Other parameters can only be set through the use of editable
configuration files.
Configuration files are organized into three groups: hardware,
application, and startup. Hardware configuration files contain hardware
and operating system settings such as keyboard, monitor, and printers.
Application configuration files contain settings for applications that are run
by the user such as the 3270 and 5250 emulators, NC Navigator, and
Login. Startup configuration files contain the list of applications
that are launched for the user, the user environment variables, and the user
menu bar buttons.
Within these groups there are three types of configuration files as defined
below:
Type
| Description
|
1
| This type of file is shipped from IBM and is replaced by the installation
program.
|
2
| This type of file is created through the use of the IBM Network Station
Manager program and is migrated from release to release. This file is
not replaced by the installation program.
|
3
| This type of file can be edited by the user. This type of file is
not migrated from release to release and is not replaced by the installation
program. Some of these files are created by the user. When you
create these files, make sure that they are created with the same file system
authorities as the Type 1 and Type 2 files.
|
The files that are created through the IBM Network Station Manager program
(Type 2) can have different scopes.
- System-wide configuration files apply to all Network Stations or
users.
- Individual IBM Network Station configuration files apply to a particular
Network Station.
- Individual user configuration files apply to a particular user.
- Group configuration files apply to a group of users.
Attention: Do not edit any files that are marked No in the
Edit column of the following tables. If you edit these files, your
changes may be overwritten by the IBM Network Station Manager program, and
they may not be migrated in future releases.
This following table shows which configuration files are affected by
setting preferences in the Setup Tasks menu of the IBM Network Station Manager
program.
To find which particular file is affected, use the table below to find the
file catagory, then go to the section for that file catagory. For
example, if you change NC Navigator preferences for a group, the affected file
would be listed in the Group Configuration Files table under the Application
Files catagory.
Files
| Setup Tasks
|
Hardware Files
|
- Hardware->Workstations
- Hardware->Printers
- Internet->Applet Viewer
|
Application Files
|
- Desktop->Standard Desktop
- 5250
- 3270
- Internet->NC Navigator
|
Startup Files
|
- Startup->Programs
- Startup->Menus
- Startup->Environment Variables
- Internet->Network
- Language
- Select User's Group
|
This section describes the directories used by the IBM Network Station
Manager program for each server platform. In this section we refer to
PRODBASE\ and USERBASE\. These are placeholders for path names.
The path names for the 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
drive 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
drive and path)
|
RS/6000
| /usr/netstation/nsm/
|
VM/ESA
| /QIBM/UserData/NetworkStation/
|
Note: | In this section we label the IBM Network Station program directories as you
would see them on the server. When Network Stations access the
directories, they may use a different path. See How
the Network Station Reads Configuration Files for more information.
|
The following tables list the hardware configuration files that are
used by the IBM Network Station Manager program. The tables indicate
which files can be edited and which files should not be edited.
Hardware configuration files contain hardware and operating system settings
such as keyboard, monitors, and printers.
A description of the hardware configuration parameters can be found in
NCDware's Remote Configuration Parameter Quick
Reference. You can obtain this document from Network Computing
Devices, Inc. (the US telephone number is 650-694-0650).
This information is also available on some platforms in the following
files:
- RS/6000 - /usr/netstation/configs/configd.doc
- OS/390 - /usr/lpp/nstation/standard/StationConfig/configd.doc
- PC Server - d:\nstation\configd2.doc where d: is a
drive letter
The settings in these files are the hardware configuration defaults in
the IBM Network Station Manager program. These settings apply to all
IBM Network Stations.
File Name
| Type
| Edit
| File Format
| Description
|
standard.nsm
| 1
| No
| ASCII
| This is the master file that controls the other configuration files
downloaded by the IBM Network Station.
|
required.nsm
| 1
| No
| ASCII
| This file contains the settings for base IBM Network Station
functions. These settings are not configurable through the IBM Network
Station Manager program.
|
control.nsm
| 1
| No
| ASCII
| This file contains the default settings in the IBM Network Station
Manager program.
|
These files are located in PRODBASE/StationConfig/. For PC Server,
these files are located in PRODBASE/configs\.
The settings in these files are the basic system-wide settings.
These settings override the shipped files and apply to all IBM Network
Stations.
File Name
| Type
| Edit
| File Format
| Description
|
hosts.nsm
| 2
| No
| ASCII
| This file contains domain name server settings set through the IBM
Network Station Manager program.
|
defaults.nsm
| 2
| No
| ASCII
| This file contains the settings set through the IBM Network Station
Manager program.
|
defaults.dft
| 3
| Yes
| ASCII
| This file may be created if it does not exist.
|
local.nsm
| 3
| Yes
| ASCII
| Found on the RS/6000 platform only. This file is created during
RS/6000 installation with settings specific to the system where the IBM
Network Station Manager program is being installed. This file may be
edited by customers and changes are migrated on the next installation.
The local.nsm file is in the following directory:
/usr/netstation/configs/.
|
These files are located in USERBASE/StationConfig/. For PC Server,
these files are located in PRODBASE/configs\.
These files are specific to a particular IBM Network Station. The
settings in these files take precedence over the system-wide files.
File Name
| Type
| Edit
| File Format
| Description
|
"name"
| 2
| No
| ASCII
| This is the master file that controls the other configuration files
called "name". Where "name" is the TCP/IP host name, IP address (dotted
decimal), or MAC address (lower case, no colons) of the IBM Network
Station. The host name must match what the Network Station is told that
its name is by DHCP or BOOTP.
|
"name".nst
| 2
| No
| ASCII
| This file contains the settings that are set through the IBM Network
Station Manager program for the IBM Network Station called "name".
|
"name".trm
| 3
| Yes
| ASCII
| This file cannot be edited until it is created by the IBM Network Station
Manager program. The IBM Network Station Manager program creates this
file when the "name" IBM Network Station has preferences configured.
The IBM Network Station Manager program does not read or write this
file.
|
These files are located in USERBASE/StationConfig/. For PC Server,
the files are located in PRODBASE/configs/.
These files are specific to a particular group of IBM Network Station
users. The settings in these files take precedence over the system-wide
files and the individual Network Station files.
File Name
| Type
| Edit
| File Format
| Description
|
"groupname".nsg
| 2
| No
| ASCII
| This file contains the settings that are set through the IBM Network
Station Manager program for the IBM Network Station group of users called
"groupname". Where "groupname" is the name of the group of
users.
|
"groupname".grp
| 3
| Yes
| ASCII
| This file cannot be edited until it is created by the IBM Network Station
Manager program. The IBM Network Station Manager program creates this
file when the IBM Network Station group of users is configured. The IBM
Network Station Manager program does not read or write this file.
|
These files are located in USERBASE/groups/"groupname"/.
These files are specific to a particular IBM Network Station
user. The settings in these files take precedence over the system-wide
files, individual IBM Network Station files, and group files.
File Name
| Type
| Edit
| File Format
| Description
|
"username".nsu
| 2
| No
| ASCII
| This file contains the settings that are set through the IBM Network
Station Manager program for the IBM Network Station user called
"username". Where "username" is the name of the user.
|
"username".usr
| 3
| Yes
| ASCII
| This file cannot be edited until it is created by the IBM Network Station
Manager program. The IBM Network Station Manager program creates this
file when the IBM Network Station "username" has preferences
configured. The IBM Network Station Manager program does not read or
write this file.
|
These files are found in USERBASE/users/"username"/.
The following tables list the application files. There are four
different applications that can be configured for the Network Station.
The tables indicate which files can be edited and which files should not be
edited. Application configuration files contain settings (X-resources)
for applications that are run by the user such as the 3270 and 5250 emulators,
NC Navigator, and the Desktop (X-Windows) Manager.
The settings in these files are shipped with the applications.
They are not configurable through the IBM Network Station Manager
program.
File Name
| Type
| Edit
| File Format
| Description
|
pref
| 1
| No
| ASCII
| This file contains the settings for the base NC Navigator
functions. The file is located at PRODBASE/mods/NAV/.
|
resources.nsl
| 1
| No
| ASCII
| This file contains the settings for the base IBM Network Station Login
functions. This file is located at PRODBASE/StationConfig/. For
PC Server, this file is located at PRODBASE/Configs/.
|
Login
| 1
| No
| Unicode
| This file contains the base translated settings for IBM Network Station
Login. This file is located at PRODBASE/nls/"locale"/MRI/.
|
boot.nsl
| 1
| No
| ASCII
| This file is used by IBM Network Station Login to indicate the file
service protocol to use to the boot server. The file is located at
PRODBASE/.
|
nsl.dft
| 3
| Yes
| ASCII or Unicode
| This file may be created if it does not exist. The settings (X
resources) in this file allow IBM Network Station Login to be
customized. For example, the appearance of the login screen can be
customized. This file is located at USERBASE/StationConfig/. For
PC Server, this file is located at PRODBASE/Configs.
|
kiosks.nsl
| 3
| Yes*
| Encoded*
| The settings in this file may be used to suppress the Network Station
login screen. This file is located at USERBASE/StationConfig/.
For PC Server, this file is located at PRODBASE/Configs\. *See
Suppressed Login
for more information about how to create this file.
|
The settings in these files are the application configuration defaults
in the IBM Network Station Manager program. These settings are applied
to all IBM Network Station users for the appropriate application.
File Name
| Type
| Edit
| File Format
| Description
|
pref (Nav)
| 1
| No
| Unicode
| This file contains the default settings for the NC Navigator. This
file overrides the NC Navigator pref product file.
|
pref (NCDwm)
| 1
| No
| Unicode
| This file contains the default settings for the X-window manager.
For Release 3, the Motif Window Manager (mwm) is used. Although the
directory is NCDwm, this file actually contains the mwm resources.
|
pref (NS3270)
| 1
| No
| Unicode
| This file contains the default settings for the 3270 emulator.
|
pref (NS5250)
| 1
| No
| Unicode
| This file contains the default settings for the 5250 emulator.
|
These files are located at PRODBASE/SysDef/"application"/.
The settings in these files are the basic system-wide settings.
These settings override the shipped files and apply to all IBM Network Station
users.
File Name
| Type
| Edit
| File Format
| Description
|
pref (Nav)
| 2
| No
| Unicode
| This file contains the system-wide settings for the NC Navigator, that
are set through the IBM Network Station Manager program.
|
pref (NCDwm)
| 2
| No
| Unicode
| This file contains the system-wide settings for the X-window manager,
that are set through the IBM Network Station Manager program. For
Release 3, the Motif Window Manager (mwm) is used. Although the
directory is NCDwm, this file actually contains mwm resources.
|
pref (NS3270)
| 2
| No
| Unicode
| This file contains the system-wide settings for the 3270 emulator, that
are set through the IBM Network Station Manager program.
|
pref (NS5250)
| 2
| No
| Unicode
| This file contains the system-wide settings for the 5250 emulator, that
are set through the IBM Network Station Manager program.
|
pref.dft
| 3
| Yes
| ASCII or Unicode
| This file may be created if it does not exist. Settings (X
resources) may be added to this file to customize any application except NC
Navigator. For the Window Manager, mwm resources should be used, not
NCDwm. NOTE: Configuration settings added to this file take
precedence over NCDwm, NS3270, NS5250, NCDterm, and Login pref files at all
levels.
|
pref.dft (Nav)
| 3
| Yes
| ASCII or Unicode
| This file may be created if it does not exist. The settings (X
resources) in this file allow the NC Navigator to be customized.
Configuration settings added to this file take precedence over settings in the
system-wide NC Navigator pref file.
|
The file pref.dft is located at USERBASE/SysDef/. All of the
other files are located at USERBASE/SysDef/"application"/.
These files are specific to a particular group of IBM Network Station
users. These settings take precedence over the system-wide
files.
File Name
| Type
| Edit
| File Format
| Description
|
pref (Nav)
| 2
| No
| Unicode
| This file contains the group settings for the NC Navigator, that are set
through the IBM Network Station Manager program.
|
pref (NCDwm)
| 2
| No
| Unicode
| This file contains the group settings for the X-window manager, that are
set through the IBM Network Station Manager program. For Release 3, the
Motif Window Manager (mwm) is used. Although the directory is NCDwm,
this file actually contains mwm resources.
|
pref (NS3270)
| 2
| No
| Unicode
| This file contains the group settings for the 3270 emulator, that are set
through the IBM Network Station Manager program.
|
pref (NS5250)
| 2
| No
| Unicode
| This file contains the group settings for the 5250 emulator, that are set
through the IBM Network Station Manager program.
|
These file are located at
USERBASE/groups/"groupname"/"application"/.
These files are specific to a particular IBM Network Station
user. The settings in these files take precedence over the group
files.
File Name
| Type
| Edit
| File Format
| Description
|
pref (Nav)
| 2
| No
| Unicode
| This file contains the user settings for the NC Navigator, that are set
through the IBM Network Station Manager program.
|
pref (NCDwm)
| 2
| No
| Unicode
| This file contains the user settings for the X-window manager, that are
set through the IBM Network Station Manager program. For Release 3, the
Motif Window Manager (mwm) is used. Although the directory is NCDwm,
this file actually contains mwm resources.
|
pref (NS3270)
| 2
| No
| Unicode
| This file contains the user settings for the 3270 emulator, that are set
through the IBM Network Station Manager program.
|
pref (NS5250)
| 2
| No
| Unicode
| This file contains the user settings for the 5250 emulator, that are set
through the IBM Network Station Manager program.
|
pref (NCDterm)
| 2
| No
| ASCII
| This file contains changes made inside the VTxxx terminal emulator by the
user on the Network Station. This file is not managed by the IBM
Network Station Manager program.
|
pref (Login)
| 2
| No
| ASCII
| This file contains the Network Station user's last selection on the
menu bar for Hide, Top/Bottom, and Lock. This file is not managed by
the IBM Network Station Manager program.
|
These files are located at USERBASE/users/"username"/"application"/.
The following tables list the startup files. The tables indicate
which files can be edited and which files should not be edited. Startup
configuration files contain settings such as: which applications are
launched for the user, the user environment variables, and the user menu bar
buttons.
The settings in these files are the defaults in the IBM Network Station
Manager program for startup. They contain default menu bar buttons,
X-Window manager launching, and mandatory environment variables. These
settings apply to all IBM Network Station users.
File Name
| Type
| Edit
| File Format
| Description
|
startup.nsm
| 1
| No
| Unicode
| This file contains the settings for environment variables, which programs
are automatically run at login, and what menu bar buttons are
displayed.
|
These files are located at PRODBASE/SysDef/.
These files are basic system-wide settings that are made through the
IBM Network Station Manager program. Settings in these files apply to
all Network Station users.
File Name
| Type
| Edit
| File Format
| Description
|
startup.nsm
| 2
| No
| Unicode
| This file contains the settings for environment variables, which programs
are automatically run at login, and what menu bar buttons are
displayed.
|
envvars.nsm
| 2
| No
| Unicode
| This file contains environment variable substitutions for Language and
Select User's Group.
|
startup.dft
| 3
| Yes
| ASCII or Unicode
| This file may be created if it does not exist. If this file exists
it is the only startup file read by the Network Station. This file may
be used to set environment variables, launch applications, and add menu bar
buttons. This file must contain the following five mandatory
environment variable statements:
- SET NSM_NAV_PREF_VERSION R3M0
- SET NSM_MWM_PREF_VERSION R3M0
- SET NSM_NCDWM_PREF_VERSION R3M0
- SET NSM_NS5250_PREF_VERSION R3M0
- SET NSM_NS3270_PREF_VERSION R3M0
|
These files are located in USERBASE/SysDef/.
See
Application Startup File Formats
for more information about startup.dft.
These files are specific to a particular group of Network Station
users. Settings in these files are made through the IBM Network Station
Manager program.
File Name
| Type
| Edit
| File Format
| Description
|
startup.nsm
| 2
| No
| Unicode
| This file contains the settings for environment variables, which programs
are automatically run at login, and what menu bar buttons are
displayed.
|
envvars.nsm
| 2
| No
| Unicode
| This file contains environment variable substitutions for Language and
Select User's Group.
|
These files are located in USERBASE/groups/"groupname"/.
These files are specific to a particular Network Station user.
Settings in these files are made through the IBM Network Station Manager
program.
File Name
| Type
| Edit
| File Format
| Description
|
startup.nsm
| 2
| No
| Unicode
| This file contains the settings for environment variables, which programs
are automatically run at login, and what menu bar buttons are
displayed.
|
envvars.nsm
| 2
| No
| Unicode
| This file contains environment variable substitutions for Language and
Select User's Group.
|
These files are located in USERBASE/users/"username"/.
This section describes the order that the Network Station reads
configuration files. The sequence that the configuration files are read
is important. If a parameter is set in more than one file, the last
setting read by the Network Station determines the final value of the
parameter. In general the download sequence is designed so that:
- A parameter set in an individual user configuration file overrides
(replaces) the same parameter in a group configuration file.
- A parameter set in a group configuration file overrides the same parameter
set in a system-wide configuration file.
- A parameter set in an individual IBM Network Station configuration file
overrides the same parameter set in a system-wide configuration file.
- A parameter set in a system-wide configuration file overrides the same
parameter set in a shipped (Type 1) configuration file.
There are exceptions for parameters that are additive. If the same
additive parameter is in more than one file, all instances of these parameters
are aggregated. Examples of additive parameters are:
- Remote printers, under Hardware
- Menu bar buttons, under Startup
- Programs to auto-start, under Startup
The configuration files are downloaded from the server to the IBM Network
Station in the following order:
Notes:
- Some files may source (cause the Network Station to read) other
files. Generally the sourcing statement is the first line in the
file.
- In this document we show all of the files that could exist on the server,
but not all files must exist. For example the individual Network
Station, individual user, group, and system-wide configuration files do not
have to exist on the server.
__ 1.
| The Network Station is powered-on.
| __ 2.
| The kernel downloads during boot (pre-login).
__ a.
| The individual Network Station "name" file is downloaded. (This is
the master file. It sources standard.nsm, "name".nst, and
"name".trm.
__ 1)
| If "name" exists (where "name" is the hostname), read it.
| __ 2)
| Else if "name" exists (where "name" is the MAC address), read it.
| __ 3)
| Else if "name" exists (where "name" is the IP address), read it.
| __ 4)
| Else read standard.nsm.
|
| __ b.
| The system-wide hardware files are downloaded. (apply to all
Network Stations):
__ 1)
| PRODBASE/StationConfig/standard.nsm (This is the master
file. It sources the next six files.)
| __ 2)
| PRODBASE/StationConfig/required.nsm
| __ 3)
| PRODBASE/StationConfig/control.nsm
| __ 4)
| USERBASE/StationConfig/local.nsm (editable, RS/6000 only)
| __ 5)
| USERBASE/StationConfig/hosts.nsm
| __ 6)
| USERBASE/StationConfig/defaults.nsm
| __ 7)
| USERBASE/StationConfig/defaults.dft (editable)
|
| __ c.
| The hardware files associated with an individual Network Station are
downloaded.
__ 1)
| USERBASE/StationConfig/"name".nst
| __ 2)
| USERBASE/StationConfig/"name".trm (editable)
|
|
| __ 3.
| The kernel starts the Network Station login program. The login
program downloads the login (pre-login screen) configuration files.
__ a.
| PRODBASE/nls/"locale"/MRI/Login
| __ b.
| PRODBASE/StationConfig/resources.nsl
| __ c.
| PRODBASE/boot.nsl
| __ d.
| USERBASE/StationConfig/kiosks.nsl (editable/encoded)
| __ e.
| USERBASE/StationConfig/nsl.dft (editable)
|
| __ 4.
| The Network Station login program shows the login screen (or uses
kiosks.nsl to supress the login screen). When the user logs in,
the login program does the following:
__ a.
| USERBASE/users/"username"/envvars.nsm (The first line of this file
sources the next file.)
| __ b.
| USERBASE/groups/"groupname"/envvars.nsm (The first line of this
file sources the next file.)
| __ c.
| USERBASE/SysDef/envvars.nsm
| __ d.
| The application (X-resource) files are downloaded.
__ 1)
| PRODBASE/SysDef/NCDwm/pref
| __ 2)
| USERBASE/SysDef/NCDwm/pref
| __ 3)
| USERBASE/groups/"groupname"/NCDwm/pref
| __ 4)
| USERBASE/users/"username"/NCDwm/pref
| __ 5)
| PRODBASE/SysDef/NS5250/pref
| __ 6)
| USERBASE/SysDef/NS5250/pref
| __ 7)
| USERBASE/groups/"groupname"/NS5250/pref
| __ 8)
| USERBASE/users/"username"/NS5250/pref
| __ 9)
| PRODBASE/SysDef/NS3270/pref
| __ 10)
| USERBASE/SysDef/NS3270/pref
| __ 11)
| USERBASE/groups/"groupname"/NS3270/pref
| __ 12)
| USERBASE/users/"username"/NS3270/pref
| __ 13)
| USERBASE/users/"username"/Login/pref
| __ 14)
| USERBASE/users/"username"/NCDterm/pref
| __ 15)
| USERBASE/SysDef/pref.dft (editable)
|
| __ e.
| The login program asks the kernel to download the hardware files.
__ 1)
| USERBASE/groups/"groupname"/"groupname".nsg
| __ 2)
| USERBASE/groups/"groupname"/"groupname".grp (editable)
| __ 3)
| USERBASE/users/"username"/"username".nsu
| __ 4)
| USERBASE/users/"username"/"username".usr (editable)
|
| __ f.
| If USERBASE/SysDef/startup.dft (editable) exists, it is
downloaded.
| __ g.
| Else, download startup files.
__ 1)
| USERBASE/users/"username"/startup.nsm (The first line of this file
sources the next file.)
| __ 2)
| USERBASE/groups/"groupname"/startup.nsm (The first line of this
file sources the next file.)
| __ 3)
| USERBASE/SysDef/startup.nsm (The first line of this file sources
the next file.)
| __ 4)
| PRODBASE/SysDef/startup.nsm
|
|
| __ 5.
| When the NC Navigator is started by the user, the application files are
downloaded.
__ a.
| PRODBASE/mods/NAV/pref
| __ b.
| PRODBASE/SysDef/NAV/pref
| __ c.
| USERBASE/SysDef/NAV/pref
| __ d.
| USERBASE/SysDef/NAV/pref.dft (editable)
| __ e.
| USERBASE/groups/"groupname"/NAV/pref
| __ f.
| USERBASE/users/"username"/NAV/pref
|
|
This section provides an overview of how the Network Station accesses
directories on the server. This helps you understand the
following:
- Which server the Network Station is accessing for a directory
- What path name the Network Station is using for the directory
- What file protocol the Network Station is using
The Network Station creates a list of mount points that it uses to access
server directories. Each mount point has a local side and a remote
side. The local mount point is the server's directory path known
by applications that run on the Network Station. The remote mount point
contains the address of the server, the directory path that is exported by the
server, and the file protocol. When applications open a file they use
the local mount point. The kernel looks up the remote mount point that
corresponds to the local mount point. The kernel then accesses the file
on the server by using the exported directory path and the protocol from the
remote mount point.
Servers generally make their directories available to outside systems by
exporting them. The exported directory is usually the same path as the
actual directory on the server. However, some platforms export
different directory paths that their actual directories. For example,
on the PC Server, the directory exported by NFS is /netstation/ while the
actual directory is c:\nstation\.
For Release 3, the local mount points follow a naming convention that is
independent of the directory that is exported by the server. Therefore,
for most servers the local mount point for a directory does not equal the
remote mount point.
The file service table (a configuration table on the Network Station),
lists the mount points and the server they go to. For Release 3, the
Network Station can access separate servers for boot data (kernel, fonts, and
so forth), terminal configuration data (attached printers, and so forth), and
user configuration data (NS5250 preferences, and so forth). Mount
points to the boot and terminal configuration servers are controlled by DHCP
or NVRAM Setup. Mount points to user configuration data are controlled
by the Network Station Login daemon (NSLD) that runs on the Login
server. When the user logs-in, the NSLD communicates with the login
program on the Network Station to set these user mount points.
The file service table may be viewed on the Network Station by pressing
Alt-Shift-Home to bring up the Console. Then Setup-> Change Setup
Parameters -> File Service should be selected.
The following steps describe the process that the Network Station uses to
set the mount points in the file service table.
- The kernel initializes the file service table with the following before
the login program is called:
Local Directory
| Remote Directory
| Protocol
| Server
|
/netstation/prodbase/
| <directory on boot server>
| <protocol on boot server>
| <boot server>
|
<directory on boot server>
| <directory on boot server>
| <protocol on boot server>
| <boot server>
|
/netstation/prodbase/configs/
| <directory on 1st configuration server>
| <protocol on 1st configuration server>
| <1st configuration server>
|
<directory on 1st configuration server>
| <directory on 1st configuration server>
| <protocol on 1st configuration server>
| <1st configuration server>
|
/netstation/prodbase/configs/
| <directory on 2nd configuration server>
| <protocol on 2nd configuration server>
| <2nd configuration server>
|
<directory on 2nd configuration server>
| <directory on 2nd configuration server>
| <protocol on 2nd configuration server>
| <2nd configuration server>
|
Where:
- <directory on boot server> is specified by DHCP option 67 or NVRAM
setup. This would normally be set to the server's exported
PRODBASE/.
- <protocol on boot server> is specified by DHCP option 211, DHCP option
43(AS/400) or NVRAM setup. The choices are tftp, rfs/400, or
nfs. If DHCP option 43 is "AS/400", the root (/) directory is also
mounted to the boot server using rfs/400.
- <boot server> is specified by DHCP option 66 or NVRAM.
- <configuration server> refers to the IBM Network Station configuration
server (hardware).
- <directory on 1st configuration server> and <directory on 2nd
configuration server> is specified by DHCP option 213 or NVRAM setup.
Option 213 can specify 2 directories. These would normally be set to
the server's exported PRODBASE/configs/.
- <protocol on 1st configuration server> and <protocol on 2nd
configuration server> are specified by DHCP option 214 or NVRAM. Option
214 can specify 2 protocols. The choices are tftp, rfs/400, or
nfs.
- <1st configuration server> and <2nd configuration server> are
specified by DHCP option 212 or NVRAM. Option 212 can specify 2
servers.
|
- When the user logs-in, the login program appends the following to the file
service table:
Local Directory
| Remote Directory
| Protocol
| Server
|
/netstation/userbase/
| </USERBASE/ on the login server>
| <protocol on login server>
| <login server>
|
/netstation/prodbase/SysDef/
| </PRODBASE/SysDef/ on the login server>
| <protocol on login server>
| <login server>
|
/netstation/homebase/users/"user"/
| <user's home on the login server>
| <protocol on login server>
| <login server>
|
If the boot server is an AS/400, Login also mounts root (/) to the boot
server.
Where:
- </USERBASE/ on the login server>is specified by the IBM Network Station
login daemon. This directory contains application and startup
preferences changed by the IBM Network Station Manager program.
- </PRODBASE/SysDef/ on the login server> is specified by the IBM Network
Station login daemon. This directory contains shipped application and
startup preferences.
- <user's home on the login server> is the user's home
directory as defined by the login server.
|
This section is meant to aid you in migrating your hand
edited configuration files to Release 3. IBM does not guarantee that
your changes will successfully migrate to Release 3. It is possible
that your changes will conflict with settings that IBM changed or added for
Release 3. If you are in doubt about the impact of your changes on
Release 3, view (BUT DO NOT SAVE) the Release 3 shipped
configuration files. Check to see if your change overrides a shipped
setting.
Before you begin making any changes to the existing files, you might want
to consider why the files were changed in the first place. It is quite
possible to discard the previous edits that were made due to new and enhanced
features in the Release 3 IBM Network Station Manager program.
In Release 2.5 you may have edited files to allow a single
full-screen session to a host, such as a 5250 session. This most likely
disabled the Network Station login program. In Release 3 it is not
desirable to disable the Network Station login program. You can allow a
single full-screen session to a host by using a slightly different
method. This method allows the Network Station login program to run,
but suppresses the Network Station login dialog. Refer to
Full-Screen Solutions
for more information.
If ypu editied defaults.dft, "name".trm, or
"username".nsm in Release 2.5, your changes will remain after
installing Release 3. If you edited a different IBM Network Station
Manager configuration file. follow the steps below:
- Save your hand edited Release 2.5 configuration files before
installing Release 3.
- To avoid errors during the installation of Release 3, remove all added or
changed statements from Release 2.5 files that you hand edited.
You can compare your files to original copies of the Release 2.5
shipped files to find your changes.
Click here to access a copy of the Release 2.5 shipped
files.
These files are licensed by IBM for use only by persons who have a valid
licensed copy of IBM Network Station Manager Release 2.5.
- Install Release 3. You may want to view (BUT DO NOT
SAVE) the Release 3 shipped files to assess the impact of your
changes.
- Move only the added or changed statements from the saved files from step 1
to the files that are shown in the table below. Refer to previous
topics in this document to understand the design of the Release 3
files.
Attention: Do not simply copy the contents of the changed
files to the editable files. This may cause unpredictable
results. Move only the new or changed information to the editable
files.
In Release 2.5, if you changed:
| For Release 3, move the added or changed statements to:
|
standard.nsm, required.nsm, control.nsm,
hosts.nsm, or defaults.nsm
| defaults.dft
|
"name" or "name".nst
| "name".trm
|
"username".nsu
| "username".usr
|
PRODBASE/mods/Login/MRI2924/Login
| USERBASE/StationConfig/nsl.dft (for PC Server
PRODBASE/Configs\nsl.dft)
|
PRODBASE/SysDefaults/NCDwm/pref, USERBASE/SysDefaults/NCDwm/pref, or
USERBASE/"username"/NCDwm/pref
| USERBASE/SysDef/pref.dft
|
PRODBASE/SysDefaults/NS3270/pref, USERBASE/SysDefaults/NS3270/pref, or
USERBASE/"username"/NS3270/pref
| USERBASE/SysDef/pref.dft
|
PRODBASE/SysDefaults/NS5250/pref, USERBASE/SysDefaults/NS5250/pref, or
USERBASE/"username"/NS5250/pref
| USERBASE/SysDef/pref.dft
|
PRODBASE/mods/NAV/pref, PRODBASE/SysDefaults/NAV/pref,
USERBASE/SysDefaults/NAV/pref, or USERBASE/"username"/NAV/pref
| USERBASE/SysDef/NAV/pref.dft
|
PRODBASE/SysDefaults/startup.nsm,
USERBASE/SysDefaults/startup.nsm, or
USERBASE/"username"/startup.nsm
| USERBASE/SysDef/startup.dft
|
Before you begin editing, make a copy of the original
file.
The configuration files that are marked Yes in the Edit column should be in
UNIX format. This means that lines must end with a line feed, not a
carriage return-line feed. The editor that you use must not insert
carriage returns.
The exceptions are startup files, which may contain carriage
returns. Any ASCII editor may be used for these files.
The files marked ASCII in the file format column must only contain
invariant (ISO 8859-1) characters.
Generally you are not required to edit Unicode (UCS-2) files. All of
the files that are marked Yes in the Edit column may be ASCII files.
You would create Unicode files only if you need to enter UCS-2 characters (for
example, Chinese). Unicode files must contain big endian UCS-2
characters. The first 2-bytes must contain the byte order mark
(BOM). The BOM must be FEFF (big endian).
On a PC, we recommend editing the files by using one of the following
editors to avoid damaging the files:
- Microsoft WordPad
- IBM EPM
On the AS/400, we recommend using Client Access to access the files.
You can also ftp the files (in binary format) from the AS/400 to another
system, edit the files, and then ftp the files back (in binary format) to the
AS/400.
On the RS/6000 platform, you can use the vi editor or any other UNIX
editor.
On the OS/390 platform, we recommend using the aedit editor.
On the VM/ESA platform, we recommend using the ASCXED editor to edit files
in the client mode.
You may also want to consult the
Redbooks
(http://www.pc.ibm.com/networkstation/support/redbooks.html)
for additional information on selecting editors and editing the configuration
files.
In order to edit "name".trm and "username".usr files, you
must first create these files by using the IBM Network Station Manager
program. For example, to create the bob.usr file, you first need
to create a user preference for bob (such as a mouse setting) using the IBM
Network Station Manager program. The IBM Network Station Manager
program creates these files with the proper permissions and links.
|