===================================================================
			 RALLY! for AS/400
			    Version 2.0a
			   Release  Notes
===================================================================

Copyright 1992-1995 by                       Attachmate Corporation
Attachmate Corporation.                      May 1995   
All Rights Reserved.


------------
INTRODUCTION
------------
						 
Welcome to RALLY! for AS/400 and EPC 5.0.  This file contains late-
breaking information that is not in your RALLY! documentation. This 
file covers the following topics.                           

* General guidelines
  - Installation
  - Migration Aid
  - TN5250 and TCP/IP
  - NS/Router
  - PC Support/400
  - Changing Routers
  - Token-Ring Network
  - Banyan SCS support
  - ATM Select Comm Server Support
  - MS SNA Server Support
  - Connecting to OS/400 Version 3 Release 1

* AS/400 ODBC Driver notes
* DBQuery
* WinHLLAPI Support
* Printer emulation notes
* File Transfer
* Toolbar
* Security Enhancements
* 122-Key Keyboard driver
* Customer support number


-----------------------
INSTALLATION GUIDELINES
-----------------------

RALLY! for AS/400 requires Windows 3.1 or above.

We do not recommend EGA screen resolution for this product.

If you are installing over a previous version of RALLY!, please be 
aware of the following: 
     
  The installation process automatically copies the files that 
  contain your previous version's session preferences. Session 
  customization files in the installed directory (typically 
  C:\USER) are copied to a new directory, such as C:\USEROLD. 
  The session customization files are then overwritten with new
  information.  

  Session customization files exist in the installed directory 
  (default is C:\USER) as keyboard files, keyboard macros, 
  color attributes, and session settings. The files that are 
  saved and overwritten are:

	COLR.ATT     - color attribute table
	MONO.ATT     - monochrome attribute table
	KB101.xx     - 101-key keyboard file
	KB83.xx      - 83-key keyboard file
	KB101IBM.xx  - 101-key IBM keyboard file
        KB122IBM.xx  - 122-key IBM keyboard file
        SMARTPAD.INI - SmartPad layout
	EW400.INI    - display and printer session settings
	DSPMSG.RCD   - sample keyboard macro
	SIGNOFF.RCD  - sample keyboard macro
	
  These files are all stored in ASCII format.
     
  You can use an editor (such as the DOS editor) to copy portions 
  of the previous customization files from USEROLD to the new 
  files in the USER directory.  If you do not want to save any of 
  your previous version's customization files, you can safely 
  delete the entire USEROLD directory.


Migrating from RALLY! version 1.x to 2.0
----------------------------------------

Please be aware that the ew400.ini file from RALLY! versions 1.x will
not work with RALLY! 2.0. You will need to reconfigure your RALLY!
sessions.
 
---------------------------------------------
Migration Aid: Installing Rally! over IRMA400
---------------------------------------------

RALLY! 2.0a will install over a previous version of RALLY!, or into
a default directory c:\epclient. It will not overwrite or remove
an existing IRMA 400 installation. 

However, you have the option of running the IRMA to RALLY! Migration Aid
located on the EPC 5.0 distribution media as migrate.exe. Refer to the 
on-line help for more information on this feature.

If you install Rally! over IRMA 400 and use the Netsoft router, be
aware that your router (.rtr) files must be updated in regards to
the router translate tables, or an error will occur. This is because 
the .rtr files contain the directory name of your IRMA 400
installation.  To prevent problems, edit the .rtr file, find the
[Workstation] section, and change the line:
 
'Translate Table= C:\IWA\RTR\E037A437.MAP'

to:
 
'Translate Table= C:\epclient\NSROUTER\E037A437.MAP'.

Note: The Migration Aid should only be used for regular installs,
and not for LAN installation.  That is, when you install the
RALLY! files to or from a shared file server then you should not
run the Migration Aid.

-----------------
TN5250 GUIDELINES
-----------------

This version of RALLY! supports Telnet.  To start a RALLY! session 
using a TN5250 connection, a compatible TCP/IP stack must be loaded 
on your workstation.  You can use any Windows socket (WINSOCK) 1.1 
compliant stack. The RALLY! for AS/400 package includes a coupon 
for Novell's LAN Workplace for DOS TCP/IP transport stack. Please 
refer to your documentation for instructions on loading this or 
other stacks.

   NOTE: When using RALLY! with a TCP/IP connection, file 
   transfer and printer emulation are not supported.


Troubleshooting TN5250
----------------------
If you are having difficulty establishing a connection with TN5250, 
make sure you have loaded the correct Windows or DOS device drivers
for the TCP/IP stack you are using.

Try to PING your host after successfully installing and loading
a TCP/IP stack.  If you cannot PING the host, then the problem is
either in loading the stack, or with the connection to the host.

Make sure that the TCP/IP address is correctly entered.

If you use a short name or alias, make sure they are defined in a
host table.

Make sure you are using a compatible TCP/IP stack.  The TN5250 
software was tested with the following TCP/IP stacks:
        
*  Attachmate Link/TCP version 3.21 and above
*  Novell LAN workplace version 4.12
*  Netmanage Chameleon and NFS version 3.11 and above
*  Windows for Workgroups TCP/IP version 3.11
*  LANmanager version 2.2 (LANmanager requires the latest 
   winsock.dll files from Microsoft)
*  Wollongong Pathways version 2.1.1 
*  Sun NFS version 5.0
*  FTP version 2.3 and above (including OnNet)
        
--------------------
NS/ROUTER GUIDELINES
--------------------

NS/Router was tested with NetWare for SAA Beta 2.016.

Please note that PC Support/400 must be installed on the AS/400
if you will be running RALLY! File Transfer, or using any advanced
APIs, such as ODBC.

If using the NS/Router to connect to a Netware for SAA 2.0 server,
please note that the router provides a TLI connection to the server
via IP using the Netware LAN Workplace for DOS stack ONLY. If the
stack is not loaded or missing, errors will occur and the connection
will fail.  Refer to the documentation which accompanies the Netware
LAN Workplace stack for information on configuring and loading the
stack. 

In any instance where the NS/Router is removed from Windows, please
be aware that the Windows drivers for 802.2 (VNS8022.386) and SDLC
(VNSAINTD.386) should also be removed from the SYSTEM.INI file to 
prevent errors from occurring during Windows startup.

For further late breaking information, please refer to NSROUTER.TXT
in C:\nsrouter.
 
-------------------------
PC SUPPORT/400 GUIDELINES
-------------------------

You must have PC Support/400 installed on your AS/400 and on your 
workstation if you are not using the NS/Router.

IBM requires that the MS Windows compatibility program, PCSWIN, is 
installed on your PC.  PCSWIN enables PC Support/400 functions to 
work correctly with Microsoft Windows.  

PCSWIN is included with PC Support/400 and can be copied to your
PC from a shared folder on the AS/400:

	If you are using OS/400 Version 1 Release 3.0, then you
	must have PTF LF70676 loaded, or Version 2 Release 1.0,
	which provides PCSWIN.COM in the QIWSFLR folder.

	If you are using OS/400 Version 2 Release 1.1 or 2.0, 
	PCSWIN.EXE is provided in the QIWSFL2 folder with the 
	standard (PID) distribution tapes. 

To install PCSWIN on your PC, run the PC Support/400 configuration
program CFGPCS.EXE, and set the Windows option to YES.  If you are
using a version of PC Support earlier than V2R2, you must copy the
PCSWIN program from the QIWSFLR folder on the AS400.

The PCSWIN program should be loaded after the PC Support/400 router
program STARTRTR.EXE.  CFGPCS creates the batch file STARTPCS.BAT 
to start these programs in the correct order.

You can run RALLY! concurrently with PC Support/400 functions, 
including virtual print and shared folders. However, it is not
necessary to load these functions in order to use RALLY! for 
AS/400.

----------------
CHANGING ROUTERS
----------------

Note: RALLY! supports only one type of APPC router at a time. If you
change routers, you may need to re-install RALLY! and choose a new
connection type. 

For more information, refer to the NS/Router-Configuration and 
Troubleshooting Guide, under Setup and Installation.

---------------------
TOKEN RING GUIDELINES
---------------------

You can use Token-Ring to connect to both a mainframe and an AS/400
using the two Attachmate Windows products: EXTRA! for 3270, and 
RALLY! for AS/400. Note that if you want to use both Windows 
products, you must change the Local Area Network settings using the
NS Configurator program when you configure the router.

*  For the 3270 version of EXTRA! for Windows, change the following
   Local Area Network setting:
	
	- IBM Token-Ring Source SAP
	  Default is 04 for both NS/Router and EXTRA! for Windows. 
	  Change the NS/Router's Source SAP to another SAP that is 
	  available for SNA. Note that the AS/400 must be configured 
	  for the same SAP. The available SAPs are listed in the
	  Token-Ring line description on the AS/400.

*  If you are using a Madge Token-Ring board, perform the following
   steps:

	1. Replace the IBM LAN Support Program drivers (DXMC0MOD.SYS
	   and DXMA0MOD.SYS) with the SMARTLSP driver included with 
	   your Madge board.

	2. Change the default I/O address for the Madge board (0A20) 
	   to the IBM-supported range--either 2A20 or 3A20. (Switch 
	   settings 1 and 2 on the board must be off.)

	3. If you are using DOS 5.0, specify the low memory option 
	   in your CONFIG.SYS file.


BANYAN SCS Support
------------------

Support has been added to connect RALLY! for AS/400 to a Banyan SCS 
communications server. You must configure and run the Banyan APPC
client before starting a RALLY! session. 

ATM Select Comm Server Support	
------------------------------

Support has been added to connect RALLY! for AS/400 to an Attachmate
Select Communications server. You must configure and run the ATM
Select APPC client before starting a RALLY! session. 

MS SNA Server Support 
---------------------

Support has been added to connect RALLY! for AS/400 to a Microsoft
SNA Communications server. The Microsoft SNA Client files are 
automatically loaded when you select MS SNA Server at install.  You 
will automatically be asked to configure the MS SNA APPC client
before starting a RALLY! session. 


Connecting to OS/400 Version 3 Release 1
----------------------------------------

If you are using Microsoft SNA Server, ATM Select Comm Server, or 
Banyan SCS connection types and you need to connect to an AS/400
running V3R1, insert the following line into the [Common] section 
of the EW400.INI file in the \USER directory:

SWCSyncLevel=0

----------------------------
Attachmate ODBC DRIVER NOTES
----------------------------

Introduction
------------

The Attachmate ODBC driver is designed to be used with the syntax
supported by SQL/400, even if you don't have SQL/400 on your AS/400.

Suppressing the Connection Window
---------------------------------

If you do not want the connection window displayed, add the fol-
lowing setting to the 'data source' section of your ODBC.INI file.

 DispCnxBox=No

Specifying YES will display the window.


Changing the Number of Buffered Lines
-------------------------------------

When reading a table on the AS/400, the driver will read a packet 
of lines to optimize the read process. The default value is a 
packet of 100 lines. 

You can modify this value by changing the following line in the 
'data source' section of your ODBC.INI file.

 NumRowsBufferized=VALUE

where VALUE equals the lines you want in the packet (default=100).


SYS/SQL Naming Convention Option
--------------------------------
By default, the *SYS option naming convention is selected. If the 
option *SYS is selected, the file name will be used in the
data source triplet (LIBRARY/OWNER/FILENAME). If the option *SQL 
is selected, the table name will be used in the data source 
triplet (LIBRARY/OWNER/TABLENAME).  For most ODBC programs,
it is recommended that you chose the *SQL option.


---------------
DBQUERY SUPPORT
---------------

To use DBQuery, you must first create the RALLY! DBQuery program 
group.

To do this:

1) Double-click the DBQuery Auto-Config icon to add the RALLY! 
   DBQuery icon to the RALLY! program group.

2) Click the RALLY! DBQuery icon to display the RALLY! DBQuery 
   1.00 program group. This program group contains icons for 
   running DBQuery, for configuring DBQuery, sample queries, and 
   the DBQuery User Manual.

RALLY! is now ready to run DBQuery. If you are familiar with 
DBQuery, select the RALLY! DBQuery icon. If you need more infor-
mation, click on the DBQuery User Manual icon.   



-----------------
WinHLLAPI SUPPORT
-----------------

WinHLLAPI is an automation tool which gives programmers the ability
to create client applications that communicate with an AS/400 host 
via the RALLY! product.  Programmers using Visual Basic, C, C++, or
other high level programming languages can access WinHLLAPI according
to the Microsoft Windows HLLAPI Specification.

By default, the AHLLAPI.DLL library is located in the \epclient
directory.

Note on HLLAPI Short Name Assignment:

In the current version of RALLY!, default HLLAPI Short Names are 
automatically assigned to each session during session configuration. 
    
EHLLAPI support added
---------------------

   The following files have been added for EHLLAPI support:

     ACS3EHAP.DLL  (installed in c:\epclient
     ACS3EHAP.H    (installed in c:\epclient
     ACS3EHAP.LIB  (installed in c:\epclient

   The EHLLAPI compatibility layer is a "wrapper" DLL (ACS3EHAP.DLL) 
   which basically calls the WinHLLAPI interface with the exact 
   same function numbers and parameters.  WinHLLAPI is based on 
   EHLLAPI with additional functionality for Windows 
   application support.  The major difference in WinHLLAPI is 
   that the user needs to call an initialization to the DLL 
   before using it, otherwise it is the same. 

   By using the EHLLAPI pass-through (ACS3EHAP.DLL) the 
   application will not need to call the initialization 
   function before doing a HLLAPI function call.

   To use the EHLLAPI pass-through, the DLL (ACS3EHAP.DLL) must 
   be in the default sub directory where the ahllapi.dll is 
   located.  By default this is the "C:\epclient" directory.  

   A Windows application may then be written in C or C++ using
   any Windows compatible compiler and development environment.
   Include the pass-through header (ACS3EHAP.H) file into the C
   or C++ source. This will give the EHLLAPI function call and
   function values.  Link with the EHLLAPI pass-through LIB 
   (ACS3EHAP.LIB).  

   Make EHLLAPI calls using the EHLLAPI function listed in the 
   header file. To find out what the parameters are,  consult the 
   WinHLLAPI manual which is available by contacting Attachmate. 
   (The EHLLAPI parameters are the same as the WinHLLAPI 
   parameters).


----------------------
RALLY! SAMPLE PROGRAMS
----------------------

Rally! Sample Programs are included with Rally 2.0. To install the
sample programs:

1) Make sure RALLY! 2.0 is installed on your PC but not running. 

2) The RALLY! Sample programs are located in the directory:
   EPCLIENT\SAMPLE1 and SAMPLE2

3) Install the RALLY! Sample Programs by running the setup program
   located in \SAMPLE1 using the Windows Run command. 

(The Rally! WINHLLAPI Developer's Guide may be ordered via the 
coupon enclosed in this package.)

------------------------------
PRINTER EMULATION ENHANCEMENTS
------------------------------

*  New easier to use and understand interface

*  Improved handling of user-defined page sizes

*  Support for Printer Transparency (ASCII Passthrough) has been
   added.  This will allow the embedding of printer control 
   information in a file in order to activate special printer
   functions, and allow ASCII documents to be printed.

*  Support has been improved for HP IV printers

-------------
FILE TRANSFER
-------------

Enhancements
------------

Support for BASIC Sequential file transfers has been added. These
files are used for sequential processing. Fields may be character
or numeric and are of variable length.  Note that the character  """ 
(double quote) is not supported as part of a string when doing an
upload.

Batch file transfers may be run from a command line using multiple
.ato files. An example would be:

        ew400ft c:\epclient\user\finance.ato sales.ato

The "-b"  option for batch transfers will shut off the 'overwrite
file warning message' and allow for hands free batch processing of 
multiple file transfers. An example of this would be:
 
        ew400ft -b c:\epclient\user\*.ato

This would run the file transfer for each .ato file found and not
show the 'overwrite file warning' message.  Please note that the
files selected for transfer can overwrite existing files with the
same name without warning with the "-b" option specified. 

Other options are as follows: (all will ignore .ato option settings)

-Cd to disable closing application when done
-Ce to enable closing application when done

-Ad to disable auto run
-Ae to enable auto run

-N to disable complete notification box
-M to minimize when running

Both 'drag and drop' and batch file transfers now retain the 
settings of each individual .ato file, including menu options.

Import Feature
--------------

File transfer import feature has been added. This allows files 
created via PC Support or Rumba to be imported and converted to
the Attachmate .ato format.

Please note that not all imported file transfer files are supported
in Rally!

Using Autostart
---------------

If you have set up the NS/Router to autostart, no system names appear
in the Host field of the file transfer edit box. This is because the 
AS/400 system links remain inactive in the router until you enter a 
name in the Host field and search for a file or run a transfer.

-------
TOOLBAR
-------

The Rally! 2.0 toolbar is now completely editable. Buttons may be
added or deleted from the standard Rally! toolbar. Support has been
added as well for allowing custom toolbar buttons to run user defined
programs. Refer to the extensive on line help for more information
on this feature.

--------------------------
SECURITY FEATURES ENHANCED
--------------------------

Improvements have been added for security in file transfer and 
session configuration. Administrators may limit these capabilities
or lock them via password control. Refer to the extensive on line
help for more information on this feature.

-----------------------
122-Key Keyboard Driver
-----------------------

Support has been added for the BOS 122-key keyboard. This support 
includes a device driver KBD122.DRV, located in the RALLY! install
directory. You must add the following line to the [boot] section
of the Windows System.ini file:

keyboard.drv=c:\epclient\kbd122.drv

----------------
CUSTOMER SUPPORT
----------------

For technical assistance with RALLY! for AS/400, call Attachmate 
Customer Support at 1-800-933-6755. (1-206-644-4010)





