VISIT OUR PAGES ON THE INTERNET _______________________________ http://www.ibm.com/software/network/support On this page, you can find: Newsgroups, code fixes, the Software Alert, Tips, and other information. From the 'pull down box,' select the product that you are interested in. ********************************************************************* * * * DATE: 03/15/2002 * * * * * * DESCRIPTION: CSA6112 * * * * README FILE FOR IBM Communications Server for OS/2 * * Warp, Version 6.1 * * * * APAR: Multiple APAR fixes, see below. * * * * * * * * This package contains APAR fixes to the product above. This * * package can be distributed to anyone who has a license for * * this product. * * * ********************************************************************* PREREQUISITES : IBM Communications Server for OS/2 Warp, _____________ Version 6.1 CSA6112 supersedes CSA6121, CSA6111 PROBLEMS FIXED in this Package: ______________________________ APARs by CSA6112: JR15642 CMLINKS H DLURXX FAILS TO INACT DLUR JR16249 FIXED PACING ANYNET CICS HOST 1002 SENSE JR16315 EEDLC FAILS GETHOSTBYNAME - FIXED ADDRESS WORKS JR16816 UPDATE TRACE FOR CCB CALLS TO MATCH LINKS JR16618 BACKUP LINK HAS INVALID AUTOREACT TIMER VALUES JR16182 STOP HPT RTP ALIVE TIMER DURING DALLY-TIME JR16817 OWNER_DIED RC POSTING SLI ACSSLI.DLL APARS added by CSA6121: JR16323 TRAP ON CMSTOP CAUSED BY TCPIP NEVER STARTED JR13626 PCOM 4.1 SENDS 0E01F4 IN XID, CAUSES LUM TRAP JR15691 DLUR SESS HANGS WHEN NMVT REQ CHAINED DATA JR16327 CORR REL & COMP_ID IN FOR XID AND NMVT JR15800 HOST NO RESP TO UNBIND(08), GW HANG LU JR15826 WKS DISC W/LULU, NO RET LU TO POOL W/TERMSELF JR15945 TN3270 SERVER SERVICE WILL NOT START JR16327 SENSE 08910004 IF NN'S NOT SAME SUBNET JR16148 CMSETUP /R WITH IP DIGIT 0 FAILS ON EEDLC JR16322 ADD ADJ_XID_CP_NAME TO ACTIVE LINKS DISPLAY JR16324 INACT LINK AT DSEN CAUSES GW TO TRAP JR15615 TRAP ACSGWSCP+1EC2 ON 6.1 W/POOLED LU JR16325 GATEWAY FAILS TO FRWD NOTIFY IF DEMAND_SDDLU APARS added by CSA6111: JR15642 PARTNER LU DELETED FROM DIRECTORY JR15168 CMR0243E FLOOD MESSAGE LOG WITH BN LINK JR15187 HPR W/CP-CP SUPP=NO SHOULD ACTIVATE IF CF=YES JR15189 CMLINKS SESS FIELD INCORRECT WITH MLTG LINKS JR15156 LUA LU_LU SESSION MAY BE LOST IF DLUR PIPE IS LOST. JR15157 CMSTOP SOFT(NORMAL) NOT PROPERLY CLOSING HPR CONN JR15644 EEDLC SENDS DATA OUT ON WRONG PRIORITY PORT JR15681 PBM PCI INTERNAL V.90 MODEM HANGS SYSTEM WHEN CONNECTING JR15225 EEDLC TRAP WHEN LINK DEACTIVATES WHILE SENDING AT SAME TIME JR15647 ALLOW NN CONNECTION TO ADJACENT CP WITHOUT CP-CP SESSIONS JR15300 REMOVE LOCATE PARTNER FOR DEPENDENT LU IF ACTLU RECEIVED JR15650 MODEM LIST SHIPPED IN V6.0 AND V6.1 NEEDS TO ANSWER CALLS JR15364 RTP TCID STOLEN BY OTHER NODES AFTER RESTART JR15395 GATEWAY HOST LINK LOSS WITH HPR/DLUR LEAVES D/S LU HUNG. JR15651 ALLOW 0 HANDLE FOR ANR DLC DEVICE DRIVER JR15412 LAN LINK FAILS TO REACTIVATE WITH SC 1016000B JR15497 GATEWAY MAY DISCONNECT HOST LINK WHEN D/S WKST DISCONNECTS JR15459 CMVC OWNER SWITCH ON LEN LINK GIVES 080E000B ON BIND JR15652 LINK AUTO REACT INITIAL TIMER VALUE ADDS INCR VALUE JR15615 TRAP IN ACSGWSCP + 1EC2 WITH POOLED LU, NO LU FREE NOTE: You can find the APAR text via http://www.ibm.com/software/network/support ___________________________________________________________________ INSTALLATION INSTRUCTIONS __________________________ NOTES This package of APAR fixes can be applied either to a target workstation or to a code server directory. This package of fixes can be applied to all language versions of Communications Server for OS/2 Warp, Version 6.1. PARTS IN THIS PACKAGE 2-19-02 5:37p 250 B05.ZIP 2-19-02 5:37p 93899 B12.ZIP 2-19-02 5:37p 149654 B13.ZIP 2-19-02 5:37p 479431 B22.ZIP 2-19-02 5:37p 478658 B23.ZIP 2-19-02 5:37p 105968 B24.ZIP 2-19-02 5:37p 45331 B28.ZIP 2-19-02 5:37p 58156 B32.ZIP 2-19-02 5:37p 147479 B44.ZIP 2-19-02 5:37p 238441 B46.ZIP 2-19-02 5:37p 66899 B48.ZIP 2-19-02 5:37p 277289 B50.ZIP 2-19-02 5:37p 113352 B57.ZIP 2-19-02 5:37p 20137 B60.ZIP 2-19-02 5:37p 6880 B65.ZIP 2-19-02 5:37p 6134 B66.ZIP 2-19-02 5:37p 21301 B78.ZIP 2-19-02 5:37p 334931 B87.ZIP 2-19-02 5:37p 798522 B97.ZIP 2-19-02 5:37p 2138 BUNDLE.LST 1-15-01 12:50p 38970 COMMAC.SYS EXECUTABLES UPDATED 02-14-02 09:54 31232 CMLIB/ACSAPLDR.EXE 07-27-01 16:18 21516 CMLIB/ACSRASP.EXE 01-28-01 23:25 134277 CMLIB/ACSSBMGT.EXE 01-15-01 13:07 43649 CMLIB/ASYNCM.LST 01-15-01 12:50 38970 CMLIB/COMMAC.SYS 01-28-01 23:31 93329 CMLIB/DISPLAY.EXE 02-14-02 09:54 883712 CMLIB/DLL/ACSAPPC.DLL 02-14-02 09:54 83968 CMLIB/DLL/ACSGWSCP.DLL 01-15-01 12:40 3912 CMLIB/DLL/ACSHPRDL.DLL 02-14-02 16:30 31731 CMLIB/DLL/ACSRUI.DLL 02-14-02 09:54 167936 CMLIB/DLL/ACSRUI16.DLL 02-14-02 16:31 63169 CMLIB/DLL/ACSSLI.DLL 02-14-02 16:30 128297 CMLIB/DLL/APPNCFG4.DLL 07-27-01 16:21 422440 CMLIB/DLL/CCDMAIN.DLL 01-28-01 23:22 587354 CMLIB/DLL/CMCONFIG.DLL 02-14-02 16:29 9561 CMLIB/DLL/EEDLC.DLL 02-14-02 16:35 175616 CMLIB/DLL/HPR.DLL 02-14-02 16:45 1540172 CMLIB/DLL/TN3270D.DLL 02-14-02 16:46 211869 CMLIB/DLL/TNIPTKT.DLL 07-27-01 16:22 25560 CMLIB/EEDLCDD.SYS 07-27-01 16:19 288867 CMLIB/FMTTRACE.EXE 01-15-01 12:48 24191 CMLIB/IDLCDD.SYS 01-15-01 12:48 68702 CMLIB/IDLCPD.SYS 07-27-01 12:20 56152 CMLIB/OCDOS250.DAT 01-28-01 23:31 119948 CMLIB/PMDSPLAY.EXE 01-28-01 23:31 43666 CMLIB/RDSPSRVR.EXE 07-27-01 16:20 49866 CMLIB/REMMAIN.EXE 01-15-01 12:48 24575 CMLIB/SDLCDD.SYS 01-15-01 12:48 86126 CMLIB/SDLCPD.SYS 02-19-02 09:56 165 CMLIB/SYSLEVEL.CSA CMFIX (APPLY SOFTWARE UPDATES) Displays a panel that enables you to apply software updates from a local drive, a LAN-attached drive, or from the Internet. To execute CMFIX, you can select the Software Update icon in the Problem Determination folder, or you can run CMFIX from an OS/2 command line. CMFIX applies software updates (APARs or PTFs) to a target workstation and/or a code server. A code server is a locally or LAN-accessible server that contains a directory of the installable Communications Server image. We will discuss the two installation methods, "Using CMFIX to Update a Code Server" and "Using CMFIX to Update a Single Target Workstation," later in this section. CMFIX also creates a file called CM2APAR.LOG on the machine that executes CMFIX. This file contains CMFIX messages. RUNNING CMFIX FROM THE COMMAND LINE When running CMFIX from an OS/2 command prompt, use the following syntax: Syntax >>--ç--.-------.--.------.--CMFIX-----------------------> '-drive-' '-path-' >--.----------------------.--.----.--.---.------------->< ³-/A--location--.----.-³ '-/Q-' '-?-' ³ '-/B-' ³ ³-/D-------------------³ '-/U-------------------' Note: Running CMFIX from the command line will not update a code server. Parameters drive The drive where the CMFIX.EXE file resides. Specify a drive if it is not the drive you are currently using. path The path where the CMFIX.EXE file resides. Use this parameter if the file is not in the path you are currently using. /A location Applies an update from the local or LAN-attached drive location. This drive must be directly accessible from your workstation. When you specify the location of the update, use the form "d:\path". /B Creates a backup of the changed files. /D Deletes a previously created backup. /U Uses a previously created backup to remove an applied update. /Q Suppresses all messages. A progress indicator is displayed requiring no operator intervention. ? Displays syntax information describing the available options. Remarks Refer to the online help for detailed information about each feature. Examples To display a panel where you can specify the location of an update and choose whether to install or remove an update, use the following statement: CMFIX To install a software update located on m:\updates, use the following statement: CMFIX /A m:\updates To view the syntax for CMFIX, use the following statement: CMFIX ? USING CMFIX TO UPDATE A CODE SERVER This is the recommended method to apply APAR fix packages to Communications Server V6.1. By following these instructions, you will have a new, updated version of Communications Server V6.1 in a "code server" directory. You can then use the code server directory when installing new workstations. 1. CREATE A CODE SERVER DIRECTORY. A code server is a locally or LAN-accessible server that contains a directory of the installable Communications Server image. To create a code server, if you have not already done so, follow these steps: a. Create a code server directory, such as COMMSVR\CODE. b. Use XCOPY to copy all the files from the \SERVER directory on the Communications Server CD-ROM to the code server directory you created in Step 1a. For example, change directories to \SERVER on the Communications Server CD-ROM and type: XCOPY *.* Q:\COMMSVR\CODE /s to copy the files. 2. EXECUTE CMFIX TO UPDATE THE CODE SERVER DIRECTORY. a. Execute CMFIX by selecting the Software Update icon in the Problem Determination folder, or running CMFIX from an OS/2 command line. b. Select the "Apply to Code Server" checkbox. c. For "Software Update Source," choose either "Local" or "Internet." "Local" means the APAR fix package is on an attached drive, and "Internet" means the package is on the IBM Internet site. d. Select the "Find" pushbutton, select the APAR fix package location, and highlight the BUNDLE.LST file. Select "OK." Then, select "OK" from the "Software Update" window. You will be prompted for the location of your code server directory. e. Close the "Software Update" window. f. Check the file cm2apar.log for any errors that may have occurred in the update process. This procedure is explained in the CMFIX online helps. Invoke CMFIX, select the Help button, and then select F2. 3. EXECUTE CMSETUP TO UPDATE COMMUNICATIONS SERVER WORKSTATIONS. a. On the Communications Server workstation that you want updated, execute CMSETUP from the code server directory. For example: Q:\COMMSVR\CODE\CMSETUP b. Follow the normal installation process until the "Refresh Product Files" window appears. Select the REINSTALL option to update your workstation with the fixes. USING CMFIX TO UPDATE A TARGET WORKSTATION Use this method if you would like to update a single Communications Server V6.1 workstation. If you add additional functions to your configuration, you will need to reapply any APAR fix packages, because CMSETUP will pull the new code from the directory where the install was executed. This will overlay any fixes previously applied. Only files that are older than the fixpack files being applied will be updated. If you use a code server, you do not need to reapply the fixes. Using the code server is the recommended method for updates. 1. EXECUTE CMFIX TO UPDATE THE WORKSTATION. a. Execute CMFIX by selecting the Software Update icon in the Problem Determination folder, or running CMFIX from an OS/2 command line. b. Select the "Apply" radio button; optionally, select the "Create Backup" checkbox. c. For "Software Update Source," choose either "Local" or "Internet." "Local" means the APAR fix package is on an attached drive(*), and "Internet" means the package is on the IBM Internet site. (*) the fix was downloaded manually from the IBM Internet site, rather than via CMFIX. d. Select the "Find" pushbutton, select the APAR fix package location, and highlight the BUNDLE.LST file. Select "OK." Then, select "OK" from the "Software Update" window. e. Close the "Software Update" window. f. Check the file cm2apar.log for any errors that may have occurred in the update process. This procedure is explained in the CMFIX online helps. Invoke CMFIX, select the Help button, and then select F2. IBM COPYRIGHT INFORMATION _________________________ IBM Communications Server for OS/2 Warp, Version 6.1 (c) Copyright International Business Machines Corporation 1988, 1996, 1998, 1999, 2000. All rights reserved. Note to U.S. Government Users - Documentation related to restricted rights - Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp. LIMIT OF LIABILITY __________________ License to the contained APAR fixes is conditioned upon the recipient holding a license to the prerequisite product. The license terms and conditions of the APAR fixes are the same as those for the prerequisite product. Please see the product license for specifics.