NTS/2* README (08/92)
---------------------

This README file contains information pertaining to the
installation, configuration, and operation of NTS/2.  It
provides compatibility information and other useful tips
for the use of NTS/2 functions.  The information was
collected during the final comprehensive system and
compatibility testing phases.  It was not finalized
before the publications were printed and we want to share
this information with you.  Also, should you encounter
problems with installation or customization of the
features of this product, please refer to the section
on conferencing tools later in this README for
information on how to get help.

The following topics are covered in this README:

o Conferencing Tool for NTS/2

o Emulator Configuration for 802.2 VDD

o DOS Settings - PC3270* for DOS emulator

o DOS Settings - PC3270 for Windows emulator

o DOS Settings - Attachmate's Extra! Extended** for DOS

o DOS Settings - Attachmate's Extra! Extended** for Windows

o DOS Settings - PC Support/400*

o DOS Settings - Wall Data's Rumba/400** emulator

o DOS Settings - Wall Data's Rumba/3270** emulator

o DOS Settings - TCP/IP* for DOS

o Application Considerations - TCP/IP* for DOS

o Installing Additional Network Drivers Via LAPS

o Installing IBM Extended Services V1.0 Remote Data Services

o Trademarks and Service Marks


Please refer to the following topics in the OS/2*
README for general information regarding
configuration and restrictions of DOS and Windows
applications running under OS/2 supervision:

o  Application considerations,

o  Performance of Windows Applications, and

o  Windows** Version 3.0 Programs Support



CONFERENCING TOOL FOR NTS/2
---------------------------

The OS2LAN CFORUM is available to present issues,
questions, and problems encountered during the
installation, customization and use of NTS/2.
The OS2LAN CFORUM is a conferencing tool on
the OS/2 Bulletin Board System.  To obtain
information about the OS/2 Bulletin Board
System call 1-800-547-1283 and ask for the
welcome package.




EMULATOR CONFIGURATION FOR 802.2 VDD
------------------------------------

To make your emulator easier to use, we recommend
creating an icon on your OS/2 desktop for your
emulator.  In the discussions below relating to
emulator settings, D:\EMULPATH refers to the drive
and path of where your emulator program is
installed.  CFGFILE refers to the name of your
emulator configuration file.  The path and
configuration file name of your particular emulator
will be different from the examples below.

Notes concerning Windows Emulators
----------------------------------

Note 1 - If a Windows emulator will not successfully
start while another Windows emulator is running it may
be necessary to start the emulators in reverse order.

Note 2 - If a Windows emulator will not successfully
start while another Windows emulator is running it may
be necessary to toggle (Ctrl-Esc) back and forth to the
OS/2 desktop or it may be necessary to minimize the
running emulator session before starting the second
emulator.

Note 3 - It is not possible to run two WinOS2 sessions
while using XGA video mode. Refer to the OS/2 README for
additional information on restrictions using WinOS2 and
XGA.



DOS Settings - PC3270* for DOS emulator
--------------------------------------

1.  On the Program panel, set the following
    parameters:

    Path/Filename = D:\EMULPATH\CFGFILE.BAT
    Parameters    = blank
    Working Directory = D:\EMULPATH

2.  On the Session panel, select DOS Full Screen.

3.  Before attempting to run PC3270 for DOS, you
    must edit your CFGFILE.BAT file, and add
    COMMAND.COM as the last line in the file.
    This must be done every time you change your
    emulator configuration.  Failure to add
    COMMAND.COM to your .BAT file will cause
    PC3270 to exit when it attempts to return
    control to DOS.


DOS Settings - PC3270 for Windows emulator
------------------------------------------

PC3270 for Windows can run either as a regular
Windows program (inside a Win-OS/2* session), or
it can run 'seamlessly.'  Seamless means the
PC3270 windows appear on top of the OS/2 desktop
directly, instead of appearing inside a Win-OS/2
command prompt.


To run PC3270 as a Win-OS/2 application:

1.  Create a file called CFGFILE.BAT.  This file
    should look like this:

    @ECHO OFF
    COPY D:\EMULPATH\CFGFILE.CNF D:\EMULPATH\$$TEMP$$.BAT > NUL
    CALL D:\EMULPATH\$$TEMP$$.BAT
    ERASE D:\EMULPATH\$$TEMP$$.BAT
    CALL D:\EMULPATH\SOMEFILE %1 %2 %3 %4 %5 %6 %7 %8 %9

2.  Create another file called SOMEFILE.BAT (this
    file is referenced in CFGFILE.BAT:

    @ECHO OFF
    C:\OS2\MDOS\WINOS2\WINOS2
    D:\EMULPATH\PCSPDOS.EXE -END

3.  On the Program panel, set the following
    parameters:

    Path/Filename = D:\EMULPATH\CFGFILE.BAT
    Parameters    = blank
    Working Directory = D:\EMULPATH

4.  On the Session panel, select DOS Full Screen.


To run PC3270 Seamlessly:

1.  Create a file called CFGFILE.BAT.  This file
    should look like this:

    @ECHO OFF
    COPY D:\EMULPATH\CFGFILE.CNF D:\EMULPATH\$$TEMP$$.BAT > NUL
    CALL D:\EMULPATH\$$TEMP$$.BAT
    WINOS2.COM PCS3270.EXE

2.  On the Program panel, set the following
    parameters:

    Path/Filename = D:\EMULPATH\PC3270W.EXE
    Parameters    = blank
    Working Directory = D:\EMULPATH

3.  On the Session panel, select Win-OS/2 window,
    click on Separate Session, then click on
    Win-OS/2 Settings.

4.  On the Win-OS/2 Settings panel, add the
    following to the end of the DOS_SHELL
    statement:

    /C D:\EMULPATH\CFGFILE.BAT

Note - If you start PC3270 for Windows, and get a message
saying there is invalid TSR information, then edit
the CFGFILE.CNF file and change the line
'REM TSR=N' to 'REM TSR=Y.'



DOS Settings - Attachmate's Extra! Extended** for DOS
-----------------------------------------------------

1.  On the Program panel, set the following
    parameters:

    Path/Filename = D:\EMULPATH\CFGFILE.BAT
    Parameters    = blank
    Working Directory = D:\EMULPATH

2.  On the Session panel, select DOS Full Screen.

3.  Before attempting to run Extra! for DOS, you
    must edit your CFGFILE.BAT file, and add
    COMMAND.COM as the last line in the file.
    This must be done every time you change your
    emulator configuration.  Failure to add
    COMMAND.COM to your .BAT file will cause
    Extra! to exit when it attempts to return
    control to DOS.

Note - It may be necessary to run the VDM configuration
utility, LTSVCFG, with the P=x parameter where x
is a nonzero value indicating the number of half
seconds the deadman timer will wait before expiring.
This will be necessary if the emulator looks like it is
hung. Typically this value should be set to 2 if needed.



DOS Settings - Attachmate's Extra! Extended** for Windows
---------------------------------------------------------

1.  Create a file called EXTRA.BAT.  This file
    should look like this:

    @ECHO OFF
    C:\OS2\MDOS\WINOS2\WINOS2

2.  On the Program panel, set the following
    parameters:

    Path/Filename = D:\EMULPATH\EXTRA.BAT
    Parameters    = blank
    Working Directory = D:\EMULPATH

3.  On the Session panel, select DOS Full Screen.

Note 1 - The Extra! for Windows installation program
normally modifies the AUTOEXEC.BAT file to add its
directory to the PATH statement, and to add a
DLCINTFC statement if Lan support is used.  This
information is also needed when running under
OS/2.  We suggest you keep this information in
your AUTOEXEC.BAT file, exactly as Extra! for
Windows placed it.  Alternatively, you can add the
DLCINTFC statement to your EXTRA.BAT file instead
of adding it to AUTOEXEC.BAT.



DOS Settings - PC Support/400*
------------------------------

PC Support will not run correctly in DOS Emulation
mode.  To run PC Support, you must start a version of
DOS (such as DOS 5.0, etc.) that will run PC Support.
Please refer to the Master Help Index of OS/2 for
information on how to start a specific version of DOS.
Search for 'Starting DOS.'

When you create a diskette or diskimage for a specific
version of DOS, you must insure the CONFIG.SYS file
for that DOS version loads the following device
drivers:

DEVICE=C:\IBMCOM\PROTOCOL\LANVMEM.SYS
DEVICE=D:\EMULPATH\EIMPCS.SYS
DEVICE=D:\EMULPATH\ECYDDX.SYS

In addition, you may want to create an AUTOEXEC.BAT
file for your specific DOS version that automatically
starts PC Support.  To do this, invoke STARTPCS.BAT
from your AUTOEXEC.BAT file.


1.  On the Program panel, set the following
    parameters:

    Path/Filename = *
    Parameters    = blank
    Working Directory = D:\EMULPATH

2.  On the Session panel, select DOS Full Screen,
    then click on DOS Settings.

3.  On the DOS Settings panel, set the following
    parameters:

    DOS_STARTUP_DRIVE = A:\
    KBD_CONTROL_BYPASS = ALT_ESC

In this example, DOS_STARTUP_DRIVE is set to
A:\ with the assumption you are loading the
specific DOS version from diskette.  If you
load the specific DOS version from a diskette
image file on your hard drive, update the
DOS_STARTUP_DRIVE accordingly.

Note 1 - The PC Support installation program may
update the CONFIG.SYS file and add two device
drivers 'EIMPCS.SYS' and 'ECYDDX.SYS.'  If these
statements are in your CONFIG.SYS, remove them.
Under OS/2, these statements will instead be
loaded from your bootable DOS diskette.

Note 2 - Each Virtual DOS Machine (VDM) will need a
separate APPC controller on the AS/400.  The controllers
can be exactly the same except for the LAN destination
service access point (LAN DSAP: 08).  A line in the
CONFIG.PCS needs to contain a matching TRSS entry
(TRSS 08).

Note 3 - It is necessary to run the VDM configuration
utility, LTSVCFG, with the P=x parameter where x
is a nonzero value indicating the number of half
seconds the deadman timer will wait before expiring.
Typically this value should be set to 1 for using a
single VDM and increased to 4 if additional VM Boot
sessions are active.  When additional VM Boot sessions
are active it is recommended to decrease the MAXWAIT
parameter in CONFIG.SYS to 1 second.

Note 4 - When running more than 2 sessions in a stress
environment it may be necessary to obtain the OS/2 2.0
Service Pak.

Note 5 - For valuable information required for operating
PC Support/400 in a VDM, please reference IBM
publication GG24-3856 entitled "Using DOS
PC Support/400 in OS/2 2.0 Virtual DOS Machines".




DOS Settings - Wall Data's Rumba/400** emulator
-----------------------------------------------

1.  Create a file called RUMBA.BAT.  This file
    should look like this:

    @ECHO OFF
    D:\PCS\STARTRTR D:\PCS\CONFIG.PCS
    C:\OS2\MDOS\WINOS2\WINOS2

    In this example, D:\PCS is the directory where
    PC Support is installed.  Rumba/400 requires
    PC Support in order to run.

2.  On the Program panel, set the following
    parameters:

    Path/Filename = D:\EMULPATH\RUMBA.BAT
    Parameters    = blank
    Working Directory = D:\EMULPATH

3.  On the Session panel, select DOS Full Screen.




DOS Settings - Wall Data's Rumba/3270** emulator
------------------------------------------------

1.  Create a file called RUMBA.BAT.  This file
    should look like this:

    @ECHO OFF
    D:\EMULPATH\WDTOKTSR.EXE /R=16 /T=8
    C:\OS2\MDOS\WINOS2\WINOS2

    The WDTOKTSR.EXE file is required by Rumba in
    order to use Lan support.  Refer to the Rumba
    program documentation for more information
    about command line parameters.  We have found
    the above parameters work in most cases.

2.  On the Program panel, set the following
    parameters:

    Path/Filename = D:\EMULPATH\RUMBA.BAT
    Parameters    = blank
    Working Directory = D:\EMULPATH

3.  On the Session panel, select DOS Full Screen.



DOS SETTINGS - TCP/IP* for DOS
------------------------------
Before you can use TCP/IP under OS/2 2.0, you must set
up certain DOS settings.  To create an icon and
initialize the DOS settings, follow these steps:

1.  On the Program panel, set the following parameters:

    o  Path/Filename = *
    o  Parameters = Blank
    o  Working Directory = C:\TCPDOS
      (Assuming TCP/IP was installed on C:\TCPDOS)

2.  On the DOS Settings panel, click on 'Session' and
    set the following parameters:

    o  DOS_DEVICE = C:\TCPDOS\BIN\NETDEV.SYS
      (Assuming TCP/IP was installed on C:\TCPDOS)


APPLICATION CONSIDERATIONS - TCP/IP* for DOS
--------------------------------------------
To run TCP/IP over the VDD, it is first necessary to run
LTSVCFG.COM with the parameter D=1.  This is necessary
because TCP/IP uses the direct station link of the 802.2
protocol.  If running over adapter 0 then run LTSVCFG
D=1, if running over adapter 1 then LTSVCFG / D=1, or if
running over adapter 2 then LTSVCFG / / D=1.  A slash is
used to signify the adapter number.  LTSVCFG can be
included in the AUTOEXEC.BAT file so it will be executed
automatically when you double click on the TCP/IP icon,
or it can be run manually from the DOS command prompt.
Regardless, LTSVCFG with the D=1 parameter must be run
before executing TCPSTART.BAT.

When running TCP/IP's file transfer application FTPD and
FTP it is necessary to clear the APPEND environment
variable on both the server and client machines.  This
can be done by commenting out the LOADHIGH APPEND
C:\OS2;C:\OS2\SYSTEM statement in the AUTOEXEC.BAT file,
or by entering APPEND=* at the DOS command prompt.  This
is necessary because if the files being transferred
appear in the APPEND path of the destination machine,
the APPEND path will override the specified destination
path.


INSTALLING ADDITIONAL NETWORK DRIVERS VIA LAPS
----------------------------------------------
There are two ways to install additional network drivers
using LAPS in the unattended mode.  The first is
described at the end of Chapter 3 in the LAN Adapter and
Protocol Support Configuration Guide.  In this method,
files are added to the LAPS diskette image on the code
server either in packed or unpacked format.  This method
is recommended when additional driver requirements are
known prior to LAPS installation.  Please note that this
method may only be used when INSTALL=PRODUCT in the LAPS
response file.

To install additional drivers via response files after
LAPS installation, you must specify INSTALL=ADDITIONAL in
the LAPS response file.  In this case, all the required
network driver files must be stored in a single
subdirectory. The /S: parameter of the LAPS invocation
must specify the location of that subdirectory.
Additionally, the drive on which LAPS is installed must
be specified by either the /T: invocation parameter or
the TARGET= keyword in the response file.



INSTALLING IBM EXTENDED SERVICES V1.0 REMOTE DATA SERVICES
----------------------------------------------------------

The Remote Data Services feature of IBM Extended Services
Version 1.0 should be installed using the Basic Configuration
and Installation Option from the Extended Services Installation
Options menu.  This will ensure that the all Extended Services
internal data structures are setup to recognize the presence of
NTS/2.



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
  NTS/2 (acronym for Network Transport Services for OS/2
  OS/2
  PC SUPPORT
  PC3270
  TCP/IP (acronym for IBM Transmission Control Protocol/
          Internet Protocol)
  WIN-OS/2

Terms denoted by a double asterisk in this file
(**) are trademarks of other companies.  Other
trademarks appearing in this file are owned by
their respective companies.

Rumba/400 and Rumba/3270 are trademarks of Wall Data Corporation
Extra! Extended is a trademark of Attachemate Corporation
Windows is a trademark of Microsoft Corporation.


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.

Copyright IBM Corporation, 1992, all rights
reserved.







