**********************************
DB2 OLAP Server Version 1.0.1
**********************************
README for SERVER only
**********************************

Welcome to IBM DB2 OLAP Server Version 1.0.1.

This README file contains information about the Server component of
DB2 OLAP Server.  This README file contains the following sections:

-------------------------------------------------
1.  ABOUT THE NATIONAL LANGUAGE VERSIONS
2.  WHAT'S NEW IN VERSION 1.0.1
3.  INSTALLATION UPDATES
4.  LATE-BREAKING DOCUMENTATION FOR VERSION 1.0.1
5.  KNOWN PROBLEMS
6.  WHERE TO FIND FIXES


1.  ABOUT THE NATIONAL LANGUAGE VERSIONS
----------------------------------------

IBM DB2 OLAP Version 1.0.1 is available in 13 languages which are listed
in the table below.

If you install the client components, make sure you also read the client
README file for your language.  The client README is stored on the
product CD-ROM and is not installed on your system with the product.
The following table lists the client README file location, where "x"
is the letter assigned to your CD-ROM drive:

 English                x:\language\us\
 Brazilian Portuguese   x:\language\br\
 Simplified Chinese     x:\language\cn\
 Czech                  x:\language\cz\
 German                 x:\language\de\
 Spanish                x:\language\es\
 French                 x:\language\fr\
 Hungarian              x:\language\hu\
 Italian                x:\language\it\
 Japanese               x:\language\jp\
 Korean                 x:\language\kr\
 Russian                x:\language\ru\
 Traditional Chinese    x:\language\tw\

Data code page conversion is not performed between the DB2 OLAP
Server clients and server.  Make sure the PC compatible code page of your
client machine matches the code page of your server machine.

If you have installed Simplified Chinese, Traditional Chinese, or Korean,
make sure you download the latest fix, which contains important fixes for
double-byte character set (DBCS) systems.  The fixes are available at the
IBM DB2 OLAP Server service web site:
     ftp://service.software.ibm.com/ps/products/db2olap/

The Using DB2 OLAP Server manual and the Spreadsheet Add-in User's
Guides are now provided online in Adobe Acrobat 3.01 .PDF format.  The
U.S. English edition of the Acrobat Reader is also provided on the
DB2 OLAP Server CD-ROM.

The PDF edition of Using DB2 OLAP Server is available in some of the
languages listed above.  To find out if an edition is available in your
language, look in the "x:\language\yy" directory on the CD-ROM, where
"x" is the drive letter of your CD-ROM, and "yy" is the two-character
abbreviation for your language.  If an edition is not available in
your language, use the English edition.

The PDF editions of the Spreadsheet Add-n User's Guides are installed
with the product.  They are located in the "z:\essbase\client" directory,
where "z:\essbase" is the path on which you installed the product.


2.  WHAT'S NEW IN VERSION 1.0.1
-------------------------------

DB2 OLAP Server Version 1.0.1 has the following new features:

- Changes to View Naming Convention
The naming convention for the DB2 OLAP Server relational views has
changed, as shown in the following examples.  The tables assume a
database called "BBBB" in an Application called AAAA, and a logon ID
of "userid":

  View type         Old view name              New view name
  ---------         -------------              -------------
  Cube view         userid.AAAABBBB@CUBEVIEW   userid.AAAABBBB_CUBEVIEW
  Fact view         userid.AAAABBBB@FACTVIEW   userid.AAAABBBB_FACTVIEW
  Star view         userid.AAAABBBB@STARVIEW   userid.AAAABBBB_STARVIEW
  LRO view          userid.AAAABBBB@LROVIEW    userid.AAAABBBB_LROVIEW
  Alias Id view     userid.AAAABBBB@ALIASID    userid.AAAABBBB_ALIASID

The following tables shows name changes for dimension views, assuming a
dimension called "PRODUCT":

  View type        Old view name              New view name
  ---------        -------------              -------------
  Dimension view   userid.AAAABBBB@PRODUCT    userid.AAAABBBBD_PRODUCT
  UDA view         userid.AAAABBBB@@PRODUCT   userid.AAAABBBBU_PRODUCT
  RAT view         userid.AAAABBBB@_PRODUCT   userid.AAAABBBBR_PRODUCT

Any DB2 OLAP Server V1.0.0 relational views that you have are
automatically migrated to the new naming convention when you first
access the corresponding database/cube.  However, if you have any
scripts or programs of your own that refer to these view names
directly then you should alter them to use the new names.

-  Euro Currency Symbol
You can include the Euro currency symbol as part of a data field
in your data load source file.

-  Linked Reporting Objects Support for URLs
You can now link Uniform Resource Locators (URLs) to data cells.

-  INCRESTRUC parameter
The INCRESTRUC parameter is not supported by DB2 OLAP Server.

-  Logging Query Durations via ESSBASE.CFG
A new parameter, TIMINGMESSAGES, lets you control whether DB2 OLAP
Server logs the duration of each spreadsheet and report query in the
application log file.

- Row Support in Spreadsheet Add-in for Excel 97
The number of rows supported by the Spreadsheet Add-in for Excel 97
has increased to 65,536 rows from 16,384 rows.  Excel 95 still
supports 16,384 rows.

-  Support for Multibyte Translations
DB2 OLAP Server V1.0.1 is now enabled to support multiple-byte
character sets, like Mandarin Chinese or Kanji.

-  Some Books Now Online
The Using DB2 OLAP Server manual and the Spreadsheet Add-in User's
Guides are now provided online in Adobe Acrobat 3.01 .PDF format.  The
U.S. English edition of the Acrobat Reader is also provided on the
DB2 OLAP Server CD.

The PDF edition of Using DB2 OLAP Server is available in some of the
languages listed at the top of this file.  To find out if an edition
is available in your language, look in the "x:\language\yy" directory
on the CD-ROM, where "x" is the drive letter of your CD-ROM, and "yy"
is the two-character abbreviation for your language.  If an edition is
not available in your language, use the English edition.

The PDF editions of the Spreadsheet Add-n User's Guides are installed
with the product.  They are located in the x:\essbase\client directory,
where "x:essbase" is the path on which you installed the product.

-  Grid API on UNIX
The Grid API is now supported on all three UNIX platforms:
Solaris, AIX, and HP-UX.


3.  INSTALLATION UPDATES
------------------------

Follow the instructions in "Using DB2 OLAP Server" to install this
product.  In addition:

- In the Using DB2 OLAP Server manual, in chapter 2, in the section
"Installing DB2 OLAP Server on AIX, Solaris, and HP-UX", add the
following to step 9:

  FOR HP-UX ONLY:  Enter the following command in the $ARBORPATH/bin
  directory:
    ln -f -s /opt/IBMdb2/V5.0/lib/libdb2.sl libesssql.sl
  where "/opt/IBMdb2/V5.0/" is the installation directory for DB2 UDB.

- On AIX and HP-UX, databases must be cataloged as remote, regardless
of whether they are local or remote.  For instructions on cataloging
databases as remote, see "Creating and Deleting a Relational Database"
in chapter 3 of Using DB2 OLAP Server.

- Do not install DB2 OLAP Server as a Windows NT Service before starting
the product for the first time.  If you do install as a Windows NT Service
before registering the product with your Company Name, name and
password, you get the following error message when trying to start
from the Services Control Panel:
    Could not start the Essbase Service service on...
Solution: From a Command window, start the ESSBASE.EXE executable
and enter the required information. Then exit and attempt to restart
from the Services Control Panel.

- When installing DB2 OLAP Server on a Windows platform, be sure to
specify a directory name that conforms to the 8 character name, 3
character extension file name format (for example, \ESSBASE\50).
Otherwise, the installation will prompt you to enter the registration
number again.  For example, \ESSBASE\5.0.1 is a directory name that
may cause installation problems.

- The Russian and Czech editions of DB2 OLAP Server are stored on the
International English CD-ROM.

- For the French and German editions of DB2 OLAP Server, take the
following steps to complete the installation of the sample files for
the spreadsheet clients:
a.  Create a directory called "client" under x:\essbase, where
    "x:\essbase" is the path on which you installed the product.
    In the client directory, create a subdirectory called "sample".
b.  For the French files, copy the contents of the \language\fr\sample
    directory of the CD to the x:\essbase\client\sample directory.
    For the German files, copy the contents of the \language\de\sample
    directory.


4.  LATE-BREAKING DOCUMENTATION NEWS FOR VERSION 1.0.1
------------------------------------------------------
Following are product changes which occurred late in the release cycle
for DB2 OLAP Server Version 1.0.1 and did not make it into the
documentation.

Some Books Now Online
- - - - - - - - - - -
The Using DB2 OLAP Server manual and the Spreadsheet Add-in User's
Guides are now provided online in Adobe Acrobat 3.01 .PDF format.  The
U.S. English edition of the Acrobat Reader is also provided on the
DB2 OLAP Server CD.

The PDF edition of Using DB2 OLAP Server is available in some of the
languages listed at the top of this README file.  To find out if an
edition is available in your language, look in the "x:\language\yy"
directory on the CD-ROM, where "x" is the drive letter of your CD-ROM,
and "yy" is the two-character abbreviation for your language.  If an
edition is not available in your language, use the English edition.

The PDF editions of the Spreadsheet Add-n User's Guides are installed
with the product.  They are located in the x:\essbase\client directory,
where "x:essbase" is the path on which you installed the product.

Do not use 8K table spaces for dimension tables
- - - - - - - - - - - - - - - - - - - - - - - -
DB2 UDB 5.2 allows table spaces of 8K pages, but these table spaces
cannot contain LONG VARCHAR columns.  DB2 OLAP Server dimension tables
use LONG VARCHAR columns to store calc equations. Therefore, when you
specify a table space for dimension tables (using the TABLESPACE keyword
in the RSM.CFG configuration file), you cannot use a table space
of 8K pages.  However, you can use a table space of 8K pages for the
DB2 OLAP Server fact table, using the FACTS keyword in the RSM.CFG file.

Where to Call for Service:
- - - - - - - - - - - - -
The online help has references to Arbor corporation; disregard these
references.  Contact IBM to get service on DB2 OLAP Server.

Essbase API:
- - - - - -
1. Essbase API applications programs that used the function
   EssGGetLROPartitionDesc() should instead use the function
   EssGGetLinkedPartitionDesc().

2. A new Visual Basic API was added, and is documented below:

EsbLROGetMemberCombo()

DESCRIPTION:
Retrieves the n'th member from the member combination list of the
current LRO.

SYNTAX:
EsbLROGetMemberCombo(hCtx, memberIndex, memberName);
ByVal hCtx        As ESB_HCTX_T
ByRef memberIndex As ESB_ULONG_T
ByVal memberName  As ESB_MBRNAME_T

PARAMETERS:
HCtx        Essbase VB API context handle.
MemberIndex Position in the member list of the member to be returned.
MemberName  Returned member's name.

RETURN VALUE:
If successful, returns a member in memberName. If fails, returns
-1 to indicate the current object is not an LRO type, or 1 to
indicate out of bounds. Out of bounds means either there is no
member at the memberIndex position, or there is no LRO at the
current item. See NOTES.

NOTES:
* EsbLROGetMemberCombo() returns the member combination (that
identifies the data cell associated with the linked object),
which memCount in ESB_LRODESC_API_T fails to return.
* To ensure that the list in memory associated with hCtx is a
list of LROs, call EsbLROListObjects() or EsbLROGetObject()
before you call EsbLROGetMemberCombo().
* After you call EsbLROListObjects(), you must call EsbGetNextItem().
ESbLROGetMemberCombo() then operates on the current LRO fetched
by EsbGetNextItem().
* You can still use memCount in ESB_LRODESC_API_T to find the
number of member names in the member combination identifying
the data cell. See Example.

ACCESS:
This function requires no special privileges.

EXAMPLE: Declare Function EsbLROGetMemberCombo Lib "ESBAPIW"
(ByVal hCtx As Long, ByVal MemberIndex As Long, ByVal MemberName
As String * ESB_MBRNAMELEN)

Sub ESB_LROGetMemberCombo()
   Dim userName   As String * ESB_USERNAMELEN
   Dim listDate   As Long
   Dim Count      As Integer
   Dim Desc       As ESB_LRODESC_API_T
   Dim i          As Integer
   Dim j          As Integer
   Dim CutOffDate As Date
   Dim MemberName As String * ESB_MEMBERNAMELEN

   Const ESB_REFERENCE_DATE = #1/1/70#
   userName       = "kkand"
   CutOffDate     = #8/1/97#
   listDate       = DateAdd("s", CutOffDate, ESB_REFERENCE_DATE)

   sts            = EsbLROListObjects(hCtx, userName, listDate, Count)

   If sts = 0 Then
      For i = 1 To Count

         '**************************************
         '* Get the next LRO item from the list
         '**************************************
         sts = EsbGetNextItem(hCtx, ESB_LRO_TYPE, Desc)

         If sts = 0 Then
            For j = 1 To Desc.memCount

               '******************************************************
               '* Get the jth mbr from the mbr list of the current LRO
               '******************************************************
               sts = EsbLROGetMemberCombo(hCtx, j, MemberName)
      Next i
   End If
End Sub

In the Arbor Essbase API online documentation, see also:
EsbGetNextItem()
EsbLROGetObject()
EsbLROListObjects()

3. EsbLROGetObject() does not currently work with EsbLROGetMemberCombo().
   To ensure that the list in memory is a list of LROs, you must
   call EsbLROListObjects() before you call EsbLROGetMemberCombo().
   Calling EsbLROGetObject() before you call EsbLROGetMemberCombo()
   does not work.

ESSCMD Commands
- - - - - - - -
For LISTOBJECTS, option 11, Linked Reporting Object, lists only stored
LROs; that is, files with the .LRO extension.  It does not list URLs,
cell notes, or linked partitions.  Use the LISTLINKEDOBJECTS command
to list those objects.

For UNLOCKOBJECT, option 11, Linked Reporting Object, unlocks stored
LROs only; that is, files with the .LRO extension.  It does not unlock
URLs, cell notes, or linked partitions.

The RENAMEOBJECTS command does not allow the renaming of files with
the .LRO extension (linked reporting objects).

Application Settings
- - - - - - - - - -
If you change an application setting before starting the application,
the application starts automatically.  If you change an application
setting followed by a database setting, and you have not selected the
database, the database setting is not effective until the next time
you start the database.

Outline Change Log
- - - - - - - - - -
The Outline Change Log configuration setting is not designed for use
with large dimension builds.  Using the OUTLINECHANGELOG setting when
changing or adding several hundred or thousand members will affect
your database restructure performance, and may cause instability.

The default file size for the Outline Change Log is 64000 bytes.  When
the file reaches this size, DB2 OLAP Server copies the contents of the
file to a backup file with the same name as the Outline Change Log
file, but with an .OLB extension (database_name.OLB).  If you want to
set the file size larger than the default of 64000 bytes, you need to
make the following entry in the ESSBASE.CFG file:
    OUTLINECHANGELOGFILESIZE n
where n is a number interpreted in bytes.  For example, entering 12800
sets the file size to 12800 bytes.  The minimum file size is 8092.

Novell Intranetware Client
- - - - - - - - - - - - - -
If you use Novell Intranetware Client for Windows 95 or Windows NT
Version 4.10 to log in to your company's network, any network drives
listed in the PATH statement of your AUTOEXEC.BAT file are removed.
If you install the Spreadsheet Add-in to a network drive, normally the
network installation path appears in the PATH statement.  For example,
your PATH statement would include a directory such as N:\ESSBASE\BIN.
If the Novell software removes this directory from your PATH, you are
unable to use the Spreadsheet Add-in software.  To work around
this problem, use the standard Windows network login, and map your
network drives in Windows Explorer or File Manager.

Copying Applications
- - - - - - - - - - -
In Application Manager, you cannot copy an application and then
perform a GetDbInfo action, because the DB2 OLAP Server agent tries to
open the .ESM file.

Installing the HTML help files
- - - - - - - - - - - - - - -
If you install the online HTML files to a hard drive, the amount of
space required for the files varies depending on whether your file
system uses File Allocation Tables (FAT).  Because the HTML
documentation is comprised of many small files, the amount of physical
memory taken up on your drive, with FAT allocation, is greater than
the total size of the HTML files.  For example, a cluster size of 32 K
on a 1 GB hard drive can require up to 40 MB of disk space for the
HTML files.  To work around this problem, allocate enough disk space
to contain the HTML files and store them centrally on a network drive.

Installation
- - - - - - -
In the Using DB2 OLAP Server manual, in chapter 2, in the section
"Installing DB2 OLAP Server on AIX, Solaris, and HP-UX", add the
following to step 9:

  FOR HP-UX ONLY:  Enter the following command in the $ARBORPATH/bin
  directory:
    ln -f -s /opt/IBMdb2/V5.0/lib/libdb2.sl libesssql.sl
  where "/opt/IBMdb2/V5.0/" is the installation directory for DB2 UDB.


5.  KNOWN PROBLEMS
------------------
Every effort has been made to ensure that DB2 OLAP Server is as
free of bugs as possible. However, there are some known problems.

Named Pipes Protocol
- - - - - - - - - - - -
Windows NT 4.0 client machines running either 16-bit or 32-bit
Spreadsheet Add-in or Application Manager cannot connect to a
remote Windows NT 4.0 server using Named Pipes protocol. The
work-around is to first login to the Windows NT server machine using
Explorer or Network Neighborhood independently of DB2 OLAP Server.
Using this method, you must login to the remote Windows NT machine
using an account with NT Administrator privilege.

Windows 95 client machines running the 32-bit Excel Spreadsheet
Add-in cannot connect to a Windows NT server using Named Pipes
protocol.

When running the server as a Windows NT registered service,
you cannot connect to the server when using Named Pipes.

Registered Service
- - - - - - - - - -
Do not log off Windows NT when the product is running as a service.
Exit the application and database and quit the product before
logging off Windows NT.

Agent
- - -
On Windows 95 and HP-UX platforms, the Agent might hang if you are
using Partitioning and you do not have a sufficient number of agent
threads.

Dimension Build
- - - - - - - -
Dimension Build from SQL source against a Solaris server running
Oracle 7.3 with SQL Net 2.3.3 when using ESSCMD and Application Manager's
Database|Load Data will crash the server.


6.  WHERE TO FIND FIXES
- - - - - - - - - - - -

Program fixes are available on the web at:

  ftp://service.software.ibm.com/ps/products/db2olap/

If you have installed Simplified Chinese, Traditional Chinese, or Korean,
make sure you download the latest fix, which contains important fixes for
double-byte character set (DBCS) systems.


**********************************
