home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 29 Fixes_o
/
29-Fixes_o.zip
/
us8110_1.zip
/
README
< prev
Wrap
Text File
|
1996-06-27
|
13KB
|
348 lines
Welcome to DB2* for OS/2* v2.1 FixPak 8110
+-- Note: ----------------------------------------------------------------+
| |
| After installation is complete, you will need to re-bind the DB2 |
| utilities against all of your databases. Refer to section 2.2 for |
| details. |
| |
| If you have received interim fixes from IBM support after 06/15/96, |
| then you should contact IBM support after the FixPak installation, to |
| request an updated version of the interim fixes. By doing this, you |
| are assured that your system is in a consistent state and no interim |
| fixes are lost. |
| |
+-------------------------------------------------------------------------+
For installation instructions please see section 2.1.2
This README file contains information for the following products and
components:
OS/2-Specific
-------------
IBM DB2 for OS/2 Server (DB2 for OS/2)
IBM DB2 for OS/2 Single-User (DB2 for OS/2)
IBM DB2 Software Developer's Kit for OS/2
IBM DB2 Client Application Enabler for OS/2
IBM DB2 Administrator's Toolkit for OS/2
DDCS for OS/2
-------------
IBM Distributed Database Connection Services* Single-User for OS/2
(DDCS Single-User for OS/2)
IBM Distributed Database Connection Services Multi-User Gateway for OS/2
(DDCS Multi-User Gateway for OS/2)
---------------------------------------------------------------------------
1. Contents for FixPak WR08110 (July 1996)
2. Installation Notes
2.1 Information for installing this FixPak
2.1.1 Pre-Requisites
2.1.2 Installation instructions
2.1.3 CID Installation instructions
2.2 Rebinding bind files - IMPORTANT
2.2.1 Rebinding for DB2 Server
2.2.2 Rebinding for DB2 Clients
2.2.3 Rebinding for DDCS Clients
2.2.4 Rebinding Specific Packages
2.3 TZ Environment Variable
2.4 LAN Support Program and NetBIOS rc=0x18
3. Miscellaneous
3.1 DB2 Family Newsletter
3.2 Customer Support
3.3 Corrective Service
For additional information please see the files README.TXT and
APAR.LST located on diskette #2.
==========================================================================
2. Installation Notes
2.1 Information for installing this FixPak
2.1.1 Pre-Requisites
This FixPak can be applied to the following DB2 for OS/2 products
with a syslevel WR08090.
DB2 v2.1 for OS/2 Server
DB2 v2.1 for OS/2 Single-User
DB2 SDK v2.1 for OS/2
DB2 CAE v2.1 for OS/2
DB2 Administrator's Toolkit v2.1 for OS/2
DDCS Single-User v2.3 for OS/2
DDCS Multi-User Gateway v2.3 for OS/2
2.1.2 Installation Instructions
To start the FixPak install, type INSTALL on a command line. You will
be presented with a list of products currently installed. Select a
product and then select UPDATE from the Action pull-down menu. You must
install the FixPak for every product listed (it is not necessary to re-boot
after each one even if the completion message says so, it is sufficient
to re-boot after all products have been updated).
2.1.3 CID Install Instructions
The FixPak install program (INSTALL.EXE) uses the same syntax and
response file keywords as DB2 for OS/2, DDCS for OS/2, SDK for OS/2, and
CAE for OS/2. Refer to the installation guide for a description of
these keywords.
o Each product must be updated separately.
o Every product (DB2 for OS/2, DDCS for OS/2, SDK for OS/2, and
CAE for OS/2) that is installed on the system must be
updated with this FixPak at the same time. You cannot mix
service levels between the products.
o A /P:"product name" command line parameter is required. See
the following sample command files on the first FixPak diskette
for the exact product titles:
DB2SVR.CMD IBM DB2 for OS/2 - Server
DB2SU.CMD IBM DB2 for OS/2 - Single-User
DB2SDK.CMD IBM DB2 Software Developer's Kit for OS/2
DB2CAE.CMD IBM DB2 Client Application Enabler for OS/2
DDCSMU.CMD IBM DDCS for OS/2 - Multi-User
DDCSSU.CMD IBM DDCS for OS/2 - Single-User
DB2ADMIN.CMD IBM DB2 Administrator's Toolkit for OS/2
o To aid in this, there is a tool called DB2RESP.EXE. This tool
generates the response files to be used during CID installations.
2.2 Rebinding bind files - IMPORTANT
Due to the new bind (.BND) files that have been shipped with this FixPak,
you will need to rebind your DB2 utilities against all your databases
after the FixPak installation. This step is necessary for the fixes in
this FixPak to become effective. The procedure of rebinding, outlined
below, only needs to be performed once per database.
2.2.1 Rebinding for DB2 Server
If you are applying fixes to the Server (either DB2 or DDCS), you must do
the following:
- At a command prompt:
db2 terminate
db2 CONNECT TO <dbname>
db2 BIND <path>\@db2ubind.lst BLOCKING ALL GRANT PUBLIC
db2 terminate
or,
- At the DB2 command line:
TERMINATE
CONNECT TO <dbname>
BIND <path>\@db2ubind.lst BLOCKING ALL GRANT PUBLIC
TERMINATE
Where <dbname> is the name of a database to which the utilities should be
bound, and where <path> is the full path name of the directory where the
bind files are located, such as \sqllib\bnd. Examine the DB2PATH
environment variable to determine the correct path. DB2UBIND.LST
contains a list of commonly required bind files used for DB2.
2.2.2 Rebinding for DB2 Clients
If you are applying fixes to a client (either CAE or SDK), and if you
are binding to a DB2 v2 database then you must do the following:
- At a command prompt:
db2 terminate
db2 CONNECT TO <dbname>
db2 BIND <path>\@db2cli.lst BLOCKING ALL GRANT PUBLIC
db2 terminate
or,
- At the DB2 command line:
TERMINATE
CONNECT TO <dbname>
BIND <path>\@db2cli.lst BLOCKING ALL GRANT PUBLIC
TERMINATE
Where <dbname> is the name of a database to which the utilities should be
bound, and where <path> is the full path name of the directory where the
bind files are located, such as \sqllib\bnd. Examine the DB2PATH
environment variable to determine the correct path. DB2CLI.LST
contains a list of bind files for DB2 Call Level Interface.
If <dbname> is a DB2 v1.x database, do not bind db2cli.lst. Instead, use
the db2cliv1.lst or specifically bind db2clics.bnd, db2cliur.bnd,
db2clirr.bnd, and db2cliv1.bnd individually. The bindfile list db2cli.lst
contains the names of bind files with DB2 v2 specific SQL syntax.
2.2.3 Rebinding for DDCS Clients
If you are using DDCS to connect to host databases, you will also need
to bind the new bind files to the host. As above, use the DB2
Command Line Processor to connect to the host database, and then
bind the utilities as follows:
HOST COMMAND
======= ===================================================
MVS BIND <path>\@ddcsmvs.lst BLOCKING ALL GRANT PUBLIC
SQLERROR CONTINUE
VM BIND <path>\@ddcsvm.lst BLOCKING ALL GRANT PUBLIC
SQLERROR CONTINUE
VSE BIND <path>\@ddcsvse.lst BLOCKING ALL GRANT PUBLIC
SQLERROR CONTINUE
OS400 BIND <path>\@ddcs400.lst BLOCKING ALL GRANT PUBLIC
SQLERROR CONTINUE
NOTE: Please refer to pp.17-30 of the DDCS User's Guide for a list of
what bind files are used for your specific client operating system.
If a bind file changes but your clients do not use that bind
file, you do not need to re-bind it.
2.2.4 Rebinding Specific Packages
If you wish to bind only the specific .bnd files to the database, issue
the following command for each database (where <bind_file> is the name of
the bind file, and <dbname> is the name of your database).
- At a command prompt:
db2 terminate
db2 CONNECT TO <dbname>
db2 BIND <path>\<bind_file> BLOCKING ALL GRANT PUBLIC
db2 terminate
or,
- At the DB2 command line:
TERMINATE
CONNECT TO <dbname>
BIND <path>\<bind_file> BLOCKING ALL GRANT PUBLIC
TERMINATE
2.3 TZ Environment Variable
When connecting a client to the server which runs on an operating
system that supports the concept of local time versus Universal
Coordinated Time (UCT, also known as Greenwich Mean Time or GMT), the
client machine should also set up timezone information that
corresponds to the server machine. If it is not set, the client may
display certain timestamps (that are returned by the server)
incorrectly (being off by the difference between the UCT and local
time).
For example, if a server is running under Pacific Standard Time
(PST) and a client is running under Eastern Standard Time (EST),
timestamps on the client will show PST unless the TZ variable is set.
2.4 LAN Support Program and NetBIOS rc=0x18
If you use IBM LAN Support Program to provide NetBIOS communications
protocol support, and you load the LAN Support Program device drivers
in DOS upper / high memory, you may encounter intermittent NetBIOS
communications errors "SQL30081, rc-0x18". To avoid these
communications errors, load the LSP device drivers in conventional
memory.
3. Miscellaneous
3.1 DB2 Family Newsletter
For the latest information about the DB2 family of products, you may
subscribe to the "DB2 Family Newsletter" (English only). Simply send
your request in a FAX to 1-905-316-4733, and include the following
information:
Name
Company name
Full mailing address
Telephone number
DB2 products you currently use
3.2 Customer Support
To speak to an IBM representative regarding assistance with this product,
please call 1-800-992-4777.
Customer support is also provided via Electronic Question and Answer (Q&A)
forums. These forums are accessible through CompuServe, IBMLink, and Usenet
Newsgroup.
(1) CompuServe
- To access the forums on CompuServe, execute GO IBMDB2.
- If you don't have access to CompuServe, call 1-800-848-8199 for
membership information in Canada or the US.
(2) Usenet Newsgroup: comp.databases.ibm-db2
- This Internet Newsgroup is a general forum for discussing questions
and/or problems encountered using the DB2 family of products.
(3) (IBMLink) Talklink OS/2 BBS
- To access the forums on IBMLink, go to the OS2BBS section.
- If you don't have access IBMLink, call 1-800-547-1283 for membership
information in Canada or the US.
3.3 Corrective Service
They can be downloaded electronically from the following locations:
(1) CompuServe
- Execute GO IBMDB2
- then go to the DB2/OS2 library to find the DB2/OS2 FixPak
- or go to the CLIENTS library to find the SDK/Win FixPak.
(2) Internet
- FTP to anonymous server ftp.software.ibm.com (previously
known as ps.boulder.ibm.com) at 198.17.57.66
- then go to ps/products/db2/fixes/<language>/<prod_vers>
where
<language> is (eg. english-us, spanish, german, etc.)
<prod_vers> is the product name/version (eg. db22v21, db2winv21, etc.)
- Use a World Wide Web (WWW) browser to connect to the DB2 Service and
Support Page.
(http://www.software.ibm.com/data/db2/db2tech/index.html)
(3) IBM PCC BBS (in US)
- Call (919) 517-0001 (in Raleigh, North Carolina)
- Then type "db2" on the main menu to find the FixPaks
The above are the primary locations where these FixPaks are uploaded.
They may also be available on other Bulletin Boards (such as the Talklink
OS/2 BBS in the US).
If you do not have access to any of the above locations, please call
1-800-992-4777 to request these FixPaks be sent to you in the mail.
For countries other than US and Canada, please look at your local
IBM OS/2 BBS or call your local DB2 Customer Service number for
assistance in obtaining them.
-----------------------------------------------------------------------
* are trademarks or registered trademarks of IBM Corporation.
** are trademarks or registered trademarks of their respective owners.
-----------------------------------------------------------------------
***********************************************************************
** **
** (c) COPYRIGHT INTERNATIONAL BUSINESS MACHINES CORPORATION 1996. **
** ALL RIGHTS RESERVED. **
** **
***********************************************************************