home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 29 Fixes_o
/
29-Fixes_o.zip
/
READMEUS.026
< prev
next >
Wrap
Text File
|
1994-12-29
|
22KB
|
582 lines
DB2/2 v1.0.1 Select Pak WR07025:
================================
Note: This Select Pak has been repackaged since its original release
to include one additional defect. If you have already installed the
Select Pak without this defect, you can add the fix by obtaining the
file FIX7025.ZIP. See the OTHER section in WHAT'S CHANGED under
AUTOCOMMIT for a description of the change.
This version of the select contains this fix.
Pre-Requisites
--------------
This Select Pak can be applied on either the refresh code level (v1.0.1,
syslevel WR07015) or on Service Pak WR07015 (syslevel WR07015).
Other Information
-----------------
WARNING: If you choose to backup your files, please be aware that any files
that already exist in the backup directory you specify will be overwritten.
If you want multiple level of backups please specify different backup
directories.
>>****>>NOTE: This Select Pak can be used to install DB2/2 engine and or
Database Administration Tools fixes.
CAUTION: If you have
1) reinstalled DB2/2 v1.0.0 (GOLD) after 94/02/11 or
2) installed DB2/2 v1.0.0 (GOLD) on top of ES10 DBM after
94/02/11,
some of your DB2/2 DLLs may then have a later date/time stamp
than the DLLs in the select pak. However, the DLLs on your
system are actually not as recent as the ones in the select pak
and do not include any fixes in the Select Pak. This is a
known defect in the original DB2/2 install program which
modifies some DLLs' date/time stamp to the date of the
installation.
If you are using the DB2FIX install, then select YES when
prompted by the install program to overwrite the DLL already
on your machine with the Select Pak one.
If you are using the CID install (DBFIXCID), then modify the
CID response file to set DBReplace=Y. If you do not, you may end
up with and inconsistent system once the CID install completes.
If you have done either 1 or 2 above and received private fixes
from IBM support after 94/02/11, then you should set DBReplace=Y.
After the select pak installation, you should reinstall the
private fixes that you received from IBM. By doing this, you
are assured that your system is in a consistent state and
no private fixes are lost.
CAUTION: If an existing version of DB2/2 is executing it should be
stopped before applying the Select Pak.
CAUTION: For client/server platforms, this Select Pak should be applied
to both server and client workstations.
>>****>>NOTE: In order to run with the new DDCS/2 fixes in WR07024,
you must install BOTH the DB2/2 Select Pak WR07025 and the DDCS/2 Select
Pak WR07024.
>>****>>NOTE: Due to new bind (.BND) files that have been shipped with
this Select Pak, you may need to rebind your databases to the DB2/2
bind files. Run "sqlbind x:\sqllib\@sqlubind.lst your_dbname" for each
of your databases (where your_dbname is the name of your database and
x: is the drive where SQLLIB is).
Contents
--------
>Installation Instructions
>CID Installation Instructions
>The DB2 Family Newsletter
>Submitting Suggestions to IBM
>What's Changed
>>Database Engine Apar Description
>>IPX/SPX Support
>>Other
>Questions and Answers
Installation Instructions
-------------------------
To start the Presentation Manager Select Pak install, type DB2FIX on a command
line, select ACTION from the action bar and then SERVICE from the pull down menu.
If you have just finished installing IBM DB2/2, IBM DB2/2 Service
Pak WR07015 (syslevel WR07015), IBM refresh code level v1.0.1,
IBM Lan Server/Requester, or IBM CM/2, please shutdown and reboot your
system before installing the DB2/2 Select Pak. 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.
CID Install Instructions
------------------------
For DB2/2 CID Select Pak install, please use the sample response file
DB2FIX.RSP provided on diskette 1. This file can be modified to fit your
installation needs.
NOTE: The keywords found in DB2FIX.RSP are the ONLY supported CID keywords in
this version of the CID install program.
The Select Pak CID install program (DBFIXCID.EXE) uses the same syntax as the
DB2/2 CID install program. Refer to the DB2/2 Installation Guide for a
description.
For a description of the CID install key words, refer to Appendix B of the
DB2/2 Installation Guide. Two keywords have been added to support the
Select Pak install:
> DBInstallEngine - install the database engine (1=YES 0=NO).
> DBReplace - replaces files on the target system if they have a later
date/time stamp than the ones shipped with the Select
Pak (1=YES 0=NO).
NOTE: The CID keyword DBUpdateType can only be equal to 1, which specifies
to install the Select Pak. No other values are supported.
NOTE: If a certain component, say, Query Manager is not installed on
a given system, specifying CID keyword DBInstallQueryManager=Y would have
no effect. It would just be ignored for that particular system and
no Query Manager fixes would be installed.
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
2S/110/1150/TOR
1150 Eglinton Avenue East
North York, Ontario
Canada, M3C 1H7
Attn: T.D. Sole
Fax: (416) 448-2114
SUBMITTING SUGGESTIONS TO IBM
-----------------------------
If you have any suggestions to enhance our products, there are two
vehicles to communicate your requirements to IBM.
* 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).
* Or, send your detailed requirements to the following address:
IBM Canada Ltd.
Database Technology Planning
2S/110/1150/TOR
1150 Eglinton Avenue East
North York, Ontario
Canada, M3C 1H7
Attn: M.H. Switzer
Fax: (416) 448-4414
WHAT'S CHANGED - APAR Descriptions
----------------------------------
The following changes have been made as a result of direct customer feedback.
The fixes contained in this Select Pak are fixes that have gone into the product
since WR07015 was shipped.
Databse Engine APAR Descriptions
--------------------------------
APAR JR00056
Previously, when users connected to DB2/6000 or DB2/MVS from a DB/2
client, the connection information was not correct. The problem was
caused by the old DBM.CMD (REXX) client code not knowing the DB2/6000
and DB2/MVS product signatures. A fix has been implemented to correct
this problem.
APAR JR07267 - Restrictions on Cobol Host Variables
Previously, a sign was not allowed in the VALUE clause of a PIC statement
in the DECLARE section of COBOL programs with imbedded SQL.
An optional sign is now allowed on numeric declarations of host variables.
Existing programs will continue to precompile as before.
For example the following is now possible:
EXEC SQL BEGIN DECLARE SECTION END-EXEC.
01 MY-VAR PIC S9(4) COMP-5 VALUE IS +5.
EXEC SQL END DECLARE SECTION END-EXEC.
APAR JR07352 - Addition subtraction of decimal numbers
This fix solves a problem with decimal addition and subtraction where negative
zero (instead of positive zero) results are generated.
APAR JR07464 - SQL0553 while importing
While importing a table which had a primary key (and an index auto created),
SQL0553 was returned because of an attempt to create an index with 'sysibm' as
qualifier. When a table was exported in IXF format, index information was stored
in the IXF file unless the qualifier of the index was SYSIBM. This comparison of the
qualifier of the index was not being executed properly so this information was stored
in the IXF file. When those files were imported again, an error occurred when
import tried to create an index with a SYSIBM qualifier.
This fix will export so that no index information will be stored in the IXF file
for indexes with the SYSIBM qualifier. To implement the fix: rebind sqlueiwi.bnd
to the database and re-export the table. (No more import error messages
will result from the failure of the creation of an index with a SYSIBM qualifier).
APAR JR07486 - Unnecessary Empty Pages
Previously, applications generated unnecessary empty pages which affected performance.
Data pages were considered full once there was no more free space for new
records OR the maximum number of records per page had been reached. Deleting records
allowed DB2/2 to reuse the space of the deleted record for future inserts. However,
once a data page contained the maximum number of records, the free space resulting
could not be reused for future updates. This caused the data file to grow larger which
was necessary to accommodate the new data being appended to the file. As a result, a REORG
operation was the only way to reclaim this unusable free space on 'full' data
pages.
This fix has remedied the problem in that DB2/2 will reclaim and reuse
any available free space for record inserts, even when there has been deleted
records on previously full pages (maximum number of records per page).
APAR JR07504 - USEREXIT Archive OS/2 Window totally blacked-out, inaccessible
Invoking the LOG USER EXIT for ARCHIVING caused the OS/2 Archive Window
to be brought up as expected but totally black. After installing the first Select
Pak for DB2/2, user exits would have no stdin/stdout/stderr. Any type of I/O
performed by the user exit would result in an error as the file handles were
inadvertently closed in the parent process and inherited by the user exit. The
same symptoms would occur if the user was doing a RETRIEVE of a log file as well.
This problem may or may not have been noticeable. If the user exit did not
perform I/O, the problem would not occur. However, during normal execution when
the user exit is invoked and I/O is required, the problem would occur.
This fix has corrected the problem in that inherited standard I/O file handles are
now kept open.
APAR JR07508 - Start/Stop using database causes swapper file to grow
When performing START USING - STOP USING multiple times in several processes
running concurrently to the same database, the SWAPPER file kept on growing due
to the same database shared memory not being disconnected properly.
A fix has been implemented which now enables the database shared memory to be freed
up properly for concurrently running processes.
APAR JR07513 - View based on column functions with distinct has bad result
This problem was associated with queries based on views that contained column
functions with DISTINCT applied to the argument. This was caused by an
oversight in the SQL compiler in which it did not recognize the need for a
SORT prior to the DISTINCT processing.
A fix has been implemented to make the SQL compiler recognize that a SORT is
required and generate a plan that ensures the records are sorted prior to the
DISTINCT processing.
APAR JR07515 - Lots of almost empty leaf pages
Adding lots of duplicate values to an index in a certain order could sometimes lead to
many almost empty leaf pages which caused the index file to grow extremely large and consume
alot of disk space. The problem was caused by a defect in the split logic for a single record
node in index manager. A fix has been implemented and the logic for splitting single record
pages has been changed to handle this situation properly.
APAR JR07516 - Trap in COBLIB.DLL when doing a CTL-BREAK while in MFCOBOL Animator
When running inside a COBOL runtime function, Micro Focus switched to a "static
COBOL stack of size approximately 8 KB". Once a signal was generated, the DB2/2 signal
handler trapped the signal and the default signal handler was invoked. The
available stack was only 4K, which is too small for DB2/2 signal handler to
operate. A fix has been implemented to correct the problem.
APAR JR07542 - SQL0104 when doing SQLBIND with grant option
When the SQLBIND command with the GRANT option (/G) was issued against a host
database like the AS/400, the error SQL01042N was returned. In this case, the
SQL0104N error indicated that "GRANT BIND, EXECUTE ON PROGRAM..." was not supported
on the AS/400. A fix has been implemented in DB2/2, so that the GRANT statement
supported by the hosts ("GRANT EXECUTE ON PROGRAM...") will be issued when the
GRANT option is specified.
APAR JR07577 - SQLNETB in CONFIG.SYS is set to 32 instead of 64
SQLNETB is a DB2/2 environment variable. It is provided to allow the user
to specify the number of NetBIOS sessions that he/she would like DB2/2
to reserve for itself from the NetBIOS pool of resources. If the
SQLNETB environment variable does not exist, at "STARTDBM" time, then
a default setting will be assumed by DB2/2.
This fix changes the actual SQLNETB default from 64 to 32 for server
configurations.
APAR JR07646 - Customer gets 3189 message too big for message buffer
A non-standard message was printed in the import/export message file in the event
that the combined length of the tokens for the message was greater than 70 bytes.
The tokens will now be truncated with this fix.
Note: After installing this fix, no other actions are required before running the
scenario. The message for SQL3189 will appear as documented in the Messages and
Problem Determination Guide. A column list is provided as the second token for message
SQL3189, this list may not be complete if the list is too long to fit in the 70 byte
limit of the sqlca.sqlerrmc.
APAR JR07663 - Incorrect SQL1042 Error Code
When an attempt was made to set the maximum file handles to a value smaller
than what was already opened by the operating system, an incorrect SQL1042
error code was returned. This has been fixed, and the SQL1042 error is no
longer returned.
APAR JR07670 - DB2/2 logs unnecessary to FFST/2
When a Presentation Manager application executes REXX SQL APIs, DB2/2 logs an unacceptable
number of FFST/2 log entries. The performance of the application was affected due to heavy
disk I/O. To handle this problem, DB2/2 now checks if the application is a Presentation
Manager application and does not log unnecessary FFST/2 log entries.
APAR JR07688 - Check Pointer Failed SQL0822
When an application was running SQL in a thread other than thread 1, the application could
potentially see error SQL0822 (bad SQLDA pointers), or trap in SQLAK32.DLL for 16-bit
applications. A fix has been implemented to correct this problem.
APAR JR07710 - Swith to turn off NetBIOS subsystem
Prior to this fix, there was no means, provided by DB2/2, to disable the NetBIOS
protocol initialization reserves NetBIOS sub-systems resources (sessions names
and ncbs). Some users would prefer to disable the NetBIOS protocol initialization,
for DB2/2, to conserve these resources. Disabling the DB2 NetBIOS initialization
would only be desirable for those not using the NetBIOS protocol for DB2/2
client/server applications.
This fix provides support for a new SQLNADPT environment variable value which would
allow the user to specify "NONE".
ie. SET SQLNADPT=NONE
NOTE: If "SQLNADPT=NONE" is set before issuing "STARTDBM" then the NetBIOS
protocol will NOT be initialized for that workstation.
After this fix, a NetBIOS client attempting to connect to the "NetBIOS disabled" server
will receive a SQLCODE "30080 '14'" (which means that the server is not ready).
"NetBIOS disabled" clients attempting to reach a server via NetBIOS will receive a
SQLCODE "30080 'FFFF'" (which means that your local DB2/2 NetBIOS protocol has not
been initialized properly).
APAR JR07757 - Table expected in WSF format has garbled column headings
The labels that are column headings did not have the preceding single quote (')
as required when exporting a WSF format file. This fix has remedied the situation.
APAR JR07758 - Thunking error in successive DARI/SQLOCALL calls
When multiple 16-bit stored procedures were called in nested levels (i.e. a 16-bit
stored procedure issues another 16-bit stored procedure from within itself) resulted in
DB2/2 mishandling the input and output SQLDA pointers. This caused the
application to receive a SQL0822 error. A fix has been implemented to correct
this problem.
APAR JR07770 - Negative zero not equal to zero (-0 <> 0)
This fix corrects a problem with the equals (=) and the not equals (<>) predicates
when both operands are zero valued decimals of identical precision and scale, or
zero valued double-precision floats.
NOTE: To implement this fix, rebind any applications with static SQL.
APAR JR07819 - Pool of memory release problem
When an application used DARI, the user received an error SQL0083C (out of memory)
if the server application returned SQLZ_DISCONNECT_PROC return value and was called
many times. This occurred because the pool of memory allocated by Run-Time Services
for the server application was not released. A fix has been implemented to correct
the problem.
APAR JR07868 - Complex queries with GROUP BY clauses
In some cases, complex queries with GROUP BY clauses caused failure or
returned incorrect results. After applying this fix, rebinding will
correct applications that were affected by this defect.
NOTE>> ONLY users who have seen this problem will have to initiate the
rebind.
IPX/SPX Support
---------------
This Select Pak includes code changes to enable the DB2 CAE/DOS v1.2 or DB2 CAE/2
v1.2 products to access the DB2/2 Server using the IPX/SPX protocol. You must install
both the DB2/2 engine and Database Administration Tools fixes from this Select Pak in
order to install all required changes for this IPX/SPX Support.
For more information on the IPX/SPX Support please refer to the DB2IPX.INF file
installed by the Select Pak on the \SQLLIB\BOOK dir:
view DB2IPX.INF
This Select Pak migrates your existing database manager configuration file. Existing
parameters in this file remain the same but two new ones will be added. You must set
these parameters before using IPX/SPX Support. Please refer to the above DB2IPX.INF
file for details.
There are some NEW and CHANGED messages related to this new IPX/SPX Support.
For more information on these please refer to the above file for details.
The following message identifiers are affected:
- SQL1066N
- SQL1067N
- SQL1073N
- SQL1340N
- SQL1341N
- SQL1342N
- SQL1343N
- SQL1392N
- SQL1393N
- SQL5014N
- SQL5019N
- SQL30081N
Other
-----
Migration of Database Manager Configuration file
This is done automatically by the Service/Select Pak install program. No
changes will be made to the existing parameters but two new ones will be added.
These can be left empty unless you want to use the IPX/SPX Support. Please
refer to the DB2IPX.ING file mentioned in the previous section for additional
information.
Translation of a QMF file
A problem existed in attempting to download a QMF file and import it in a DBCS
environment. The fix solves this problem and translates the QMF file as intended.
DB2/2 Base Address Changes
The DLL base address for DB2/2 has been modified in order to get around an OS/2
APAR PJ11671. No functionality changes were made as part of this APAR.
1042/Trap on Recovery
A potential recovery problem related to an index file size that could cause a
trap or 1042 during recovery has been fixed.
Autocommit
When DBMCOMMIT was not set or set to YES, operations performed through
DBM -C UPDATE or DBM -C DROP on the database could not be rolled back.
Now, operations done with DBM -C can always be rolled back regardless
of what DBMCOMMIT is set to.
Note: This problem only exists in the first release of Select Pak 7025
and not in Service Pak 7015 or DB2/2 v1.0.1.
QUESTIONS AND ANSWERS
---------------------
Q: What do I look for if my application ABENDED while connected to a database?
A: Look for a .TRP file in the x:\SQLLIB directory, where x is the
installation drive for DB2/2. This file is created when DB2/2 ABENDs.
The file contains the user's stack and current register information. Using
this information you should be able to find the problem. If you are unable to
resolve the condition, phone IBM support.
Q: What are the recommended trace settings for DB2/2?
A:
>sqltrc on -l 1000000 -e 10
>sqltrc dump trace.dmp
>sqltrc fmt trace.dmp trace.fmt
This procedure will create a 1 MB trace file which is used by IBM support
to help resolve many DB2/2 problems. The TRACE.FMT file will be an ASCII
file with DB2/2 activity recorded during the problem recreation.
Q: When using DB2/2 with the Lotus Datalens product, I receive the following
message when attempting to connect to a DB2/2 database:
Error Code SQL0804N and you are unable to connect.
What is wrong?
A: Lotus 1-2-3 for OS/2 has a driver called DATALENS that allows you to bring
data from a database into your spreadsheet.
This is a known problem with the Lotus Datalens product. The fix is
available from your local Lotus Technical Support centre in a SLIPSTREAM
driver package as of August 1993.