OS/2 Shareware BBS: Product/Product.zip/visquein.zip/FTB87A.INF

OS/2 Help File | 1994-07-12 | 156KB | 4,122 lines

ΓòÉΓòÉΓòÉ 1. Notices ΓòÉΓòÉΓòÉ

References in this publication to IBM products, programs, or services do not
imply that IBM intends to make these available in all countries in which IBM
operates. Any reference to an IBM product, program, or service is not intended
to state or imply that only IBM's product, program, or service may be used. Any
functionally equivalent product, program, or service that does not infringe any
of IBM's intellectual property rights may be used instead of the IBM product,
program, or service. Evaluation and verification of operation in conjunction
with other products, except those expressly designated by IBM, is the user's
responsibility.

IBM may have patents or pending patent applications covering subject matter in
this document. The furnishing of this document does not give you any license to
these patents. You can send license inquiries, in writing, to:

IBM Corporation
IBM Director of Licensing
208 Harbor Drive
Stamford, Connecticut 06904-2501
U.S.A.


ΓòÉΓòÉΓòÉ 2. Examples ΓòÉΓòÉΓòÉ

This publication contains examples of data and windows used in daily business
operations. They are intended only to be illustrative of the types of functions
available in IBM Visualizer Query for OS/2 and may contain the names of
individuals, companies, brands, and products. All of these names are
fictitious, and any similarity to the names and addresses used by an actual
business enterprise is entirely coincidental. Windows shown in this publication
are intended to be examples and may not be exact representations of actual
windows.

This publication contains sample programs. Permission is hereby granted to copy
and store the sample programs into a data processing machine and to use the
stored copies for internal study and instruction only. No permission is granted
to use the sample programs for any other purpose.


ΓòÉΓòÉΓòÉ 2.1. Trademarks ΓòÉΓòÉΓòÉ

The following terms, denoted by an asterisk (*), used in this publication, are
trademarks or service marks of IBM Corporation in the United States of America
or other countries:

AIX                                     IBM
Application System/400                  Operating System/2
AS/400                                  OS/2
DATABASE 2                              OS/400
DB2                                     QMF
DB2/2                                   SQL/400
DB2/400                                 SQL/DS
DB2/6000                                Ultimedia
DB2/VM & VSE                            VSE/ESA
FFST/2                                  VTAM
First Failure Support Technology/2      XGA

The following terms, denoted by a double asterisk (**), used in this
publication, are trademarks of other companies:

80386          Intel
80486          Intel
CompuServe     CompuServe Incoporated
dBASE IV       Borland International Inc
Lotus          Lotus Development Corporation
1-2-3          Lotus Development Corporation


ΓòÉΓòÉΓòÉ 3. About this book ΓòÉΓòÉΓòÉ

This book is for people who need to carry out any of the following tasks:

o Install IBM Visualizer Query for OS/2 (referred to throughout this book as
  Visualizer) and any of the Visualizer optional products

o Use Visualizer to access SQL databases

o Install corrective service to Visualizer products

o Report a problem to IBM


ΓòÉΓòÉΓòÉ 3.1. How this book is organized ΓòÉΓòÉΓòÉ

This book is divided into:

o Part 1, Installing Visualizer, which describes how to install Visualizer, and
  the optional Visualizer components.

o Part 2, Data connections, which describes how to connect to SQL databases and
  other data sources.

o Part 3, Supporting Visualizer, which describes how to get information on
  Visualizer, how to resolve Visualizer problems, and how to report Visualizer
  defects.

o Part 4, Appendixes, provides supplementary information, including:

   - Datatype conversions
   - Tips for optimizing the performance of Visualizer products
   - TalkLink and CompuServe contact information


ΓòÉΓòÉΓòÉ 3.2. Visualizer components ΓòÉΓòÉΓòÉ

The components in the Visualizer package are:

o This book
o IBM Visualizer Query for OS/2: Quick Install Card
o IBM Visualizer Query for OS/2: Using, SH45-5089
o Seven installation diskettes
o One sample database diskette
o One Personal Application System/2 registration diskette


ΓòÉΓòÉΓòÉ 4. Preparing to install Visualizer products ΓòÉΓòÉΓòÉ

This chapter describes the installation requirements for Visualizer and
provides a brief overview of the different types of installations that are
available.


ΓòÉΓòÉΓòÉ 4.1. Installation requirements ΓòÉΓòÉΓòÉ

The following hardware and software products are required to run Query for
OS/2. Visualizer optional products have the same requirements unless otherwise
noted in the manual supplied with the optional product.

Hardware requirements

The minimum hardware configuration for Visualizer is:

o Personal computer with an 80386** processor
o VGA display and graphics adapter
o 16MB memory
o A mouse or pointing device

The recommended hardware configuration for Visualizer is:

o Personal computer with an 80486** processor
o XGA* or SVGA display and graphics adapter
o 16MB memory
o A mouse or pointing device

Disk space requirements

The minimum disk space requirements for the U.S. English version of Query for
OS/2 are:

o 15MB for each standalone workstation or LAN server
o 0.5MB for each LAN requester
o 60KB on the boot drive of the workstation used to install Visualizer
o 20MB on the drive on which the SWAPPER.DAT file is located

The amount of disk space required to use Visualizer increases in proportion to
the amount of data stored. Although the installation procedure checks whether
you have sufficient space to install Visualizer, you should ensure that there
is enough disk space for future expansion.

Software requirements

To run Visualizer, you must have IBM Operating System Version 2.1 (Program
Number 5621-077) or the equivalent DBCS version installed.

The installation of IBM DATABASE 2* OS/2* (Program Number 5622-044), or IBM
OS/2 DATABASE 2 Client Application Enabler/2 (Program Number 5622-129) is also
required if you intend to use any of the following Visualizer components:

o SQL Database
o SQL Table
o SQL View

Visualizer supports DB2/2 Versions 1.0, 1.0.1, and 1.2. It also supports CAE/2
Versions 1.1 and 1.2.

If you install DB2/2 service level WR07015 on DB2/2 1.0, you must also install
service level WR07025.

If you are using DB2/2 1.0.1, service level WR07025 must be installed.

Other requirements

When you install the standalone or LAN requester version of a Visualizer
product, the directory in which the product is to be installed must be in the
LIBPATH environment variable of the CONFIG.SYS file. If the directory is not in
the LIBPATH when you start an installation, the installer will add the
directory to the LIBPATH and then ask you to shut down and restart the
workstation before continuing. To avoid having to shut down and restart your
workstation during the installation, before you start the process:

 1. Edit the CONFIG.SYS file and add the directory to the LIBPATH statement.

 2. Shut down and restart the workstation.


ΓòÉΓòÉΓòÉ 4.2. National languages ΓòÉΓòÉΓòÉ

Query for OS/2 is available for the following national languages:

Language                 Primary code page
Dutch                    850
French                   850
German                   850
Italian                  850
Japanese                 932 and 942
Korean                   949
Spanish                  850
Traditional Chinese      950
U.S. English             850

In addition:

o Bi-directional language support is available when you use Visualizer products
  with code pages 862 and 864.

o Traditional Chinese character support is available for the U.S. English
  version of Visualizer with code pages 948 and 950.


ΓòÉΓòÉΓòÉ 4.2.1. Installing more than one language ΓòÉΓòÉΓòÉ

You can install more than one language version of a Visualizer product and then
select the language you want to use. If you do so, all the different language
versions of one product must be installed in one location.

Each additional language is installed using the standard install procedures
detailed in Installing Visualizer on standalone workstations, through
Automating Visualizer installation,

To change the language you are working in:

 1. Open the Visualizer profile notebook.

 2. Select the Visualizer tab.

 3. Select the language you want to use from the Language list.

Query for OS/2 and the Visualizer optional products do not have to be installed
in the same language.

Note:   The language used by the Visualizer templates does not change when you
        switch languages. The templates always use the language that they were
        first installed in.


ΓòÉΓòÉΓòÉ 4.2.2. DBCS fonts ΓòÉΓòÉΓòÉ

DBCS versions of Visualizer products normally use Mincho 10 point font on VGA
displays and Mincho Proportional 12 point font on other displays. However, with
DBCS versions of Charts for OS/2 and Reports for OS/2 you can use:

o Mincho and Gothic fonts (which can be installed as an optional product)

o Mincho Medium and Gothic Medium fonts (which are packaged with DBCS versions
  of OS/2).


ΓòÉΓòÉΓòÉ 4.3. The Visualizer environment ΓòÉΓòÉΓòÉ

Visualizer can be installed:

o On a standalone workstation.

  If you install Visualizer on a standalone workstation, it will run on that
  workstation only. For more information, see Installing Visualizer on
  standalone workstations,

o On a local area network (LAN)

  A LAN installation of Visualizer has two components: the LAN server and the
  LAN requester. Both components must be installed to run Visualizer from a LAN
  server.

  When you install Visualizer as a LAN server, it can be run remotely from any
  requester workstation that can access the Visualizer directories on the LAN
  server. It cannot be run directly from the LAN server. However, the LAN
  requester version of Visualizer can be installed and run on the Visualizer
  LAN server.

  Because the whole of Visualizer is installed only on the LAN server, less
  hard disk space is used on each LAN requester. However, the performance of
  Visualizer may be reduced by this type of installation.

  For more information, see Installing Visualizer products on a LAN server and
  Installing Visualizer products on a LAN requester.

You can also create a distribution copy of Query for OS/2 or an optional
product. A distribution copy is an exact copy of the installation diskettes
stored on the hard disk of a workstation. It can then be used to install the
product onto standalone workstations, LAN servers, or LAN requesters in the
same way as from the product diskettes. For more information, see Making a
distribution copy of Visualizer products.


ΓòÉΓòÉΓòÉ 4.3.1. Visualizer and DB2/2 ΓòÉΓòÉΓòÉ

Although Visualizer is primarily designed for use with DB2/2, it can be used on
workstations that do not have DB2/2 or CAE/2 installed. If you do not have
access to DB2/2 when you install Visualizer, the database objects that cannot
be used (SQL Database,  SQL Table, and SQL View) are not placed in the OS/2
Templates or Visualizer Shadows of templates folders.

If DB2/2 is installed after Visualizer, the SQL Database,  SQL Table, and SQL
View objects are automatically placed in the OS/2 Templates folder. You can
then create shadows of the objects in the Visualizer Shadows of templates
folder manually.


ΓòÉΓòÉΓòÉ 4.3.2. Sample DB2/2 database ΓòÉΓòÉΓòÉ

A sample DB2/2 database called CELDIAL is supplied with Query for OS/2. This
database is provided in addition to the object samples you can select during
installation.

The CELDIAL database must be installed separately from Query for OS/2, using
the diskette labelled Sample Database. You must have OS/2 REXX support
installed before you can install the sample database. Further information about
how to install this database, and about using all the samples provided, can be
found by double-clicking on the Using Query for OS/2 Samples online manual in
the Samples folder.


ΓòÉΓòÉΓòÉ 4.3.3. Visualizer optional products ΓòÉΓòÉΓòÉ

A number of Visualizer optional products are separately available. These
include:

o IBM Visualizer Charts for OS/2
o IBM Visualizer Development for OS/2
o IBM Visualizer Ultimedia* Query for OS/2
o IBM Visualizer Plans for OS/2
o IBM Visualizer Procedures for OS/2
o IBM Visualizer Statistics for OS/2

The optional products are installed, updated, and deleted using the same
procedures as for Query for OS/2 unless otherwise noted in the manual supplied
with the optional product.


ΓòÉΓòÉΓòÉ 4.3.4. REXX in Visualizer ΓòÉΓòÉΓòÉ

Several items in Visualizer use REXX. Because REXX is an optional part of the
OS/2 installation, make sure that REXX is installed on your workstation if you
plan to use:

o Autologon for applications that access data

o The sample installation programs used for DDCS support of DB2/2, DB2/VM & VSE
  (SQL/DS)*, and OS/400*


ΓòÉΓòÉΓòÉ 4.3.5. Using Visualizer with Personal Application System/2 ΓòÉΓòÉΓòÉ

Personal Application System/2 Version 3 products are compatible with
Visualizer. If you want to use Visualizer and Personal Application System/2
together on the same workstation, follow these steps before installing
Visualizer.

 1. Insert the Visualizer Personal AS Version 3 registration diskette into your
    diskette drive.

 2. At an OS/2 command prompt, type:

        a:pasv3reg deregister

    Then press Enter.

 3. Shut down and restart the workstation.

 4. Install Visualizer.


ΓòÉΓòÉΓòÉ 4.3.5.1. Running Personal Application System/2 with Visualizer ΓòÉΓòÉΓòÉ

By default, Visualizer is used to open both Personal Application System/2 and
Visualizer objects. If you want to open an object using Personal Application
System/2 instead of Visualizer:

 1. Open the object's pop-up menu.

 2. Select the arrow to the right of Open.

 3. Select Personal AS from the cascade menu.


ΓòÉΓòÉΓòÉ 4.3.5.2. Deleting Personal Application System/2 ΓòÉΓòÉΓòÉ

If you have Visualizer and Personal Application System/2 installed on the same
workstation and want to delete Personal Application System/2:

 1. Delete Personal Application System/2 using the method described in Personal
    Application System/2: Installing and Supporting, SH45-5501.

 2. Shut down and restart the workstation.

 3. Insert the Personal AS Version 3 registration diskette into your diskette
    drive.

 4. To reinstate the Visualizer objects, at an OS/2 command prompt, type:

        a:\FTBADDIN

    Then press Enter.


ΓòÉΓòÉΓòÉ 4.3.5.3. Deleting Visualizer ΓòÉΓòÉΓòÉ

If you have Visualizer and Personal Application System/2 installed on the same
workstation and want to delete Visualizer:

 1. Delete Visualizer.

 2. Shut down and restart the workstation.

 3. Insert the Personal AS Version 3 registration diskette into your diskette
    drive.

 4. At an OS/2 command prompt, type:

        a:pasv3reg register

    Then press Enter.

 5. Shut down and restart the workstation.


ΓòÉΓòÉΓòÉ 4.4. Management of temporary files ΓòÉΓòÉΓòÉ

Visualizer creates temporary files while it is running. To place the temporary
files in a specific directory, add the SET FTB1TEMP= statement to your
CONFIG.SYS file. For example, SET FTB1TEMP=C:\TMP directs all temporary files
to C:\TMP.

If you do not add this statement to your CONFIG.SYS file, these files are held
in the directory identified by the SET FTB1DIR= statement. The temporary files
all begin with FTB.

The FTB1DIR directory also contains other files that are used by Visualizer. Do
not delete any of the above files if they are present. Do not delete temporary
files if any Visualizer object is open, as the object may be using them.


ΓòÉΓòÉΓòÉ 5. Installing Visualizer on standalone workstations ΓòÉΓòÉΓòÉ

This chapter describes how to install Visualizer products on a standalone
workstation. You can install either from the product diskettes, or from a
directory with a distribution copy of the product. See Making a distribution
copy of Visualizer products, for more information about making a distribution
copy.

When you install Query for OS/2, your original CONFIG.SYS file is copied to the
FTB1DIR directory as CONFIG.ORG.

The standalone versions of Visualizer products cannot be installed on a
workstation where the LAN requester version of Visualizer is already installed.

Note:   You are advised that a license is required for each workstation on
which Visualizer is being used.


ΓòÉΓòÉΓòÉ 5.1. Overview of the standalone installation process ΓòÉΓòÉΓòÉ

The Visualizer installation process performs the following tasks for a
standalone installation:

o Transfers the product files to the installation directory

o Creates the Visualizer folder on the workplace and registers the Visualizer
  objects

o Updates the CONFIG.SYS file if necessary

o Creates a Database folder in the Visualizer folder if you chose to install
  the Query for OS/2 database folder creation component. A folder is created
  for each database that you can access.

o Copies the sample files and creates the Samples folder inside the Visualizer
  folder,

o Copies the manuals and creates the Manuals folder inside the Visualizer
  folder, if you chose to install the Visualizer manuals.

o Copies the tutorials and creates the Tutorials folder inside the Visualizer
  folder, if you chose to install the Visualizer tutorials.


ΓòÉΓòÉΓòÉ 5.2. Installing Visualizer ΓòÉΓòÉΓòÉ

To install a Visualizer product on a standalone workstation:

 1. If you are installing from diskette, insert Diskette 1 into the diskette
    drive and, at a command prompt, enter:

        a:\install

    where a is the name of the diskette drive.

    If you are installing from a distribution copy on a LAN server, at a
    command prompt, enter: x:\install

    where x is the name of the drive on which the distribution copy is stored.

    The Product Information window is displayed.

 2. In the Product Information window, select the OK push button.

    The Instructions for Installation window is displayed.

 3. After you have read the installation instructions, select the Continue push
    button.

    The Installation and Maintenance window is displayed. This window contains
    a list of all the Visualizer products that can be installed.

 4. From the list of products, select the standalone product you want to
    install. For example, when installing Query for OS/2, select Query for OS/2
    (Standalone).

 5. From the Action menu, select the Install choice.

    The Install window is displayed.

 6. There are two check boxes in the Install window:

   o Update CONFIG.SYS
   o Overwrite files

    By default, the Update CONFIG.SYS check box is selected. This enables the
    installation process to automatically update the CONFIG.SYS file with the
    settings required to run Visualizer. Deselect this check box if you want
    the installation process to store the required changes in the CONFIG.ADD
    file on the boot drive and not update CONFIG.SYS. However, Visualizer
    cannot run and other Visualizer objects cannot be installed until these
    changes have been added to the CONFIG.SYS file.

    By default, the Overwrite files check box is not selected. This means that
    the installation will prompt you if it encounters any Visualizer files in
    the installation location. Select this check box if you want to overwrite
    Visualizer files without being prompted.

 7. Select the OK push button.

    The Install Directories window is displayed. This window contains a list of
    all the components that are available for installation. To display a
    description of a component, select it from the Select the components that
    you want to install list, then select the Descriptions push button.

 8. Select the components you want to install from the list. When you select a
    component or the Select all push button, the number of bytes needed for
    installation is shown.

 9. To check that there is sufficient space to install the Visualizer product,
    select the Disk space push button.

    The Disk Space window is displayed. This window shows how much space is
    available on all drives to which you have access, including read-only
    access. Visualizer cannot be installed on read-only drives.

10. Select a drive from the list on the Disk Space window. This displays the
    amount of space available and whether installation of the component is
    possible on that drive.

    After you select a drive from the Bytes available on drive list, you can
    specify that Visualizer will be installed on the drive by selecting the
    Change directories to selected drive check box.

11. Select the OK push button to close the Disk Space window.

12. By default, Visualizer products are installed in the C:\FTW directory. If
    you want to install the product in another directory, or on another drive,
    overtype the information in the File Directory field in the Install
    Directories window.

13. Select the Install push button to install the components you selected.

    On starting, the installation program checks that your workstation fulfills
    the Visualizer software requirements (see Installation requirements for
    more details). If any requirement is not met, the installation program
    displays an explanatory message and stops.

    The Install Progress window is displayed. Also, while the product is being
    installed, details of other Visualizer products are displayed in the
    Welcome to Visualizer window.

    If you are installing from diskette, you are prompted to insert a new
    diskette when necessary.

    If you need to stop the installation at any point, select the Stop push
    button. You are then given the option of removing any files already copied
    during installation.

    If the Update CONFIG.SYS check box is selected, CONFIG.BAC, a backup copy
    of your CONFIG.SYS file, is saved in the root directory of your boot drive.
    In addition, if you are installing Query for OS/2, a backup copy of your
    CONFIG.SYS file is saved in the Visualizer work directory as CONFIG.ORG.

    When the installation is complete, a message is displayed. It informs you
    whether you need to shut down and restart the workstation before using the
    product. It also informs you whether you need to shut down and restart the
    workstation before installing another Visualizer product.

14. Close the installation program.

15. If necessary, shut down and restart the workstation.

To start Visualizer, open the Visualizer folder and open the Visualizer object
you want to work with.

After you install a Visualizer product, do not move files from their installed
locations. Only files in their original installed locations are updated when
you apply program temporary fixes.


ΓòÉΓòÉΓòÉ 6. Installing Visualizer products on a LAN server ΓòÉΓòÉΓòÉ

If your workstation is connected to a LAN, you can save disk space by running
Visualizer from a LAN server. With this type of installation, some files are
stored on your workstation, but most of Visualizer is stored on a LAN server.

This chapter describes how to install Visualizer products onto a LAN server so
that they can be used from workstations on the LAN. Installing Visualizer
products on a LAN requester, describes how to install and run Visualizer
products from LAN requesters.

You can install Visualizer products directly onto the LAN server, or from a
workstation that is connected to it. You cannot run Visualizer from a LAN
server directly. Instead, you must install the LAN requester version of the
Visualizer product on the server workstation and use Visualizer from there.

LAN server versions of the Visualizer optional products do not have to be
installed on the same server as the Query for OS/2 LAN server.

Note:   You are advised that a license is required for each workstation on
which Visualizer is being used.


ΓòÉΓòÉΓòÉ 6.1. Overview of the LAN server installation process ΓòÉΓòÉΓòÉ

The Visualizer installation process performs the following tasks for a LAN
server installation:

o Transfers product files

o Creates a Visualizer Installing and Supporting folder on the workstation that
  is used to install Visualizer onto the LAN server. This folder contains the
  installation and maintenance utility.

Because the LAN server installation makes no changes to the CONFIG.SYS file,
there is no need to shut down and restart your workstation.


ΓòÉΓòÉΓòÉ 6.2. Preparing for LAN server installation ΓòÉΓòÉΓòÉ

Before you install a Visualizer product onto a LAN server, choose:

o The LAN server to be used

o The Visualizer installation directory (the default is C:\FTW.)

o A network alias for the chosen location

o The requester IDs that will have access to the network alias

After you install a Visualizer product onto the server:

o Give the network alias and server ID for each installed language version of
  the Visualizer product to each requester that will use the Visualizer Network
  Resource.

o Provide each requester ID with read and execute access to the directories in
  which the Visualizer product was installed.

o Provide a logon assignment for each user so that they are automatically
  linked to the Visualizer directories when they log on to the LAN.


ΓòÉΓòÉΓòÉ 6.3. Installing Visualizer on a LAN server ΓòÉΓòÉΓòÉ

To install a Visualizer product onto a LAN server:

 1. If you are installing from diskette, insert Diskette 1 into the diskette
    drive and, at a command prompt, enter:

        a:\install

    where a is the name of the diskette drive.

    If you are installing from a distribution copy on a LAN server, at a
    command prompt, enter:

        x:\install

    where x is the name of the drive on which the distribution copy of the
    Visualizer product is stored.

    The Product Information window is displayed.

 2. In the Product Information window, select the OK push button.

    The Instructions for Installation window is displayed.

 3. After you have read the installation instructions, select the Continue push
    button.

    The Installation and Maintenance window is displayed. This window contains
    a list of all the Visualizer products that can be installed.

 4. From the list of products, select the LAN server product. For example, when
    installing Query for OS/2, select Query for OS/2 (Server).

 5. From the Action menu, select the Install choice.

    The Install window is displayed.

 6. There are two check boxes in the Install window:

   o Update CONFIG.SYS
   o Overwrite files

    By default, the Overwrite files check box is not selected. This means that
    the installation will prompt you if it encounters any Visualizer files in
    the installation location. Select this check box if you want to overwrite
    Visualizer files without being prompted.

    No changes are made to the CONFIG.SYS file when Visualizer products are
    installed on a LAN server.

 7. Select the OK push button.

    The Install Directories window is displayed. This window contains a list of
    all the components that are available for installation. To display a
    description of a component, select it from the Select the components that
    you want to install list, then select the Descriptions push button

 8. Select the components you want to install from the list. When you select a
    component or the Select all push button, the number of bytes needed for
    installation is shown.

    If any of the Visualizer optional components are to be used from the LAN
    requesters, ensure they are installed on the LAN server.

 9. To check that there is sufficient space to install the Visualizer product,
    select the Disk space push button.

    The Disk Space window is displayed. This window shows how much space is
    available on all drives to which you have access. Visualizer cannot be
    installed on read-only drives.

10. Select a drive from the list on the Disk Space window. This displays the
    amount of space available, and whether installation of the component is
    possible on that drive.

    After you select a drive from the Bytes available on drive list, you can
    specify that Visualizer will be installed on the drive by selecting the
    Change directories to selected drive check box.

11. Select the OK push button to close the Disk Space window.

12. By default, Visualizer products are installed in the C:\FTW. directory. If
    you want to install the Visualizer product in another directory, or on
    another drive, overtype the information in the File Directory field in the
    Install Directories window.

13. Select the Install push button to start the installation.

    On starting, the installation program checks that your workstation fulfills
    the Visualizer software requirements (see Installation requirements for
    more details). If any requirement is not met, the installation program
    displays an explanatory message and stops.

    The Install Progress window is displayed. Also, while the product is being
    installed, details of other Visualizer products are displayed in the
    Welcome to Visualizer window.

    If you are installing from diskette, you are prompted to insert a new
    diskette when necessary.

    If you need to stop the installation at any point, select the Stop push
    button. You are then given the option of removing any files already copied
    during installation.

    When installation is complete, a message is displayed, informing you that
    the process is complete. You do not need to restart your workstation.

14. Close the installation program.

You must now install the Visualizer product onto a workstation that can access
the LAN server. The next chapter describes how to install Visualizer products
on a LAN requester.

After you install a Visualizer product, do not move files from their installed
locations. Only files in their original installed locations are updated when
you apply program temporary fixes.


ΓòÉΓòÉΓòÉ 7. Installing Visualizer products on a LAN requester ΓòÉΓòÉΓòÉ

This chapter describes how to install Visualizer products on a workstation so
that they can be run from a LAN server. To run Visualizer on a LAN requester,
the workstation must be attached to a LAN server on which the LAN server
component of the Visualizer product is installed. For more information about
LAN server installation, see Installing Visualizer products on a LAN server.

A LAN requester version of a Visualizer product cannot be installed on a
workstation where the standalone version is already installed. It can be
installed and run on a workstation on which the LAN server version of
Visualizer is installed.

Note:   You are advised that a license is required for each workstation on
which Visualizer is being used.


ΓòÉΓòÉΓòÉ 7.1. Overview of the LAN requester installation process ΓòÉΓòÉΓòÉ

The Visualizer installation process performs the following tasks for a LAN
requester installation:

o Transfers the product files to the installation directory

o Creates the Visualizer folder on the workplace and registers the Visualizer
  objects

o Updates the CONFIG.SYS file if necessary

o Creates a Database folder in the Visualizer folder if you chose to install
  the Query for OS/2 database folder creation component. A folder is created
  for each database that you can access.

o Copies the sample files and creates the Samples folder inside the Visualizer
  folder, if you chose to install the Visualizer samples.

o Copies the manuals and creates the Manuals folder inside the Visualizer
  folder, if you chose to install the Visualizer manuals.

o Copies the tutorials and creates the Tutorials folder inside the Visualizer
  folder, if you chose to install the Visualizer tutorials.


ΓòÉΓòÉΓòÉ 7.2. Preparing for LAN requester installation ΓòÉΓòÉΓòÉ

Before installing a Visualizer product on a LAN requester, ensure that:

o You have the server ID and the network alias for the location of Visualizer

o Your requester is linked to the LAN resource where Visualizer is installed
  and that you have read and execute access to it


ΓòÉΓòÉΓòÉ 7.3. Installing Visualizer products onto a LAN requester ΓòÉΓòÉΓòÉ

To install Visualizer onto a LAN requester:

 1. If you are installing from diskette, insert Diskette 1 into the diskette
    drive and, at a command prompt, enter:

        a:\install

    where a is the name of the diskette drive.

    If you are installing from a distribution copy on a LAN server, at a
    command prompt, enter:

        x:\install

    where x is the name of the drive on which the distribution copy of
    Visualizer is stored.

    The Product Information window is displayed.

 2. In the Product Information window, select the OK push button.

    The Instructions for Installation window is displayed.

 3. After you have read the installation instructions, select the Continue push
    button.

    The Installation and Maintenance window is displayed. This window contains
    a list of all the Visualizer products that can be installed.

 4. From the list of products, select the LAN requester product. For example,
    when installing Query for OS/2, select Query for OS/2 (Requester).

 5. From the Action menu, select the Install choice.

    The Install window is displayed. Do not make any changes in this window.

 6. Select the OK push button.

    The Install Directories window is displayed. This window contains a list of
    all the components that are available for installation. To display a
    description of a component, select it from the Select the components that
    you want to install list, then select the Descriptions push button

 7. Select the components you want to install from the list. When you select a
    component or the Select all push button, the number of bytes needed for
    installation is shown.

 8. To check that there is sufficient space to install the Visualizer product,
    select the Disk space push button.

    The Disk Space window is displayed. This window shows how much space is
    available on all drives to which you have access. Visualizer cannot be
    installed on read-only drives.

 9. Select a drive from the list on the Disk Space window. This displays the
    amount of space available and whether installation of the component is
    possible on that drive.

    After you select a drive from the Bytes available on drive list, you can
    specify that the Visualizer product will be installed on the drive by
    selecting the Change directories to selected drive check box.

10. Select the OK push button to close the Disk Space window.

11. By default, Visualizer products are installed in the C:\FTW directory.
    Change this to the drive and path of the LAN requester that you will be
    using.

12. By default, the directory of the LAN server installation of Visualizer
    products is set to a default of S:\. Change this to the drive and path of
    the LAN server installation of the product that you will be using.

13. Select the Install push button to start the installation.

    On starting, the installation program checks that your workstation fulfills
    the Visualizer software requirements (see Installation requirements for
    more details). If any requirement is not met, the installation program
    displays an explanatory message and stops.

    The Install Progress window is displayed. Also, while the product is being
    installed, details of other Visualizer products are displayed in the
    Welcome to Visualizer window.

    If you are installing from diskette, you are prompted to insert a new
    diskette when necessary.

    If you need to stop the installation at any point, select the Stop push
    button. You are then given the option of removing any files already copied
    during installation.

    A backup copy of your CONFIG.SYS file is saved in the root directory of
    your boot drive.

    When the installation is complete, a message is displayed. It informs you
    whether you need to shut down and restart the workstation before using the
    product. It also informs you whether you need to shut down and restart the
    workstation before installing another Visualizer product.

14. Close the installation program.

15. If necessary, shut down and restart the workstation.

You can now run Visualizer from the LAN server. To start it, open the
Visualizer folder and open the Visualizer objects you want to work with.

After installing Visualizer, do not move files from their installed locations.
Only files in their original installed locations are updated when you apply
program temporary fixes.


ΓòÉΓòÉΓòÉ 8. Making a distribution copy of Visualizer products ΓòÉΓòÉΓòÉ

A distribution copy is an alternative to installing Visualizer from diskettes.
It enables you to install the Visualizer product from a central location such
as a LAN server. This chapter explains how to make a distribution copy of a
Visualizer product.

When you make a distribution copy of a Visualizer product, all the files from
the installation diskettes (or another distribution copy) are copied onto the
target workstation.

You can create a distribution copy for each set of Visualizer diskettes. Each
distribution copy contains the installation information for one Visualizer
product in one language only. Therefore, you should put distribution copies of
each different Visualizer product in different locations.

Note:   You are advised that a license is required for each workstation on
which Visualizer is being used.


ΓòÉΓòÉΓòÉ 8.1. Making a Visualizer distribution copy ΓòÉΓòÉΓòÉ

To make a distribution copy of a Visualizer product:

 1. If you are creating the distribution copy from diskette, insert Diskette 1
    into the diskette drive and, at a command prompt, enter:

        a:\install

    where a is the name of the diskette drive.

    If you are creating the distribution copy from another distribution copy on
    a LAN server, at a command prompt, enter:

        x:\install

    where x is the name of the drive on which the distribution copy is stored.

    The Product Information window is displayed.

 2. In the Product Information window, select the OK push button.

    The Instructions for Installation window is displayed.

 3. After you have read the installation instructions, select the Continue push
    button.

    The Installing and Maintenance window is displayed. This window contains a
    list of all Visualizer products that can be installed.

 4. From the list of products, select the distribution copy product. For
    example, when installing Query for OS/2, select Query for OS/2
    (Distribution Copy).

 5. From the Action menu, select the Install choice.

    The Install window is displayed.

 6. There are two check boxes in the Install window:

   o Update CONFIG.SYS
   o Overwrite files

    By default, the Overwrite files check box is not selected. This means that
    the installation will prompt you if it encounters any Visualizer files in
    the installation location. Select this check box if you want to overwrite
    Visualizer files without being prompted.

    No changes are made to the CONFIG.SYS file when making a distribution copy.

 7. Select the OK push button.

    The Install Directories window is displayed.

 8. Select the Visualizer Distribution Copy component from the list. The number
    of bytes needed for the copy is displayed.

 9. To check that there is sufficient space to install the distribution copy,
    select the Disk space push button.

    The Disk Space window is displayed. This window shows how much space is
    available on all drives to which you have access. The distribution copy
    cannot be installed on read-only drives.

10. Select a drive on the Disk Space window. This displays the amount of space
    available, and whether the distribution copy can be installed on that
    drive.

    After you select a drive from the Bytes available on drive list, you can
    specify that the distribution copy will be installed on the drive by
    selecting the Change directories to selected drive check box.

11. Select the OK push button to close the Disk Space window.

12. By default, the distribution copy is stored in the C:\FTB1\DIST directory.
    If you want to install the distribution copy in another directory, or on
    another drive, overtype the information in the File Directory field in the
    Install Directories window.

13. Select the Install push button to create and install the directory copy.

    The Install Progress window is displayed.

    If you are creating the distribution copy from diskette, you are prompted
    to insert a new diskette when necessary.

    If you need to stop the installation at any point, select the Stop push
    button. You are then given the option of removing any files that have
    already been copied.

    When the process is complete, a message is displayed informing you that the
    distribution copy has been created.

    No changes are made to the CONFIG.SYS file, so there is no need to shut
    down and restart your workstation.

14. Close the installation program.

You can use the distribution copy to install the Visualizer product onto a
standalone workstation, a LAN server, or a LAN requester, by entering INSTALL
from the location on which the distribution copy is stored.


ΓòÉΓòÉΓòÉ 9. Automating Visualizer installation ΓòÉΓòÉΓòÉ

The installation of Visualizer products can be automated using the
Configuration, Installation and Distribution (CID) method. This chapter
describes how to create response files and command line parameters to install,
update, and delete Visualizer non-interactively.

A Visualizer product can be installed as a LAN requester only when a Visualizer
LAN server version of the product is already installed on the network.

Note:   You are advised that a license is required for each workstation on
which Visualizer is being used.


ΓòÉΓòÉΓòÉ 9.1. Installing Visualizer automatically ΓòÉΓòÉΓòÉ

To automate the installation, update, or deletion procedure of a Visualizer
product:

 1. Create a distribution copy of the Visualizer product on a LAN server. See
    Making a distribution copy of Visualizer products for more information.

 2. Check that the directory in which the Visualizer product is to be installed
    is in the LIBPATH environment variable of the CONFIG.SYS file. If the
    target directory is not in the LIBPATH:

    a) Edit the CONFIG.SYS file and add the Visualizer installation directory
       to the LIBPATH environment variable.

    b) Shut down and restart the workstation.

 3. Using an editor, create a response file. When creating a response file:

   o Start each parameter on a new line

   o Do not omit any parameter

   o Save the response file in a directory to which the target workstation has
     read and write access

   o Do not save the response files in the target or source directory

    The following table lists the response file parameters required for each
    non-interactive operation.

   Installing       FILE
                    AUX1
                    COMP
                    CFGUPDATE
                    OVERWRITE

   Updating         CFGUPDATE
                    SAVEBACKUP

   Deleting         COMP
                    DELETEBACKUP

    where:

   FILE
             Specifies the target directory in which the product will be
             installed.

   AUX1
             Specifies the directory in which the LAN server component of the
             Visualizer product is already installed. This parameter is
             required only for a LAN requester installation.

   COMP
             Specifies the names of the components to be installed. For the
             U.S. English version of Query for OS/2 these are:

              Query for OS/2 (English)
              Query for OS/2 Database Folder Creation
              Query for OS/2 Samples (English)
              Query for OS/2 Manuals (English)
              Query for OS/2 Tutorials (English)

   Refer to Optional product install parameters for details of the component
   names of the optional Visualizer products.

   For example, to install the Query for OS/2 code, enter:

      COMP=Query for OS/2 (English)

   Component names depend on the language you are installing and are
   case-sensitive. When specifying the names, include all necessary blank
   spaces, and do not enclose them in quotes.

   CFGUPDATE
             Specify CFGUPDATE=AUTO to update your CONFIG.SYS file
             automatically.

             Specify CFGUPDATE=MANUAL to place the necessary updates in a file
             called CONFIG.ADD in the root directory of your boot drive. These
             updates must be added to your CONFIG.SYS file before running
             Visualizer.

   OVERWRITE
             Specify OVERWRITE=YES to overwrite files if they already exist in
             the install directory.

             Specify OVERWRITE=NO to keep the original files.

   SAVEBACKUP
             Specify SAVEBACKUP=NO to update files without a backup.

             Specify SAVEBACKUP=YES to keep a backup of any files that are
             updated. If you choose to keep a backup, you can restore the
             updated Visualizer product back to the level it was before the
             program temporary fix was applied.

   DELETEBACKUP
             Specify DELETEBACKUP=NO to delete the product itself.

             Specify DELETEBACKUP=YES to only delete backups of any program
             temporary fixes that have been applied.

 4. Start the process from the target workstation, but not from the source or
    target directories. Ensure that you prefix the command with the full path
    of the distribution copy for an install operation, or the installed
    directory for an update or delete operation.

   o To install a Visualizer product, at an OS/2 command prompt enter:

          INSTALL /A:I /L1:error_log /L2:history_log /O:DRIVE /R:response_file
            /S:source /C:catalog_file /P:product_name /X

   o To update a Visualizer product, at an OS/2 command prompt enter:

          FTBWINS /A:U /L1:error_log /L2:history_log /O:DRIVE /R:response_file
            /S:source /C:catalog_file /P:product_name /X

   o To delete a Visualizer product, at an OS/2 command prompt enter:

          FTBWINS /A:D /L1:error_log /L2:history_log /O:DRIVE /R:response_file
            /C:catalog_file /P:product_name /X

    where:

   /A Specifies the type of operation:

      I  For an install operation
      U  For an update operation
      D  For a delete operation

   error_log Specifies the fully qualified name of the file to be used to store
      any errors encountered during the operation.

   history_log Specifies the fully qualified name of the file to be used to
      store any messages sent by the operation.

   DRIVE Specifies that the product is being installed from an OS/2
      environment.

   response_file Specifies the fully qualified name of the response file

   source Specifies the fully qualified location of the distribution copy of
      the Visualizer product. For an update operation, specify the directory of
      the program temporary fixes or an updated distribution copy.

   catalog_file Specifies the fully qualified filename of the product's catalog
      file. The following table lists the catalog file associated with each
      Visualizer product.

      Product                       Catalog file
      Charts for OS/2               FTCICAT.ICF
      Development for OS/2          FTDICAT.ICF
      Procedures for OS/2           FTPICAT.ICF
      Plans for OS/2                FTWICAT.ICF
      Query for OS/2                FTBICAT.ICF
      Statistics for OS/2           FTSICAT.ICF
      Ultimedia Query for OS/2      FTVICAT.ICF

      For install, the file is located in the same directory as your
      distribution copy.

      For update, the file is located in the same directory as the program
      temporary fix.

      For delete, the file is located in the directory in which the Visualizer
      product was installed.

   product_name Specifies the product to be installed:

      Query for OS/2 (Standalone)
      Query for OS/2 (Server)
      Query for OS/2 (Requester)
      Query for OS/2 (English Distribution Copy)

   The name must be entered exactly as it appears in the catalog file. Refer to
   Optional product install parameters for details of the product names of the
   optional Visualizer products.

   /X Specifies a non-interactive operation. This must be the last parameter
      specified.

After the process completes, check the error log to ensure that the operation
was successful and to find out if you need to shut down and restart the
workstation.

The following is an example of a response file that can be used to install a
Requester copy of the English version of Query for OS/2 and the Query for OS/2
English samples to the D:\FTW directory:

FILE=D:\FTW
AUX1=X:\FTW
COMP=Query for OS/2 (English)
COMP=Query for OS/2 Samples (English)
CFGUPDATE=AUTO
OVERWRITE=NO
CREATESHADOWS=NO

To start this install, at an OS/2 command prompt, enter:

INSTALL /A:I /L1:c:\error_log /L2:c:\history_log /O:DRIVE
  /R:x:\cid\install.rsp /S:x:\distcopy /C:x:\distcopy\ftbicat.icf
  /P:IBM Visualizer Query for OS/2 (Requester) /X

In this example, the distribution copy is installed on a LAN resource
identified as X, in a subdirectory called DISTCOPY. The LAN server component is
installed on the same resource, in a subdirectory called FTW. The response file
has been stored on the same resource, in the CID subdirectory.


ΓòÉΓòÉΓòÉ 10. Deleting Visualizer products ΓòÉΓòÉΓòÉ

This chapter describes how to delete Visualizer products from a workstation.
You must delete all optional Visualizer products before deleting Query for
OS/2. Preparing to delete Visualizer

Although the object icons of a Visualizer product are removed when you delete
the product, the corresponding object files are not deleted from the OS/2 file
system. Therefore, the Visualizer folder can still contain files even when no
icons are shown.

To ensure that all objects are removed from the Visualizer folder so that it
can be deleted, move any folders and objects that you have created within the
folder to another location before you delete a Visualizer product from your
workstation,


ΓòÉΓòÉΓòÉ 10.1. Deleting Visualizer from a workstation ΓòÉΓòÉΓòÉ

To delete Visualizer products:

 1. In the Visualizer folder, open the Utilities folder.

 2. Open the Visualizer Installing and Supporting utility.

 3. From the View menu, select Installed products.

 4. Select the name of the Visualizer product you want to delete.

 5. From the Action menu, select Delete.

 6. Select the components that you want to delete.

 7. Select the Delete push button to delete the components.

    The Progress Indicator window is displayed.

 8. When the delete process finishes, shut down and restart your workstation
    before deleting any other Visualizer product.

Some files remain in the installation location when you remove Visualizer
products from a LAN server. After you deleted all the Visualizer products on a
LAN server, delete the following files:

   FTBINSTS.EXE
   FTBIPRCS.EXE
   FTBIPII.DLL
   FTBIEXTS.DLL
   FTBIHPLB.HLP
   FTBIICIS.ICO
   FTBIMSG.MSG

Deleting DB2/2

If you delete DB2/2, shadows of DB2/2 objects will behave unpredictably. To
avoid this problem, always delete any shadows of SQL Table, SQL View, and SQL
Database objects when you delete DB2/2.

Re-installing Visualizer

If you re-install Query for OS/2, any Query for OS/2 objects that are still
stored on the workstation will be shown on the desktop, or in the appropriate
folder when that location is refreshed. Objects created using an optional
Visualizer product, are shown only if that optional product is also
re-installed. For example, to access charts created using Charts for OS/2 you
must re-install both Query for OS/2 and Charts for OS/2.


ΓòÉΓòÉΓòÉ 11. Overview of data sources ΓòÉΓòÉΓòÉ

This chapter describes the data sources you can access with IBM Visualizer
Query for OS/2 and the minimum levels of software required for that access.
Visualizer objects can access and use data from many sources:

o SQL data

  Visualizer accesses local and remote databases in DB2/2*, DB2/6000*, DB2,
  DB2/VM & VSE (SQL/DS), and AS/400* database.

  When IBM Visualizer Query for OS/2 is installed on your workstation, you can
  access SQL data stored in a DB2/2 database and present it in a report, or use
  it with other Visualizer objects. Through a local area network (LAN), you can
  use Visualizer to access data from remote sources-the data can be stored in
  database servers on host mainframes or shared LAN resources.

o Visualizer tables

  Visualizer tables store your data in a non-relational format in the
  Visualizer internal file system.

o Other applications

  You can exchange data with any other application that supports DDE or the
  OS/2 clipboard.

o OS/2 File System data

  You can exchange data with PC products that use the following file formats:

   - DBF (including dBASE IV** and Lotus** 1-2-3**)
   - DIF
   - Flat (FLT)
   - List (also known as Comma Separated Variable (CSV) and Delimited ASCII
     (DEL) )
   - IXF
   - PCIXF
   - WSF

o Other AS/400 data

  Instead of using DB2/2 to access AS/400 databases, you can use IBM PC
  Support/400 Version 2.2. Additionally, PC Support/400 also provides access to
  AS/400 physical and logical files.

o Other host data

  You can link to Application System on the host and access data:

   - from host AS tables
   - from tables in DB2 and DB2/VM & VSE (SQL/DS) using AS
   - through an AS Customized Data Interface (CDI)
   - from VSAM files using AS
   - from ISPF files using AS
   - from APL files using AS
   - from QMF* queries using AS

For information about using these data sources, see IBM Visualizer Query for
OS/2: Using.


ΓòÉΓòÉΓòÉ 11.1. Software requirements for accessing data ΓòÉΓòÉΓòÉ

The following diagram shows the relationship of various data sources with the
software required to connect to them is shown in the following diagram:

Depending on the software you have installed, you can access:

o Visualizer tables and OS/2 data

  With only Visualizer installed on your workstation, you can use Visualizer
  tables and OS/2 file system data.

o Local databases

  If you have DB2/2 with the Standalone option installed on your workstation,
  you can create and maintain local databases.

o Remote workstation database

  Remote DB2/2 and DB2/6000 data is available if you have either the DB2/2
  Client or CAE/2 installed on your workstation.

o Host databases

  With either DDCS/2 on your LAN, or by connecting to an AIX* system that has
  DDCS/6000, you can connect to host systems to access DB2, DB2/VM & VSE
  (SQL/DS), and AS/400 databases.

o OS/400 data

  With PC Support/400 on both your workstation and the target OS/400 system,
  you can access OS/400* databases as well as OS/400 physical and logical
  files.

o Other host data

  A variety of host data formats are available by connecting to host
  Application System using either Advanced Program-to-Program Communication
  (APPC) or Server-Requester Programming Interface (SRPI).

The minimum levels of software you need to connect to these data sources are as
follows:

On your workstation

To access local OS/2 data:

o IBM DATABASE 2* OS/2 (DB2/2) Version 1.0 or 1.2

To access data on remote OS/2 or AIX6000 workstations, one of the following:

o IBM DATABASE 2 OS/2 (DB2/2) Version 1.0 or 1.2
o IBM DATABASE 2 Client Application Enabler/2 Version 1.1 or 1.2

On your LAN

To access remote data on host systems, at least one of the following:

o IBM SAA* Distributed Database Connection Services/2 (DDCS/2)
  Version 2.0

o IBM SAA Distributed Database Connection Services/6000 (DDCS/6000) Version 1.1

o PC Support/400 Version 2.3

On the target workstation

To access remote DB2 workstation data, at least one of the following:

o IBM DATABASE 2 OS/2 (DB2/2) Version 1.0 or 1.2
o IBM DATABASE 2 AIX (DB2/6000) Version 1.1

On the target host system

To access remote data on host systems, at least one of the following:

o On an MVS system: IBM DATABASE 2 (DB2) Version 2.3

o On a VM system: Structured Query Language/Data System (SQL/DS*) Version 3.3

o On a VSE/ESA* system: Structured Query Language/Data System (SQL/DS) Version
  3.4

o On an AS/400 system: IBM Operating System/400* (OS/400) Version 2.3 and IBM
  PC Support/400 Version 2.3.

Using host Application System

To connect to host AS using APPC:

o Application System Version 3 Release 2

o Network and host system hardware and software, including one of the
  following:

   - OS/2 Version 2.1 with Communications Manager/2

   - OS/2 Version 2.1 with VM Programmable Workstation Communication Services
     (VM PWSCS)

To connect to host AS using SRPI:

o One of the following:

   - Application System Version 3 Release 2

   - Application System Version 3 Release 1, plus program temporary fixes
     (PTFs)

   - Application System Version 2 Release 2, plus PTFs

o Network and host system hardware and software, including OS/2 Version 2.1
  with Communications Manager/2


ΓòÉΓòÉΓòÉ 12. Accessing DB2/2, DB2/6000, DB2, and DB2/VM & VSE (SQL/DS) databases ΓòÉΓòÉΓòÉ

This chapter describes how Visualizer can access local and remote databases
that are stored in the following database managers:

o DB2/2
o DB2
o DB2/VM & VSE* (SQL/DS)
o DB2/6000*

There are two steps for giving Visualizer access to databases:

 1. Catalog the database in the database directory of DB2/2 or CAE/2. Refer to
    your DB2/2, or CAE/2 documentation for more information.

 2. Bind Visualizer to the database. This creates packages in the database that
    contain information that Visualizer uses to access the database. You must
    be authorized to bind the databases, as described in Authorization for
    binding. See Binding databases automatically for instructions for binding
    the databases.

Note:   To allow controlled access to AS/400 databases, first follow the
        instructions in Accessing AS/400 databases. That chapter describes how
        to create and give Visualizer access to the two physical files
        FTBADM/TABLES and FTBADM/COLUMNS. You can use FTBCRTTABS, a
        semi-automated sample REXX/400 procedure provided with Visualizer, to
        create the files in the database. After creating the files, you start
        the binding process, which creates an access package in each database.
        Then return here and follow the instructions in this chapter to
        complete the bind process.


ΓòÉΓòÉΓòÉ 12.1. Authorization for binding ΓòÉΓòÉΓòÉ

After you catalog databases in the DB2/2 or CAE/2 database directory, you must
bind Visualizer packages to the databases. You must be authorized to do this.
This section describes the authorizations you need depending on the database
manager you are accessing.

To use individual tables and views within a database, you must obtain access
from their owners or the database administrator. You can grant access to your
tables and views to other users on your system. See IBM Visualizer Query for
OS/2: Using for more information.

When users who have these authorizations start using Visualizer objects, the
bind process is performed automatically. If they do not have the authorization,
then someone who has authorization must perform the bind for them as described
in this chapter. For DB2/2 and DB2/6000

Your OS/2 user ID must have the SYSADM or DBADM authority. Local administrators
automatically have SYSADM authority on any local databases. To obtain authority
to access remote databases, contact the appropriate database administrator.

Note:   When you install OS/2, a default local administrator ID is created. It
has a user ID of USERID and a password of PASSWORD. To change the administrator
ID or create new user IDs, use the User Profile Management facilities provided
by OS/2. For DB2

The user ID (userid) that connects to DB2 to bind the Visualizer packages needs
to have SYSADM authority. DB2/VM & VSE (SQL/DS)

The user ID (userid) that connects to DB2/VM & VSE (SQL/DS) to bind the
packages needs, as a minimum, the authority granted by the following SQL
statements:

GRANT DBA TO userid IDENTIFIED BY password
GRANT SELECT ON SYSTEM.SYSCATALOG TO FTBADM WITH GRANT OPTION
GRANT SELECT ON SYSTEM.SYSTABAUTH TO FTBADM WITH GRANT OPTION
GRANT SELECT ON SYSTEM.SYSUSERAUTH TO FTBADM WITH GRANT OPTION
GRANT SELECT ON SYSTEM.SYSCOLUMNS TO FTBADM WITH GRANT OPTION
GRANT SELECT ON SYSTEM.SYSVIEWS TO FTBADM WITH GRANT OPTION
GRANT SELECT ON SYSTEM.SYSINDEXES TO FTBADM WITH GRANT OPTION
GRANT SELECT ON SYSTEM.SYSKEYCOLS TO FTBADM WITH GRANT OPTION
GRANT SELECT ON SYSTEM.SYSKEYS TO FTBADM WITH GRANT OPTION


ΓòÉΓòÉΓòÉ 12.2. Binding databases automatically ΓòÉΓòÉΓòÉ

This section describes how to bind databases using the Visualizer Database
Binder tool. If your installation is accessing remote databases, it is
recommended that you or someone else bind the databases for all your users.
Databases that are shared by many users need to be bound by only one user.

Note:   If you are binding AS/400 databases, first follow the instructions in
        Bind Visualizer to the AS/400 database, then return here and follow the
        instructions in this section.

The Database Binder:

o Creates views needed by the Visualizer objects.

o Binds Visualizer packages to the databases.

o Grants users PUBLIC authorization. If you do not want to grant PUBLIC
  authorization to all the users on your system, you can revoke the authorities
  and manually grant selective authorizations. For more information, refer to
  The Database Binder object.

The Database Binder uses the bind files stored in the directory specified by
the FTB1PATH environment variable in your CONFIG.SYS file. The output message
files are written into the directory specified by the FTB1DIR environment
variable. For each database, the name of the message file is the same as the
cataloged database name followed by the extension .MSG.

To bind databases automatically:

 1. Open the Visualizer folder.

 2. Open the Utilities folder.

 3. Open the Database Binder object.

 4. In the Database Binder window, select the Select All button if you want to
    bind all the databases in the Cataloged Databases list. If you don't want
    all the databases in the list, you can select individual ones for binding.

    Deselect All removes highlighting from all the databases in the list.

 5. Select OK.

If you later catalog or create additional databases, you must bind them too.


ΓòÉΓòÉΓòÉ 12.2.1. Database folder contents ΓòÉΓòÉΓòÉ

The Visualizer Database folder only displays those tables and views to which
the user has been given explicit access. Visualizer is not aware of any access
privileges that are implicitly granted by operating system dependant security
facilities such as RACF (MVS or VM), User Profile Management (OS/2), or group
membership (AIX). Therefore, to ensure that all required tables and views are
displayed in the Visualizer Database folder, you must use the SQL GRANT
statement to give database access privileges to users, even if this duplicates
privileges granted elsewhere.


ΓòÉΓòÉΓòÉ 12.3. Configuring DB2/2 to support Visualizer ΓòÉΓòÉΓòÉ

The DB2/2 configuration parameter numrc controls the maximum number of
concurrent connections to remote databases. You can adjust this parameter using
the Update Database Manager Configuration DB2/2 command.

If you change this value, remember that each Visualizer object requires a
separate connection to use a remote database.


ΓòÉΓòÉΓòÉ 13. Accessing AS/400 databases ΓòÉΓòÉΓòÉ

This chapter describes how to enable Visualizer to access AS/400* database
(DB2/400*) data. You must create two AS/400 physical files, FTBADM/TABLES and
FTBADM/COLUMNS. The names of these files start with the Visualizer file prefix
FTB. You use the REXX EXEC FTBCRTTABS to populate them with the information
required by Visualizer. You must also have Execute authority on the access
package for this release and SELECT authority on FTBADM/TABLES and
FTBADM/COLUMNS for each database. Contact your database administrator for help.

For each AS/400 database to be accessed from Visualizer, follow this procedure.
The steps are detailed later in this chapter.

 1. Set the coded character set identifier (CCSID) code page.

 2. Create the FTBADM library on the AS/400 system.

 3. Create journal files in the FTBADM library.

 4. In the FTBADM library, create AS/400 physical files that will contain the
    file definitions for FTBADM/TABLES, and FTBADM/COLUMNS.

 5. Create AS/400 physical files in the FTBADM library to temporarily contain
    the REXX EXECs FTBCRTTABS, READFILE, and WRITEFILE.

 6. Start journaling for the physical files. This enables DB2/2 to insert data
    into the files.

 7. Insert the definition information for FTBADM/TABLES and FTBADM/COLUMNS from
    DB2/2 into the AS/400 definition files.

 8. Insert the REXX EXECs FTBCRTTABS, READFILE, and WRITEFILE, into the
    temporary physical files.

 9. Create the source physical file, FTBADM/QREXSRC, and copy the REXX EXECs
    from the temporary files to members FTBCRTTABS, READFILE, and WRITEFILE.

10. Delete the temporary files and stop journaling.

11. Create FTBADM/TABLES and FTBADM/COLUMNS, using the data definition files.

12. Run FTBCRTTABS to populate FTBADM/TABLES and FTBADM/COLUMNS.

13. Bind Visualizer to the AS/400 database.


ΓòÉΓòÉΓòÉ 13.1. Preparation ΓòÉΓòÉΓòÉ

Before you register Visualizer with an AS/400 database, check that:

o You can establish a connection to the AS/400 database from a DB2 command
  prompt.

o You have access to an AS/400 terminal session.

o Your AS/400 user ID has *SECOFR privileges or *ALLOBJ authority.


ΓòÉΓòÉΓòÉ 13.2. Set the CCSID code page ΓòÉΓòÉΓòÉ

Check that the CCSID code page is set to a valid value other than 65535.

If you need to change the CCSID, use the CHGSYSVAL command to change the CCSID
setting. For example, to set the CCSID to U.S. English, at an AS/400 command
prompt, type:

chgsysval sysval(qccsid) value(037)

Then press Enter.

For more information on CCSID code page settings, see Application System/400
National Language Support Guide.

Visualizer cannot access data that was created using CCSID 65535 (*HEX FFFF).
However, you can change the code page of existing AS/400 files using the CHGPF
command. For example, to set the CCSID of an existing file, type:

chgpf file(library/filename) ccsid(37)

Then press Enter.

where:

library   Specifies the name of the library in which the file is stored.
filename  Specifies the name of the physical file.


ΓòÉΓòÉΓòÉ 13.3. Create the FTBADM library ΓòÉΓòÉΓòÉ

To create the FTBADM library:

 1. Log on to the AS/400.

 2. At an AS/400 command prompt, type:

        crtlib ftbadm

    Then press Enter.


ΓòÉΓòÉΓòÉ 13.4. Create journal files in the FTBADM library ΓòÉΓòÉΓòÉ

Use the files you create in this section to journal the temporary files, and
then to journal the FTBADM/TABLES and FTBADM/COLUMNS files.

To create the journal files, at an AS/400 command prompt, enter the following
commands:

crtjrnrcv jrnrcv(ftbadm/ftbjrnrcv)

crtjrn jrn(ftbadm/ftbjrn) jrnrcv(ftbadm/ftbjrnrcv)


ΓòÉΓòÉΓòÉ 13.5. Create empty data definition files ΓòÉΓòÉΓòÉ

Create the temporary physical files into which you later copy the data
definition files and REXX EXECs. To create temporary physical files to contain
the data definition for FTBADM/TABLES:

 1. Create the physical files. At an AS/400 command prompt, type:

        crtsrcpf file(ftbadm/ftbtab) mbr(*FILE)

    Then press Enter.

 2. Change the physical files' attributes. At an AS/400 command prompt, type:

        chgpfm file(ftbadm/ftbtab) mbr(ftbtab) srctype(pf)

    Then press Enter.

 3. Create another file and empty member for the data definition of
    FTBADM/COLUMNS. At an AS/400 command prompt, type:

        cpyf fromfile(ftbadm/ftbtab) frommbr(ftbtab)
            tofile(ftbadm/ftbcol) tombr(ftbcol) crtfile(*YES)

    Then press Enter.


ΓòÉΓòÉΓòÉ 13.6. Create temporary files for the REXX EXECs ΓòÉΓòÉΓòÉ

You create the REXX EXECs FTBCRTTABS, READFILE, and WRITEFILE as temporary
files, because only the first member of a file can be accessed through DDCS/2.
In the EXECs are stored as three members of one physical file.

 1. Create the three physical source files to be used as temporary files that
    are to receive the three REXX EXECs:

    a) Create the first empty file. At an AS/400 command prompt, type:

              crtsrcpf file(ftbadm/temp1) mbr(*FILE)

       Then press Enter.

    b) Set the file's attributes. At an AS/400 command prompt, type:

              chgpfm file(ftbadm/temp1) mbr(temp1) srctype(rexx)

       Then press Enter.

 2. Copy the empty file to create two more empty files. At an AS/400 command
    prompt, enter the following commands:

        cpyf fromfile(ftbadm/temp1) frommbr(temp1)
            tofile(ftbadm/temp2) tombr(temp2) crtfile(*YES)

        cpyf fromfile(ftbadm/temp1) frommbr(temp1)
            tofile(ftbadm/temp3) tombr(temp3) crtfile(*YES)


ΓòÉΓòÉΓòÉ 13.7. Journal the physical files ΓòÉΓòÉΓòÉ

You must journal the physical files so that data can be inserted from DB2/2. To
start journaling, at an AS/400 command prompt, enter the following commands:

strjrnpf file(ftbadm/ftbtab) jrn(ftbadm/ftbjrn)

strjrnpf file(ftbadm/ftbcol) jrn(ftbadm/ftbjrn)

strjrnpf file(ftbadm/temp1)  jrn(ftbadm/ftbjrn)

strjrnpf file(ftbadm/temp2)  jrn(ftbadm/ftbjrn)

strjrnpf file(ftbadm/temp3)  jrn(ftbadm/ftbjrn)


ΓòÉΓòÉΓòÉ 13.8. Insert definitions and REXX EXECs ΓòÉΓòÉΓòÉ

Insert the data definition information and REXX EXECs into the AS/400 physical
files you just created:

 1. Ensure that your AS/400 is configured and cataloged to DDCS/2.

 2. Log on at a workstation on which Visualizer is installed.

 3. Change to the directory in which IBM Visualizer Query for OS/2 is
    installed. This directory contains the bind and SQL files that enable
    database access.

 4. Connect to the AS/400 database to be enabled. If you are using CAE/2, at an
    OS/2 command prompt, enter:

        db2 connect to database_name [user user_id using password]

    If you are using DB2/2, at an OS/2 command prompt, enter:

        dbm connect to database_name

    where:

   database_name    Specifies the name of the database you want to connect to.
   user_id          Specifies the user ID you used in step 2.
   password         Specifies the password you used in step 2.

    The user ID and password parameters are required for remote databases that
    are defined with an authentication of DCS.

    Your AS/400 user ID must be authorized to insert data into tables in the
    FTBADM library. Contact your database administrator.

 5. If you are using CAE/2, at an OS/2 command prompt, enter:

        db2 -v -f ftbsqli4 > filename

    If you are using DB2/2, at an OS/2 command prompt, enter:

        ftbsqli4 database_name > filename

    where:

   database_name    Specifies the name of the database you want to connect to.
   filename         Specifies the name of a file used to store the command
                    output.

    This command may take a few minutes to run.

    When the command finishes, check that all steps completed successfully by
    reviewing the contents of filename with an editor. The command may be rerun
    if any part of the operation does not complete successfully.


ΓòÉΓòÉΓòÉ 13.9. Copy the REXX EXECs to FTBADM/QREXSRC ΓòÉΓòÉΓòÉ

Copy the temporary files that hold the REXX EXECs FTBCRTTABS, READFILE, and
WRITEFILE to separate members of the physical source file, FTBADM/QREXSRC.

At an AS/400 command prompt, enter the following commands:

cpyf fromfile(ftbadm/temp1) frommbr(temp1) tofile(ftbadm/qrexsrc)
    tombr(ftbcrttabs) crtfile(*YES)

cpyf fromfile(ftbadm/temp2) frommbr(temp2) tofile(ftbadm/qrexsrc)
    tombr(readfile) mbropt(*ADD)

cpyf fromfile(ftbadm/temp3) frommbr(temp3) tofile(ftbadm/qrexsrc)
    tombr(writefile) mbropt(*ADD)


ΓòÉΓòÉΓòÉ 13.10. Delete the temporary files and stop journaling ΓòÉΓòÉΓòÉ

Delete the temporary files. At an AS/400 command prompt, enter the following
commands:

dltf file(ftbadm/temp1)

dltf file(ftbadm/temp2)

dltf file(ftbadm/temp3)

Stop journaling on the files that contain the data definitions. At an AS/400
command prompt, enter the following commands:

endjrnpf file(ftbadm/ftbtab)

endjrnpf file(ftbadm/ftbcol)


ΓòÉΓòÉΓòÉ 13.11. Create FTBADM/TABLES and FTBADM/COLUMNS ΓòÉΓòÉΓòÉ

Create the FTBADM/TABLES and FTBADM/COLUMNS files and start journaling them:

 1. Create the FTBADM/TABLES and FTBADM/COLUMNS. At an AS/400 prompt, enter the
    following commands:

        crtpf file(ftbadm/tables) srcfile(ftbadm/ftbtab) srcmbr(ftbtab)

        crtpf file(ftbadm/columns) srcfile(ftbadm/ftbcol) srcmbr(ftbcol)

 2. Start journaling the files to the journal file created in Create journal
    files in the FTBADM library. At an AS/400 prompt, enter the following
    commands:

        strjrnpf file(ftbadm/tables) jrn(ftbadm/ftbjrn)

        strjrnpf file(ftbadm/columns) jrn(ftbadm/ftbjrn)


ΓòÉΓòÉΓòÉ 13.12. Run FTBCRTTABS to populate FTBADM/TABLES and FTBADM/COLUMNS ΓòÉΓòÉΓòÉ

Run the FTBCRTTABS EXEC to populate FTBADM/TABLES and FTBADM/COLUMNS with the
information required by Visualizer. Before running FTBCRTTABS, make sure that
the REXX source code of FTBCRTTABS is already in FTBADM/QREXSRC as members
FTBCRTTABS, READFILE, and WRITEFILE.

To avoid file contention and shorten the run time, run this program outside
periods of peak activity on the AS/400. You must have *SECOFR privileges or
have *ALLOBJ authority to run FTBCRTTABS because read authority to
QSYS/QADBXREF cannot be granted to other AS/400 users.

To run FTBCRTTABS directly, at an AS/400 command prompt, enter the strrexprc
command in the following format:

strrexprc srcfile(ftbadm/qrexsrc) srcmbr(ftbcrttabs) parm('parms')

where parms are the user-supplied parameters.

To speed up run time, FTBCRTTABS can also be run as a batch command. To submit
FTBCRTTABS as a command to batch, at an AS/400 command prompt, enter the
strrexprc command in the following format:

sbmjob cmd(strrexprc srcfile(ftbadm/qrexsrc)
    srcmbr(ftbcrttabs) parm('parms'))

where parms are the user-supplied parameters.

The format of the user-supplied FTBCRTTABS parameters is as follows:

ΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼Γö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇ
   Γöé          ΓöîΓöÇΓöÇΓöÇΓöÇ,ΓöÇΓöÇΓöÇΓöÇΓöÉ   Γöé ΓööΓöÇDATADICTΓöÇΓöÿΓööΓöÇSQLCATALOGΓöÇΓöÿ
   Γöé                   Γöé   Γöé
   Γö£INCLUDEΓöÇ(ΓöÇΓöÇΓöÇlibraryΓöÇΓö┤ΓöÇ)ΓöÇΓöñ
   Γöé          ΓöîΓöÇΓöÇΓöÇΓöÇ,ΓöÇΓöÇΓöÇΓöÇΓöÉ   Γöé
   Γöé                   Γöé   Γöé
   ΓööEXCLUDEΓöÇ(ΓöÇΓöÇΓöÇlibraryΓöÇΓö┤ΓöÇ)ΓöÇΓöÿ

INCLUDE
            Restricts the views to a particular set of libraries.

EXCLUDE
            Specifies all libraries except a library set.

            INCLUDE and EXCLUDE are mutually exclusive. An error message is
            displayed if both are specified. To save run time, you can specify
            these choices for a limited number of libraries.

library
            Provides simple masking by using the * suffix. For example,
            INCLUDE(FTB*,LIB2,LIB4) selects all libraries beginning with FTB,
            plus the libraries LIB2 and LIB4. The EXCLUDE parameter can be used
            in the same manner.

DATADICT
            Specifies whether the data dictionary files are to be added to the
            tables. If DATADICT is not specified, these files are ignored. This
            refers only to files that begin with QIDCT. Ignoring these files
            reduces run time.

SQLCATALOG
            Specifies whether the SQL catalog files are to be added to the
            tables. If SQLCATALOG is not specified, the SQL catalog files are
            ignored. This refers to only the files created when an SQL/400*
            CREATE COLLECTION command is run, such as QSQCOLUMNS, QSQTABLES,
            and SYSINDEXES and others. Ignoring these files reduces run time.

The following command is an example of user-supplied parameters that generate
FTBADM/TABLES and FTBADM/COLUMNS for all tables in the FTBTESTLIB library:

strrexprc srcfile(ftbadm/qrexsrc) srcmbr(ftbcrttabs)
    parm('include(ftbtestlib) datadict')


ΓòÉΓòÉΓòÉ 13.12.1. Considerations when running FTBCRTTABS ΓòÉΓòÉΓòÉ

o FTBCRTTABS checks that FTBADM/TABLES and FTBADM/COLUMNS are created in the
  correct format. If they are not created correctly, FTBCRTTABS stops and
  displays the following messages:

   - table object in error with CHKOBJ return code code

   - FTBADM/TABLES and FTBADM/COLUMNS must be created before this program is
     run. Refer to installation guide

o If the parameters are incorrect, the program ends, and one of the following
  messages is displayed:

   - Invalid expression ignored in parms field expression

   - INCLUDE must be followed by a bracketed list of libraries

   - EXCLUDE must be followed by a bracketed list of libraries

   - INCLUDE and EXCLUDE can not be specified together

   - Right parenthesis missing on INCLUDE

   - Right parenthesis missing on EXCLUDE

   - Invalid entry in parameter list with entries library list. Each entry must
     be a word separated by a comma (,), without any embedded spaces.

o FTBCRTTABS processes QSYS/QADBXREF, and places information about each
  database file in FTBADM/TABLES and FTBADM/COLUMNS. Visualizer can access
  files that are not in the FTBADM/TABLES file. However, such files are not
  displayed when you list the contents of the AS/400 database.

  Messages are displayed if the program encounters error conditions, such as
  when a file has no field information, or when FTBADM/TABLE or FTBADM/COLUMNS
  are already in use. These messages have the following format:

   - Error obtaining field information about object code

     where:

      object    Is a valid file for which data is to be included in the files
                FTBADM/TABLES and FTBADM/COLUMNS.
      code      Represents the code returned from the DSPFFD command used to
                acquire this information.

   - Error occurred writing to file. Make sure the file is not being used
     elsewhere and try again

     where:

      file      Is either FTBADM/TABLES or FTBADM/COLUMNS.

FTBCRTTABS might request too much memory to store the information about the
appropriate files. The job may fail if resources are exhausted. Therefore,
include only libraries that are needed. Specify DATADICT and SQLCATALOG choices
only when those resources are needed. This also helps to minimize the run time.

The administrator should maintain the list of required libraries that are
supplied as input to FTBCRTTABS. When a file is required within a library, the
whole library is searched for valid files.


ΓòÉΓòÉΓòÉ 13.13. Bind Visualizer to the AS/400 database ΓòÉΓòÉΓòÉ

Use the Visualizer Database Binder object to complete the database binding by
following the instructions in Binding databases automatically.


ΓòÉΓòÉΓòÉ 14. Accessing AS/400 data using PC Support/400 ΓòÉΓòÉΓòÉ

This chapter describes how to use Visualizer with PC Support/400 to:

o Access data from AS/400 files (physical and logical)
o Access data from SQL tables and views on the AS/400
o Store data into AS/400 files
o Store data into SQL tables on the AS/400

For example, you can create a Visualizer report from data you hold on the
AS/400 and save the report into a shared folder on the AS/400 using an OS/2
file format. You can then include the report either in a document on the AS/400
or in a word processor document on your workstation.

To access AS/400 databases from Visualizer using IBM SAA* Distributed Database
Connection Services/2, see Accessing AS/400 databases.

If you have PC Support/400 installed, you can access AS/400 data directly from
Query, Report, and Visualizer table objects. In Visualizer table, the Type list
is in the Import window, which is available from the Table menu.

For example, if you want to create a report and all the data you need is
already present in one AS/400 physical file, logical file, SQL table, or SQL
view, you can access the data directly from the Visualizer table, Query, and
Report objects. If you want to combine data held on the AS/400 with data held
in Visualizer tables, first copy the AS/400 data into a Visualizer table. Then
use Visualizer Query to combine the Visualizer tables.


ΓòÉΓòÉΓòÉ 14.1. Preparing to use the AS/400 ΓòÉΓòÉΓòÉ

Before accessing AS/400 data from Visualizer for the first time, you need to:

 1. Ensure that PC Support/400 is installed on your workstation. See AS/400 PC
    Support/400 OS/2 Installation and Administration Guide.

 2. Ensure that Communications Manager/2 is configured correctly for PC
    Support/400.

 3. Make a note of your AS/400 system name, also known as the partner logical
    unit (PLU) alias, as defined in Communications Manager/2. You need it to
    reply to a Visualizer prompt. If you do not know your PLU alias, contact
    your system administrator.


ΓòÉΓòÉΓòÉ 14.2. Example of accessing AS/400 data ΓòÉΓòÉΓòÉ

This is an example of how to access data from the AS/400 within a Visualizer
report. Use similar steps to access data within the Query and Visualizer table
objects.

 1. Start your PC Support/400 session, if you have not already done so.

 2. Create a new report:

    a) Open the Visualizer folder.

    b) Open the Shadows of Templates folder.

    c) Drag the Reports for OS/2 template to a folder or the desktop.

       An unnamed report window is displayed.

 3. Select  from the tool bar.

    The Select a Table or Query window is displayed.

 4. Select AS/400 from the Type list.

    The AS/400 System Name window is displayed.

 5. In AS/400 System Name, type the AS/400 system name (PLU alias).

 6. Select OK. The AS/400 libraries you can access are displayed in the
    Locations list. The information in the list is taken from the Visualizer
    Profile object.

    Visualizer needs to have the AS/400 system name defined so that it can
    communicate with the AS/400 using PC Support/400. If you have not started
    PC Support/400, Visualizer issues a message asking you to do so.

 7. Do one of the following:

   o From the Locations list, select the AS/400 library that contains the file
     you want to use.

   o Type \library in the Location field following the AS/400 name.

    The files are then displayed in the Locations list.

 8. Select the AS/400 file you want from Locations. The AS/400 file members are
    now shown in the Names list.

 9. From Names, select the AS/400 file member that provides the data for the
    report you want to create.

10. Select OK.

    The Select Columns window of Visualizer Report is displayed.

11. Complete and save the report. See IBM Visualizer Query for OS/2: Using for
    more information about creating reports.

There are differences in the way data is stored in Visualizer, SQL databases,
and the AS/400 system. The differences are described in Data conversions.


ΓòÉΓòÉΓòÉ 15. Accessing host data using Application System ΓòÉΓòÉΓòÉ

You can use IBM Visualizer Query for OS/2 to access a variety of host data
sources by connecting to Application System (AS) on MVS or VM systems. This
chapter describes three different ways to connect to AS:  APPC, VM PWSCS, and
SRPI connections.

You can define the connection to the AS server in the Profile field on page 3
of the Visualizer section of the Profile notebook. The profile name describes
the type of connection to AS. Details of this profile are normally specified in
the DASPWAPI.INI file. Your default server type can also be set in
DASPWAPI.INI. If DASPWAPI.INI does not exist, SRPI connections using a profile
name of DASSERV are used by default.

Before connecting to AS:

o Communications Manager/2 must be installed, unless you are using VM PWSCS.

o For SRPI connections, ensure the following:

   - The SRPI feature of your Communications Manager system is installed and
     activated.

   - You can use AS in the 3270 terminal emulation session you will use for
     Visualizer data transfer.

   - You have an SRPI profile available for you to use; see Creating SRPI
     profiles for OS/2.

   - If you are using AS on VM, ensure that you have access to the AS program
     code (including the DASSERV MODULE). For more information, see Application
     System: Supporting and Customizing (VM).

   - If you are using AS on MVS, ensure the following:

      -- The MVSSERV parameter list, ddname CHSPARM, includes an item
         specifying DASSERV (in columns 1 to 7).

      -- Appropriate definitions are in place to enable you to access the AS
         program code.

o For APPC connections, ensure that you have set up the appropriate Side
  Information or DASPWAPI.INI entry as described in Using APPC connections.

o For VM PWSCS connections, ensure that you have set up VM PWSCS definitions or
  DASPWAPI.INI entry as described in Using VM PWSCS connections.

o For APPC or VM PWSCS connections, ensure the following:

   - Your support group has set up the required connections, and that the
     required host definitions (MVS, VM, VTAM*, and so on) are in place.

   - On MVS or VM, you must set up a suitable Transaction Program (TP) profile.
     You need to know the name of this profile. The user ID that is used for
     the connection must have access to the Transaction Program and the
     required security authority to run the profile.

o To access host data from Visualizer, you must first establish the host
  environment that allows AS to access that host data.

Your AS administrator should install any PTFs that are required to permit the
transfer of Visualizer data and specifications.

You need to know the number of the host code page that provides the correct
character translation when data is transferred.

See Application System: Client Connections, for more details.


ΓòÉΓòÉΓòÉ 15.1. Using SRPI connections ΓòÉΓòÉΓòÉ

When your application requests an SRPI connection to the SRPI AS server
program, the software on your workstation requires the following information:

o SRPI server name-always DASSERV for the SRPI AS server program
o 3270 emulation session ID on which the communication operates

Communications Manager/2 keeps this information in SRPI profiles. Each profile
has a name, called a SRPI alias.

If you are running an application using an SRPI connection between AS and
Visualizer, the communication profile used must specify a type of SRPI and the
correct SRPI alias as the servername.


ΓòÉΓòÉΓòÉ 15.1.1. Creating SRPI profiles for OS/2 ΓòÉΓòÉΓòÉ

A default SRPI profile may already have been defined. Contact your OS/2
workstation coordinator to confirm whether you need to set up your own SRPI
profile. If you need to, follow these instructions to create or change an SRPI
profile:

 1. Open the Communications Manager/2 folder.

 2. Select Communications Manager Setup.

    The Communications Manager Setup window is displayed.

 3. Select Setup.

    The Open Configuration window is displayed.

 4. Select or type in the name of your Communications Manager/2 configuration
    file. Ask your installation's OS/2 workstation coordinator if you do not
    know this name.

 5. Select OK.

    The Communication Manager Configuration Definition window is displayed.

 6. Select the correct connection type on the Workstation Connection Type list.

 7. Select 3270 emulation on the Feature or Application list.

 8. Select Configure.

    The 3270 Emulation through connection_type window is displayed.

 9. Select Advanced.

    The Communications Manager Profile List Sheet window is displayed.

10. Select 3270 SRPI.

11. Select Configure.

    The Server Requester Programming Interface window is displayed.

12. If you want to update an existing profile or the associated 3270 session
    information:

   o To update an existing profile:

       a) Select the required profile from the list.

          The Server Alias window for that profile is displayed.

       b) Change the comment, if appropriate.

       c) Type in the server name.  This must be DASSERV for AS.

       d) Select Save to save this information.

   o To change the 3270 session for an existing profile:

       a) Select the required 3270 Long Session name from the list.

       b) Select the arrow next to that 3270 Long Session name.

       c) Select the required 3270 session from the list.

    If you want to create a new profile or the associated 3270 session
    information:

   o Creating a new profile:

       a) Select File.

       b) Select New.

          The Server Alias window is displayed.

       c) Add a comment, if necessary.

       d) Type in the server name. This must be DASSERV for AS.

       e) Select Save as.

       f) Type in the new profile name.

       g) Select OK.

   o Adding the 3270 session information:

       a) Select the new profile from the list.

       b) Select the arrow next to the 3270 Long Session name field to display
          the list.

       c) Select the appropriate 3270 session.

13. Close the Server Requester Programming Interface window.

    The Communications Manager Profile List Sheet window is displayed.

14. Select Close.

    The Communications Manager Configuration Definition window is displayed.

If you need to, follow these instructions to configure the Communications
Manager/2 workstation information:

 1. Select Options from the menu bar.

 2. Select Change workstation information from the list.

    The Workstation Information window is displayed.

 3. If SRPI is not already selected, select SRPI.

 4. Select OK.

    The Communications Manager Configuration Definition window is displayed.

 5. Select Close.

    A window containing message ACS2121 is displayed:

        Would you like to dynamically update your SNA resources?

 6. Select Yes or No, as appropriate, depending on whether you want the update
    to be performed.

 7. When the Communications Manager Setup window is displayed, select Close.
    This returns you to the Communications Manager/2 folder.

If you want to use more than one 3270 session ID for data transfer, you should
create another SRPI profile with a different server alias. Specify the new
server alias in the Visualizer Host AS Settings window. The default values can
be set using the Visualizer Profile notebook. The Host AS Settings window can
also be accessed from the Import and Export menu choices of Visualizer objects.


ΓòÉΓòÉΓòÉ 15.1.2. Starting SRPI on MVS ΓòÉΓòÉΓòÉ

The communication runs in your normal TSO/E address space (user ID). On the
workstation, switch to the 3270 emulation session and log on to TSO/E as
normal.

To establish SRPI communications mode, enter MVSSERV. The MVSSERV logo is
displayed and communication is enabled. You can switch back to the workstation
program and use the SRPI communication facilities.

Although you can switch back to the 3270 emulation session while the
communication facilities are in use, do not terminate MVSSERV until they have
finished. If you terminate MVSSERV while communications facilities are still
running, AS terminates and the workstation program may report error conditions.


ΓòÉΓòÉΓòÉ 15.1.3. Starting SRPI on VM ΓòÉΓòÉΓòÉ

SRPI communication runs in your normal VM (CMS) virtual machine (user ID). On
the workstation, you must switch to the 3270 emulation session and log on to VM
(CMS) as normal.

Ensure you have your AS minidisk or SFS directory accessed. If not, enter the
necessary LINK or ACCESS commands or follow the procedures defined by your
installation.

To establish SRPI communications mode, enter CMSSERV. The CMSSERV logo is
displayed, and communication is enabled. You can switch back to the workstation
program and use the AS communication facilities.

Although you can switch back to the 3270 emulation session while communication
facilities are in use, do not terminate CMSSERV until the facilities have
finished. If you terminate CMSSERV while communications facilities are still
running, AS terminates and the workstation program may report error conditions.

Do not use a single AS session for both communication and normal end-user
support, such as a VMAS terminal session or the command interface. Commands
that invoke AS should not be issued from the CMSSERV command prompt.


ΓòÉΓòÉΓòÉ 15.1.3.1. Unsolicited messages ΓòÉΓòÉΓòÉ

You can avoid receiving unsolicited messages by issuing the CP command SET MSG
OFF before starting CMSSERV. When an unsolicited screen update occurs, the
CMSSERV logo is replaced by other data. This temporarily blocks the SRPI data
flow. To restore the data flow, switch to the 3270 emulation session and
restore the logo (for example, by clearing the screen).


ΓòÉΓòÉΓòÉ 15.1.4. Logging on automatically with SRPI ΓòÉΓòÉΓòÉ

Many Visualizer objects can use REXX commands to start the connection to AS (if
the connection is not already started). Specify the logon command in the Host
AS Settings window. The default logon command is FTBLNMV for MVS and FTBLNVM
for VM. The following sample files are provided for you to customize:

FTBLNMV.CMD for TSO/E logon
FTBLNVM.CMD for VM logon

To customize a sample command file for use on your own system:

 1. First copy the appropriate sample file to your own file. In the following
    example, the file, LOGON.CMD, is used to create an autologon script for a
    VM system:

        copy ftblnvm.cmd logon.cmd

 2. Edit the command file to suit your installation. Customize the file between
    the following two comment lines:

        /* Start your specific logon process here          */
        ...
        /* Specific logon process ends here                */

    Command files are processed in a large loop. The file searches for strings
    on the host screen and provides appropriate replies. For example:

             When Findit('HOLDING') Then
               Zx = ENF(Comm_Name,'SEND','@C')

    looks for the word HOLDING on the host screen and sends a Clear command
    when it is found. The definitions for the keyboard mnemonics can be found
    in OS/2 EHLLAPI Programming Reference.

 3. After you have edited your command script, use a utility such as PMREXX to
    check for errors. PMREXX runs outside of the Visualizer environment.

    For example, change the Trace 'o' to Trace 'a' in the file. This enables
    the lines of the REXX file to be traced. Execute the logon script from an
    OS/2 full-screen session by typing:

        pmrexx command_file_name UserID NodeID Session

    PMREXX shows each command in the file as it is executed, together with any
    errors that occur.

After you have created a suitable command script for your environment, specify
its name and parameters in the Host AS Settings window.


ΓòÉΓòÉΓòÉ 15.2. Using APPC connections ΓòÉΓòÉΓòÉ

When your application requests an APPC (or VM PWSCS) connection to the APPC AS
server program, the APPC software on your workstation requires the following
information. For more details, see Application System: Client Connections.

Partner LU Network address of the target computer. This is the network LU name
   of the APPC/MVS scheduler (for MVS systems) or the AVS gateway (for VM
   systems). Your installation's network support specialist can provide this
   information. You can use defined alias names as well as the full network
   name in OS/2 Communications Manager.

   If you are using a VM PWSCS direct connection to your VM system (that is,
   without using the SNA network), see VM Programmable Workstation
   Communication Services Operating Guide and Programming Reference Version 1
   Release 2, SC24-5645.

Partner TP APPC AS server program TP name.  This is the name of the program
   that handles APPC connections to AS. Your installation's AS product
   coordinator should provide this information. For MVS systems, it is the name
   of a TP profile entry. For VM systems, it is either a nickname (specified in
   the $SERVER$ NAMES file) or the actual name of the program.

   APPC AS server program TP type.  Define this as a "normal" TP, not a
   "Service" TP.

Security type Conversation security type: Same, None, or Program. Normally for
   AS the choice is Same or Program. Follow any guidelines or standards set by
   your installation when making your choice. For more information, see
   Application System: Client Connections.

Mode name Connection mode name-this defines some characteristics of the
   connection. Your installation's network support specialist can tell you
   this. A suitable mode for AS connections is #INTER, a standard mode that
   most APPC software components support.

User ID/Password If conversation security type is Program:

   User ID   Conversation security user ID: your MVS (TSO/E) or VM (CMS) user
             ID

   Password  Conversation security password: the current valid password of your
             MVS (TSO/E) or VM (CMS) user ID

For more information about VM PWSCS, see Using VM PWSCS connections.


ΓòÉΓòÉΓòÉ 15.2.1. Creating or changing Side Information on OS/2 ΓòÉΓòÉΓòÉ

Visualizer uses the CPI Communications interface to the APPC connection
services. The CPI Communications architecture name for the table or file
containing sets of this information is Side Information. The name for a single
entry is symbolic destination name.

Although conversation security type, conversation security user ID, and
conversation security password do not form part of the symbolic destination
name, the OS/2 implementation of CPI Communications includes them in the Side
Information entries. You can override Side Information parameters by using the
server profile entry, see Application System: Client Connections, for more
information.

To create or change a Side Information entry, using Communications Manager/2:

 1. Open the Communications Manager/2 folder.

 2. Select Communications Manager Setup.

    The Communications Manager Setup window is displayed.

 3. Select Setup.

    The Open Configuration window is displayed.

 4. Select or enter the name of your Communications Manager/2 configuration
    file. Ask your OS/2 workstation coordinator if you do not know this name.

 5. Select OK.

    The Communication Manager Configuration Definition window is displayed.

 6. Select the correct connection type on the Workstation Connection Type list.

 7. Select CPI Communications on the Feature or Application list.

 8. Select Configure.

    The Communications Manager Profile List Sheet window is displayed.

 9. Select SNA Features.

10. Select Configure.

    The SNA Features List window is displayed.

11. If you want to add a new Side Information entry:

    a) Select CPI Communications Side Info on the features list.

    b) Select Create.

    If you want to alter an existing Side Information entry:

    a) Select CPI Communications Side Info on the features list.

    b) Select the entry you wish to alter.

    c) Select Change.

12. Follow the instructions on the screen to create or change the Side
    Information entry as you require. For details of what you need to change,
    see Using APPC connections.

13. Select Close.

    The Communications Manager Profile List Sheet window is displayed.

14. Select Close.

    The Communications Manager Configuration Definition window is displayed.

15. Select Close.

    A window containing the message ACS2121 is displayed:

        Would you like to dynamically update your SNA resources?

    Select Yes or No depending on whether you want the update to be performed.

16. When the Communications Manager Setup window is displayed, select Close.
    This returns you to the Communications Manager/2 folder.


ΓòÉΓòÉΓòÉ 15.2.2. Using the APPC AS server program on MVS systems ΓòÉΓòÉΓòÉ

The APPC AS server program runs in an APPC/MVS address space, not in your TSO/E
user address space. This means that you can perform other tasks in your TSO/E
user address space, and in MVS batch address spaces, while running an
application that communicates with AS using an APPC or VM PWSCS connection.
However, if another task is running AS, each address space must use a different
AS application code.

You cannot log on to an APPC/MVS address space.


ΓòÉΓòÉΓòÉ 15.2.3. Using the APPC AS server program on VM systems ΓòÉΓòÉΓòÉ

The APPC AS server program runs in your own CMS virtual machine. This means
that you cannot use your CMS virtual machine to perform other work (including
running AS) while running an application that communicates with AS using an
APPC connection. To enable your virtual machine to run the APPC AS server
program, you (or your installation's VM systems administrator) must arrange for
certain conditions to be set up. See Application System: Client Connections,
for more details.

APPC/VM queues the connection if the connection request from your application
arrives when your virtual machine is busy (your virtual machine is not at the
CMS Ready; prompt). When you exit from the program you are running, the APPC AS
server program starts automatically.

If your virtual machine is not logged on when the connection request from your
application arrives, VM automatically logs your virtual machine on (in
disconnected mode). Your PROFILE EXEC, and anything that it calls, must
complete in disconnected mode without any intervention. For example, do not
call facilities like RDRLIST. Upon completion of the PROFILE EXEC, your virtual
machine must have the CMS minidisk or SFS directory containing the APPC AS
server program accessed.


ΓòÉΓòÉΓòÉ 15.3. Using VM PWSCS connections ΓòÉΓòÉΓòÉ

When your application requests a VM PWSCS connection to the APPC AS server
program, you should do the following:

o Configure the system configuration files (optional).
o Configure the communications directory.


ΓòÉΓòÉΓòÉ 15.3.1. Configuration files ΓòÉΓòÉΓòÉ

To set up VM PWSCS for use, the client workstation must be configured so that
VM PWSCS can be run in the workstation's environment. STARTUP.CMD and
CONFIG.SYS are updated automatically during the installation of VM PWSCS. The
installation process also prompts for the local domain controller name and the
user's user ID and password. Your LAN administrator should update the user
directory file for the domain controller with this user ID and password.

When VM PWSCS is installed in the client workstation, the correct statements
are added to CONFIG.SYS.

Complete descriptions of these statements are found in the OS/2 Command
Reference.

To start VM PWSCS when the client workstation is switched on, the ACPKSTRT
command must be added to STARTUP.CMD. For example, you can specify the
following ACPKSTRT command in STARTUP.CMD or add a program reference to the
OS/2 Startup folder (in the OS/2 System folder).

call c:\pwscs\acpkstrt c \pwscs user acpi.ini

For more information on configuring the system configuration files, see the VM
PWSCS Operating Guide and Programming Reference Version 1.2.


ΓòÉΓòÉΓòÉ 15.3.2. Communications directory file ΓòÉΓòÉΓòÉ

A user program must identify the following:

o Location and name of the APPC AS server program
o Conversation security type
o Connection mode name

If the conversation security type is Program (PGM), access security user ID and
password information is also needed. This information is known as Side
Information and is associated with a symbolic destination name. The
communications directory file contains sets of information; each set comprises
a symbolic destination name and its associated Side Information.

The default file identifier for the communications directory is ACPI.DIR. To
create or change an entry in the communications directory, use the VM PWSCS
CSCMD command. This displays a window from which you can select the VM PWSCS
CONFIGURE function and update the communications directory file. The
communications directory information is defined as follows:

Symbolic destination name The 1- to 8-character name as specified in the user
  program.

Partner LU name An LU name qualifier plus a target LU name. It is written as:

    luname_qualifier.target_lu

  The LU name qualifier is an 8-byte name that specifies whether the APPC AS
  server program is in an adjacent TSAF collection (in which case it is the
  name of the VM system that is common to both the CS and the TSAF collection),
  or it is in the SNA network (in which case it is the name of the AVS or OS/2
  gateway).

  The target LU name is an 8-byte name that specifies one of the following:

   o User ID where the APPC AS server program resides (if the APPC AS server
     program is in an adjacent TSAF collection)

   o AVS gateway name through which the APPC AS server program is accessed (if
     the APPC AS server program resides on a VM system)

   o Remote LU name where the APPC AS server program is located

Transaction Program name The 1- to 64-character APPC AS server program name as
  defined at the target LU.

   o If the APPC AS server program is located in a VM system, this may be the
     nickname specified in the $SERVER$ NAMES file (on the user ID to which the
     connection is to be directed), or the actual program name.

   o If the APPC AS server program is located in an MVS system, this is the
     name of a TP profile specified in the TP profile data set associated with
     the target LU.

Mode name The 1- to 8-byte field that defines some characteristics of the
  connection. A suitable mode is #INTER.

Security Specifies the security level of the conversation. It is either NONE,
  SAME, or PGM.

Security user ID The 1- to 8-character user ID of the requester on the target
  LU. It is used only if conversation security is SECURITY(PGM).

Security password The 1- to 8-character password of the target LU user ID. It
  is used only if conversation security is SECURITY(PGM).

For more information about VM PWSCS, see Application System: Client
Connections.


ΓòÉΓòÉΓòÉ 16. Diagnosing Visualizer problems ΓòÉΓòÉΓòÉ

This chapter provides information to help you resolve problems that may occur
while using Visualizer.

During normal operation, Visualizer displays information, warning, and error
messages. For example, a message might inform you that an event has occurred or
prompt you when an action is required. However, Visualizer may also display
messages that indicate it has encountered an unexpected error condition. This
chapter describes what to do if you encounter a Visualizer problem and explains
how to use the Visualizer diagnostic aids.


ΓòÉΓòÉΓòÉ 16.1. Error messages ΓòÉΓòÉΓòÉ

In Visualizer, messages are displayed when the cause of a problem is unclear
and there is no preprogrammed solution. These are called unexpected errors.

If a message identifies an unexpected error, make a note of the message number
and the circumstances under which the error occurred. For example, try to
record the following:

o What you were doing immediately before the error occurred

o What happened after the error occurred

o Details of any other software that was running at the time

o Details of any recent changes made to settings, row, or column selections

o Whether you were using new data, or data that you had successfully used
  before

o Whether the data was held on your workstation or was imported from somewhere
  else
In addition, if the problem occurred while an object was accessing a database,
check whether the problem was caused by the database by referring to the
appropriate database manual.

Try to reproduce the error. This is important, because it helps you to
determine the cause of the problem and also helps the Visualizer support staff
if you need to submit a defect report.


ΓòÉΓòÉΓòÉ 16.1.1. Messages FTB4421, FTB4600, and FTB4801 ΓòÉΓòÉΓòÉ

Visualizer may issue one of these messages if your workstation has insufficient
free hard disk space. Check that free space is available so that the
SWAPPER.DAT file can expand.

If there is insufficient free space on the drive on which the SWAPPER.DAT file
is located, move it to another drive or move other files to free some space.
Try to make sure that the SWAPPER.DAT file is not located on the same disk as
the print spool file or the Visualizer temporary files.

If there is sufficient free disk space on the SWAPPER.DAT drive, the problem
you have encountered is likely to be within Visualizer itself. In this case,
you or your local service personnel should report the problem to IBM using the
procedure detailed in Reporting defects to IBM.


ΓòÉΓòÉΓòÉ 16.2. The Visualizer runtime log files ΓòÉΓòÉΓòÉ

Visualizer can produce several log files that may be used as diagnostic aids
for problems that are encountered when running Visualizer. Some logs are
created automatically, other logs are created only when specified. This section
describes the logs and explains how to produce them.

The logs are stored in the Work folder in the Visualizer folder.


ΓòÉΓòÉΓòÉ 16.2.1. The Visualizer install logs ΓòÉΓòÉΓòÉ

During installation, any messages that are displayed are also saved in the
FTBERROR.LOG file. This file is located on the boot drive of the workstation
you are installing from.

During an install or delete operation, the installer cleans up any SQL
Database, SQL Table, and SQL View objects found on the workstation. The
FTBDIN.LOG file records this information.


ΓòÉΓòÉΓòÉ 16.2.2. The Visualizer message log ΓòÉΓòÉΓòÉ

While it is running, Visualizer automatically logs any messages in the FTBLOG
file. The log is a useful source of information when you are trying to find the
cause of a problem. However, because the oldest information in the log is lost
when the log exceeds 16KB, save a copy of it as soon as possible after a
problem has occurred.

Finding the message log

FTBLOG is located in the directory identified by the SET FTB1DIR statement in
the CONFIG.SYS file. To identify the FTB1DIR directory name, either type SET at
an OS/2 command prompt, or look in the CONFIG.SYS file.

Accessing the message log

A Visualizer object continues to generate messages until it is closed.
Therefore, to ensure that the message log is complete, close all your
Visualizer objects, then copy the log files using the OS/2 COPY command.

Browsing the message log

Each log entry starts with a time-stamp record that indicates when an event
occurred. The time stamp is followed by such information as printer parameters,
values of internal variables, and message numbers.

The log can also contain additional error messages that were not displayed.
This is because Visualizer reduces the number of messages shown by not
displaying all its system-level messages.

Normally, each message contains a reference to the name and class of the
failing object. The object classes include:

IBMAPPLICATN        Used by development applications

IBMCHART            Used by charts

IBMPLAN             Used by plans

IBMREPORT           Used by reports

IBMQUERY            Used by queries

IBMSQLSTATEMENT     Used by SQL statements

IBMSTATS            Used by statistics

IBMSQLTABLE         Used by SQL objects

IBMTABLE            Used by product tables


ΓòÉΓòÉΓòÉ 16.2.3. The SQL database log ΓòÉΓòÉΓòÉ

Whenever an SQL database, SQL table, or SQL view object is used, Visualizer
updates the FTBTRACE.LOG file. It records significant system events, unusual or
abnormal conditions and system errors. The file is created automatically and
continues to grow until deleted. It can be deleted at any time.

Object tracing

FTBTRACE.LOG can also be used to trace activity of Visualizer components.
However, because this facility is intended to help IBM identify the source of
defects within Visualizer, only use FTBTRACE.LOG in this way when asked to do
so by an IBM Support representative.

To activate an object trace, follow these steps:

 1. At an OS/2 command prompt, type:

        ftbtrflg

    Then press Enter.

    The current FTBTRACE.LOG trace settings are displayed.

 2. At the command prompt, type the letter that identifies the component to be
    traced, then press Enter.

    The type of tracing information is displayed.

    There are two types of trace entry:

   Entry/Exit    Is used to trace the flow of control into and out of
                 procedures and methods

   Other         Is used as a progress indicator through a procedure or method

    Use the Both choice to specify both Entry/Exit and Other tracing.

 3. At the command prompt, type the number that identifies the tracing required
    for that component, then press Enter.

 4. Repeat steps 2 through 3 for each component you want to trace.

 5. When you have specified all the components to be traced, type:

        E

    Then press Enter.


ΓòÉΓòÉΓòÉ 16.2.4. Other diagnostic aids ΓòÉΓòÉΓòÉ

Visualizer also contains other specialized diagnostic aids. When necessary, you
may be asked to use them to collect more detailed information about a problem.

A set of tracing options can be specified when starting an object from the OS/2
command prompt. Each diagnostic applies to a different part of Visualizer. If
necessary, IBM will identify what trace information is required and give
instructions on how to send the information to IBM for analysis.

To open a Visualizer object with a trace option switched on, at an OS/2 command
prompt, enter:

FTBAS3 /Cclass /Nname trace

where:

class  Specifies the class of the object that is failing

name   Specifies the location and name of the object that is failing

trace  Specifies the type of trace required:

   DATATRACE     Creates the FTBSQL and FTBAS400 files

   DDETRACE      Creates the FTBDDE file

   DRGTRACE      Creates the FTBDRG file

   HOSTTRACE     Creates the DASTRACE file in the FTB1DIR directory and log
                 files on the host system

For example, to create the DDETRACE file for a report called MYREPORT.REP, at a
command prompt, type:

FTBAS3 /CIBMREPORT /NC:\DESKTOP\MYREPORT.REP DDETRACE

Then press Enter.


ΓòÉΓòÉΓòÉ 16.3. SYS3xxx errors ΓòÉΓòÉΓòÉ

If a SYS3xxx error occurs while you are running a user-written application, the
system error may originate with that application. In this case, report the
error to the developer of the application.

If a SYS3xxx error occurs when you are using a Visualizer object, report the
error to IBM as the problem probably lies within Visualizer or an OS/2 service
used by Visualizer.

If you get a SYS3xxx error, always record the system error information, because
it may help to determine the cause of the problem. To obtain the system error
information:

 1. Select Display register information in the System Error window

 2. Select OK.

    The register information is displayed in a window.

 3. As a minimum, record the following information:

   o The window title
   o The message number and text of the message
   o The keyword and characters following each of:

      CS:EIP=
      SSLIM=
      CSLIM=


ΓòÉΓòÉΓòÉ 16.4. Database problems ΓòÉΓòÉΓòÉ

For problems related to:

o SQL databases
o AS connections
o OS/400 data using PC Support/400, or
o Other data types

read the appropriate sections of Overview of data sources. through Accessing
AS/400 databases.


ΓòÉΓòÉΓòÉ 16.5. Problems with metafiles, picture viewer, and printing ΓòÉΓòÉΓòÉ

Some versions of First Failure Support Technology/2* (FFST/2*) may cause
problems if:

o You use Visualizer graphics in OS/2 metafile format with the OS/2 Picture
  Viewer

o You save or print metafiles from Visualizer

To overcome problems of empty or invalid files metafiles being created:

 1. Edit the CONFIG.SYS file and comment out the RUN=...\EPW.EXE statement.

    For example, change RUN=D:\OS2\EPW.EXE to REM RUN=D:\OS2\EPW.EXE.

 2. Edit the STARTUP.CMD file and add the statement:

        DETACH EPW.EXE

    As the first line in STARTUP.CMD.

 3. Shut down and restart the workstation.


ΓòÉΓòÉΓòÉ 16.6. Text missing from a printed report ΓòÉΓòÉΓòÉ

Some printer drivers have font settings that must be deselected when printing
objects, such as Reports for OS/2, that use graphics. If reports that are
displayed correctly on screen are printed with missing rows of text, open the
Printer Properties window of the printer used to print the report and check
whether the selected printer settings support graphic output.

For more information on the settings, refer to the help on the Printer
Properties window or the printer documentation.


ΓòÉΓòÉΓòÉ 17. Reporting defects to IBM ΓòÉΓòÉΓòÉ

This chapter describes how to report a defect in Visualizer to IBM.

Isolating problems

When you find a problem in Visualizer, first check that your workstation has
the latest level of corrective service. For information on how to check the
Visualizer service level, see For information on how to check the OS/2 service
level, see You can find news of PTFs on the VISUALIZ forum of Talklink and the
Visualizer forum on CompuServe** (see or through your local IBM representative.

See for more information about applying corrective service.

If you have installed the latest corrective service and still have the problem,
try to reproduce it using the samples that are provided with the product. By
describing the defect in terms of these samples, you help eliminate any
dependency on your own data. This simplifies the process of problem
determination. Try to reproduce the problem without running other, unnecessary,
applications.

If co-workers use Visualizer, check whether they can reproduce the problem
using the information that you have recorded. If they cannot reproduce it, try
to provide additional information that enables them to do so.


ΓòÉΓòÉΓòÉ 17.1. Reporting a defect ΓòÉΓòÉΓòÉ

If you cannot resolve a problem and believe that it is caused by a defect
within Visualizer itself, complete the defect report form (see Defect report
form) and then contact your IBM service organization. For details of the
customer support available in your country, see the service document included
in the Visualizer package, or contact your IBM representative.

When you mail or fax details of the defect to IBM, include a copy of the
appropriate log entries and the completed defect report form.

When you report a defect, IBM service staff check whether that defect has
already been identified. If a correction is being developed, or if a correction
is already available, it can be sent to you.

If the defect you are reporting has not been reported before, the IBM service
staff attempt to reproduce it. To reproduce the defect, your software
environment, and sometimes your hardware environment, may need to be
duplicated. Therefore, when you report a problem, make sure that you provide
enough information to enable the IBM staff to reproduce the problem.

Always provide the Visualizer, DB2/2, and OS/2 product service levels. If the
problem occurs during printing, include full details of the printer driver type
and version, and any appropriate information about printer settings.

If error messages were issued, provide the FTBLOG and FTBTRACE.LOG files. Also,
if system messages were issued, provide the information detailed in this
chapter.


ΓòÉΓòÉΓòÉ 17.2. Determining Visualizer service levels ΓòÉΓòÉΓòÉ

Each time your Visualizer system is updated, the service level that you have
applied is recorded on your system. There is a unique service level for each
PTF.

When you report a problem to IBM, always include details of the service levels
of each Visualizer product installed at the time the problem occurred.

To find the service level of an installed Visualizer product:

 1. Open the Installation and Support program from the Utilities folder in the
    Visualizer folder.

 2. Select the View menu.

 3. Select Installed Products.

 4. Select the Product Description in the window.

 5. Select the Details menu.

 6. Select Product Status.

 7. Select the appropriate component.

 8. Select Service Level.

    The install date, origin, and service level information is displayed.

The service level is a 6-character string, for example, GBA48A.

The format of the service level is as follows:

Character 1    C    Corrective service

               G    Packed shipment release code

               T    Test level of corrective service

Character 2    B    Query for OS/2

               C    Charts for OS/2

               D    Development for OS/2

               W    Plans for OS/2

               P    Procedures for OS/2

               S    Statistics for OS/2

               V    Ultimedia Query for OS/2

Character 3    Modification level of the code. This character depends on the
               version, release, and modification level of the Visualizer
               product.

Character 4    The year of the release of the code, for example: 1 (1991), 2
               (1992).

Character 5    The month of the planned release of the code (1 through 9 for
               January through September and A for October, B for November, and
               C for December).

Character 6    The order of the diskette package or shipment within the month
               if two or more are issued in the same month, for example, A, B,
               C.


ΓòÉΓòÉΓòÉ 17.3. Determining OS/2 service levels ΓòÉΓòÉΓòÉ

To determine the service level of your operating system, at any OS/2 command
prompt, type:

syslevel

Then press Enter.

Check that your OS/2 system levels conform to those required by Visualizer (see
Preparing to install Visualizer products for more information).


ΓòÉΓòÉΓòÉ 17.4. Receiving program temporary fixes ΓòÉΓòÉΓòÉ

Program temporary fixes (PTFs) are used to update Visualizer. They are
distributed on corrective service diskettes (CSDs). The READ.ME file, which is
provided on the CSDs, includes details of the corrected problems and any
enhancement features. Each corrective service for a product level includes all
the fixes that were on previous CSDs for that release of the product.

Corrective service for Visualizer products is available from IBM until their
announced end of service date. Contact your local IBM representative for
details of how to obtain corrective service in your country.


ΓòÉΓòÉΓòÉ 18. Updating Visualizer products ΓòÉΓòÉΓòÉ

When you report a defect, IBM checks whether that defect has already been
identified. If a correction is being developed, or if a correction is already
available, it can be sent to you as a program temporary fix (PTF) on Corrective
Service Diskettes (CSDs).

This chapter explains how to update Visualizer with a PTF.


ΓòÉΓòÉΓòÉ 18.1. Preparing to update Visualizer products ΓòÉΓòÉΓòÉ

Program temporary fixes contain modifications to Visualizer products.

Before you install a PTF:

 1. Read the instructions contained in the READ.ME file on diskette 1 of the
    corrective service diskette.

    PTFs are issued separately for each Visualizer product. However, it may be
    necessary to apply corresponding PTFs to more than one product. For
    example, before a PTF is applied to an optional product, you may also have
    to apply a PTF to Query for OS/2.

    If you have installed a Visualizer product in more than one language, PTFs
    must be applied to each language version of the product.

 2. Use the Visualizer Installing and Supporting utility to review the current
    service level details of your installed Visualizer products. See
    Determining Visualizer service levels, for more information.

 3. Before you apply a PTF, make sure that Visualizer is not in use.

    If you are applying a PTF to a LAN installation, instruct all requesters to
    stop using Visualizer and its optional products, then remove their access
    to the products on the LAN server. If you installed Visualizer onto a
    server from a remote workstation, apply the PTF using the same remote
    workstation.

    Install the PTF on the LAN server and ensure any corresponding PTF level is
    applied to the products on LAN requesters.


ΓòÉΓòÉΓòÉ 18.2. Applying PTFs ΓòÉΓòÉΓòÉ

To apply PTFs to Visualizer or any of the optional Visualizer products:

 1. Close all Visualizer objects.

 2. Insert the first corrective service diskette into the diskette drive.

 3. Open the Visualizer Installing and Supporting utility. On standalone and
    LAN requester installations, the utility is in the Utilities folder in the
    Visualizer folder. On a LAN server installation, the utility is in the
    Installing and Supporting folder on the desktop.

 4. From the File menu, select Catalog, then select Drive... from the cascade
    menu.

    The Open Drive Catalog window is displayed.

 5. In the Drive field, type A.

 6. In the Filename field, enter the name of the file that contains the PTF.
    The following file naming convention is used for Visualizer PTFs:

   Product                       PTF file
   Charts for OS/2               FTBICAT.ICF
   Development for OS/2          FTDICAT.ICF
   Procedures for OS/2           FTPICAT.ICF
   Plans for OS/2                FTWICAT.ICF
   Query for OS/2                FTBICAT.ICF
   Statistics for OS/2           FTSICAT.ICF
   Ultimedia Query for OS/2      FTVICAT.ICF

 7. Select the Open push button.

    The Installation and Maintenance window is displayed.

 8. From the View menu, select Current catalog.

 9. Select the Visualizer product you want to update.

    If more than one language version of the product is installed on the
    workstation, all language versions of the product are updated.

10. From the Action menu, select Update.

    If you chose to keep a backup version of the files replaced by the update,
    ensure that you have sufficient disk space.

    The Progress window is displayed while the files are being updated.

11. Close the installation program.

12. If you apply a PTF to a LAN server, restore LAN requester access to the
    network resource.

You may need to apply the PTF to all LAN requester installations that have
access to a serviced LAN server installation. For confirmation, check the file
containing details of the PTF.


ΓòÉΓòÉΓòÉ 18.3. Removing PTFs ΓòÉΓòÉΓòÉ

If you keep a backup when you install a PTF, you can also remove it.

To remove a PTF:

 1. Open the Visualizer Installing and Supporting utility. For standalone and
    LAN requester installations, the utility is kept in the Utilities folder in
    the Visualizer folder. For a LAN server installation, the utility is in the
    Installing and Supporting folder on the desktop.

 2. From the View menu, select Updated products.

    Products that have had service applied are listed.

 3. Select the products you want to restore.

 4. From the Actions menu, select Restore.

    The Progress window is displayed while the files are being restored.

    When the restore is complete, a message is displayed.

 5. Close the installation program.


ΓòÉΓòÉΓòÉ 19. Optional product install parameters ΓòÉΓòÉΓòÉ

This appendix lists the COMP and Product name install parameters for the
Visualizer optional products. For more details on how to automate the
installation of Visualizer products, see Automating Visualizer installation.

Charts for OS/2

COMP parameters

o Charts for OS/2 (English)
o Charts for OS/2 Samples (English)
o Charts for OS/2 Manual (English)
o Charts for OS/2 Tutorials (English)

Product name parameters

o Charts for OS/2 (Standalone)
o Charts for OS/2 (Server)
o Charts for OS/2 (Requester)
o Charts for OS/2 (English Distribution Copy)

Development for OS/2

COMP parameters

o Development for OS/2 (English)
o Development for OS/2 Samples (English)
o Development for OS/2 Manuals (English)

Product name parameters

o Development for OS/2 (Standalone)
o Development for OS/2 (Server)
o Development for OS/2 (Requester)
o Development for OS/2 (English Distribution Copy)

Plans for OS/2

COMP parameters

o Plans for OS/2 (English)
o Plans for OS/2 Samples (English)
o Plans for OS/2 Manual (English)

Product name parameters

o Plans for OS/2 (Standalone)
o Plans for OS/2 (Server)
o Plans for OS/2 (Requester)
o Plans for OS/2 (English Distribution Copy)

Procedures for OS/2

COMP parameters

o Procedures for OS/2 (English)
o Procedures for OS/2 Samples (English)
o Procedures for OS/2 Manual (English)

Product name parameters

o Procedures for OS/2 (Standalone)
o Procedures for OS/2 (Server)
o Procedures for OS/2 (Requester)
o Procedures for OS/2 (English Distribution Copy)

Statistics for OS/2

COMP parameters

o Statistics for OS/2 (English)
o Statistics for OS/2 Samples (English)
o Statistics for OS/2 Manual (English)

Product name parameters

o Statistics for OS/2 (Standalone)
o Statistics for OS/2 (Server)
o Statistics for OS/2 (Requester)
o Statistics for OS/2 (English Distribution Copy)

Ultimedia Query for OS/2

COMP parameters

o Ultimedia Query for OS/2
o Ultimedia Query for OS/2 8-bit Scapes Catalog
o Ultimedia Query for OS/2 8-bit Images for Scapes Catalog
o Ultimedia Query for OS/2 24-bit Scapes4 Catalog
o Ultimedia Query for OS/2 8-bit Images for Scapes4 Catalog

Product name parameters

o Ultimedia Query for OS/2 (Standalone)
o Ultimedia Query for OS/2 (Server)
o Ultimedia Query for OS/2 (Requester)
o Ultimedia Query for OS/2 (English Distribution Copy)


ΓòÉΓòÉΓòÉ 20. Optimizing Visualizer performance ΓòÉΓòÉΓòÉ

This appendix details changes you can make to your workstation to improve the
performance of Visualizer products. Remember that changes to the CONFIG.SYS
file only take effect after you have shut down and restarted your workstation.

You are recommended to make a backup copy of your CONFIG.SYS file before making
any of these changes.


ΓòÉΓòÉΓòÉ 20.1. Setting the disk cache size ΓòÉΓòÉΓòÉ

The optimum disk cache size depends on the amount of memory fitted to your
workstation. If the workstation has less than 16MB of memory, set the disk
cache size to 10% of the total memory size. If the workstation has 16MB of
memory or more, set the disk cache size to 2048KB.


ΓòÉΓòÉΓòÉ 20.1.1. HPFS file systems ΓòÉΓòÉΓòÉ

On workstations that use the HPFS file system, the cache size is specified by
the IFS statement.

If your workstation has 16MB of memory or more, edit your CONFIG.SYS file and
set the cache parameter of the IFS statement to 2048. For example:

IFS=C:\OS2\HPFS.IFS /CACHE:2048 /CRECL:4...

If your workstation has less than 16MB of memory, edit your CONFIG.SYS file and
remove the cache parameter from the IFS statement. For example:

IFS=C:\OS2\HPFS.IFS /CRECL:4...

OS/2 automatically allocates 10% of memory to the disk cache if no cache
parameter is specified.


ΓòÉΓòÉΓòÉ 20.1.2. FAT file systems ΓòÉΓòÉΓòÉ

On workstations that use the FAT file system, the cache size is specified by
the DISKCACHE statement.

If your workstation has 16MB of memory or more, edit your CONFIG.SYS file and
set the value immediately after the DISKCACHE statement to 2048. For example:

DISKCACHE=2048,LW,128,AC:E

If your workstation has less than 16MB of memory, edit your CONFIG.SYS file and
set the value immediately after the DISKCACHE statement to 10% (rounded to the
nearest multiple of 64) of the workstation memory size. For example, if there
is 4MB of memory on your workstation specify:

DISKCACHE=440,LW,...


ΓòÉΓòÉΓòÉ 20.1.3. General improvements ΓòÉΓòÉΓòÉ

If your workstation uses only the HPFS file system, delete the DISKCACHE
statement from your CONFIG.SYS file.

If your workstation uses only the FAT file system, edit your CONFIG.SYS file
and delete the IFS statement that refers to the boot drive.

If your workstation uses both the HPFS file and FAT file systems, both the IFS
and DISKCACHE statements are necessary. To ensure optimum performance, check
that the combined cache sizes do not exceed 2048KB or 10% of workstation
memory, as appropriate.

If you change the IFS or DISKCACHE statements, change the BUFFERS statement to:

BUFFERS=10

If your CONFIG.SYS file contains the following statement:

BASEDEV=IBM2SCSI.ADD

change it to:

BASEDEV=IBM2SCSI.ADD /GS:9

Similarly, if your CONFIG.SYS file contains the following statement:

BASEDEV=IBM2SCSI.ADD /LED

change it to:

BASEDEV=IBM2SCSI.ADD /LED /GS:9

Use the CHKDSK command to find out what type of file system is used on a disk.


ΓòÉΓòÉΓòÉ 20.2. Optimizing the SWAPPER.DAT file ΓòÉΓòÉΓòÉ

By default, OS/2 places the SWAPPER.DAT file in the C:\OS/2\SYSTEM directory.
Its optimal location is in the root directory of the most used partition of the
least used hard disk drive.

If your workstation has only one hard disk drive, make sure that the
SWAPPER.DAT file is located in the same partition as Query for OS/2. If you
have two hard disk drives, make sure that OS/2 and Query for OS/2 are on
different hard disks and that the SWAPPER.DAT file is in the root directory of
the OS/2 partition.

Try to make sure that your SWAPPER.DAT file is sufficiently large to cope with
your normal workload without having to expand. To specify the size of your
SWAPPER.DAT:

 1. Start all the applications that you use concurrently.

 2. Use the DIR command to see how large the SWAPPER.DAT has become.

 3. Edit your CONFIG.SYS file and modify the SWAPPATH statement.

    For example, to specify that a warning is displayed when there is less than
    4MB of memory available and that SWAPPER.DAT has a minimum size of 20MB,
    change the SWAPPATH statement to:

        SWAPPATH=x:\ 4096 20480

    where x is the disk drive where the SWAPPER.DAT is located.

Specifying a minimum size of 20MB for your SWAPPER.DAT is a good starting point
for workstations with up to 16MB of memory. However, check that there is
sufficient free space available before doing this.


ΓòÉΓòÉΓòÉ 20.3. Optimizing startup times ΓòÉΓòÉΓòÉ

When all Visualizer objects have been closed, the object startup component of
Visualizer continues to run for 30 minutes. During this period, the time taken
to open a Visualizer object is reduced.

The length of time that the component remains active can be set by changing the
FTB1PRELOAD environment variable in the CONFIG.SYS file. Therefore, if you open
Visualizer objects infrequently, you can reduce the time taken to open them by
setting FTB1PRELOAD to a large value.

For example, to specify that the startup component will remain active for 45
minutes after the last Visualizer object has been closed, edit your CONFIG.SYS
file and change the FTB1PRELOAD variable to:

SET FTB1PRELOAD=45

Alternatively, if you specify FTB1PRELOAD=0, the Visualizer startup component
is unloaded from memory as soon as the last Visualizer object is closed. You
may want to do this if your workstation is short of memory, or if you access
the Visualizer code from a LAN Server and need to release the LAN Server drive
containing the Visualizer code.


ΓòÉΓòÉΓòÉ 21. Deleting Visualizer in case of unrecoverable installation errors ΓòÉΓòÉΓòÉ

This appendix describes what to do if you encounter an unrecoverable error
while you are installing or deleting standalone or LAN requester versions of
Visualizer products.

To restore your system to the state it was in before you installed the
Visualizer product:

 1. Delete any files in the \INSTTEMP.FTB directory.

    During installation, Visualizer creates a number of temporary files. If the
    Visualizer installation process does not complete successfully, these files
    may remain undeleted.

 2. Insert the first Visualizer diskette into your diskette drive.

 3. To delete all references to installed Visualizer products from the OS2.INI
    and EPFIS.INI files, at an OS/2 command prompt, type:

        a:\FTBSETUP

    When FTBSETUP finishes, a message is displayed informing you whether you
    need to shutdown and restart the workstation.

 4. If necessary, shutdown and restart the workstation.

If you were installing a Visualizer product, you can now restart the
installation procedure.

To completely remove Visualizer from your workstation, continue with the
following steps:

 1. Replace the CONFIG.SYS file with the CONFIG.ORG backup file. (The install
    program automatically creates CONFIG.ORG in the WORK subdirectory of the
    installation directory).

 2. If the workstation has a STARTUP.CMD file, the installer may have created a
    backup copy of it. If there is a STARTUP.CMD file in the TMPDEFER
    directory, replace the workstation's STARTUP.CMD file with this backup
    file.

 3. Delete all Visualizer templates from the OS/2 directory.

 4. Delete all the files from the directory on which you installed Visualizer.


ΓòÉΓòÉΓòÉ 22. Communicating with other Visualizer users ΓòÉΓòÉΓòÉ

This appendix explains how you can exchange ideas and information about
Visualizer products.

Talklink

A VISUALIZ Bulletin Board is available on the IBM TalkLink service in the
U.S.A. For details of TalkLink fees and access information, call 1-800-547-1283
from within the U.S.A., or [phone] from outside the U.S.A.
Alternatively, you can write to:

Talklink
IBM Corporation
PO Box 2150
Atlanta
GA 30301-9949
U.S.A.

This bulletin board enables Visualizer users to exchange ideas about
Visualizer. It is also available to IBM employees, including those from the
Visualizer developers.

In addition to normal IBM information channels, the bulletin board includes
details of corrective service for available Visualizer products.

CompuServe

If you have access to CompuServe, you can write directly to the Visualizer
section maintained by the Warwick Software Development Laboratory.

To do this, connect to CompuServe, GO IBMDB2, and look for the Visualizer
section.


ΓòÉΓòÉΓòÉ 23. Requesting enhancements ΓòÉΓòÉΓòÉ

The Visualizer developers and support personnel want to learn how you believe
the Visualizer products might be enhanced.

You can submit an enhancement request by fax or mail, using a copy of the
Visualizer Enhancement Request form on the next page. If you do so, the
laboratory staff will respond to you. However, IBM cannot guarantee that any
request submitted will be included in any future level of the product.

Summarize the enhancement or the problem that you are trying to overcome in the
Abstract section. Try to make the Abstract suitable for a keyword search. State
the problem you want to overcome, rather than a particular solution.


ΓòÉΓòÉΓòÉ 23.1. Visualizer enhancement request form ΓòÉΓòÉΓòÉ


Name       ____________________________________________________

Company    ____________________________________________________

Address    ____________________________________________________

           ____________________________________________________

           ____________________________________________________

           ____________________________________________________

Telephone  ____________________________________________________

Electronic Mail  ______________________________________________

Abstract   ____________________________________________________

           ____________________________________________________

Enhancement description  ______________________________________

           ____________________________________________________

           ____________________________________________________

           ____________________________________________________

What do you want to achieve with the enhancement?

           ____________________________________________________

           ____________________________________________________

           ____________________________________________________

           ____________________________________________________

           ____________________________________________________


ΓòÉΓòÉΓòÉ 24. Defect report form ΓòÉΓòÉΓòÉ

Always complete a defect report form before you contact IBM. Edit a copy of the
Defect Report Form (FTB1FORM.TXT) The form is in the Work folder in the
Visualizer folder.

The form is designed to help you to record sufficient information for IBM to
reproduce your problem. Here are some suggestions:

o Give as much information as possible.

o If you do not know or are unsure of the information, reply don't know.

o If you have extra information or information not covered by the form, include
  it on a separate sheet.


ΓòÉΓòÉΓòÉ 25. Data conversions ΓòÉΓòÉΓòÉ

With Visualizer, you can access SQL data, AS/400 data, Visualizer tables, and
other sources. When you convert data from one source to another, the data is
stored differently, depending on the format of the source. This appendix
describes what happens to data types, primary keys, and columns when you
convert:

o Visualizer tables to SQL data
o SQL data to Visualizer tables
o Visualizer tables to AS/400 data
o AS/400 data to Visualizer tables


ΓòÉΓòÉΓòÉ 25.1. Visualizer table and SQL table conversions ΓòÉΓòÉΓòÉ

SQL tables and Visualizer Visualizer tables store data differently. This
section describes the differences in data types and how primary keys are used.

SQL data type                      Visualizer table data type
INTEGER                            Numeric
SMALLINT                           Numeric
FLOAT                              Numeric
DECIMAL                            Numeric
NUMERIC                            Numeric
CHAR                               Character
VARCHAR                            Character
LONGVARCHAR                        Character
TIMESTAMP                          Character
DATE                               Date
TIME                               Time
GRAPHIC                            Graphic
VARGRAPHIC                         Graphic
LONGVARGRAPHIC                     Graphic

Visualizer table data type    SQL data type
Character                     VARCHAR
Numeric                       FLOAT
Date                          DATE
Time                          TIME
Graphic                       VARGRAPHIC

Character columns in Visualizer tables can be up to 254 characters in length.
Data from Character(Variable) columns longer than 254 characters is truncated
and lost when it is transferred to Visualizer tables.

When a new SQL table is created from a Visualizer table, Character(Variable)
columns are created to hold the character data columns from the Visualizer
table.

Numbers within Visualizer tables are held in floating-point form with an
accuracy of 15 digits. When a new SQL table is created from a Visualizer table,
Scientific Notation columns are created to hold the numeric columns from the
Visualizer table. Decimal column types are not created.

Date and Time columns from Visualizer tables are transferred to equivalent
column type and vice versa. The System date and time column type is not
supported by Visualizer tables.


ΓòÉΓòÉΓòÉ 25.1.1. Primary keys ΓòÉΓòÉΓòÉ

When an SQL table is imported into a Visualizer table, the columns in the SQL
table's primary key become the new key columns for the Visualizer table. If the
SQL table has no primary key, Visualizer creates an additional Key column in
the Visualizer table to maintain the row order. Regardless of whether or not
you change the data, if you export this Visualizer table back to the same SQL
table, you must delete the Key column added by Visualizer and assign at least
one of the original columns as the primary key that defines the row order. When
a new SQL table is created by exporting a Visualizer table, no primary key is
defined for the SQL table.


ΓòÉΓòÉΓòÉ 25.2. Visualizer table and AS/400 conversions ΓòÉΓòÉΓòÉ

AS/400 data is stored differently from Visualizer tables. This section
describes how the differences in data types and columns are handled.


ΓòÉΓòÉΓòÉ 25.2.1. Data types ΓòÉΓòÉΓòÉ

AS/400 data type              Visualizer table type
P    Packed decimal           Numeric
S    Zoned decimal            Numeric
B    Binary                   Numeric
F    Floating-point           Not supported by PC Support/400
A    Character                Character
H    Hexadecimal              Character
L    Date                     Character
T    Time                     Character
Z    Timestamp                Character
J    DBCS-Only                Graphic
E    DBCS-Either              Graphic
O    DBCS-Open                Graphic

Visualizer table type         AS/400 data type
Character                     A    Character
Numeric                       P    Packed decimal
Date                          A    Character
Time                          A    Character
Graphic                       J    DBCS-Only


ΓòÉΓòÉΓòÉ 25.2.2. Columns ΓòÉΓòÉΓòÉ

Character columns on AS/400 can be very wide. For Visualizer tables, the
largest number of characters in any one column is 254. If the column of
characters on the AS/400 is larger than the Visualizer maximum, only the first
254 characters of each column value will be transferred to the Visualizer
table.

Hexadecimal columns on the AS/400 are transferred to Character columns in
Visualizer tables. The resulting column will not be formatted.

Numbers within Visualizer tables are held in floating-point with an accuracy of
15 digits. When numbers of a higher accuracy are transferred from AS/400, the
numbers are rounded. When numeric data is transferred to an existing table
column on the AS/400, the data type of the AS/400 column is retained.

If the AS/400 column data type is too small to hold the values from the column
in the Visualizer table, the data is not transferred and a message is issued.
When a new AS/400 table is created, the numeric columns are transferred to the
AS/400 as packed decimals. However, if the numbers in the Visualizer table
exceed 31 digits, a character column will be created on the AS/400 to hold the
values.


ΓòÉΓòÉΓòÉ 25.2.2.1. Column names ΓòÉΓòÉΓòÉ

Column names on the AS/400 can be up to 10 characters long. Column names in
Visualizer tables can be up to 20 characters long. When data is transferred
from AS/400 to a Visualizer table, all column names are transferred without
changes. When data is transferred from Visualizer to the AS/400, any column
names longer than 10 characters are truncated. If this creates duplicate column
names, Visualizer adds a unique number to the end of each duplicate column
name.


ΓòÉΓòÉΓòÉ 25.2.2.2. Number of columns ΓòÉΓòÉΓòÉ

The PC Support/400 limit for the number of columns is 256 (for PC Support/400
Release 2 and Release 3). This limit means that when you import data from the
AS/400 using PC Support/400, an error occurs, and the data is not transferred
to the Visualizer table. To avoid this problem, create a view of the AS/400
data-a subset of the data with 256 or fewer columns.


ΓòÉΓòÉΓòÉ 25.2.2.3. ASCII to EBCDIC sort orders ΓòÉΓòÉΓòÉ

You should note the differences in the sort sequences between ASCII and EBCDIC.
Visualizer table data is held in the ASCII sort sequence, and AS/400 data is
held in the EBCDIC sort sequence. As a result, data transfer between Visualizer
tables and the AS/400 may give unexpected results.


ΓòÉΓòÉΓòÉ 26. The Database Binder object ΓòÉΓòÉΓòÉ

When you use Visualizer to access a database that has not previously been
bound, it attempts to bind to the database automatically. However, binding will
be successful only when the user has administrator authority on that database.

To enable all Visualizer users to access a shared database, the Database Binder
object must be invoked manually from the Visualizer utilities folder by a user
with database administrator authority.

The Database Binder object performs the following actions:

 1. Creates views on system catalog tables used by Visualizer objects.

 2. Binds Visualizer bind files to create database packages.

 3. Grants PUBLIC EXECUTE authority on database packages.

 4. Grants PUBLIC SELECT authority on the views created.


ΓòÉΓòÉΓòÉ 26.1. Database views created by Visualizer ΓòÉΓòÉΓòÉ

Views are created using the following definitions.

The Database Binder object will not fail if it is unable to create these views.
Therefore, if you want to limit the list of tables that are made available to
Visualizer users, create views of the required definition before running the
binder. When doing this, take care to ensure that the column structure of the
views is the same as those listed below.

For DB2/VM & VSE (SQL/DS)

CREATE VIEW FTBADM.TABLES
          (NAME,CREATOR,TYPE,COLCOUNT,CARD,REMARKS) AS
          AS SELECT TNAME,CREATOR,''T'',NCOLS,ROWCOUNT,REMARKS FROM
          SYSTEM.SYSCATALOG

CREATE VIEW FTBADM.COLUMNS
         (TBCREATOR,TBNAME,NAME,COLTYPE,KEYSEQ,COLNO,REMARKS)
         AS SELECT CREATOR,TNAME,CNAME,COLTYPE,0,
         COLNO,REMARKS FROM SYSTEM.SYSCOLUMNS

For DB2/2, DB2/6000, or DB2

CREATE VIEW FTBADM.TABLES
          (NAME,CREATOR,TYPE,COLCOUNT,CARD,REMARKS) AS
          SELECT NAME,CREATOR,TYPE,COLCOUNT,CARD,REMARKS FROM
          SYSIBM.SYSTABLES

CREATE VIEW FTBADM.COLUMNS
          (TBCREATOR,TBNAME,NAME,COLTYPE,KEYSEQ,COLNO,REMARKS)
          AS SELECT
          TBCREATOR,TBNAME,NAME,COLTYPE,KEYSEQ,COLNO,REMARKS
          FROM SYSIBM.SYSCOLUMNS


ΓòÉΓòÉΓòÉ 26.2. Visualizer Packages ΓòÉΓòÉΓòÉ

This section lists the bind files used and the packages created. For all
databases

Bind files

o FTBSQUR.BND
o FTBSQCS.BND
o FTBSQRR.BND
o FTBSQL1.BND
o FTBQMOBJ.BND

Packages

o FTBADM.FTB101UR
o FTBADM.FTB102CS
o FTBADM.FTB103RR
o FTBADM.FTB100L1
o FTBADM.FTB100QM

For DB2

The bind files listed in FTBSDSN.LST are bound into the FTBADM collection. The
package names are:

o FTBADM.FTBDLTBL
o FTBADM.FTBDLCOL
o FTBADM.FTBDLPRI
o FTBADM.FTBDGTBL
o FTBADM.FTBDVIEW
o FTBADM.FTBDLIND
o FTBADM.FTBDLREL
o FTBADM.FTBSEXEC

For DB2/2 and DB2/6000

The bind files listed in FTBSSQL.LST are bound into the FTBADM collection. The
package names are:

o FTBADM.FTBSLTBL
o FTBADM.FTBSLCOL
o FTBADM.FTBSLPRI
o FTBADM.FTBSGTBL
o FTBADM.FTBSVIEW
o FTBADM.FTBSLIND
o FTBADM.FTBSLREL
o FTBADM.FTBSEXEC

For DB2/VM & VSE (SQL/DS)

The bind files listed in FTBSARI.LST are bound into the FTBADM collection. The
package names are:

o FTBADM.FTBALTBL
o FTBADM.FTBALCOL
o FTBADM.FTBALPRI
o FTBADM.FTBAGTBL
o FTBADM.FTBAVIEW
o FTBADM.FTBALIND
o FTBADM.FTBALREL
o FTBADM.FTBSEXEC

For AS/400 database

The bind files listed in FTBSQSQ.LST are bound into the FTBADM collection. The
package names are:

o FTBADM.FTBQLTBL
o FTBADM.FTBSEXEC