CAE/2 v1.2 (WR07043) & SDK/2 v1.2 (WR07048) Service Paks ======================================================== Welcome to DB2 OS/2 Client - DB2 Client Application Enabler/2 (CAE/2) v1.2 - DB2 Software Developers's Kit/2 (SDK/2) v1.2 Please see section 1.2 for Service Pak install information Service Pak WR07043 should be used to update clients that were installed using CAE/2 v1.2 product diskettes. Service Pak WR07048 should be used to update clients that were installed using SDK/2 v1.2 product diskettes. PART 1 of this file contains important information about these Service Paks. It includes installation instructions and details changes to the product since the shipping of Service Paks WR07037 and WR07038. WR07043 and WR07048 are cumulative Service Paks and contain all code changes since the initial product was released. NOTE (1): If an existing version of CAE/2 or SDK/2 is executing it should be stopped before applying the Service Pak. NOTE (2): If you have received private fixes from IBM Support after 95/05/04, then you should contact IBM support after the Service Pak installation, to request an updated version of the provate fixes. By doing this, you are assured that your system is in a consistant state and no private fixes are lost. ======== Contents 1.0 PART 1 - Service Pak WR07043 & WR07048, May 1995 1.1 Introduction 1.2 Information for installing this Service Pak 1.2.1 Pre-Requisites 1.2.2 Installation Instructions 1.2.3 CID Install Instructions 1.2.4. After Installation (IMPORTANT) 1.2.4.1 Copying files from \OS2\INSTALL directory 1.3 General Information 1.3.1 Service Information (U.S.A / Canada) 1.3.1.1 CAE/2 and SDK/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 CAE/2 & SDK/2 APAR Descriptions 1.4.1.1 APAR JR08296: Numeric LU names rejected when cataloging APPN nodes 1.4.1.2 APAR JR08351: SYS3171 in QUECALLS.DLL calling CM/2 - cae/2 only 1.4.1.3 APAR JR08352: No FFST folders after installing product 1.4.1.4 APAR JR08404: Export from DB2/2 v2.1 from CAE/2 v1.2 client Hangs 1.4.1.5 APAR JR08430: SQLBIND returns LF-CR instead of CR-LF 1.4.1.6 APAR JR08456: Downlevel server interrupt problem 2.0 PART 2 - Service Pak WR07037 & WR07038, January 1995 2.1 Defects Fixed 2.1.1 CAE/2 & SDK/2 APAR Desciptions 2.1.1.1 APAR IC08006 : Lotus Query Fails 2.1.1.2 APAR IC08044 : Detach from Novell Fileserver 2.1.1.3 APAR IX45867 : Fortran Precompiler problem 2.1.1.4 APAR IX46939 : TCP/IP is NON-BLOCKING 2.1.1.5 APAR JR08143 : Logon Password, 8 character maximum 2.1.1.6 APAR JR08175 : Domain logons not treated as valid logon 2.1.1.7 APAR JR08263 : Unloading UPM or NETAPI DLLs 2.1.2 First Failure Support Technology (FFST) CSD 485 2.1.2.1 CM alerts not being received at host 2.1.2.2 NO INHERIT bit was not set 2.1.2.3 Trap in EPWCUA.DLL when using software installer to INSTALL 2.1.2.4 Starting EPW.EXE caused a ghost window in minimized window viewer 2.1.2.5 Multiple Message Log Formatters Displayed 2.1.2.6 Trap D in DOSCALL1:DOSSEMSET as called by EPWSVC16 2.1.2.7 Verify Hang/CMSTOP ABNORMAL did not work on CM 1.11 2.1.2.8 Make EPWINST use WPS icons on OS/2 2.0 and above 2.1.2.9 FFST/2 Message Log Formatter caused SYS3175 on OS/2 WARP 1.0 PART 1 - Service Pak WR07043 & WR07048, May 1995 1.1 Introduction This Service Pak provides fixes to problems reported since the initial release of the products. The effects and descriptions of these changes is the subject of the following topics. 1.2 Service Pak Installation 1.2.1 Pre-Requisites The CAE/2 Service Pak can be applied to the following level of CAE/2 v1.2 - CAE/2 v1.2.0 (GOLD, syslevel WRx7000) - Service Pak WR07037 (syslevel WRx7037) - CAE/2 v1.2.1 Refresh Code (syslevel WRx7037) The SDK/2 Service Pak can be applied to the following level of SDK/2 v1.2 - SDK/2 v1.2.0 (GOLD, syslevel WRx7000) - Service Pak WR07038 (syslevel WRx7038) - SDK/2 v1.2.1 Refresh Code (syslevel WRx7037) (where letter 'x' in the db21v1 indicates the country code for this Service Pak: Country x U.S.A. 0 France F Italy I Germany G Japan J Spain S ) NOTE: This Service Pak cannot be applied to any version of DB2/2 Query Manager, Distributed Client Feature. These products have a separate Service Pak. 1.2.2 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 CAE/2 v1.2 OR SDK/2 v1.2 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 files, please be aware that any files that already exist in the backup directory you specify will be overwritten. If you want multiple levels of backups please specify different backup directories. 1.2.3 CID Installation Instructions The Service Pak CID install program (DB2CID.EXE) uses the same syntax as the CAE/2 & SDK/2 install program. Refer to the DATABASE 2 Client Application Enabler/2 User's Guide (version 1.2), Chapter 3, for a description. For CAE/2 & SDK/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: * DBUpdateType DBBackupSystem DBStopCommunications DBUpdateConfigSys DBInstallQueryManager ** DBInstallEngine DBReplace For a description of the CID install keywords, refer to Appendix J of the DATABASE 2 Client Application Enabler/2 User's Guide (version 1.2). * 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 client database engine - 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 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 levels of backups please specify different backup directories. 1.2.4 After Installation (IMPORTANT) 1.2.4.1 Copying files from \OS2\INSTALL directory This Service Pak updates the file DB2LVL.ASC in \OS2\INSTALL directory of your workstations boot drive. This file is installed by the initial product install and also used by the remove function. Without the newer version of this file, the remove function will not work. If you use the product diskettes to the remove the product then you must TEMPORARILY change the DB2LVL.ASC on diskette 1 to the new one installed by the Service Pak. If you then use those diskettes to do a product install you must put the original DB2LVL.ASC file back onto the diskette before installing. To copy this file to diskette 1 of the CAE/2 OR SDK/2 product diskette: copy Y:\OS2\INSTALL\DB2LVL.ASC A: (where A: contains CAE/2 or SDK/2 DISK 1 Y: is the workstation's boot drive ) 1.3 General Information 1.3.1 Service Information (U.S.A / Canada) 1.3.1.1 CAE/2 and SDK/2 Support Call 1-800-992-4777 for information regarding free and chargeable service options or to receive assistance on - IBM Client Application Enabler/2 (CAE/2) Version 1.2 - IBM Software Developer's Kit/2 (SDK/2) Version 1.2 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 by Service Paks. A Service Pak contains all fixes that have accumulated since the product first became generally available. Service Paks will 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 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 CLIENTS section for questions and answers. -Use CLIENTS 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 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 ps.boulder.ibm.com (198.17.57.66) -Enter 'anonymous' as the userid and your complete e-mail address as the password. -Go to ps/products/db2/fixes NOTE: The ps.boulder.ibm.com FTP site contains Corrective Service for all languages supported by the family of DB2 workstation products. OR -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. c/o Tina Kocevski Grenville Management & Printing 25 Scarsdale Rd. Don Mills, Ontario Canada M3B 2R2 Fax: (416) 449-4119 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 group at TOROLAB2(DBMREQ) * Or, send your detailed requirements to the following address: IBM Canada Ltd. c/o Tina Kocevski Grenville Management & Printing 25 Scarsdale Rd. Don Mills, Ontario Canada M3B 2R2 Fax: (416) 449-4119 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 CAE/2 Service Pak WR07037 (syslevel WRx7037) and SDK/2 Service Pak WR07038 (syslevel WRx7038) was shipped. 1.4.1 CAE/2 & SDK/2 APAR Descriptions 1.4.1.1 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. 1.4.1.2 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. 1.4.1.3 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. 1.4.1.4 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. 1.4.1.5 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. 1.4.1.6 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. 2.0 Part 2 - Service Pak WR07037 & WR07038, January 1995 2.1 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 CAE/2 v1.2.0 (GOLD, syslevel WR07000) and SDK/2 v1.2.0 (GOLD, syslevel WR07000) was shipped. 2.1.1 CAE/2 & SDK/2 APAR Descriptions 2.1.1.1 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. 2.1.1.2 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. 2.1.1.3 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. 2.1.1.4 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. 2.1.1.5 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. 2.1.1.6 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. 2.1.1.7 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. 2.1.2 First Failure Support Technology (FFST) CSD 485 The FFST/2 CSD 485 is shipped with this Service Pak. The descriptions of FFST changes since CSD 460 (shipped with CAE/2 v1.2 WR07000 or SDK/2 v1.2 WR07000) are described in this section. 2.1.2.1 CM alerts not being received at host When using the alert generating program to route Communications Manager (CM) alerts through CM gate-way to Netview host it was found that alerts were not being received at the host. This fix corrects the problem. 2.1.2.2 NO INHERIT bit was not set Pipe handles did not have the NO INHERIT bit set. This fix sets the NO INHERIT bit. 2.1.2.3 Trap in EPWCUA.DLL when using software installer to INSTALL When installing a product that uses IBM Software Installer Version 1.1 for OS/2 a trap occured in EPWCUA.DLL. The trap occurred a number of seconds after the installation had indicated that it was complete and 'hung' the OS/2 prompt from which "a:install" was typed. This fix corrects the problem. 2.1.2.4 Starting EPW.EXE caused a ghost window in minimized window viewer Executing EPW.EXE from anything other than CONFIG.SYS caused a ghost window to appear in the Minimized Window Viewer. For example, if EPW.EXE was not running, executing EPW.EXE from the command line would produce the ghost window. Also, If EPW was running, executing EPW OFF, then EPW ON produced the ghost window as well. Another time this problem occured was when FFST/2 was stopped and started via Dos calls (DosExecPgm) from code. This fix corrects the problem. 2.1.2.5 Multiple Message Log Formatters Displayed The problem occured when 1 copy of the message log formatter was open and another was inadvertantly started. The user receives a pop-up asking if they would like to open another message log formatter. The reply is either OK or CANCEL. If CANCEL was chosen and a second copy was started anyway. This fix corrects the problem. 2.1.2.6 Trap D in DOSCALL1:DOSSEMSET as called by EPWSVC16 When starting the message log formatter a trap occured when running the following scenario: Four 3270 sessions were running over a Token-Ring network with an ehllapi application running in a loop that searches continuously for a particular string to appear in a session. After a long period (ie. 24 hours) and the log formatter is started a trap D sometimes occurs in DAOCALL1:DOSSEMSET. This fix corrects the problem. 2.1.2.7 Verify Hang/CMSTOP ABNORMAL did not work on CM 1.11 The problem occured when an X.25/ISDN configuration running on Communications Manager (CM) 1.11 was stopped abnormally through SSM and then CMSETUP.EXE was started. When exiting out of CMSETUP, verification of the configuration never ended (was hung) and CM would not stop. This fix corrects the problem. 2.1.2.8 Make EPWINST use WPS icons on OS/2 2.0 and above This fix installs the FFST OS/2 2.0 icons for OS/2 versions 2.0 or greater. For OS/2 versions before 2.0, FFST OS/2 1.3 icons are installed. 2.1.2.9 FFST/2 Message Log Formatter caused SYS3175 on OS/2 WARP After running the Message Log formatter from FFST/2 a SYS3175 error was encounterd. The problem occured on OS/2 WARP while running FFST/2 concurrently with CM/2 1.11. This fix corrects the problem. *********************************************************************** ** ** ** (c) COPYRIGHT INTERNATIONAL BUSINESS MACHINES CORPORATION 1995. ** ** ALL RIGHTS RESERVED. ** ** ** ***********************************************************************