.TH ISOTAILOR 5 "5 July 1988"
.\" $Header: /f/osi/support/RCS/isotailor.5,v 7.8 91/02/22 09:46:48 mrose Interim $
.\" $Log: isotailor.5,v $
.\" Revision 7.8 91/02/22 09:46:48 mrose
.\" Revision 7.7 90/11/21 11:37:51 mrose
.\" Revision 7.6 90/10/29 18:37:21 mrose
.\" Revision 7.5 90/07/09 14:50:51 mrose
.\" Revision 7.4 90/01/11 18:38:00 mrose
.\" Revision 7.3 89/12/12 16:14:33 mrose
.\" Revision 7.2 89/11/30 23:51:52 mrose
.\" Revision 7.1 89/11/27 10:30:48 mrose
.\" Revision 7.0 89/11/23 22:27:37 mrose
The \fIisotailor\fR file contains information used to run-time
configure the ISODE distribution.
Entries are separated by end\-of\-line (or the end\-of\-file).
The character `#' at the beginning of a line indicates a comment line.
The entries come in several types. There are general ISODE
configuration parameters, operating system specific tailoring and
interface specific tailoring parameters.
.SH "LOCAL ENVIRONMENT TAILORING"
There are some variables that are used to make up for deficiencies in
operating systems, or to override the operating system. These are
This takes a string as a parameter and is used as
the name of the local host if the \fIgethostname\fR call
(or equivalent, e.g., \fIuname\fR)
is not used. This will also override any other run-time determination
This takes a string as a parameter and indicates the directory where
the ISODE user programs are kept (be sure to use a trailing slash).
This takes a string as a parameter and indicates the directory where
the ISODE system programs are kept (be sure to use a trailing slash).
This takes a string as a parameter and indicates the directory where
the ISODE configuration files are kept (be sure to use a trailing slash).
There are a number of options that can be set for each layer of ISODE.
The first variable indicates the default logging directory,
the other variables give information about each log file.
This variable takes a string as a parameter and indicates the
directory where the ISODE log files are kept (be sure to use a
The remaining variables are all configured in the same way and are in
xyzlevel: [none] [exceptions] [notice] [pdus] [trace] [debug] [all]
The filename can be either the name of a file of a `\-' in which case
the standard error is used. If the filename contains the string `%d'
then this is replaced by the current process id.
The normal level for this style of tailoring is to set exceptions. The
other two values can be added in when debugging, if so desired.
The current variables in this format are as follows.
compatlevel native services subsystem
addrlevel addressing subsystem
tsaplevel transport level
psaplevel presentation elements
psap2level presentation level
acsaplevel association control level
rtsaplevel reliable transfer level
rosaplevel remote operations level
.SH "TRANSPORT STACK TAILORING"
There are several variables which can be used to en/disable configured
TS-stacks and to define OSI communities and their relationship
which takes one or more of the following values:
[tcp] [x25] [bridge] [tp4] [all]
indicates which TS-stacks should be enabled.
This is useful when multiple machines (with different interfaces)
share the same executables.
the \fB\*(EDisotailor\fR file is a normally symbolic link to
\fB/private\*(EDisotailor\fR.
which takes one or more OSI community names as a value.
Each community name must be defined as a macro in the
\fIisomacros\fR\0(5) file.
which takes one or more of the following values:
[int-x25] [janet] [internet] [realns] [localTCP] [all]
This variable is used to distinguish membership in various OSI communities.
a site with an X.25 connection might be attached to the International X.25
network, but not the JANET.
Thus \fIts_stacks\fR would include \*(lqx25\*(rq,
and \fIts_communities\fR would include \*(lqint-x25\*(rq but not
Note that the ordering of communities is important:
network addresses will be tried in the order that their respective
communities are listed with this variable.
.IP default_nsap_community
which takes an integer value,
declaring the default community to be used for NSAP addresses.
.IP default_x25_community
declaring the default community to be used for X.25 (DTE) addresses.
.IP default_tcp_community
declaring the default community to be used for TCP (RFC1006) addresses.
These are the parameters that are used in the Transport-Service Bridge
A list of pairs of values.
The first of each value should be a community as defined in the
\fIts_communities\fP variable
(obviously the values \*(lqnone\*(rq and \*(lqall\*(rq are not permissible).
The second value of the pair should be a presentation address using
the ISODE \*(lqstring\*(rq format.
When a call is to be placed and the network corresponds to one
of the communities given here, then a call through the bridge given in
the second variable will be made automatically.
This variable contains a string encoded presentation address which the
bridge will listen on by default.
This should normally consist of a set of network addresses with no selectors
Consider the case of a host with access to both the Internet and the
International X.25 network.
This host might have this entry in its \fIisotailor\fR file:
tsb_default_address: Internet=sheriff+17004\\|Int-X25(80)=23426020017299+PID+03018000
This tells the bridge to listen on two network endpoints.
Hosts in the Internet community wishing to reach the International
X.25 community would have this entry in their \fIisotailor\fR file:
tsb_communities: int-x25 Internet=sheriff+17004
hosts in the International X.25 community wishing to reach the
Internet community, would have the entry:
tsb_communities: internet Int-X25(80)=23426020017299+PID+03018000
.SH "INTERFACE SPECIFIC TAILORING"
Most interfaces that ISODE runs over have some form of tailoring.
These are usually very dependent on the interface. Each interface
which supports tailoring will now be described.
.SS "General X.25 Tailoring"
There are two specific variables that can be used with any X.25
This is the X.121 address that ISODE processes will listen on
It may be a full X.121 address or a sub-address.
This is the X.25 protocol ID that ISODE processes will listen on by default.
Traditionally, this is the first four octets of the CUDF in hex-notation,
There are also three variables for performing address
manipulation as required by some network vendors.
If this has the value `on' then any international DTEs (i.e.
having non\-local DNICs) will have a leading zero introduced
before being passed to the network.
If this has the value `on' then any local DTEs (i.e. having the
local DNIC) will have this DNIC removed before being passed to
This should be set to the local DNIC (the first four digits of the
DTE) of the host machine.
It should only be set if one or both of the previous two
variables has the value `on'.
There are also two variables for logging X.25 statistics.
Defines the level of logging to be used for X.25 statistics logging.
(At present, only \*(lqnotice\*(rq level messages are generated.)
Defines the filename to be used for X.25 statistics logging.
These setting are only useful when SUN_X25 is defined along with X25.
The effect of these parameters is more fully documented in the Sun manuals.
Set to 1 or 0 to enable/disable reverse charging.
This should be set to one of 0 (default), 16, 32, 64, 128, 256, 512 or
1024 to set the send/receive packet size.
This sets the send/receive window sizes. Legal values are 0 (default),
This sets the sending/receiving throughput values. Legal values are 0
(default) 75, 150, 300, 600, 1200, 2400, 4800, 9600, 19200, 48000.
Closed user group request. Set to either 0 or 1.
Sets the closed user group index number.
Sets the fast select parameters. Either 0, 1 or 2.
Recognised private operating agency parameters.
when the Camtec X.25 is accessed via the
This selects which port on the Camtec card will be used
for outgoing calls, and takes the value A, B or #.
A and B are the two X.21 WAN interfaces and # is the
Listening is automatically done on all three ports.
These are parameters that are used in the tp0bridge implementation.
The host machine that is running the tp0bridge.
This is the TCP port that is to be used
The default is 146, which should be in defined in /etc/services.
The X.121 address of the remote host.
The X.121 address to listen on for incoming calls, on the remote host.
The protocol ID used for listening along with the previous address.
This is encoded as a string of eight hex digits.
A string used to discriminate the network. When attempting to place an
X.25 call with BRIDGE_X25 and real X25 configured in, this string is
used to decide which interface to use. If the string is empty, the
bridge will be used. If it is set to `\-' the bridge will not be used.
If the string is anything else, it is compared against the called
X.121 address. If there is a match, then the bridge is used, otherwise
the real interface is used.
.SH "SESSION SERVICES TAILORING"
Ther are three variables that can be tailored:
The number of seconds to drain on session aborts.
The number of seconds to drain on session disconnects.
The number of seconds to drain on session refuses.
.SH "DIRECTORY SERVICES TAILORING"
There are two variables that can be tailored:
This takes either the string \*(lqon\*(rq or \*(lqoff\*(rq as a parameter.
then the \*(lquser-friendly namservice" will be used to perform
If the nameservice lookup fails,
the stub-directory will be used as a fallback.
This is the transport address of the nameservice.
It is specified using the ISODE \*(lqstring\*(rq format,
Internet=wp.psi.net+17006
which indicates that the nameservice lives in the TCP/IP communications domain
on TCP port \*(lq17006\*(rq at host \*(lqwp.psi.net\*(rq.
The nameservice is accessed via the OSI CO-mode transport service,
so other kinds of addresses (e.g., X.25 addresses can be used as well).
.SH "PROGRAM-SPECIFIC TAILORING"
a program-specific tailoring file is consulted before the system\-wide
The program-specific file is called \fB\&.myname_tailor\fR in the user's
where \*(lqmyname\*(rq is the name that the program was invoked with.
.ta \w'$HOME/.myname_tailor 'u
\*(EDisotailor ISODE tailoring file
$HOME/.myname_tailor program-specific tailoring file
\fIThe ISO Development Environment: User's Manual, Volume 2:
Underlying Services\fR, \*(lqThe ISODE Tailoring File\*(rq.
University College London
projects / unix-history / blob