General Administration Tasks
This section describes:
-
Configuration that you will need to carry out in remote non-UNIX environments.
Configuring the Remote Environment
For a user in a remote non-UNIX environment to be able to use the facilities provided by UNIX-Connect, certain tasks must be carried out in that environment. These tasks are outlined below - for full details see the appropriate system documentation.
Reality Databases
Remote Logon
To allow a user to log onto a remote environment from a Reality database, you must do the following:
-
Use CREATE-ACCOUNT to create a remote account. The user will log onto this account in order to connect to the remote environment.
-
Use SSM to specify that the user has remote logon (interactive) enabled.
Remote File Access
To allow a Reality database user to access files in a remote environment, you must do the following:
-
Use CREATE-ACCOUNT to create a pointer to each remote account to be accessed.
-
Use SET-FILE to create a Q-pointer for each file to be accessed.
-
Use SSM to specify that the user has remote logon (server) enabled.
Program to Program Communication
If a user needs to use program to program communication, you must use SSM to specify that he or she has remote logon (server) enabled.
Network User-ids
To enable connections to a server to succeed, server-side user-ids and passwords must be configured at the client end. On Windows you should use SSM to enter network user-ids and passwords. On UNIX this is achieved using netadmin.
Note
On a Windows incoming connection, user-ids are validated on the database. On a UNIX incoming connection, user-ids are validated by the operating system.
SovereignX Environment
All system administration tasks on an SX system are carried out in the UNIX environment. See Printer Administration, The ROUTE-FILE, Session Manager and Network Security, and the SovereignX System Administration and Utilities Manual for details.
In order for one SovereignX environment to communicate with another (for instance to use the remote printing facility) local USERS-FILE entries must include a subrecord of the remote environment name with a destination user-id and associated password.
Time Synchronisation
The time on the local UNIX system can be synchronised to that of a remote UNIX system by logging on as root and running the synctime program. This has the following syntax:
synctime systemName {-l userId,password}
where
systemName is the local ROUTE-FILE name for the remote host.
userId is the name of a user on the remote system.
password is the remote user's password.
The -l option and its parameters can be omitted if you have been granted equivalence with a user on the remote system, or if you have a USERS-FILE entry for the remote host.
If the times on the two systems differ by more than 1 second, the local time will be updated. The program will report if the times are already synchronised.
Note
Users other than root can also run the synctime command. In this case, the time settings for the two systems will be reported, but the time on the local system will not be changed.
Environment Variables
The following environment variables can be set globally by the system administrator, or by individual users:
UC_TLI_CONNECT_TO
The UC_TLI_CONNECT_TO environment variable defines the length of time, in milliseconds, for which the UNIX-Connect software will attempt to establish an outgoing connection. This timeout applies only to connections that use the Transport Library Interface (TLI) - it does not apply to X.25 connections.
The default setting of UC_TLI_CONNECT_TO is 12000 milliseconds (2 minutes).
Setting UC_TLI_CONNECT_TO to -1 specfies that the UNIX-Connect software will attempt to establish an outgoing connection indefinitely.
UC_PROCPLID The UC_PROCPLID environment variable determines the PLId format used for daemon processes that do not already have a PLId.
-
If UC_PROCPLID is not set, or is set to 0, a PLId with the format UNIX-SerialNo will be generated.
-
If UC_PROCPLID is set to 1, a PLId with the format UPROC-SerialNo-Process will be generated. This setting should be used if a unique PLId is required.