OS/2 Shareware BBS: Product/Product.zip/visquery.zip/FTBEXTRA.INF

OS/2 Help File | 1994-07-14 | 18KB | 488 lines

ΓòÉΓòÉΓòÉ 1. Important information for Visualizer Query for OS/2 ΓòÉΓòÉΓòÉ

This document contains important information on changes that have been made to
Visualizer Query for OS/2 since the manuals went to press. Ensure that you are
familiar with the contents of this document before you install Visualizer Query
for OS/2.


ΓòÉΓòÉΓòÉ 2. Database Samples and Personal AS V3 registration ΓòÉΓòÉΓòÉ

When installing Visualizer Query for OS/2 on a system, note that the Database
Samples diskettes and the Personal AS V3 Registration diskette are not loaded
as part of the installation program.


ΓòÉΓòÉΓòÉ 3. Changes to the installation documentation ΓòÉΓòÉΓòÉ

The following section describes the changes and addenda to Visualizer Query for
OS/2: Installing and Supporting (SH45-5087-00) manual.

Chapter 1      Installing more than one language

               This is an addendum to the list, Changing the national language
               you are working in.

               The SQL Database, SQL Table, and SQL View objects do not reflect
               national language changes made to the Visualizer profile object
               until OS/2 is shutdown and restarted.

Chapter 6      Values for the product_name (/P) variable should contain an
               underscore (_). For example:

                              Query for OS/2 (Requester) should be
                              Query_for_OS/2_(Requester)

               The component names are as listed in the manual.

Chapter 7      Deleting DB2/2

               If you delete DB2/2 from a workstation where Visualizer Query
               for OS/2 is installed, shadows of SQL Database, SQL Table and
               SQL View objects can behave unpredictably. To avoid this
               problem, always delete any shadows of these objects before
               deleting DB2/2.

Chapter 8      Software requirements for accessing data

               This is an additional paragraph directly under the heading.

               The software versions and releases listed for the required
               products are the earliest releases required. Subsequent releases
               will also work.

Chapter 8      Software requirements for accessing data

               The following replaces the text for the Local databases list
               item.

               If you have DB2/2 with the standalone or the client with local
               databases options installed on your workstation, you can create
               and maintain local databases.

Chapter 9      Binding databases automatically

               The following replaces the text for the third item in the
               Database Binder list. The Database Binder grants EXECUTE
               privileges on the Visualizer packages to PUBLIC. If you do not
               want to have these privileges granted to PUBLIC, you can revoke
               them and then grant them selectively to appropriate users.

               Replace the text in the To bind databases automatically list.
               with the following:

               1. Open the Visualizer folder
               2. Open the Utilities folder
               3. Double-click on the Database Binder icon
               4. Select the appropriate databases from the displayed list
               5. Select Bind.

Chapter 15     Applying PTFs

               This is an addendum to list item 1.

               To apply a PTF, all Visualizer objects must be closed, and any
               Visualizer SQL Database, Visualizer SQL Table, or Visualizer SQL
               View objects must be asleep. To put an SQL object to sleep:

               1. Close the object.
               2. Move the object icon (and any shadows of the object) into a
               folder.
               3. Close the folder.

               Approximately 90 seconds after the folder is closed, its objects
               will go to sleep.

               Note:   The Visualizer folder often contains several of these
               objects, so the Visualizer folder must be closed before applying
               a PTF.

Appendix H     Visualizer Packages

               The Packages list should read:

               FTBADM.FTB100UR
               FTBADM.FTB100CS
               FTBADM.FTB100RR
               FTBADM.FTB100L1
               FTBADM.FTBQM01

               Ignore the phrase, into the FTBADM collection, in the sections
               referring to DB2/2, DB2/6000, DB2/VM, VSE, and AS/400.
               Collections only exist in DB2.


ΓòÉΓòÉΓòÉ 3.1. DB2/2 configuration parameters to support Visualizer ΓòÉΓòÉΓòÉ

In Chapter 9 of Visualizer Query for OS/2: Installing and Supporting, under the
heading Configuring DB/2 to support Visualizer, the following applies:

In Visualizer, most DB2/2 configuration parameters do not require additional
user analysis. However, because Visualizer generates database connections
implicitly, this section has been included to help you calculate the value of
the numrc parameter for your workstation.

To calculate the maximum number of connections generated between Visualizer
objects and remote databases, use the following rules:

o Database object

    1. The first database object with an opened icon or details view adds a
       connection to the database.
    2. Subsequent instances of database objects that use the same database do
       not add new connections.
    3. A connection to a database is not removed until all the database objects
       using that database have gone to sleep.

       Sleep is defined as shutting down the workstation, the folder containing
       the object having been closed for more than 90 seconds, or deleting the
       object. Closing an object view does not put the object to sleep.

o Enter SQL Window

    1. Each opened SQL Window causes a connection to the database.
    2. The connection to the database is dropped when the SQL Window is closed.

o Visualizer SQL Table Object

    1. The first instance of a Visualizer SQL Table object with applied
       settings changes causes a connection to the database that contains the
       table.
    2. Subsequent instances of different SQL Table objects in the same database
       do not add new connections.
    3. When all SQL Table objects that have applied definitional changes to the
       database have gone to sleep, the connection to a database is removed.

o Data Viewer

    1. Each opened Contents view of an SQL Table or SQL View causes a database
       connection.
    2. When the contents view is closed, the database connection is dropped.

o Query, Report, and SQL Statement

    1. Each open Query or Report that contains data from an SQL Table or SQL
       View, causes a connection to the database. Each opened SQL Statement,
       also cause a connection to the database.
    2. When the object is closed, its connection to the database is dropped.

When the number of database connections generated by Visualizer Query for OS/2
is known, base the numrc value on expected usage.

For a general user, the recommended default values for numrc are:

numrc - client 8, client with local databases 8

If you experience a problem with insufficient resources for connections when
using Visualizer (for example, SQL codes - 957, 30080), you can fix it by
closing Visualizer objects to release database connections, or by increasing
the value of the numrc parameter.

If you have a large number of connections, you may run out of communications
protocol resources (for example, NetBIOS or APPC sessions) before the upper
limit of numrc is reached. For details of how to increase sessions resources,
refer to the configuration guide of your communications protocol product.

Make sure that numrc does not exceed the value of the SQLNETB environment
variable set in the CONFIG.SYS file. This variable defines the maximum number
of sessions allowed for DB2/2. For more information on tuning DB2/2, refer to
the DB2/2 Guide.

There are also configuration parameters to consider for each database. See the
DB2/2 Guide for recommended values, but note that the default values for a
typical database will work for Visualizer Query for OS/2.


ΓòÉΓòÉΓòÉ 4. Changes to the user documentation ΓòÉΓòÉΓòÉ

o The reference to the IBMSQLVIEW object in Appendix B of Visualizer Query for
  OS/2: Using (SH45-5089-00) is not correct. IBMSQLVIEW is not a valid object
  within this module, and it cannot be opened from the FTBAS3 module using the
  command line. Ignore further references to IBMSQLVIEW in the remainder of
  Appendix B.

o Before opening and browsing an SQL Table or SQL View from the OS/2 command
  line, you must start Database Manager by issuing the command STARTDBM

  Database Manager will start automatically when one of the following
  Visualizer objects accesses the database:

  SQL Database
  Query
  Report
  SQL Statement
  Table


ΓòÉΓòÉΓòÉ 5. Deleting a Visualizer LAN requester component ΓòÉΓòÉΓòÉ

Before deleting a LAN requester component of Visualizer from a workstation,
ensure that the workstation has write access to the Visualizer directory on the
LAN server.

If the workstation does not have write access to the Visualizer directory when
you delete the LAN requester component, the CONFIG.SYS file is deleted from the
workstation, and the following message is displayed:

EPF1227: An error occured completing the deferred installation
         preparation.

If this happens, copy the backup of the CONFIG.SYS file to the boot drive of
your workstation before shutting down and restarting.

Note:   The backup version of the CONFIG.SYS file is stored in the TMPDEFER
sub-directory in the directory where the requester component of Visualizer is
installed.


ΓòÉΓòÉΓòÉ 6. OS/2 APAR information ΓòÉΓòÉΓòÉ

This section describes OS/2 APARs that currently affect Visualizer Query for
OS/2.

 1. OS/2 APAR PJ09399 - OS/2 2.1 Default Decimal Separator

    This APAR documents a problem with the decimal separator default value set
    in OS/2. If this problem is not corrected in OS/2 before the installation
    of Visualizer Query for OS/2, the Visualizer Profile object inherits the
    incorrect settings from OS/2. Reset the Visualizer Profile object manually
    if you encounter unexpected errors.

    This problem is caused by a default of blank in the Decimal places setting
    of OS/2. To overcome the problem, change the setting to a numeric value,
    for example 2, in both OS/2 and Visualizer.

    If you have already installed Visualizer Query for OS/2, correct the
    problem by opening the Visualizer Profile notebook and correct the Currency
    and Numbers settings.

    To correct the OS/2 settings, open the Country icon in the System Setup
    folder and change the Time, Date and Numbers settings.

 2. OS/2 APAR PJ14733 - Dropping shadows of SQL tables and SQL views on other
    Visualizer objects

    Pending the resolution of this APAR, you cannot drop a shadow of an SQL
    Table or an SQL View onto a Visualizer object.


ΓòÉΓòÉΓòÉ 7. Binding to a remote database ΓòÉΓòÉΓòÉ

You cannot bind Visualizer packages directly to remote DB2/MVS, SQL/DS, AS/400,
and DB2/6000 databases from a non-OS/2 environment. It must be done from a
workstation that can access a remote database through DRDA. To do this, ensure
that your DB2 administrator has copies of the bind files listed in the
following files:

FTBSDSN.LST         DB2 for MVS
FTBSARI.LST         SQL/DS
FTBSQSQ.LST         AS/400
FTBSSQL.LST         DB2/2 and DB2/6000
FTBWSQL.LST

For example, when the files are on a workstation, and you are using a remote
DB2 database, the DB2 administrator should execute the following DB2/2
commands, or CAE/2 equivalents:

SQLBIND @FTBSDSN.LST db2alias /k=all /g=public
SQLBIND @FTBWSQL.LST db2alias /k=all /g=public

Following this, the SQL statement contained in the following files should be
executed:

FTBDSNW.SQL         AS/400
 FTBARIW.SQL        SQL/DS
 FTBQSQW.SQL        DB2 for MVS
 FTBSQLW.SQL        DB2/2 and DB2/6000

The view definitions may be tailored as required, as long as the columns are
not changed.


ΓòÉΓòÉΓòÉ 7.1. Binder object ΓòÉΓòÉΓòÉ

An additional bind file called FTBTAIX.BND and has been included in the list
files FTBWSQL.LST.

The execute privileges on the package created from this bind file are available
to users.


ΓòÉΓòÉΓòÉ 8. VM and MVS Application System Version 3.2 ΓòÉΓòÉΓòÉ

Before using Visualizer Query for OS/2 to import reports from VM or MVS
Application System Version 3.2, ensure that a PTF for new function APAR PN59350
has been applied to the Host AS system.


ΓòÉΓòÉΓòÉ 9. Database Folder object ΓòÉΓòÉΓòÉ

o If you are not already logged on when a Visualizer database folder object is
  opened, a logon dialog is displayed. Population of the database folder will
  not continue until you have logged on.

  The logon dialog will not be displayed if another Visualizer object, other
  than a database folder, already has a composed view open. This means that the
  database folder cannot be populated.

  Therefore, if you are not logged on and a composed view of a Visualizer
  object is open, database folders cannot be opened successfully. If the
  composed views of all Visualizer objects are closed, then opening a database
  folder causes the logon dialog to appear, and the operation will work
  correctly.

  The converse is also true. You cannot open the composed view of any
  Visualizer objects (other than database folders) while the logon window is
  displayed. However, once the user has logged on locally, the problem no
  longer exists because the logon dialog will not need to be displayed.

  To avoid this problem either logon before using Visualizer objects, or open a
  Visualizer database folder first.

  If you have not logged on, and database folders are failing to populate,
  close all the views of Visualizer objects and then open a Database folder
  again. This causes the logon dialog to appear and normal operation to be
  resumed.

  Note:   Because of the above restriction, it is strongly recommended that
  Visualizer objects are not placed in the OS/2 Startup folder.

  If you are working in an environment where you need to access databases on
  different servers (including DRDA access to host databases), you can avoid
  problems with multiple logons by using the same user IDs and passwords on all
  the systems. Then, logging on locally before starting Visualizer ensures that
  no further logons are required, irrespective of how many different database
  accesses are made.

  Alternatively, you can avoid problems with multiple logons by using User
  Profile Management to create a user logon profile for the local userid. This
  ensures that you will be automatically logged on to all other systems when
  you log on locally.

o If you are copying a Visualizer table to a database folder, and SQL error -
  805 occurs, bind the product again, as described in Chapter 9 of Visualizer
  Query for OS/2: Installing and Supporting.

o Message 4072: The database is not responding. is displayed when the Data
  Viewer is attempting to fetch rows of data from a database, but does not
  receive a response from the database for about 30 seconds. This condition can
  occur when other applications have locks on the database, or when there are
  problems communicating with the database. No further data will be displayed
  by the Data Viewer.


ΓòÉΓòÉΓòÉ 10. Database locking ΓòÉΓòÉΓòÉ

If you use a Visualizer object to access a database table where locks are being
held by another user, in some circumstances, the Visualizer object will wait
for the locks to be released before resuming normal operation.

When this occurs, the OS/2 cursor will show the busy icon.

If you want to close the object before normal operation resumes, press
Ctrl+Break.


ΓòÉΓòÉΓòÉ 11. Opening settings for a DB2/6000 table or view ΓòÉΓòÉΓòÉ

Pending the resolution of the DB2/2 APAR JR00056, using DB2/2 with an APPC
connection to a DB2/6000 database causes system error: SYS3175 when you open
the settings notebook of a DB2/6000 table or view. However, you can open and
use tables and views in a DB2/6000 database without problems.

If you encounter a SYS3175 error, you must shutdown and restart your
workstation before continuing, although you still will not be able to show the
settings for a DB2/6000 table or view using Visualizer.

This problem does not occur when you use CAE/2 to connect to a DB2/6000
database.


ΓòÉΓòÉΓòÉ 12. Printing ΓòÉΓòÉΓòÉ

There are two ways to set portrait and landscape options on a printer. You can
use either the workplace shell Printer object settings notebook to set the
default options for the print queue represented by the printer object.
Alternatively, you can use the Options push button on the Copies window. The
Copies window is displayed when a print request is made from some Visualizer
objects, such as Report. This method only changes the properties for the
current print job and is not recommended because options set in this way may
not be reflected in the printed output.

The recommendation therefore is to create one Workplace Shell Printer object
for each variation of printer options required. For example, you could create
one object for landscape printing, and another for portrait printing, both
represent queues that will print on the same printer. In this way, the required
printout can be achieved without having to modify any print options.


ΓòÉΓòÉΓòÉ 13. Drag-and-drop in Data Viewer ΓòÉΓòÉΓòÉ

o Dragging from the Data Viewer to another Visualizer object is only permitted
  when the data is in browse mode.

  Note:   Links enabled in this way will not be active links.

o Report may wait when requesting data that is being updated in Data Viewer.
  You can avoid this by using Save or Revert in the Data Viewer.


ΓòÉΓòÉΓòÉ 14. General ΓòÉΓòÉΓòÉ

o Visualizer Query for OS/2 does not support OS/2 Extended Services Database
  Manager. However, this will not be detected until an object attempts to
  connect to DBM, and the following message, Unable to load SQLA32, appears.

o Visualizer Query for OS/2 optimizes database access by sending all requests
  directly to the database. This means that errors arising will result in
  messages from the database itself.

  Not all messages are detectable by Visualizer. These messages are not
  supported by online help. In such circumstances, refer to the appropriate
  documentation for the database you are using.

o On shutdown, the system may sometimes appear to hang. After two minutes, the
  shutdown completes successfully. In most cases, you can significantly reduce
  this delay by pressing Crtl+Esc. A window is displayed asking you to close
  the desktop, followed by another message informing you that shutdown is
  complete. The workstation can then be switched off.

  Alternatively, this situation can be prevented by shutting down the LAN
  Requester before you shutdown the system.

o A problem may occur when using DB2/2 1.0.1 (which was a refresh of DB2/2
  including service up to level 7015). If the Database Manager is not already
  started, attempts to start it automatically from within Visualizer may fail.
  Once this has happened the Database Manager cannot be started from an OS/2
  command line.

  When corrective service is applied to bring DB2/2 to level 7025, this problem
  is removed. However, if you are at level 7015, start the Database Manager
  from an OS/2 command line before using Visualizer objects. You can put a DBM
  START DATABASE MANAGER command into the file, STARTUP.CMD.

o If you try to Select Columns when building a Query, you cannot Rename
  Columns, Calculate Columns, or Select Rows and the icons on the tool bar and
  the choices on the Query menu are not available.

o In a report, column headings can be split over multiple lines. The points at
  which these splits occur can be controlled in the following way:

    1. Double-click on the column heading to open the Settings window.

    2. Change the value of the Depth in lines field. Standard word-wrapping
       will be applied to the heading text.

    3. If you want line breaks at specific points in the text, insert line feed
       characters at the point where you want the line to end.

       To insert line feed characters into text:

       a) Move the edit cursor to the required break-point in the text.

       b) Press the Alt key, then type 1 followed by 0 on the numeric keypad.

       c) Select Apply on the Settings window to display the text over multiple
          lines.