home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 29 Fixes_o
/
29-Fixes_o.zip
/
wr07012.zip
/
wr07012.INF
(
.txt
)
< prev
next >
Wrap
OS/2 Help File
|
1993-08-24
|
9KB
|
199 lines
ΓòÉΓòÉΓòÉ 1. Installation ΓòÉΓòÉΓòÉ
Installation Prerequisites
1. If you have just finished installing IBM DB2/2, IBM Lan Server/Requester or
IBM CM/2, shutdown and reboot your system before installing the DB2/2
Select Paks. You will have to reboot twice, once after the installation of
these products to process any locked files, and a second time before using
the Select Pak, to process some remaining locked files.
2. If you are planning to install IBM LAN Netview/2 or IBM CM/2 with DB2/2 on
the same machine, you MUST install DB2/2 and the Select Paks before the
other products. Otherwise, DB2/2 may replace some common files that are
shared among these products with an earlier version of the same files.
This may cause undesirable results in the other products.
To install the Select Pak
o Unzip the file WR07012.ZIP (use PKUNZIP)
o Before starting the install you will need to know the drive that OS/2 is
installed on and the drive where DB2/2 1.0 is currently installed
o Run WR07012.CMD in the directory in where it was unzipped.
Note: If you ran the install command file an OS/2 full screen, you will be
returned to the desktop upon exitting. Be sure to return to the correct
session to proceed with the installation.
Installation Errors
If the Select Pak installation aborts with an error, then your DB2/2 system may
be left in an inconsistent state. Possible causes for this are:
1. Your OS/2 swapper file has become too big and there is no more room for the
temporary files that the install program needs to install.
2. The file 'LSI.MSG' under x:\OS2\install (x is your boot up drive) is locked
and cannot be overwritten. You need to reboot to unlock this file.
After you correct the cause of the problem, you must restart the Select Pak
installation and let it complete successfully in order to bring your DB2/2
system to a consistent state.
Re-installing DB2/2 Gold
If you ever re-install DB2/2 from the original installation disks, you should
first copy the following files from WR07012.PKZ to the DB2/2 1.0 installation
diskette 1:
o LSI.MSG
o IBMLANLK.SYS
o IBMLANLK.EXE
These changed files correct a problem in the original installation program
which causes the current date to be given to the files being installed instead
of leaving the date untouched. This fix is required since the Select Pak
install program checks the existing file date before installing the Select Pak
files. If the date of the file already installed is later than the Select Pak
file date, then the install program will ask you whether this file should be
replaced or not. If you re-install from your original DB2/2 diskettes after the
date the Select Pak was finalized then you would be asked whether you want to
overwrite ALL of the Select Pak files (one at a time). Changing the above
three files on your original DB2/2 diskettes will stop this from happening.
ΓòÉΓòÉΓòÉ 2. The DB2 Family Newsletter ΓòÉΓòÉΓòÉ
This is a bi-monthly newsletter that reports the latest news for the family of
DB2 products (DB2 AND DDCS on all available platforms: OS2, AIX, MVS...)
If you are interested in receiving this newsletter, please mail or fax your
request to
IBM Canada Ltd.
Database Technology Planning
31/110/895/TOR
895 Don Mills Rd.
North York, Ontario
Canada, M3C 1W3
Attn: L. G. Pedron
Fax: 416-448-2114
ΓòÉΓòÉΓòÉ 3. Submitting Suggestions to IBM ΓòÉΓòÉΓòÉ
If you have any suggestions to enhance our products, there are two vehicles to
communicate your requirements to IBM.
o If your organization has an IBM Representative, discuss your requirements
with your IBM Representative, and have them submit your requirements to the
Database Technology Planning group at TOROLAB2(DBMREQ).
o Or send your detailed requirements to the following address:
IBM Canada Ltd.
Database Technology Planning
31/110/895/TOR
895 Don Mills Rd.
North York, Ontario
Canada, M3C 1W3
Attn: L. G. Pedron
Fax: 416-448-2114
ΓòÉΓòÉΓòÉ 4. What's Changed ΓòÉΓòÉΓòÉ
Return to the table of contents and select one of the sub-branches of this
heading.
ΓòÉΓòÉΓòÉ 4.1. APARs ΓòÉΓòÉΓòÉ
The following changes have been made as a result of direct customer feedback.
Premature Termination when using Panels (APAR JR06270)
This fixes a problem that causes Query Manager to terminate unexpectedly. The
problem occurs when you change the size of a repeated rows field in a panel
where the field has a one to many relationship (Only on 8515 monitors).
Under OS/2 2.0 there is a formatting problem with repeated rows on the 8515
monitor. This problem, as well as the unexpected Query Manager termination can
be corrected by installing OS/2 corrective Service Pak 6055.
Negative Zeros (-0) (APAR JR06371)
In Extended Services 1.0, it is possible to get a result of -0 when subtracting
two decimal columns with the same value. This fix corrects the problem and is
applicable whether the database was migrated from OS/2 Extended Edition 1.3 or
created under Extended Services 1.0.
Premature termination using list boxes (APAR JR06684)
Query Manager has been corrected to prevent termination in situations where no
items in a list box are selected and the cursor has been scrolled off the
screen.
Dutch Translation Error (APAR JR06851)
In the Dutch language version, default and ascending indexes were shown as
'Dalend', which is Dutch for descending. This has been corrected.
Exceptions when using Callable Interface (APAR JR06882)
This fix corrects a problem where Query Manager incorrectly releases storage in
a process where the callable interface is being used from a REXX procedure. One
symptom of the problem is an addressing exception in some non-Query Manager
piece of code running in the same process.
Report Text Length (APAR JR06913)
This fix corrects a problem where the maximum length of report text was reduced
by one character for each variable inserted in the text. The condition is
fixed in all of the report text fields. (page heading text, break heading text,
etc.)
Index Display of Column Names (APAR JR06969)
This fix corrects the problem where a column name is truncated to 15-1/2 when
using the 'Show Index' function.
TAB/Arrow Keys in Procedures (APAR JR06986)
TAB and arrow keys now work as intended in message boxes created by the SAY
command.
Package Name For QM in DB2/2 (APAR JR07179)
Formerly, all levels and versions of Query Manager used the same package name
when binding to a database. However, because of the different dates on the
bind files for Extended Servicess 1.0 and DB2/2, a rebind was required each
time a client of one type accessed a database following a client of the other
type. Consequently, unless the user(s) had database administrator authority,
they were not allowed to perform the rebind. Thus, in an environment with a
mix of Extended Services 1.0 and DB2/2 clients, users could be denied access to
Query Manager.
This problem is fixed by using different package names for different versions
of Query Manager. The files:
o qrwn.dll
o qrw3*.bnd (8 files)
should be applied to every DB2/2 client and server on the system. Omitting
even one client will cause the problem to reoccur if that client is allowed to
connect to the database.
ΓòÉΓòÉΓòÉ 4.2. Other Changes ΓòÉΓòÉΓòÉ
Large Output Queries
Query Manager has been changed to display an error message when it runs out of
disk space on its 'working' drive while doing a 'save data' operation. The
data produced by the query is no longer available following this condition. The
user should free some additional space on the working drive and run the query
again.