***************************************************************************
(c) Copyright 2000 International Business Machines Corp.

README.MPT for Multi-Protocol Transport Services (MPTS*)        4/2000
***************************************************************************
                          Table Of Contents
***************************************************************************

SECTION 1: INSTALLATION AND CONFIGURATION
         1.1 - SELECT CONFIGURE WHEN UPGRADING MPTS*
         1.2 - RECONFIGURING PROTOCOLS
         1.3 - INSTALLING PREVIOUS VERSIONS OF LAN TRANSPORT (NTS/2-MPTS)
         1.4 - CANNOT START MPTS* DUE TO LOCKED FILES
         1.5 - ADDED PARAMETERS IN CONFIG.SYS CLEARED
         1.6 - CONFIGURING A LAN INTERFACE FOR TCP/IP
         1.7 - INSTALLING MPTS OVER CD-ROM VERSION OF LAN SERVER 3.0
         1.8 - READMAC.TXT FILE FOR ADDITIONAL INFORMATION ON MAC
               DRIVER INSTALLATION AND CONFIGURATION
         1.9 - INSTALLING NetBIOS FOR TCP/IP OVER IBM NetBIOS VERSION 1
         1.10 - SOCKETS DEVICE DRIVER CONFIGURATION PARAMETERS
         1.11 - BOOT ERRORS DURING Alt-F1, F2 (Use original CONFIG.SYS)
         1.12 - TRAP 0008 EXCEPTION ON OS/2 WARP 4.0 AND WORKSPACE ON
                DEMAND CLIENTS
         1.13 - NETBIOS OVER TCPIP PROTOCOL CONFIGURATION CHANGE REQUIRED
                IF SYS1201 MESSAGE OCCURS DURING IPL

SECTION 2: NETBIOS
         2.1 - NETBIOS RAM USAGE
         2.2 - NETBEUI RAM CALCULATIONS
         2.3 - NETBEUI PROTOCOL.INI PARAMETERS

SECTION 3: OS/2* NETBIOS OVER TCP/IP*
         3.1 - NATIVE SOCKETS OVER NETBIOS

SECTION 4: MPTS SECURE SERVICE
         4.1 - SECURE SERVICE ENABLER
         4.2 - JAVA 1.1.6 OR GREATER REQUIRED FOR SECURE SERVICE
               ENABLER GUI
         4.3 - SETTING JAVA_HOME FOR SECURE SERVICE ENABLER GUI
         4.4 - MPTS MAKEDISK UTILITY AND SECURE SERVICE
         4.5 - OVERRIDING DEFAULTS FOR IKEYMAN

SECTION 5: KERNEL DEBUG NETWORK PROTOCOL
         5.1 - USAGE OF KERNEL DEBUG NETWORK PROTOCOL

SECTION 6: TRADEMARKS AND SERVICE MARKS


***************************************************************************
SECTION 1           INSTALLATION AND CONFIGURATION
***************************************************************************
___________________________________________
1.1 - SELECT CONFIGURE WHEN UPGRADING MPTS*

When upgrading an existing configuration when installing this
new release of MPTS the user must select Configure after the install to
validate their LAPS Configuration and also update the CONFIG.SYS file.
This new MPTS may include different TCP/IP transport drivers from your
current version, so unless CONFIG.SYS is updated, the configuration
may not be successfully migrated.

_____________________________
1.2 - RECONFIGURING PROTOCOLS

When reconfiguring protocols that affect LAN Server* or OS/2 Peer*, you
should reconfigure through the LAN Server* (instead of MPTS*) to assure
that LAN Server* or OS/2 Peer* files are updated. If installing MPTS and
reconfiguring through LAN Server*, the reconfiguration should take place
after the required MPTS installation system reboot.  This is necessary in
order to complete the MPTS installation of locked files.

________________________________________________________________
1.3 - INSTALLING PREVIOUS VERSIONS OF LAN TRANSPORT (NTS/2-MPTS)

Some IBM products include earlier versions of the LAN Transport as a feature
of their programs.  These earlier versions of LAN Transport may be NTS/2*
or MPTS*.  If you install one of these products that include an earlier
version of LAN Transport after installing the current version of MPTS*,
do not reinstall the LAN Transport from that product.  Earlier versions
of NTS/2* and MPTS* are functional subset of the current MPTS* and must never
overlay the current version of MPTS*.  Since the current version of MPTS*
is a superset of earlier LAN Transports, products that use the current
version of MPTS* will function normally running over it.  So, all CSD's and
APAR fixes must be for the version that is installed.

If attempting an earlier version of the Transport over the current MPTS*,
prior to the installation a panel will warn you that you are about to
install an earlier version of LAPS than the one already on your system.
You should select "NO" to exit the installation.

For a CID install, set the upgrade_level = same (or old) in the
inst_section of your response file  to prevent overlaying MPTS*
with an older version of the Transport.

The OS/2 command "syslevel" will give the user information on the version
of LAN Transport that is currently installed on the system.  The syslevel
files for MPTS are:

       IBM OS/2 LAN Adapter and Protocol Support (syslevel.trp)
       IBM OS/2 Socket/Multi-Protocol Transport Services (syslevel.mpt)


___________________________________________
1.4 - CANNOT START MPTS DUE TO LOCKED FILES

  Occassionally, the MPTS configuration utility will not allow the user
  to reconfigure due to Locked Files.  The following message will appear:

      You have re-installed MPTS.  Locked files will not allow you to start
      MPTS.

      You must exit MPTS, shutdown, and restart your workstation before you
      can start MPTS.

  If you have not re-installed MPTS, then delete the file IBMLANLK.LST
  found in the \OS2\INSTALL directory on the boot drive.  This will allow
  you to start MPTS.  DO NOT delete this file if you have re-installed
  MPTS and have not executed a shutdown and booted on the same boot drive.

____________________________________________
1.5 - ADDED PARAMETERS IN CONFIG.SYS CLEARED

If parameters has been added to drivers in the CONFIG.SYS file,
and those drivers are part of the MPTS configuration, MPTS will
not maintain the parameters if you do a new MPTS configuration
where CONFIG.SYS is updated.
Parameters can be specified on the AFNB.SYS driver in order
to configure Native Netbios socket support. If an update
of CONFIG.SYS is performed by MPTS the original version of
CONFIG.SYS is saved as CONFIG.MPT.


____________________________________________
1.6 - CONFIGURING A LAN INTERFACE FOR TCP/IP

When the IBM TCP/IP Base Kit is not installed on the system, you can
configure the system for TCP/IP support as follows:

     1. Using the LAPS panel, assign the TCP/IP protocol to a PHYSICAL
        adapter (e.g. IBM Token-Ring Compatible adapter).  If desired,
        you can also configure the TCP/IP OVER NetBIOS protocol.  Note
        that if you already have NetBIOS configured for this adapter, you
        will be required to change the "LOGICAL ADAPTER" number.  These
        values apply to this panel only and have no relationship to
        selections on other panels.

        NOTE: You do not have to change the LOGICAL ADAPTER number for
              any of the other protocols unless prompted to do so.

     2. Return to the "Configure" panel and select TCP/IP Configuration
        and press the Configure button.

     3. From the "TCP/IP Configuration" panel, select "Network interface
        parameters" and press the Configure button.

     4. On the "Configure TCP/IP Network Interface Parameters" panel,
        highlight the PHYSICAL lan adapter that you have installed on the
        system and to which you previously assigned the TCP/IP protocol.

     5. Press the Activate button to activate the interface.  For example:
        if you had only an IBM Token Ring Compatible adapter installed,
        you would only activate adapter 0 (since there's only one PHYSICAL
        adapter) even though in step 1 about you referred to two LOGICAL
        adapters.

     6. Enter the appropriate IP information (or check the Enable DHCP box)
        and save the information.

     7. Returning to the previous panels and exiting MPTS will configure
        the system and update config.sys (if selected).

     8. Reboot to activate the new configuration.


___________________________________________________________
1.7 - INSTALLING MPTS OVER CD-ROM VERSION OF LAN SERVER 3.0

If installing MPTS over a version of LAPS that was previously installed
with the CD-ROM version of LAN Server 3.0, the READONLY file attribute
must be removed from all files in the \IBMCOM directory and all of its
sub-directories prior to installing MPTS.  To remove the READONLY file
attribute, execute the following command from an OS/2 command prompt:

              ATTRIB -R \IBMCOM\*.* /S

_______________________________________________________________
1.8 - READMAC.TXT FILE FOR ADDITIONAL INFORMATION ON MAC DRIVER
      INSTALLATION AND CONFIGURATION

A complete list of supported adapter cards and information on
MAC drivers can be found in the READMAC.TXT file located in the
IBMCOM\MACS subdirectory on a system installed with MPTS.  Prior to
installation, this file may be extracted from the product diskette
containing the MACS.ZIP file by using the following command:

          pkunzip2 macs.zip ibmcom\macs\readmac.txt

MPTS also provides specific readme files for various MAC drivers.  These
files have the file extension of .TXT or .DOC and are located in the IBMCOM\MACS
subdirectory on a system installed with MPTS.  Prior to installation, these
files may be extracted from the product diskettes containing the MACS.ZIP
file.  To view which MAC drivers have a readme text file associated with it,
issue the following commands on the MACS.ZIP file:

          pkunzip2 macs.zip *.txt /v

          pkunzip2 macs.zip *.doc /v

To extract a specific file, use the following command on the appropriate
ZIP file:

          pkunzip2 macs.zip ibmcom\macs\driver_name.txt

                               or

          pkunzip2 macs.zip ibmcom\macs\driver_name.doc

______________________________________________________________
1.9 - INSTALLING NetBIOS FOR TCP/IP OVER IBM NetBIOS VERSION 1

When installing MPTS on a system that was previously configured for
NETBIOS for TCP/IP using the "IBM NetBIOS Version 1 for OS/2 program"
the new MPTS device drivers are not compatible with the IBM NetBIOS
Version 1 product. You must complete the following steps:

    1. Using the newly installed MPTS, reconfigure the system using MPTS
       and select the NetBIOS over TCP/IP protocol.

    2. Configure the NetBIOS socket interface using MPTS.

    3. BEFORE rebooting, edit the config.sys file and make the following
       changes:

        A. Delete the DEVICE=<d>:\<netbios2 product path>\NBDRIVER.SYS
           statement.

        B. Edit the LIBPATH statement to remove the reference to the
           netbios2 product path.

     4. You can remove the IBM NetBIOS for TCPIP product.


_____________________________________________________
1.10 - SOCKETS DEVICE DRIVER CONFIGURATION PARAMETERS

The following are configurable parameters that can be specified on the

          DEVICE=C:\MPTN\PROTOCOL\SOCKETS.SYS

in the config.sys file:

          /c:#                debug comport number; default is 2
          /v                  display banner at boot time
          /uis:0              turn off unique id for select(); default in on
          /mem:#              number of 4k bye clusters allocated at
                              initialization time.  default is 75, valid
                              range si from 30 to 32766
          /gdt:#              max number of 64k byte blocks stack can allocate.
                              default is 80.


--------------------------------------------------------------
1.11 - BOOT ERRORS DURING Alt-F1, F2 (Use original CONFIG.SYS)

If using the OS/2 Boot Recovery options of Alt-F1 and then F2, it is
possible one or both of the following errors may occur during the boot
sequence.

SYS1718: The system cannot find the file C:\MPTN\PROTOCOL\IFNDIS.SYS
specified in the device statement of config.sys.
Press Enter to continue...

SYS1718: The system cannot find the file C:\TCPIP\BIN\VDOSTCP.VDD
specified in the device statement of config.sys.
Press Enter to continue...

The  OS/2 Boot Recovery mechanism allows the end-user to use the original
CONFIG.SYS created by the OS/2 install process. Installing, uninstalling,
or upgrading OS/2 components can remove files referenced by this version
of CONFIG.SYS.  When this occurs messages of the above type can appear.

Earlier versions of MPTS:

        Referenced the file IFNDIS.SYS, this version no longer uses
        IFNDIS.SYS and the installation process removes this file.
        MPTS did not ship the file VDOSTCP.VDD, instead TCP/IP shipped
        the file.  MPTS now ships this file and places it in the
        \MPTN\BIN sub-directory while deleting the copy found
        in the \TCPIP\BIN sub-directory.

These actions causes the boot-up errors using the original config.sys file.


The user  can resolve the recovery boot-up errors by modifying the
\os2\boot\config.x file located on the boot drive.  It  is the CONFIG.SYS
file used to boot-up during the F2 recovery process.  The following can
be done to the \os2\boot\config.x file to resolve the recovery boot-up errors:

  - Execute the following command

                  ATTRIB -R \OS2\BOOT\CONFIG.X

  - Edit the \os2\boot\config.x file with any text editor (i.e. TEDIT.EXE)

  - Modify the following statement in the config.x file

      From

            DEVICE=C:\MPTN\PROTOCOL\IFNDIS.SYS

      To

            REM DEVICE=C:\MPTN\PROTOCOL\IFNDIS.SYS

  - Modify the following statement in the config.x file

      From

           RUN=C:\TCPIP\BIN\VDOSTCP.VDD

      To

           RUN=C:\MPTN\BIN\VDOSTCP.VDD

   - Save the \os2\boot\config.x file


   - Execute the following command

                       ATTRIB +R \OS2\BOOT\CONFIG.X


You may also edit the \os2\boot\config.x file and place the following
statement in it:

                  PAUSEONERROR=NO

This will display the error messages during boot-up but processing will
continue without any intervention.

NOTE:  Should you fall back to a previous MPTS version, you may need to
reverse the above changes to CONFIG.X.


------------------------------------------------------------
1.12 - TRAP 0008 EXCEPTION ON OS/2 WARP 4.0 AND WORKSPACE ON
       DEMAND CLIENTS

A trap 0008 exception may occur when executing a redirected install
of MPTS package on an OS/2 Warp 4.0 system.  A similar trap 0008 may
also occur when booting a WorkSpace on Demand client after upgrading
to the new MPTS package.  If this occurs, apply OS/2 Warp 4.0 fixpak
XR_M013 or higher and retry the installation.


----------------------------------------------------------------
1.13 - NETBIOS OVER TCPIP PROTOCOL CONFIGURATION CHANGE REQUIRED
       IF SYS1201 MESSAGE OCCURS DURING IPL

The NetBIOS over TCPIP protocol (TCPBEUI) has a restriction that some of it's
resources that are configured must fit within a 64k boundary.  The overhead
value for this 64k boundary calculation has increased with MPTS 6.0 by
500 bytes.  The increase in the overhead may cause previously working
TCPBEUI configurations to exceed the 64k boundary.  It may be necessary to
reconfigure the TCPBEUI resources after installing MPTS 6.0 to prevent
the following error from occurring during ipl:

              sys1201: The device driver
              C:\IBMCOM\PROTOCOL\TCPBEUI.OS2 specified in the
              DEVICE statement on line xx of the CONFIG.SYS was
              not installed.  Line xx is ignored.  This error
              will cause other errors to follow during ipl.

The following error message will be logged in the \ibmcom\lantran.log file
as well:

LT00136: System resources are not available to hold the current parameter
         configuration in PROTOCOL.INI.  IBM TCPBEUI did not load.

One reconfiguration to prevent this is to the decrease the TCPBEUI
"TCP-Frame descriptors" parameter by 20. For example, if it's currently
configured for 132, change it to 112.

***************************************************************************
SECTION 2                       NETBIOS
***************************************************************************
_______________________
2.1 - NETBIOS RAM USAGE

The NetBIOS API device driver uses a single 64K data area for allocate
of resources.  To determine the resources to allocate for NetBIOS API
you need to know the RAM usage of the NetBIOS API driver to stay within
the 64K limitation.  The sum of the following must be less than or equal
to 64KB:

- 11200 bytes overhead
- 95 bytes for each NCB available to the NetBIOS API
- 15*(NCBs available to the NetBIOS API - 15)
     (use 0 if less than 0)
- 990 for each adapter configured for NetBIOS

Examples for the NetBIOS API RAM utilization are in the LAN Technical
Reference.

If you have exceeded the 64K limitation the following error will occur
during IPL:

LT00065: The configuration parameters defined in PROTOCOL.INI exceed
the 64KB work area.  NetBIOS 4.0 support has ended.

______________________________
2.2 - NETBEUI RAM CALCULATIONS

The calculation of NetBEUI RAM usage can be automatically calculated
using the NB64K utility applet found in the MPTSAPLT.ZIP file.  The formula
to determine the NetBEUI RAM usage can be found Appendix C in the MPTS*
Configuration Guide.

If you have exceeded the 64K limitation the following error will occur
during IPL:

LT00097: System resources are not available to hold the current parameter
configuration in PROTOCOL.INI.  IBM* NETBEUI did not load.

_____________________________________
2.3 - NETBEUI PROTOCOL.INI PARAMETERS

The NETBEUI section of the PROTOCOL.INI file has two configurable parameters
that are not listed in the documentation, SIDEBAND and BALANCE.  These
parameters should not be changed from their default values.  When not
present in the PROTOCOL.INI file, these two parameters are set to the
correct values automatically.  The default values (when not present in
PROTOCOL.INI) are as follows:

  SIDEBAND = 1
  BALANCE  = 2

Setting SIDEBAND to 1 enables a performance enhancement used by LAN Server*
for sending small frames.  Setting SIDEBAND to 0 disables this performance
enhancement.  BALANCE is used to control how NETBEUI chooses which adapters
are used when an NCB.LISTEN command is issued on a machine with multiple
network adapters.  If two network adapters on the same machine are on
the same network segment (bridged segment) then setting BALANCE to 0
disables load balancing, setting BALANCE to 1 puts it into load balancing
mode and setting BALANCE to 2 lets NETBEUI decide the appropriate load
balancing mode.


***************************************************************************
SECTION 3              OS/2* NETBIOS OVER TCP/IP*
***************************************************************************
______________________________________
3.3 - NATIVE SOCKETS OVER NETBIOS

The SO_SNDTIMEO and SO_RCVTIMEO options are no longer supported on
the GETSOCKOPT and SETSOCKOPT calls for AF_INET or AF_NB.


When coding sockets calls using the AF_NB protocol, the following
should be noted:
   - AF_NB does not support connect-connect.
   - The NetID coded in the address structure is the local adapter, and not
     the target machine's adapter.
   - AF_NB does not support OOB data.  You may get either ENOPROTOOPT
     10042 or EOPNOTSUPP 10045 error code.
   - If you issue a bind followed by a connect, AF_NB will verify that the
     NetID on the connect call is the same as the NetID on the bind call.
   - If you do an implicit bind, AF_NB will use the NetID specified on the
     connect call.
   - AF_NB does not support shutdown type 1 or shutdown type 2.  Issuing
     either results in a error code of 10045. However, if shutdown type 2
     was requested, a shutdown type 0 will be performed.

Customization considerations:
   - In order to use AF_NB, USEMAXDATAGRAMS must be set to YES in
     \IBMCOM\PROTOCOL.INI. The default for USEMAXDATAGRAMS is NO.
   - The maximum number of NCBs available to each session is configurable
     to a maximum of 255. Running out of NCBs results in a program hang.
   - If you manually modify statements in CONFIG.SYS, be aware that the
     modifications will be lost if you re-install or upgrade MPTS.
   - The default customization for NetBios is not sufficient to support the
     maximum backlog that may be coded on a listen. Also, when the backlog
     is reached, AF_NB connect reports a successful connection. A NetBios
     connection is considered successful when the listening and connect
     NCBs are completed. The server does not know that the backlog has
     been reached until later. The server will hangup the session making
     it unusable.
   - \IBMCOM\PROTOCOL.INI and \IBMLAN\IBMLAN.INI defaults for maximum
     number of names are not sufficient when running on a multiple
     LAN adapter system with either LAN Server or LAN Requester installed.
   - When using AF_NB protocol, error code 10055 may mean that you have run
     out of names in the names table. Increasing the maximum in
     \IBMCOM\PROTOCOL.INI and CONFIG.SYS should alleviate the problem.


***************************************************************************
SECTION 4              MPTS SECURE SERVICE
***************************************************************************
____________________________
4.1 - SECURE SERVICE ENABLER

Certain versions of MPTS 6.00 contain a Secure Service Enabler. IBM
secure applications when installed onto these versions of MPTS will share
the Secure Service Enabler to provide secure communications from this
machine to other secure servers or clients. MPTS 6.00 installs both the
3.3 and 4.0 versions of the Secure Service Enabler.

-------------------------------------------------------------------
4.2 - JAVA 1.1.6 OR GREATER REQUIRED FOR SECURE SERVICE ENABLER GUI
Java 1.1.6 or greater is required to run the Secure Service Enabler GUI
program.  The 3.3 version of the GUI program is ikmgui.cmd whereas the
4.0 version is gsk4ikm.cmd.  The 3.3 program is normally found in the
\ibmgsk\bin sub-directory and the 4.0 program is normally found in the
\ibmgsk40\bin sub-directory on the drive in which MPTS was installed.

NOTE: The Secure Service Enabler GUI programs do not support JAVA 1.3.

------------------------------------------------------
4.3 - SETTING JAVA_HOME FOR SECURE SERVICE ENABLER GUI
The Secure Service Enabler GUI programs (ikmgui.cmd and gsk4ikm.cmd)
will attempt to automatically detect JAVA_HOME when it's not already
defined by the user. The assumption for this auto detection is that the
environment variable LIBPATH contains the JDK library directory
"...\JAVA11\LIB".  If a user has installed the JDK in a directory with
a non-default name "JAVA11", the detection will fail and the user will
have to explicitely set JAVA_HOME environment variable prior to executing
the Secure Service Enabler GUI program.  The following error may occur if
the JAVA_HOME environment variable is not set correctly:

      Unable to initialize threads: cannot find class java/lang/Thread

----------------------------------------------
4.4 - MPTS MAKEDISK UTILITY AND SECURE SERVICE
The MPTS diskette images created by MPTS's makedisk.exe utility does
not contain the MPTS Secure Services.  The installation of MPTS' Secure
Services is only available from the CD-ROM media image.

-------------------------------------
4.5 - OVERRIDING DEFAULTS FOR IKEYMAN
MPTS installs ikminit.pro file in the \ibmgsk40\classes sub-directory. In order
to override defaults for iKeyman, the ikminit.pro file must be re-named to
ikminit.properties. The ikminit.properties file contains variable assignment
statements that allow the user to override defaults for iKeyman.  For example,
by default iKeyman uses the file named certreq.arm to contain a certificate
request.  If the user wanted iKeyman to us a different default
(say, certificate.request), they could edit the ikminit.properties file to
specify:

               DEFAULT_CERTREQ_NAME=certificate.request

The version of ikminit.pro that is shipped with MPTS has all assignment
statements commented out.  When the user wishes to change a default, they
must rename the ikminit.pro file to ikminit.properties file and edit to
uncomment the desired assignment statement.  Because the file ikminit.pro
must be renamed to ikminit.properties, this requires that the Secure
Services be installed on either a HPFS or JFS disk partition.

***************************************************************************
SECTION 5          KERNEL DEBUG NETWORK PROTOCOL
***************************************************************************

SECTION 5: KERNEL DEBUG NETWORK PROTOCOL

--------------------------------------------
5.1 - USAGE OF KERNEL DEBUG NETWORK PROTOCOL
The Kernel Debug Network Protocol (KDBNET.SYS) is one of the selectable
protocols, and is installed and configured as part of MPTS.
Use MPTS to select KDBNET.SYS in the same manner as selecting
802.2 or NETBIOS.

KDBNET.SYS, together with debug kernel, OS2KRNLD, allows remote debug of the
target machine via TCP/IP network by a host machine running ICAT.  Thus
the target machine and the host machine can be at different locations.

The  "KDB Network adapter IP address" and "KDB Network adapter subnet
IP mask" parameter fields must be changed to the actual IP address and
netmask of the local machine.


***************************************************************************
SECTION 6           TRADEMARKS AND SERVICE MARKS
***************************************************************************

Terms denoted by a single asterisk in this file
(*) are trademarks of the IBM* Corporation in the
United States and/or other countries.  These terms
include:

  IBM
  LAN Server
  MPTS  (acronym for IBM Multiple Protocol Transport Services
         for OS/2)
  NTS/2 (acronym for Network Transport Services for OS/2
  OS/2
  PC SUPPORT
  TCP/IP (acronym for IBM Transmission Control Protocol/
          Internet Protocol)

Terms denoted by a double asterisk in this file
(*) are trademarks of the Novell**, Inc. in the
United States and/or other countries.  These terms
include:

  Novell
  NetWare

IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESSED OR
IMPLIED, INCLUDING WITHOUT LIMITATION, WARRANTIES
OF FITNESS AND MERCHANTABILITY WITH RESPECT TO THE
INFORMATION IN THIS DOCUMENT. BY FURNISHING THIS
DOCUMENT, IBM GRANTS NO LICENSES TO ANY RELATED
PATENTS OR COPYRIGHTS.

