home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 29 Fixes_o
/
29-Fixes_o.zip
/
READ7030.ZIP
/
readme.sql
< prev
next >
Wrap
Text File
|
1995-01-23
|
35KB
|
894 lines
DB2/2 v1.0 Service Pak 7030
==============================
Welcome to DB2/2
This README file contains information for DB2/2 v1.0 Service Pak 7030.
Please see Section 1.2 for Sevice Pak install information.
Part 1 contains important information about this Service Pak. It includes
installation instructions and details changes to the product since the
shipping of Select Pak 7025.
Parts 2,3 and 4 are in the file README.OLD on Diskette 1.
Part 2 contains the descriptions of changes made to the product in Select Paks
7025, 7023 and 7022.
Part 3 contains the information for Service Pak 7015.
Part 4 contains descriptions of changes made by Select Paks 7010 and 7012.
NOTE (1): If an existing version of DB2/2 is executing it should be
stopped before applying the Service Pak.
NOTE (2): For client/server platforms, this Service Pak should be
applied to both DB2/2 v1.0 server and DB2/2 v1.0 client workstations.
NOTE (3): After installation is complete, you will need to re-bind your
databases. Refer to section 1.2.5.1 for details.
NOTE (4): If you have received private fixes from IBM support after
94/11/01, then you should contact IBM support after the service pak
installation, to request an updated version of the private fixes. By
doing this, you are assured that your system is in a consistent state
and no private fixes are lost.
========
CONTENTS
1.0 Part 1 - Service Pak 7030 DECEMBER, 1994
1.1 Introduction
1.2 Service Pak Installation
1.2.1 Pre-Requistes
1.2.2 Co-Requistes
1.2.3 Installation Instructions
1.2.4 CID Installation Instructions
1.2.5 After installation (IMPORTANT)
1.2.5.1 Rebinding bind files
1.2.5.2 Copying files from \os2\install directory
1.3 General Information
1.3.1 Service Information (US/Canada)
1.3.1.1 Database 2 OS/2 and Distributed Database Connection Services/2 Support
1.3.1.2 Electronic Customer Support and Corrective Service
1.3.1.3 Accessing Corrective Service and Customer Support
1.3.2 The DB2 Family Newsletter
1.3.3 Submitting Suggestions to IBM
1.4 Defects Fixed
1.4.1 Database Engine APAR Descriptions
1.4.1.1 APAR JR00056: Incorrect Connection Information
1.4.1.2 APAR JR07732: Hang on CONNECT
1.4.1.3 APAR JR07740: SELECT - ORDER BY fails with SQL0902
1.4.1.4 APAR JR07869: "STATUS" no longer a reserved word in REXX
1.4.1.5 APAR JR07918: SQLCIAA trapped when Netbios session broken
1.4.1.6 APAR JR07919: DBM GET SYSTEM STATUS failed
1.4.1.7 APAR JR07970: SYS3175 with many NETBIOS clients
1.4.1.8 APAR JR07973: UPDATE returned invalid ROW COUNT
1.4.1.9 APAR JR08020: SQLSTATE set to blanks after FETCH
1.4.1.10 APARs JR08022, JR08150: Memory leak in SQLEFREE API
1.4.1.11 APAR JR08057: Log full errors
1.4.1.12 APAR JR08061: SYS3171 if APPN workstation network id set to null
1.4.1.13 APAR JR08111: DB22KILL failed
1.4.1.14 APAR JR08153: Inexact Floating Point Exception
1.4.1.15 APAR JR08155: Truncated value of NP,FP in DBM REORGCHK
1.4.1.16 APAR JR08157: APPC error F015-00000000
1.4.1.17 APAR JR08180: RUNSTATS returned incorrect results
1.4.1.18 APAR JR08211: PCDR lost connections
1.4.1.19 APAR JR08218: SQL1042 When doing ROLLFORWARD AND STOP
1.4.1.20 APAR JR08257: Floating point exception errors
1.4.1.21 APAR JR08263: Fix for DB2/2 running on WARP
1.4.1.22 APAR IX45867: Fortran precompiler problem
1.4.2 Other Database Engine Fixes
1.4.2.1 Unable to startdbm with IPX
1.4.2.2 Importing from CD-ROM failed with SQL3025N
1.4.2.3 UPM node logon
1.4.3 DOS/Windows Requester APAR Descriptions
1.4.3.1 APAR JR07968: SQL30080 when trying to use alternate adapter
1.4.4 Query Manager APAR Descriptions
1.4.4.1 APAR JR07346: Incorrect data in header text
1.4.4.2 APAR JR07467: Problem with BREAKS in QM forms
1.4.4.3 APAR JR07475: Could not use 3 or 9 as mnemonic keys
1.4.4.4 APAR JR07904: Invisible text while changing row conditions
1.4.4.5 APAR JR07797: Extra headers for updated records
1.4.4.6 APAR JR08152: Shift-F9 did not bring up Command line window
1.4.4.7 APAR JR08198: QRW0541 with TRACE ON
1.4.5 Database Administration Tools (DBAT) Changes
2.0 Part 2 - Select Pak 7025 MAY, 1994
2.1 Select Pak 7025 - Database Engine and Database Administration Tools (DBAT)
2.1.1 IPX/SPX support
2.1.2 Database Engine and DBAT APAR Descriptions
2.1.2.1 APAR JR00056 - Incorrect connection information
2.1.2.2 APAR JR07267 - Restrictions on Cobol Host Variables
2.1.2.3 APAR JR07352 - Addition subtraction of decimal numbers
2.1.2.4 APAR JR07464 - SQL0553 while importing
2.1.2.5 APAR JR07486 - Unnecessary Empty Pages
2.1.2.6 APAR JR07504 - USEREXIT Archive OS/2 Window totally blacked-out, inaccessible
2.1.2.7 APAR JR07508 - Start/Stop using database causes swapper file to grow
2.1.2.8 APAR JR07513 - View based on column functions with distinct has bad result
2.1.2.9 APAR JR07515 - Lots of almost empty leaf pages
2.1.2.10 APAR JR07516 - Trap in COBLIB.DLL when doing a CTL-BREAK while in MFCOBOL Animator
2.1.2.11 APAR JR07542 - SQL0104 when doing SQLBIND with grant option
2.1.2.12 APAR JR07577 - SQLNETB in CONFIG.SYS is set to 32 instead of 64
2.1.2.13 APAR JR07646 - Customer gets 3189 message too big for message buffer
2.1.2.14 APAR JR07663 - Incorrect SQL1042 Error Code
2.1.2.15 APAR JR07670 - DB2/2 logs unnecessary to FFST/2
2.1.2.16 APAR JR07688 - Check Pointer Failed SQL0822
2.1.2.17 APAR JR07710 - Swith to turn off NetBIOS subsystem
2.1.2.18 APAR JR07757 - Table expected in WSF format has garbled column headings
2.1.2.19 APAR JR07758 - Thunking error in successive DARI/SQLOCALL calls
2.1.2.20 APAR JR07770 - Negative zero not equal to zero (-0 <> 0)
2.1.2.21 APAR JR07819 - Pool of memory release problem
2.1.2.22 APAR JR07868 - Complex queries with GROUP BY clauses
2.1.3 Other Database Engine and DBAT fixes
2.1.3.1 Migration of Database Manager Configuration file
2.1.3.2 Translation of a QMF file
2.1.3.3 DB2/2 Base Address Changes
2.1.3.4 1042/Trap on Recovery
2.1.3.5 Autocommit
2.2 Select Pak 7023 - DOS/Windows Requester APAR Descriptions
2.2.1 APAR JR07462 - Display thread on DB2/MVS
2.2.2 APAR JR07728 - Application Abends
2.3 Select Pak 7022 - Query Manager APAR Descriptions
2.3.1 APAR JR07499 - Directory Naming
2.3.2 APAR JR07742 - Searching tables with Long Varchar
3.0 Part 3 - Service Pak 7015 JANUARY, 1994
3.1 Database Engine APAR Descriptions
3.1.1 APAR JR06426 - Referential Integrity Check Error
3.1.2 APAR JR06964 - BETWEEN Predicates with Character Host Variables
3.1.3 APAR JR06984 - Incorrect results on Query with Joins
3.1.4 APAR JR07076 - Referential Integrity Trap
3.1.5 APAR JR07282 - MicroFocus Cobol Applications
3.1.6 APAR JR07368 - Remote Client Hang
3.1.7 APAR JR07373 - BACKUP/RESTORE From a Privileged Window
3.1.8 APAR JR07387 - Trap E
3.1.9 APAR JR07388 - Vendor Application State
3.1.10 APAR JR07408 - SQLVAR verification
3.1.11 APAR JR07418 - Memory Failure
3.1.12 APAR JR07430 - OS/2 2.1 - START USING DATABASE Returns -1042
3.1.13 APAR JR07438 - GET DATABASE STATUS
3.1.14 APAR JR07439 - Applications with no SQL Statements
3.1.15 APAR JR07453 - SQLCODE -902 from SQLRASSM
3.1.16 APAR JR07659 - Trap in UPDATE.SQB
3.2 Database Administration Tools APAR Descriptions
3.2.1 APAR JR07468 - Recover Database with REPLACE EXISTING Option
3.3 DOS/Windows Requester APAR Descriptions
3.3.1 APAR JR05949 - SQLWARN0
3.4 Query Manager APAR Descriptions
3.4.1 APAR JR06499 - Numeric Global Variables
3.4.2 APAR JR07253 - Accessing Views from a Remote Client
3.4.3 APAR JR07278 - Large Numbers of Query Manager Variables
3.4.4 APAR JR07400 - Query Manager Icon Titles
3.5 Other Changes
3.5.1 Database Engine
3.5.1.1 Explain Support for Numeric Scalars
3.5.2 DOS\Windows Requester
3.5.2.1 DOS\Windows applications using Japanese Code pages
3.5.3 Query Manager
3.5.3.1 Large Output Queries
3.6 Questions and Answers
4.0 Part 4 - Select Pak 7010 JULY, 1993
4.1 Select Pak 7010 - Database Engine APAR Descriptions
4.1.1 APAR JR06827 - Blocking Selects
4.1.2 APAR JR06867 - Running in a LAN security shell
4.1.3 APAR JR06918 - Message Tokens
4.1.4 APAR JR06975 - Guest ID support not allowed
4.1.5 APAR JR07102 - Backwards Table scan
4.1.6 APAR JR07196 - Communication Performance
4.1.7 APAR JR07196 - Thread Termination
4.1.8 APAR JR07196/JR07197 - NetBIOS Communication Error
4.1.9 APAR JR07198 - Stopdbm Hang
4.1.10 APAR JR07300 - FFST/2 Trap
4.1.11 APAR JR07310 - MAXLOCKS
4.1.12 APAR JR07324 - Invalid Records
4.2 Select Pak 7012 - Query Manager APAR Descriptions
4.2.1 APAR JR06270 - Premature Termination when using Panels
4.2.2 APAR JR06371 - Negative Zeros (-0)
4.2.3 APAR JR06684 - Premature termination using list boxes
4.2.4 APAR JR06851 - Dutch Translation Error
4.2.5 APAR JR06882 - Exceptions when using Callable Interface
4.2.6 APAR JR06913 - Report Text Length
4.2.7 APAR JR06969 - Index Display of Column Names
4.2.8 APAR JR06986 - TAB/Arrow Keys in Procedures
4.2.9 APAR JR07179 - Package Name For Query Manager in DB2/2
1.0 Part 1 - Service Pak 7030 DECEMBER, 1994
1.1 Introduction
This Service Pak provides fixes to problems reported since General
Availability of Version 1.0.0. The effects and descriptions of these
changes to the product is the subject of the following topics.
1.2 Service Pak Installation
This Service Pak can be used to install fixes for all components of
DB2/2 v1.0 ( Database Engine, DOS/Windows Requester, Query Manager
and Database Administration Tools.)
NOTE: If you have
1) reinstalled DB2/2 v1.0.0 (GOLD) after 94/11/01 or
2) installed DB2/2 v1.0.0 (GOLD) on top of ES10 DBM after
94/11/01,
some of your DB2/2 DLLs may then have a later date/time stamp
than the DLLs in the service pak. However, the DLLs on your
system are actually not as recent as the ones in the service pak
and do not include any fixes in the Service 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 DB2INST install, then select YES when
prompted by the install program to overwrite the DLL already
on your machine with the Service Pak one.
If you are using the CID install (DB2CID), 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.
1.2.1 Pre-Requistes
This Service Pak can be applied to any of the following levels of DB2/2 v1.0
- DB2/2 v1.0.0 (GOLD, syslevel WR07000)
- Select Paks 7010, 7012 (syslevel WR07010)
- Service Pak 7015 (syslevel WR07015)
- DB2/2 v1.0.1 Refresh Code (syslevel WR07015)
- Select Paks 7022, 7023, 7025 (syslevel WR07025)
The Service Pak can be used to update all DB2/2 v1.0 configurations
(server, standalone, client, client with local databases and OS/2 distributed
client feature.)
1.2.2 Co-Requistes
In order to run with the new DDCS/2 v2.0 fixes in Service Pak 7031, you
must install BOTH the DB2/2 Service Pak 7030 and the
DDCS/2 v2.0 Service Pak 7031.
For client/server platforms, appropriate Service Paks should be
applied to all DB2/2 server and client workstations. This Service
Pak can be applied to all DB2/2 v1.0 servers and clients.
If this Service Pak is applied to DB2/2 v1.0 clients connecting to a
DB2/2 v1.2 server, or a DB2/2 v1.0 server acting as a host for
DB2/2 v1.2 clients, the Service Pak 7035 should be applied
to the DB2/2 v1.2 workstations.
1.2.3 Installation Instructions
To start the Presentation Manager Service Pak install, type DB2INST 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, an IBM DB2/2 Service or Select
Pak, IBM Lan Server/Requester, or IBM CM/2, please shutdown and reboot your
system before installing this DB2/2 Service Pak.
You may have to reboot twice, once after the installation of these products to
process any locked files, and a second time after installing this Service Pak
to process some additional locked files.
NOTE: 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.
1.2.4 CID Install Instructions
The Service Pak CID install program (DB2CID.EXE) uses the same syntax as the
DB2/2 CID install program. Refer to the DB2/2 Installation Guide for a
description.
For DB2/2 CID Service Pak install, please use the sample response file
DB2CID.RSP provided on diskette 1. This file can be modified to fit your
installation needs.
NOTE: The keywords found in DB2CID.RSP are the ONLY supported CID keywords in
this version of the CID install program. These keywords are:
DBBACKUPSYSTEM
DBSTOPCOMMUNICATIONS
DBUPDATECONFIGSYS
* DBUPDATETYPE
DBUSEREXIT1
DBINSTALLDATABASETOOLS
DBINSTALLQUERYMANAGER
DBINSTALLDOSREQSUPPT
DBINSTALLWINREQSUPPT
DBINSTALLDOCUMENTATION
** DBINSTALLENGINE
DBCOPY
DBINCLUDE
DBUSEREXIT2
** DBREPLACE
For a description of the CID install key words, refer to Appendix B of the
DB2/2 Installation Guide.
* NOTE (1): The CID keyword DBUpdateType can only be equal to 1, which specifies
to install the Service Pak. No other values are supported.
** NOTE (2): Two keywords have been added to support the Service 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 Service
Pak (1=YES 0=NO).
NOTE (3): 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.
NOTE (4): 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.
1.2.5 After Installation - IMPORTANT
1.2.5.1 Rebinding bind files
Due to new bind (.BND) files that have been shipped with this Service Pak,
you will need to rebind your DB2/2 bind files to your databases after the
Service Pak installation. This step is necessary for the fixes in this Service
Pak to become effective.
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 containing the SQLLIB directory).
The above step only needs to be performed once per database. If multiple
clients use the same database, the database needs rebinding on only one client.
1.2.5.2 Copying files from \os2\install directory
This Service Pak updates the files DBMLVL.ASC and DCFLVL.ASC
in \OS2\INSTALL directory of your workstation's boot drive.
These files are installed by the initial product install and also used
by the remove function. Without the newer versions of these files,
the remove function will not work. If you use the product diskettes
to remove the product
then you must TEMPORARILY change the .ASC files on diskette 1
to the new ones installed by the service pak. If you then use those
diskettes to do a product install you must put the original
versions of the .ASC files back onto the diskettes before installing.
To copy these files to diskette 1 of the product diskettes:
for DB2/2 diskette 1,
copy Y:\OS2\INSTALL\DBMLVL.ASC A: (where A: contains DB2/2 DISK 1)
(Y: is the workstation's boot drive)
for OS/2 DCF diskette 1,
copy Y:\OS2\INSTALL\DCFLVL.ASC A: (where A: contains OS/2 DCF DISK 1)
(Y: is the workstation's boot drive)
1.3 General Information
1.3.1 Service Information (US/Canada)
1.3.1.1 Database 2 OS/2 and Distributed Database Connection Services/2 Support
Call 1-800-992-4777 for information regarding free and chargeable
service options or to receive assistance on
- IBM DATABASE 2 for OS/2 (DB2/2) Version 1.2 and Version 1.0
- IBM Distributed Database Connection Services/2
(DDCS/2) Version 2.2 and Version 2.0
Assistance is also available using the electronic options described below.
1.3.1.2 Electronic Customer Support and Corrective Service
The following electronic support is available:
Customer support is provided via a questions-and-answers (Q&A) forum
provided by the DB2/2 Service Team. The forum is accessible
through CompuServe, IBMLink, and TALKLink as described below.
Corrective Service is provided in two forms - Select Paks
and Service Paks. A Service Pak contains all fixes that have
accumulated since the product first became generally available.
A Select Pak is a small group of fixes that have accumulated since
the last Select or Service Pak and can be packaged by components
within a product.
Service Paks will be issued approximately every 6 to 8 months
and Select Paks may be issued approximately every 3 to 4 months
depending on the number, severity and visibility of fixes that have
accumulated.
If you cannot obtain these Select or Service Paks electronically please
call 1-800-992-4777 to request them to be sent to you in the mail.
1.3.1.3 Accessing Corrective Service and Customer Support
CompuServe - call 1-800-848-8199 in Canada or the US for membership information.
-Execute GO IBMDB2.
-Use DB2/2 section for questions and answers.
-Use DB2/2 library for fixes and other files.
US (IBMLink) TALKLINK OS/2 BBS call 1-800-547-1283 for membership information.
-Go to OS2BBS in TALKLINK.
-Choose Service Package section (Corrective Service only).
-Access DB2OS2 FORUM (Q&A and Technical Support).
Canadian IBMLink OS/2 BBS - call 905-474-6666 or 1-800-268-3100 for
membership information.
-Go to IBMLink from the IIN Menu.
-Type ICONF on the IBMLink Desktop.
-Select View from the Conference File Selection List.
-Select Option 5 Select Files and type: WR* * (NOTE: these two asterisks are
wildcards) (Corrective Service only).
-Select DB2OS2 FORUM (Q&A and Technical Support).
The Select and Service Paks are also available on the Technical
Connection CD ROM. To order call 1-800-992-4777.
The next methods are available for Corrective Service only.
Internet.
-FTP to anonymous server software.watson.ibm.com (129.34.139.5).
-Enter 'anonymous' as the userid and your complete e-mail address as the
password.
-Go to pubs/db2/os2 directory.
Canadian IBM PS BBS - to dial into the BBS call 905-316-4255 Toronto,
416-492-1823 Toronto, 514-938-3022 Montreal, or 604-664-6464 Vancouver
(8 databits, no parity, 1 stop bit).
-Go to area 34 OS/2 Database and Host.
US IBM PCC BBS - to dial into this BBS, call 919-517-0001 Raleigh (8 databits,
no parity, 1 stop bit).
-Go to Directory 4 (the CSD Directory).
1.3.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
2S/110/1150/TOR
1150 Eglinton Avenue East
North York, Ontario
Canada, M3C 1H7
Attn: T.D. Sole
Fax: (416) 448-2114
1.3.3 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
1.4 Defects Fixed
This section describes changes that have been made to the product as a result
of direct customer feedback. The descriptions contained in this section are for
the fixes that have gone into the product since Select Paks 7025, 7023, and
7022 shipped.
1.4.1 Database Engine APAR Descriptions
1.4.1.1 APAR JR00056: Incorrect Connection Information
When a DB2/2 user connnected to DB2/6000 or other DB2 workstation platforms,
the connection information returned was incorrect.
This is a further fix to the same problem corrected in Select Pak 7025.
1.4.1.2 APAR JR07732: Hang on CONNECT
This fix prevents a database client from hanging at a database
'CONNECT' request to a remote database.
1.4.1.3 APAR JR07740: SELECT - ORDER BY fails with SQL0902
A SELECT with ORDER BY clause against a view, if the order by element
was a constant, returned SQL0902. For example, previously it was
not possible to perform the following query on a view V1 created
with column X as a constant:
SELECT * FROM V1 ORDER BY X
This problem has been fixed and the error SQL0902 is no longer returned
under such circumstances.
1.4.1.4 APAR JR07869: "STATUS" no longer a reserved word in REXX
The error SQL0104 resulted in REXX applications, if the keyword "STATUS"
was used as an indentifier. "STATUS" is no longer a reserved word in
REXX applications and can be used as a host variable name.
1.4.1.5 APAR JR07918: SQLCIAA trapped when Netbios session broken
Previosly a broken netbios connection between a DB2/2 server and a client
caused the SQLCIAA agent at the server for that netbios session to trap.
This problem has been fixed and the netbios session no longer traps at
the server if the netbios connection to a client is severed.
1.4.1.6 APAR JR07919: DBM GET SYSTEM STATUS failed
DBM GET SYSTEM STATUS did not work properly in a remote program load
environment. SQLCODE 0004 was returned rather than displaying the status.
This fix has corrected the problem.
1.4.1.7 APAR JR07970: SYS3175 with many NETBIOS clients
A SYS3175 or SYS3171 trap error was encountered in SQLC.DLL on systems
utilizing multiple LAN adapters for DB2 when there were many NETBIOS clients.
The DB2/2 NetBIOS protocol design has been modified to prevent the
trapping situation from occuring.
1.4.1.8 APAR JR07973: UPDATE returned invalid ROW COUNT
Previosly an UPDATE instruction like
UPDATE SET COL1 = 'aaa' where col2 = bbb
sometimes generated an invalid row count in SQLCA.SQLERRD(3)
if an index existed on the same columns as in the UPDATE
statement. This was caused due to the fact that after a row
was updated, it was relocated in the index file, making it susceptible
to be updated again with the same information, producing an
invalid row count.
This defect has been fixed to ensure that the row count in SQLERRD2
will be incremented correctly while updating a row in an indexed table/view.
1.4.1.9 APAR JR08020: SQLSTATE set to blanks after FETCH
Previously, an application precompiled with /L=0 (default option)
caused the SQLSTATE to be set as blanks (i.e. SQLSTATE=' ')
after a FETCH instruction, causing NULL truncation.
This problem has been rectified.
1.4.1.10 APARs JR08022, JR08150: Memory leak in SQLEFREE API
Repeated calls to SQLEFREE API could have resulted in the following error:
SQL1022: There is not enough memory available to process this command.
A fix has been implemented to prevent this memory leak.
1.4.1.11 APAR JR08057: Log full errors
Previously customers performing an IMPORT REPLACE on 3 tables consequtively,
each while the target table already existed, encountered problems.
During the first IMPORT, 1 log full was encountered, however the importing
completed successfully. The second IMPORT encountered many log full scenarios,
while allowing the IMPORT to continue each time. The third IMPORT failed
when attempting to truncate the target database.
These problems have been fixed.
1.4.1.12 APAR JR08061: SYS3171 if network id for APPN workstation set to null
In the past if a user cataloged an APPN workstation and specified NULL for the
Network ID, a trap message similar to the following one was received when
the user tried to connect:
SYS3171 in ACSSVC.DLL 0005:13fe4148
This has been fixed to enable the user to connect successfully from
an APPN workstation without encountering a system trap.
1.4.1.13 APAR JR08111: DB22KILL failed
When invoked, DB22KILL did not always disconnect all APPC client
connections to the DB2/2 server. This fix corrects the problem.
1.4.1.14 APAR JR08153: Inexact Floating Point Exception
If in a 16-bit COBOL application the FLOATING POINT INEXACT BIT was not
masked, the application intermittently saw Inexact Floating Point
exception when it issued CONNECT TO a database.
To function properly, DB2/2 requires the INEXACT BIT to be masked.
DB2/2 now detects the INEXACT EXCEPTION and masks the INEXACT BIT
explicitly to prevent the application from seeing the trap.
1.4.1.15 APAR JR08155: Truncated value of NP,FP in DBM REORGCHK
When a DBM REORGCHK was performed, the NP and FP values were truncated
if the number of pages in SYSIBM.SYTABLES exceeded 99999. NP and FP can
be up to 6 digits long and this fix ensures their values are not truncated.
However, this fix may cause DBM REORGCHK output to misalign and/or
exceed 80 characters in width when NP and FP are large.
1.4.1.16 APAR JR08157: APPC error F015-00000000
Previously database applications connecting/disconnecting from a database
accessed via APPC sometimes received the APPC error sense code:
F015-00000000 Insufficient stack size
This problem has been resolved.
1.4.1.17 APAR JR08180: RUNSTATS returned incorrect results
Prior to the implementation of this fix, running statistics (RUNSTATS) returned
incorrect AVECOLLEN (average column length) under certain circumstances.
This fix corrects the problem.
1.4.1.18 APAR JR08211: PCDR clients intermittently lost connection
When PC DOS Requester (PCDR) clients were connected to a DB2/2
server, the server could get into a state where it would lock out
further PCDR clients from establishing a connection. However, the
server continued to function properly for the clients still connected
to it.
This problem has been fixed to prevent new PCDR clients from being
locked out by the server.
1.4.1.19 APAR JR08218: SQL1042 when doing ROLLFORWARD AND STOP
If the use of a database was abnormally terminated, e.g. due to a power
failure, the subsequent recovery of the database, using the command
ROLLFORWARD AND STOP, generated the following error message:
SQL1042 An unexpected system error occured.
This message could also be produced after the STOP button was pressed
in the recovery tool, if the backup of the abnormally terminated database
was restored using rollforward from the recovery tool . The error only
occured if the database was configured with USEREXIT=ON and LOGPRIMARY=63.
This has been fixed and the SQL1042 is no longer returned under such
circumstances.
1.4.1.20 APAR JR08257: Floating point exception errors
This fix adds floating point exception protection to handle floating
point underflow/overflow errors. Floating point exceptions have
the potential to trap the operating system. This fix sets the estimate
number of records involved in a query to default to a system
minimum/maximum when a floating point exception is encountered,
thereby preventing a system trap.
1.4.1.21 APAR JR08263: Fix for DB2/2 running on WARP
Previosly DB2/2 DLLs were not being unloaded appropriately from the
memory in OS/2 WARP 3.0. Prior to this fix, NetViewDM/2 encountered
problems while running concurrently with DB2/2 on WARP.
This fix is necessary for Net View DM/2 users requiring support for DB2/2
in the WARP release of OS/2.
1.4.1.22 APAR IX45867: Fortran precompiler problem
The Fortran precompiler did not have a provision for identifiers that began
with keywords (e.g. end, program, function, subroutine, etc.).
If a Fortran source file with embedded SQL statements had variables
such as endFlag and programName, the Fortran compiler produced a
redeclaration error for the generated Fortran source. This fix corrects
the problem and allows identifiers to begin with keywords.
1.4.2 Other Database Engine Fixes
1.4.2.1 Unable to STARTDBM with IPX
IPX users receievd the error SQL1066N upon issuing STARTDBM under the
following conditions:
1) The database(DB) server's Netware connection table had more than one entry;
2) The connection to the Netware file server that the DB server searched
for was not in the LAST entry of the table; and
3) A bindery object with the same name that the DB server was
using already existed.
The error message SQL1066N is no longer recieved under the above mentioned
conditions.
1.4.2.2 Importing from CD-ROM failed with SQL3025N
Previously, an error occurred when trying to import data from a CD-ROM drive.
The following error code was returned:
SQL3025N: The datafile parameter is not valid.
This fix has corrected the problem.
1.4.2.3 UPM node logon
While connecting to a DB2/MVS database via DDCS/2 or to a remote DB2/2
database from a DCF client or a DB2/2 client the user is prompted for a
UPM node logon for starting the first session. Sessions started subsequently
from the client to the same node do not prompt for a UPM logon.
Previously however, several minutes after two or more sessions
were successfully started from the client to connect to the same node, a UPM
logon panel popped up on the client machine, even though there was no attempt
made on the client machine to open another session. This logon panel contained
corrupted node information and hung up the existing sessions on the client.
This problem has been fixed and the erroneous logon panel is no longer
displayed.
1.4.3 DOS/Windows Requester APAR Descriptions
1.4.3.1 APAR JR07968: SQL30080 when trying to use alternate adapter
Previously, a DB2/2 DOS Client received SQL30080 RC=15 while attempting to use
an alternate adapter if the workstation was configured for both primary and
alternate adapters. This fix correct the problem.
1.4.4 Query Manager (QM) APAR Descriptions
1.4.4.1 APAR JR07346: Incorrect data in header text
Incorrect data was displayed in the header text of a Query Manager report
using a form. This error occured if a variable column (eg. &N) was
referenced in the header text of the report and the report exceeded 1 page
per break (breaks are used to group the report output by unique column
values). This problem has been fixed.
1.4.4.2 APAR JR07467: Problem with BREAKS in QM forms
In a Query Manager form, if there were only a few lines on a page
before a BREAK, then a new page would not be started after the break.
This problem has been fixed.
1.4.4.3 APAR JR07475: Could not use 3 or 9 as mnemonic keys
When creating a Query Manager Menu, users can specify a
mnemonic for each menu action. This allows them to press just
the mnemonic key to execute the menu action when the menu is
being run. The problem was that a mnemonic of 3 or 9 did not work
if 3 or 9 was pressed on the number pad. Instead, page up and page
down were performed. All other numbers on the keypad worked
fine as mnemonics. This fix allows 3 and 9 to be used as mnemonic
keys on the number pad.
1.4.4.4 APAR JR07904: Invisible text while changing row conditions
After creating a prompted query, if you try to change the row
conditions, you get a window titled "Change Left-Side of row
condition". Prior to this fix, the text in this window was partly
invisible (blanked out). This fix allows the text to be viewed
in its entirety.
1.4.4.5 APAR JR07797: Extra headers for updated records
Previously, forms produced to display QM output had more than one header
in the output. Extra headers were generated before the entries for updated
records. This fix ensures no additional headers are received in in the QM
output forms.
1.4.4.6 APAR JR08152: Shift-F9 did not bring up Command line window
In Query Manager (QM), once in the "main selection" for a database, the
Commands pulldown menu indicates that Shift-F9 can be used to bring up the
command line pop-up window. Shift-F9 did not bring up the QM Command
line pop-up window. This fix corrects the problem.
1.4.4.7 APAR JR08198: QRW0541 with TRACE ON
On a DBCS system (JAPAN), Query Manager (QM) returned QRW0541 RC= 11008
when trying to initialize. This occured if OS/2 System trace was on. This
fix corrects the problem and allows QM to initialize with TRACE ON.
1.4.5 Database Administration Tools (DBAT) Changes
Minor copyright changes have been made to Database Administration Tools.
Parts 2,3 and 4 are in the file README.OLD on Diskette 1.
***********************************************************************
** **
** (c) COPYRIGHT INTERNATIONAL BUSINESS MACHINES CORPORATION 1994. **
** ALL RIGHTS RESERVED. **
** **
***********************************************************************