CAE/2 (WR07094) v1.2 & SDK/2 (WR07095) v1.2 FixPak APAR information =================================================================== FixPaks WR07094,WR07095 ----------------------- APAR IC10328: SQLSTATISTICS result in a syntax-error SQL statement APAR IC10437: sqln=0 & sqld>sqln in SQLDA for FETCH brings Server down APAR IC10798: SYSOWNER keyword is ignored if specified on connect string APAR IC10903: MS QUERY CANNOT ACCESS TO SYNONYM IN SQL/DS DATABASE APAR IC11014: GPF when a number of ODBC apps open/close connections intercha APAR IC12009: GPF in DB2W.DLL durinng connect from ODBC app APAR IX48568: Better estimate the size of a backup to an adsm server APAR IX52278: CLP truncates the results of a query and returns DB21018E. APAR IX54235: bind with grant does not commit APAR IX56697: APP terminates when appc session is killed (SIGUSR1) APAR JR08474: Login SDK/2,CAE/2 ---> DB2/2 successful with blank userid APAR JR08493: server does not return the fifth token in SQLERRMC field APAR JR08526: SDK/2 Hangs for a select with large number of columns APAR JR08620: Problem Description APAR JR08633: SQLSTATE 7002 on a select from MS Excel with 1.2 and 2.1 DB2 APAR JR08705: log info in sqlofica at a lower level & check level 1st APAR JR08769: Issue t_sndis async. APAR JR08887: SQL3025N: IMPORT a file from NFS mounted drive into a remote D FixPaks WR07043,WR07048 ----------------------- APAR JR08296: Numeric LU names rejected when cataloging APPN nodes When issuing 'Catalog APPN Node' with a numeric Local LU name or Local Partner LU name, the numeric name was rejected. But, using CM/2 (Communications Manager/2), or DB2/2's database directory tool (DIRECT), a numeric name was accepted. This fix corrects the problem with the 'Catalog APPN Node' accepting numeric names. APAR JR08351: SYS3171 in QUECALLS.DLL calling CM/2 Previously, applications accessing a database using the APPC protocol could receive stack overflow errors. Errors may have been in the form of F015 in Communication Manager/2 (CM/2), or system trap SYS3175. This has been fixed. APAR JR08352: No FFST folders after installing product Previously, the FFST folder may have been removed during installation if CM/2 1.11 was already installed on the system. This problem has been fixed. APAR JR08404: Export from DB2/2 v2.1 from CAE/2 v1.2 client Hangs Previously, the CAE/2 v1.2 or SDK/2 v1.2 client would 'hang' after a successfull connection to a DB2/2 v2.1 (beta) server, using the NETBIOS protocol. This problem has been fixed. APAR JR08430: SQLBIND returns LF-CR instead of CR-LF Previously, when redirecting the SQLBIND output to a file, the utility generated a () as the first two characters in the file instead of the expected . Prior to this fix correcting the problem, using the /M option would produce the desired as expected. APAR JR08456: Downlevel server interrupt problem Previously an interrupt issued from a CAE/2 v1.2 or SDK/2 v1.2 client against a DB2/2 v2.1 (beta) or DB2/6000 v2.1 (beta) server was ignored when using the NETBIOS or IPX/SPX communications protocol. This fix corrects the problem. FixPaks WR07037,WR07038 ----------------------- APAR IC08006 : Lotus Query Fails While connected to DB2/6000, the client did not handle code page specific queries from Lotus correctly. This fix corrects the problem. APAR IC08044 : Detach from Novell Fileserver Previously, after the CAE/2 client attached to the Novell fileserver to read the bindery object containing the network address of the OS/2 DB2/2 server, the client did not subsequently detach from the fileserver. This fix corrects the problem. Now, after reading the bindery object, the client remains attached only if had been previously attached to the fileserver, otherwise it detaches from the fileserver. 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. APAR IX46939 : TCP/IP is NON-BLOCKING The send function of TCP/IP is NON-BLOCKING, meaning that we are unable to verify that the entire buffer will all be sent in one send call. This resulted in the client hanging. This fix corrects the problem by checking for partial sends. APAR JR08143 : Logon Password, 8 character maximum When a CAE/2 application connected to a DB2/6000 server which had a password longer than 8 characters, the application would receive the error 'SQL0567N "" is not a valid authorization ID'. This was caused by CAE/2 truncating the password to 8 characters. This fix corrects the problem. APAR JR08175 : Domain logons not treated as valid logon Domain logins were not considered to be a valid remote login. This fix corrects the problem. APAR JR08263 : Unloading UPM or NETAPI DLLs This fix prevents CAE/2 from unloading the UPM or NETAPI DLLs unless we have explicitly loaded them within CAE/2. Applications loading either of these DLLs will require this fix when integrating with CAE/2 on OS/2 Warp. *********************************************************************** ** ** ** (c) COPYRIGHT INTERNATIONAL BUSINESS MACHINES CORPORATION 1996. ** ** ALL RIGHTS RESERVED. ** ** ** ***********************************************************************