SBClient 5.5.0
September 2010
==============

This README document is divided into the following sections:

What's New in SBClient 5.5.0
Operating System Requirements
Data Server Requirements
Important Notes
Installation Information
Currently Supported Communication Protocols
Currently Supported Terminal Emulations
Enhancements and Fixes in Version 5.5.0
Known Issues
Miscellaneous Information


What's New in SBClient 5.5.0
============================

** Rebranded Product
--------------------
SBClient 5.5.0 has been rebranded to show ownership by Rocket Software. 


** Updated/Rebranded Documentation Set
--------------------------------------
The SystemBuilder documentation set has been updated to reflect changes in
the product, including the product name and default path names. 


Operating System Requirements
=============================

Minimum operating system requirements for SBClient 5.5.0 are:


Windows Server 2003: Service Pack 1 or later
Windows Vista: Professional, Enterprise, or Ultimate edition,
               Service Pack 2 or later
Windows XP: Professional edition, Service Pack 3 or later
Windows 7: Professional, Enterprise, or Ultimate edition


Data Server Requirements
========================

The minimum data server requirements of the SBClient 3GL Host API are as follows:

UniData 7.1.20 or later on Windows or UNIX
UniVerse 10.2.3 or later (Pick compatibility) on Windows or UNIX


Important Notes
===============

Notes on User Types for Installing SBClient on Windows
------------------------------------------------------
To install SBClient on Windows Server 2003, Windows XP Professional,
Windows Vista, or Windows 7, the user must be either an Administrator or
Power User.


Exporting SBClient Settings
---------------------------
Existing customers who installed SBClient 5.4.4 or earlier may have
session configurations, scripts, phone books, toolbars, and Smart Query
definitions that can be used in SBClient 5.5.0 or later. To save settings
from SBClient 5.4.4 or earlier, you can export the settings to a file before
installing SBClient 5.5.0 or later. After installing the latest version of
SBClient, you can then import the files containing settings that you saved.
For instructions, see Chapter 2, "Installing SBClient on a Standalone PC" in
SBClient Getting Started.


GUI Tokens and UNIX STTY Settings
---------------------------------
When installing the bootstrap for the Host Library, setting the UNIX kill
character to any character less than 127 can cause the installation to fail.

The LNEXT token (usually set to 'Ctrl - V') is a literal next character on SVR4
and 4.4+BSD UNIX. The LNEXT character is recognized on input in Extended mode
only; it causes any special meaning of the next character to be ignored. The LNEXT
character is discarded when processed, but the next character entered is passed to
the process. The LNEXT character is in conflict with one of the internal SBClient
tokens. If it is enabled, you need to turn it off. You can turn off Extended mode
by entering 'stty -iexten'. 

SBClient makes extensive use of ASCII characters 1 and 2 (Ctrl-A and Ctrl-B)
for communications protocols. You should ensure that these are not used by UNIX or
terminal server line settings.

7-bit communications utilities on Unix, such as "rlogin", should not be used in
conjunction with SBClient.


Euro Character
--------------
The Euro character is not included in the SB or System Builder font. The reason
is that there is no international consensus as to where the character should be
positioned within an OEM. IBM has decided to place the character at position 159,
while Xerox has chosen position 186, Microsoft has chosen position 128, and
Monotype and many other companies have chosen position 168.

When communicating with a UniData or UniVerse etc host, the host in most cases
uses an OEM character set. Since most Windows fonts are ANSI fonts, SBClient must
do an OEM-to-ANSI conversion on data coming from the host and an ANSI-to-OEM
conversion on data going to the host. SBClient calls the standard Windows API to
do the conversions. The problem is that the Windows API knows nothing about the
Euro or its OEM position.  

If the user is using the SB or System Builder font, SBClient does not perform a
conversion when communicating with an OEM host because these are already OEM
fonts. This means that if the application on the host sends CHAR(159), the IBM
Euro position, and System Builder font uses the Xerox position 186, the display
is incorrect.  

Therefore, SBClient needs to know the position of Euro character according to the
host and this has to match the position in the SB or System Builder font. If the
user is using an ANSI font, such as Courier New (with Euro support), SBClient
needs to perform a conversion, but the standard Windows conversion will not work.  

Currently, two solutions are available:

- If the Euro character is required, download Microsoft's new Courier font (or a
similar font from another vendor), and select it from the Setup/Fonts window.
A translation table should be set up. (For further information, see the section on
the new translation functionality in the Using SBClient manual.) The table should
specify ANSI-to-OEM mappings in the [output] section and OEM-to-ANSI mappings in
the [input] section. If using a Microsoft font, the host's Euro character position
should be mapped to CHAR(128) in the [input] section of the translation table and
vice versa in the [output] section. You can map an Alt or Ctrl key to CHAR(128) in
the [display] section so the user can enter the character from any keyboard.

- For detailed information on a second workaround solution for display of European
currency symbols, see the SBClient 5.4 New Features manual.


Installation Information
========================

There have been some reports of Norton AntiVirus causing SBClient to freeze or
fail during installation. If you experience difficulties during installation,
please disable Norton AntiVirus until SBClient installation is complete.

Microsoft Outlook communicates with an Exchange server, which tends to slow the
system dramatically during installation and DDE. We recommend closing Microsoft
Outlook while installing SBClient.

During installation of SBClient, files are copied to the directory chosen by the
user. The default installation folderis C:\U2\SBClient. Some files are copied to
other locations, as listed below.

The following SBClient files are copied to the WINDOWS\SYSTEM directory if the
files do not exist or if older versions of the files are found in the target
directory:

   MFC40.DLL
   MFC42.DLL
   MSVBVM50.DLL
   MSVCRT.DLL
   MSVCRT20.DLL
   MSVCRT40.DLL
   MSVCIRT.DLL
   MSCHART.OCX
   MSCAL.OCX
   MSCOMCTL.OCX
   PSAPI.DLL
   OLEAUT32.DLL
   COMCAT.DLL
   OLEPRO32.DLL
   ASYCFILT.DLL
   STDOLE2.TLB
   COMCTL32.OCX
   GRID32.OCX
   SBPVDT60.OCX
   MSMAPI32.OCX
   MSCHART.OCX
   MSCAL.OCX
   SB.FON
   SB.TTF
   U2LICN.DLL
   MANY2PDFX.OCX   

The following third-party software file is copied to the WINDOWS\SYSTEM directory
only if the file does not exist or if an older version of the file is found
on the target machine:
   CTL3DV2.DLL to the WINDOWS\SYSTEM directory

The following fonts are installed to the system:
   System Builder=SB.FON
   SB Font (True Type)=SB.TTF


Currently Supported Communication Protocols
===========================================

Connection by standard serial line is supported with a variety of COM
ports and baud rates. The only network communication stack supported is
TCP/IP through the Windows Socket (Winsock) interface.


Currently Supported Terminal Emulations
=======================================

SBClient currently provides support for the following terminals:
  
   ANSI
   VT52     
   VT100    
   VT220
   VT320    use VT220 with "ANSI color" on
   Wyse 50  use Wyse 60 with "Embedded" on
   Wyse 60
   Wyse 120

An SB+ mode is available for all the above terminal types. Set this mode
when using SB/XA Application Server to enable a number of subtle
functionality differences. To set the SB+ mode, open the SBClient Setup
menu. In the Terminal Setup option, select the SB+ Mode check box. We
recommend using VT220 when communicating with SB/XA for optimal performance.   


Enhancements and Fixes in Version 5.5.0
=======================================

-  In version 5.4.4, the Control Panel > Add or Remove Programs >
SBClient uninstall program did not remove SBClient. Instead, it attempted
to upgrade SBClient. This issue has been fixed in version 5.5.0 and the
uninstall program works as designed. SBXA-334

- The default installation path was changed from C:\IBM to C:\U2, and "IBM"
was removed from other path names in the product in version 5.5.0. Accordingly,
the path names have been changed in text and in screen shots throughout the
version 5.5.0 SBClient manuals. SBXA-438

- In selection grids displayed in GUI mode, changing the sort order of the
records multiple times corrupted the return value, so multivalues in @VALUE
were left empty. A fix has been implemented to prevent this problem in version
5.5.0. SBXA-1268

- In previous versions, TU.TO.EXCEL did not function with non-English
versions of Microsoft Excel. Support has been added in version 5.5.0
in SBClient as follows: If you use more than one language version
of Excel, you can create a version of EXCEL.MACRO for each language (such
as EXCEL.MACRO.FR or EXCEL.MACRO.SP) and store it in TUDEFN. TU.TO.EXCEL
will then select the required version of the EXCEL.MACRO. SBXA-1340

- The SBZ file transfer protocol failed when attempting to transfer data from
multilevel files in version 5.2.4 and later. This issue has been resolved in
version 5.5.0. SBXA-1410 

- The shape and blink properties of the cursor can be set in character mode only.
In GUI mode, Windows properties are applied. This limitation is noted in Chapter
2, "Configuring a Session," in Using SBClient. SBXA-1863

- At version 5.5.0, the SBClient silent installation program has been modified
to check for Administrator privileges, and, if absent, for Elevated privileges.
The silent installation can be run with either of these privileges. SBXA-1920 

- When installing earlier versions of SBClient on Windows Vista,
the operating system displayed an unknown publisher warning. In version
5.5.0, the SBClient installation program has been signed with the Rocket
Software certificate, and the warning is no longer displayed. SBXA-2545

- When deleting multiple Classic session configurations in SBClient, the
dialog box confirming the deletion contained a spelling error. The spelling of
"cofigurations" has been corrected to "configurations". SBXA-2560 

- In versions 5.3.4 and later, downloading a file using the Network Copy
protocol failed if the process took more than two minutes. This issue has
been resolved in SBClient 5.5.0. SBXA-3025

- In previous versions of SBClient, GUI screens were not downloaded
when performing file transfers using the Network Copy protocol on Windows
Vista. This issue has been addressed so file transfers download GUI data
properly in Network Copy mode. SBXA-3061

- If a code table is updated by an expression and the expression supplied  
value with leading zeros, the leading zeros were suppressed. This has been
fixed. SBXA-3290

- Enhancements have been made in version 5.5.0 to remove SBClient's
dependencies on the BTrieve database engine. Due to the change in file
format, you may want to save settings from SBClient 5.4.4 or earlier. For
further information, see the section "Exporting SBClient Settings" above.
SBXA-3436

- When running SBClient in GUI mode on Windows 7 or Vista with the Aero theme,
menu bars disappeared and then reappeared after clicking or rolling the mouse
over the area or running another process. A code fix has been implemented in
version 5.5.0, and menus are displayed normally. SBXA-3453  
  

Fixes in Version 5.4.4
======================

- If a code table is updated by an expression and the expression supplied  
value with leading zeros, the leading zeros were suppressed. This has been
fixed. 11190*USA 

- In selection grids displayed in GUI mode, changing the sort order of the
records multiple times corrupted the return value, so multivalues in @VALUE
were left empty. A fix has been implemented to prevent this problem in version
5.4.4. 11488*USA


Fix in Version 5.4.3
====================

- A memory conflict that occurred under certain circumstances caused sbocx.dll to
fail. This issue has been resolved in version 5.4.3. 11293*USA


Enhancements and Fixes in Version 5.4.2
=======================================

- In versions 5.3.7 through 5.4.1, if users selected an item in a grid and
clicked the copy button on the grid's toolbar, the SBClient window was minimized.
This has been fixed. 7463*USA  

- In SBClient versions 5.3.4 and later, a customer experienced a problem in which
VT220.DLL sometimes prevented display of data in GUI screens. A fix to VT220.DLL
that existed in version 5.3.3 was removed in versions 5.3.4 and later; that fix
has been restored to correct the problem. 9562*USA  

- SBClient 5.4.1 and later have been tested and certified to install and run
on Windows Vista. 35849*USA

- In SBClient versions 5.4.2 and earlier, online Help is distributed in the .hlp
file format. To view the Help on Windows Vista, you must download the winhlp32.exe
program from Microsoft This free download is available at the following URL:
http://www.microsoft.com/downloads/details.aspx?familyid=6ebcfad9-d3f5-4365-8070-334cd175d4bb&displaylang=en
35893*USA

- The Windows Vista security feature does not recognize SBClient as a known
publisher. When installing SBClient 5.4.1 or later on Windows Vista, the unknown
publisher warning appears, and you must clear the warning to proceed with the
installation. 35897*USA
 

New Features and Enhancements in Version 5.4.1
==============================================

- SBClient 5.4 introduced the silent install feature. In a silent install,
the program looks at the license.txt file to get four items of data required
to register the product: Serial Number, User Name, Organization, and Key.
It then passes this data as arguments to the register.exe utility. In version
5.4, register.exe did not provide a return code to indicate whether SBClient
was registered successfully using these four data items as input. At version
5.4.1, register.exe writes a return code and associated message to the
licenserc.txt file:
  0 - SBClient was licensed successfully.
  2 - User name and organization name are required.
  3 or 4 - Invalid serial number or license key.
You can check the licenserc.txt file for the return code and associated
message, or you can find the same information in the sbclient_install.log
file under the installation directory. 35077*USA

- At version 5.4.1, SBClient supports the ability to distribute Secure
Sockets Layer (SSL) configuration in a silent install. Complete the
following steps to set up a silent install with SSL:
  1. On the local machine, install SBClient to the same drive and
     directory in which it is to be installed on the target machines. 
  2. On the local machine, create a certs directory under the
     SBClient installation directory.
  3. In this certs directory on the local machine, create the SSL
     certificates to be distributed to the target machines.
  4. Configure the SSL property list in SBClient and make sure it
     works as expected.
  5. Exit SBClient.  
  6. A new utility called SBCSSL.exe is shipped with SBClient 5.4.1.
     On the local machine, choose Start > Run, and enter SBCSSL.exe
     at the Open prompt. The utility creates a file named SBClientSSL
     in the current directory. The file contains SSL configuration
     information.
  7. Create the silent install master image (usually a CD or other
     media for use in distributing the silent setup to the
     target machines):
     - Copy the SBClientSSL file from the local machine to the
       master image media.
     - Create a certs directory on the master image media. Note that
       the SBClientSSL file and the certs directory must both exist
       in the installation directory of the distribution media to
       enable the silent setup to create a certs directory on the
       target machines. 
     - Copy all certificates from the certs directory on your local
       machine to the certs directory on the master image media.
     - Create a silent install response file called setup.iss,
       following the instructions under "Creating a Response File"
       in Chapter 4, "Installing SBClient 5.4 in Silent Mode" in the
       SBClient Getting Started manual.
     - Copy the SBClient setup.exe and setup.iss files to the
       master image media. 
  8. Run the silent install, following the instructions under
     "Running the Silent Setup" in the same chapter.

When running a silent install that has been set up in this manner,
at the end of the install, the program opens the SBClientSSL file on
the distribution media and applies the SSL configuration information
to the Registry on the target machine. It then creates a certs
directory on the target machine and copies all certificates from the
certs directory on the distrubtion media to the certs directory on
the target machine.

As a related enhancement, two new options have been added to the
Setup menu. The Export SSL Settings option is for use in creating an
SBClientSSL file. It calls SBCSSL.exe, which gets SSL items from the
Registry and writes that content to the SBClientSSL file. The Import
SSL Settings option is for use in copying the content of the
SBClientSSL file to the Registry. It calls SBCSSL.exe, which reads
the SBClientSSL file and writes its content to the Registry.    
35326*USA   

- The MS_Terminal_Server.doc file was updated to remove references to
terminal server licensing and non-terminal server licensing. In SBClient
version 5.2.4 and later, only one type of SBClient license is supported,
and it is used for both terminal server and non-terminal server
installations. 35223*USA 


New Features and Enhancements in Version 5.4
============================================

- The SBClient 5.4 installation program was rewritten in InstallShield 10.5,
bringing it current with industry standards. The new installation program
offers a silent installation as well as the standard installations on
stand-alone PCs and network server/client PCs. For details, see the SBClient
5.4 New Features manual on the documentation CD. 5395*USA

- A new dialog box has been added in the SBClient 5.4 installation program
that enables users to select a preference for running multiple sessions of
SBClient on a single instance of the SBClient engine or multiple instances
of the SBClient engine. For information about this feature of the new
installation program, see the SBClient 5.4 New Features manual on
the documentation CD. 34796*USA      

-  SBClient 5.4 supports two variations of the launch screen, offering you a
choice of the legacy launch screen or a new launch screen in the standard U2
format as a preference. For detailed information about the new launch screen
and setting or changing your preference, see the SBClient 5.4 New Features
manual on the documentation CD. 34217*USA 

- New splash screens are displayed when starting SBClient or getting
information from Help > About SBClient. For details, see the SBClient 5.4
New Features manual on the documentation CD. 3865*USA

- The Start bar and system tray icon for SBClient sessions has been changed
from the legacy icon to a new icon. 34597*USA  

- In previous versions, SBClient sent a warning message to the user every two
minutes if the product was installed without an authorization key or license
number. At version 5.4, SBClient no longer sends warning messages in this
situation. If the product is installed without an authorization key or license
number, it runs for a trial period of 60 days and then stops. This feature is
documented in the SBClient 5.4 New Features manual on the documentation CD.
3693*USA   

- At version 5.4, SBClient upgrades to new open SSL libraries. These new SSL
libraries are the same as those used in UniData 7.1 and incorporated in the
forthcoming release of UniVerse 10.2. For details, see the SBClient 5.4 New
Features manual. 33507*USA

- The license text files are now included on the product CD the location
of the license files is shown on the splash screen displayed from Help >
About SBClient. 33179*USA

- The InstallShield program for SBClient 5.4 implements a Software
Electronic Licensing (SEL) version of the license agreement using the
License Access Process (LAP), in compliance with industry standards.
32600*USA


Known Issues
============

- Cursor Properties Cannot Be Set in GUI Mode
The shape and blink properties of the cursor can be set in character mode
only. In GUI mode, Windows properties are applied. This limitation is noted
in Chapter 2, "Configuring a Session," in Using SBClient. 9537*UK

- Limitation of Secure File Transfers through SSL
SSL provides secure file transfers only if you use the SBZ file transfer
type. Other file transfer types do not support SSL functionality. Even if
SSL is enabled for the session, file transfers with FTP or Network Copy
are not secure. Notes have been added in the Using SBClient manual.
34290*USA and 34352*USA

- Long Numbers Display Incorrectly in GUI ListView Mode
Due to limitations of ActiveX controls, long numbers are truncated or padded
with zeros, or digits are overwritten in GUI ListView mode. 7789*USA

- Problem with Deleting User Environment Variables
When attempting to delete a user environment variable, the user
highlights the variable and clicks the Delete button. The variable is
deleted from the display; however, the variable remains in the sbopen.ini
file. This issue will be addressed in a future version. 5345*USA

- Issue with Running SBClient on Dual Monitors
When running SBClient in GUI mode on a system enabled for dual monitors
with SB+ MAINWIN running on the secondary monitor, SB+ screens and dialog
boxes are displayed in the main monitor. This behavior does not comply
with Windows standards, which specify that the program remember the
monitor on which the screen was last displayed. 34167*USA

- Message Text in Deleting Multiple Configurations
When deleting multiple SBClient configurations, the confirmation message
is the same as that displayed when deleting a single configuration.
34798*USA

- Pressing ESC in Delete Confirmation Dialog Box Executes the Deletion
Regardless of whether the OK or Cancel button has focus in a delete
confirmation dialog box, if you press ESC or click the Close button
(the X in the upper right corner of the dialog box), the deletion is
executed.  34799*USA

- Date Fields Sorted as String
Date fields are sorted as strings in list view in GUI mode. This is a known
issue with GUI mode that will be addressed in a future version. 4249*USA

- SBClient Does Not Support Roaming User Profiles
The user profile is stored on the C: drive in Documents and Settings on the
user's computer, so roaming user profiles are not supported. 4023*USA      

- Printing PCL or Binary Files Using AUX Printing
Users requested the ability to print a PCL file using AUX printing. However,
the AUX printing feature is not designed to print PCL or binary files. The
original idea of AUX printing was that whatever would normally be displayed on
the terminal screen would be diverted to the printer. Based on this principle,
you would never have the ability to dump a binary file to your terminal screen
because it does not handle binary data. The same holds true of terminal emulation:
SBClient cannot handle binary data in this mode.
Workaround solution:
Transport the PCL file to the client and print from there without going through
the AUX printing interface and emulation. 5461*USA

- SBClient Does Not Support All Character Sets
Although Windows 2000, Windows XP, and Windows 2003 provide full multilanguage
support, SBClient supports only the English and Western European character sets
on these operating systems. 4290*USA 


Miscellaneous Information
=========================

- UniVerse Case Inversion
When logging in to a UniVerse account, UniVerse inverts the current case of the
characters. This can cause problems with the 3GL Host API communicating with the
client. We suggest that you turn off case inverting in a login proc/paragraph.

- The Wyse terminal emulations use the Wyse ANSI keyboard.  If you want to
emulate the Wyse EPC keyboard remap, using the Terminal Configuration>Key
Mapping dialog box to remap the following keys:
	  Insert to (27)r
	  Shift+Insert to (27)q
	  Delete to (127)
	  Shift+Tab to (27)I

- Input Buffer Size
On some platforms, when data is sent to the host where the data is larger than
the input buffer, the system may "hang".  In most cases SBClient knows the 
correct size of the input buffer and will break the data into small enough 
blocks, however there are some cases where SBClient only finds out the size 
after the data transfer has already failed.  SBClient always tries to re-send 
the data but on some platforms it is too late.  If you experience problems 
when uploading the host code or doing DDE transfers, set the value of the 
input buffer to an actual value rather than the default of Auto.  If the 
system hangs again, try a smaller value.  Keep trying smaller values until the
system works correctly.

- GUI Watchdog Timer
When in GUI mode, SBClient periodically sends a sequence to the host to check
that the host is still 'alive'. If the host fails to return a sequence within
a certain length of time, SBClient knows that it is not running and displays a
dialog box to inform the user. The frequency at which SBClient checks the host
is called the watchdog timer. The timer can be configured in the GUI parameters
setup screen. The default value is 0 seconds (the feature is turned off). A
second parameter controls the timeout period, or the length of time to wait after
sending an escape sequence to the host before displaying a dialog box. You can
also set this value from the GUI parameters screen. The default timeout period is
0 seconds (the feature is turned off). Setting the above values to 0 switches off
the watchdog timer.  

- Network Copy
If you are using Network Copy between multiple NT domains (for example, the domain
you need to connect to is different from the one which you logged in to), we
recommend that you create a drive mapping to the TEMP directory on the Windows NT
server. See the online help for instructions. Mapping a drive will avoid problems
with authentication when connecting to this domain. Note: This drive mapping
should always be reconnected at login time.
