IBM Communications Server for Windows provides SNA connectivity for Windows systems, allowing it to connect to IBM z/OS Communications Server and other SNA implementations that support LLC, SDLC, X.25, Channel, and Enterprise Extender connections.
CS/WIN Version 6.1.2 FixPack 4 is an upgrade that includes previous FixPack updates. It is not a full install, and requires that V6.1.2 is installed at GA level or with FixPack 1, FixPack 2 or FixPack 3 or Fixpack3 refresh level installed. Only fixpacks greater than FixPack 4 should be installed after this installation.
The 6.1.2.3 refresh of CS/WIN provides a complete install package with FixPack 3 integrated. This is not that package. For more information, see the CS/WIN support document "Communications Server for Windows, Version 6.1.2 -- Latest Fix Pack"
This document contains information supplementary to the online help and the publications. It describes such things as newly-added functions, hints, tips, restrictions, and corrections.
Thank you for choosing Communications Server!
[Return to top of section] [Return to top of document] [Table of Contents]
Check the web sites listed in section 6 for the latest information about this product.
Notes:
[Return to top of section] [Return to top of document] [Table of Contents]
| JR25146.EXE | Self extracting binary that includes all FixPack 4 files: READMEFP4.HTM, NLSPACK4.EXE, SERVER4.EXE, APIPACK3.EXE |
| READMEFP4.HTM | Documentation of content, fixes, new functions, and install instructions for all packages. |
| NLSPACK4.EXE | Self extracting executable that contains FixPack 4 language files to be installed on the CS/WIN 6.1.2 Server machine. The English version of this module is installed as part of the server install by default. If CS/WIN 6.1.2 was installed using a non-English language, you must install the appropriate version of this NLS module after the server installation. |
| SERVER4.EXE | Self extracting executable that contains FixPack 4 files to be installed on the CS 6.1.2 Server machine. |
| APIPACK3.EXE | Self extracting executable that contains
FixPack 3 files to be installed on CS 6.1.2 API Client machine. NOTE: There is no change in client after Fixpack3 release. So, if you are already at fixpack3 or csnt6.1.2.3 refresh level of the client then no update is required. |
[Return to top of section] [Return to top of document] [Table of Contents]
pccfgXXX.dll: FIXPACK4 update for Configuration Gui.
[Return to top of section] [Return to top of document] [Table of Contents]
2.2.1 Integrated with server update
2.2.2 Separate, after server update
[Return to top of section] [Return to top of document] [Table of Contents]
pcsnops.exe and pcstrcres.dll
in the server update package with those included from the appropriate
sub-directory of this package.PCCFG.XXX.DLL from the NLS package
directory to the server package directory. Note, this file will not
exist in the server package because it is unique for each language.INSTFIX.BAT file with an appropriate
rename and copy statement for the PCCCFGXXX.DLL module.
(where XXX reflects the language).
See existing rename and copy statements in INSTFIX.BAT
for format.Perform the installation of the server package update. See section 3 for instructions.
[Return to top of section] [Return to top of document] [Table of Contents]
NLSPACK4.EXE to a temporary directory.
NLSPACK4.EXE /d
The package will expand and create a sub-directory for the NLS updates for each supported CS/WIN language.
NLS_INSTFIX.BAT file
for specific usage instructions. For example:
NLS_INSTFIX (no parameters; environment variables will be used)NLS_INSTFIX > nlsfp4.txt 2>&1 (silent install)NLS_INSTFIX c:\ibmcs (specify the directory)NLS_INSTFIX c:\ibmcs > nlsfp4.txt 2>&1 (silent install, specify directory)NOTE: NLS_INSTFIX.BAT checks if a PCOMM version less than 5.7 CSD3 is installed and if true, does not update the Trace Facility. CS/WIN 6.1.2 would use the Trace Facility installed by PCOMM. If you have installed PCOMM 5.7 CSD3 (or later), PCOMM 5.8 or PCOMM 5.9 on CS/WIN 6.1.2, PCOMM will not install its Trace Facility. In this case, NLS_INSTFIX will update the CS/WIN 6.1.2 Trace Facility.
If versions of PCOMM prior to 5.7 CSD3 are installed, you will not have any of the CS/WIN 6.1.2 Trace Facility updates or enhancements.
[Return to top of section] [Return to top of document] [Table of Contents]
| New APARs included in FixPack 4 since FixPack 3 (or csnt6.1.2.3 refresh install) | |
| JR23011 | TRAP in TN3270WN.EXE when using EXPLICIT LUs instead of a POOL. |
| JR23166 | CPIC ERROR 080F6051,SECURITY VIOLATION with USERID. |
| JR23168 | Services set to MANUAL fail to start at boot when running csstart -a. |
| JR23366 | HANG RUNNING ARTIC X25 WITH CS/WIN 612. |
| JR23367 | Windows Performance Monitor not show CS/WIN OBJECTS after CS installation |
| JR23522 | CRASH in LLC2 when cycling NODE or rebooting. |
| JR23674 | TRAP IN TNSERVER module TN3270wn.exe processing RUI_TERM. |
| JR23909 | ANYNET GATEWAY MEMORY LEAK |
| JR24119 | CRASH IN APPNBASE during boot up time. |
| JR24223 | RUI_INIT FAILS WITH INVALID_COMMAND_COUNT error. |
| JR24759 | INFO BUNDLER fails to create CSPDDATA.EXE after installing fixpack3. |
| JR24771 | IBM SNA CLIENT Services fails to start after installing Fixpack3. |
| JR24932 | UNINSTALL may fail when user is a DOMAIN ADMIN. vs LOCAL ADMINSTRATOR. |
| JR25010 | BLUESCREEN IN APPNAPI while processing the RUI verb after RUI_TERM response being processed. |
| JR25017 | BLUESCREEN IN APPNBASE ON LOCATE(rsp) RARE OCCURANCE |
| JR25142 | EEDLC IPV6 ADDRESS SUPPORT. |
| JR25143 | IBMCSADMIN CAPABILITIES. |
| JR25144 | QUERY_CONVERSATION ADDED TO CSDISPLAY. |
| JR25145 | MAX_RECEIVE_PACING_WIN IN MODE DEFINITION. |
| JR25156 | TN3270 server trap causing cycle of the node to recover. |
| JR25210 | ADDITIONAL RTP TUNING PARAMETERS. |
APARs included in FixPack 3 since FixPack 2 | |
| JR20878 | TRAP IN SPLITSTACK - CLIENT SERVER |
| JR21008 | CRASH IN APPN.SYS HANDLING EEDLC link deactivation. |
| JR21053 | SLI-CLOSE HANG ON SNA API CLIENT. |
| JR21104 | NF to Information Bundler to run Silent/Quiet. |
| JR21107 | NODE FAILS TO START AT BOOT DUE TO PDLNDLDL.SYS. |
| JR21180 | Disable Active Directory for TNSERVER. |
| JR21204 | VTAM ABEND0A9 RCFF13 ISTRPCRS due to CS/WIN HPR. |
| JR21237 | CRASH IN SNAPS APPN.SYS. |
| JR21250 | Add CONNECTION KEEP ALIVE for implicit EEDLC links. |
| JR21259 | SNAP UPDATES. |
| JR21261 | CRASH IN TN3270WN.EXE during cleanup up. |
| JR21299 | LU FORMAT ERROR,INVALID CHANGE DIRECTION. Sense 400D0000 |
| JR21316 | EEDLC SOURCE PORTS now use 12000-120004. |
| JR21437 | BLUESCREEN using IBM4758 Hardware Encryption card. |
| JR21518 | TNserver LU HANG processing SHUTD/SHUTC. |
| JR21543 | APAR TO DOCUMENT CS/WIN 6.1.1 Fixpack4. |
| JR21544 | AFTER APPLYING JR20053 TN3270 CLIENT can't reconnect. |
| JR21546 | A PACKAGE TO HELP CLEANUP CS/WIN files from bad install. |
| JR21604 | RMCSNT does not remove new 612 device drivers. |
| JR21848 | LUA API changed to handle bind differently. |
| JR21850 | CSDISPLAY COMMAND FAILS TO DISPLAY tnserver data. |
| JR21942 | Link fails to activate after host IPL. |
| JR22234 | BLUESCREEN IN APPNBASE. |
| JR22419 | NODE CONFIG displays wrong adapter/sap. |
APARS included from FixPack 2 | |
| JR20370 | Support added for SSE BITS in APPN locates. |
| JR20377 | BLUESCREEN in EEDLC reporting link failure. |
| JR20407 | CS/WIN 6.1.2 FIXPACK1. |
| JR20453 | BLUESCREEN in EEDLC in link recovery. |
| JR20454 | Hang in Node Configuration Utility. |
| JR20352 | TRACE format incorrect. |
| JR20241 | Access violation in client CCS.DLL. |
| JR20491 | Trace GUI main menus blank in CS/WIN NLS versions. |
| JR20436 | CPIC appl. hangs running dependent LU62. |
| JR20487 | BLUESCREEN in APPN.SYS processing locates. |
| JR20566 | HPR Performance Enhancements. |
| JR20830 | Trap when selecting SNA counters in MS Perfmon utility. |
| JR21726 | Sense code 20010000/20110000 when segmenting data running PU concentrator or TN3270E Gateway |
| JR21848 | RUI (LUA API) changes in processing incoming BIND |
APARS included from FixPack 1 | |
| JR19449 | Resolves 4 problems on the APICLIENT. |
| JR19492 | Cumulative Service APAR for CS/6.1.2. |
| JR19517 | BLUESCREEN running EEDLC in PDLNDOEM.SYS. |
| JR19595 | TRAP in WINSLI32.DLL using SLI API on server |
| JR19828 | TN3270 SERVER connection error TNS0010E. |
| JR19920 | BLUESCREEN in APPN.SYS running EEDLC. |
| JR19932 | GSKIT DENIAL-OF-SERVICE VULNERABI |
| JR20053 | TN3270 Server HANG after network outage. |
| JR19694 | CSTRACE AUTO fails if CS installed on other than C:drive. |
| JR19779 | NODEOPS allows starting of node when already running. |
| JR19784 | SLI_BID gets posted with incorrect data length (0). |
| JR19787 | TN3270 SERVER LU HUNG and fails to reconnect. |
| JR19788 | APICLIENT problem with SLI-BIND or SLI-STSN extensions. |
| JR19912 | SNA HANG when CPs up on link other than pref. NN Srv. lnk. |
| JR19921 | SNA LINKs fail to retry to recover link. |
| JR20032 | SNA CP-CP sessions fail to switch to prefered NNS. |
| JR20159 | EEDLC LIVENESS TIMER default changed to ENABLED. |
| JR20275 | Updates to STOP NODE AND LOCATE processing. |
| JR20329 | TN3270 SERVER sessions fail to reconnect to same LU. |
| JR19572 | APICLIENT HANGs running PCOM 3270 LUA using cut/paste. |
| JR20147 | Update CSTRACE to add WRITE-T0-DISK and msgid option. |
| JR20175 | Severe Performance problems running HPR over EEDLC. |
| JR20436 | CPIC app. HANG running dependent LU62 sessions. |
[Return to top of section] [Return to top of document] [Table of Contents]
Directory of C:\IBMCS or %SNAROOT% (Communications Server installation directory)
10/19/2006 12:16 PM 32,768 adaptinst.exe 10/19/2006 02:12 PM 45,056 adminapi.dll 10/19/2006 02:06 PM 32,768 adminpre.dll 10/19/2006 02:12 PM 401,408 adminserver.dll 10/19/2006 02:06 PM 69,632 adminstrings.dll 10/19/2006 01:51 PM 77,824 adRAPIClient.dll 10/19/2006 02:14 PM 40,960 adRAPIStubs.dll 10/19/2006 01:50 PM 53,248 adRapiUtil.dll 10/19/2006 02:27 PM 69,632 aftp.exe 10/19/2006 02:26 PM 151,552 aftpapi.dll 10/19/2006 02:27 PM 147,456 aftpserv.dll 10/19/2006 03:33 PM 32,768 anutil.dll 10/19/2006 03:47 PM 20,480 anybsd.dll 10/19/2006 01:57 PM 24,576 ANYINIT.dll 10/19/2006 03:34 PM 20,480 anyloadr.exe 10/19/2006 01:58 PM 110,641 anymsg.dll 10/19/2006 03:48 PM 20,480 anyqryss.dll 10/19/2006 03:33 PM 20,480 anytrace.dll 10/19/2006 03:34 PM 32,768 anytrc.dll 10/19/2006 03:34 PM 20,480 anytrfmt.dll 10/19/2006 03:48 PM 28,672 anyws2in.dll 10/19/2006 03:47 PM 32,768 anyws32.dll 10/19/2006 03:42 PM 20,480 anywsipc.dll 10/19/2006 01:30 PM 434,176 apitrc32.dll 10/19/2006 01:17 PM 32,768 cpicmsg.dll 10/19/2006 02:04 PM 36,864 cscm.dll 10/19/2006 02:24 PM 32,768 csdisplay.exe 10/19/2006 01:59 PM 32,768 csevtmsg.dll 10/19/2006 02:03 PM 49,152 csformat.dll 10/19/2006 02:05 PM 32,768 cslba.dll 10/19/2006 02:24 PM 20,480 cslic.exe 10/19/2006 01:23 PM 32,768 csmls.dll 10/19/2006 02:03 PM 45,056 csmmsg.dll 10/19/2006 02:04 PM 188,416 csnia.dll 10/19/2006 02:00 PM 24,576 csnlg.dll 10/19/2006 01:27 PM 135,168 CSNTPD.exe 10/19/2006 02:06 PM 28,672 csqel.dll 10/19/2006 02:24 PM 20,480 csquery.exe 10/19/2006 02:05 PM 73,728 cssec.dll 10/19/2006 02:05 PM 40,960 cssma.dll 10/19/2006 02:24 PM 24,576 csstart.exe 10/19/2006 02:24 PM 24,576 csstop.exe 10/19/2006 02:04 PM 40,960 cstlm.dll 10/19/2006 02:03 PM 20,480 csutlc.dll 10/19/2006 02:03 PM 24,576 csutls.dll 10/19/2006 02:04 PM 24,576 csxlib.dll 10/19/2006 02:00 PM 20,480 cs_waitnt.exe 10/19/2006 01:49 PM 20,480 defsecur.dll 10/19/2006 01:39 PM 32,768 discovrd.dll 10/19/2006 01:31 PM 118,784 dlctrc32.dll 10/19/2006 01:51 PM 32,768 emutocfg.dll 10/19/2006 01:15 PM 24,576 fmt_util.dll 10/19/2006 01:48 PM 57,344 fmtcapi.dll 10/19/2006 01:27 PM 28,672 fmteng.dll 10/19/2006 01:49 PM 24,576 fmtmsg.dll 10/19/2006 01:49 PM 49,152 FMTNODE.DLL 10/19/2006 02:15 PM 24,576 FMTNOPS.dll 10/19/2006 02:27 PM 24,576 getsense.exe 10/19/2006 01:57 PM 57,344 hotstby.dll 10/19/2006 02:03 PM 20,480 ibmcsprf.dll 10/19/2006 01:59 PM 69,632 ibmsa.dll 10/19/2006 02:00 PM 16,384 ibmsa.exe 10/19/2006 01:59 PM 98,304 ibmslp.dll 10/19/2006 03:33 PM 20,480 ipc.dll 10/19/2006 03:35 PM 114,688 ippmm.dll 10/19/2006 02:21 PM 40,960 ldlc.dll 10/19/2006 02:20 PM 24,576 ldlcenu.dll 10/19/2006 01:58 PM 24,576 limgmt.dll 10/19/2006 01:58 PM 69,632 limgmtd.dll 10/19/2006 02:21 PM 32,768 lspmsg.dll 10/19/2006 01:13 PM 32,768 MILLUTIL.DLL 10/19/2006 03:33 PM 159,744 mptncmm.dll 10/19/2006 01:26 PM 155,648 msgbrwsr.exe 10/19/2006 01:17 PM 28,672 MSGIO.dll 10/19/2006 01:17 PM 28,672 Msgmsg.dll 10/19/2006 12:49 PM 16,384 NI_MSG.DLL 11/02/2006 08:03 AM 98,304 NODEINIT.DLL 10/19/2006 01:15 PM 28,672 nopsmsg.dll 10/19/2006 12:03 PM 9,453 ntcmpd.bat 10/19/2006 12:03 PM 79,240 ocdnts50.dat 10/19/2006 01:32 PM 494,592 ocdconvt.dll 10/19/2006 12:49 PM 286,720 pccfgenu.dll 10/19/2006 12:50 PM 24,576 PCS_AGNT.EXE 10/19/2006 12:49 PM 16,384 PCS_STAB.DLL 10/19/2006 12:48 PM 94,208 Pcscapi.dll 10/19/2006 12:40 PM 32,768 pcscca.exe 10/19/2006 12:57 PM 1,511,424 pcscfg.exe 10/19/2006 12:27 PM 28,672 pcsfmtpi.dll 10/19/2006 12:22 PM 151,552 pcsmfcx.dll 10/19/2006 01:17 PM 438,272 pcsnops.exe 10/19/2006 12:17 PM 24,576 pcsw32x.dll 10/19/2006 01:32 PM 36,864 pdlcsmsg.dll 10/19/2006 01:32 PM 52,076 PDLCSMSG.HLP 10/19/2006 01:41 PM 32,768 pdlnafmt.dll 10/19/2006 01:34 PM 32,768 pdlncfgf.dll 10/19/2006 01:35 PM 69,632 pdlncfmt.dll 10/19/2006 01:37 PM 10,752 pdlndfmt.dll 10/19/2006 01:38 PM 24,576 pdlneadu.dll 10/19/2006 01:34 PM 32,768 pdlneptf.dll 10/19/2006 01:39 PM 45,056 pdlnmfmt.dll 10/19/2006 01:39 PM 28,672 pdlnshaf.dll 10/19/2006 01:39 PM 24,576 pdlnslef.dll 10/19/2006 01:39 PM 24,576 pdlnsv2f.dll 10/19/2006 01:40 PM 28,672 pdlnsx2f.dll 10/19/2006 01:37 PM 10,752 pdlwofmt.dll 10/19/2006 12:26 PM 45,056 rasbut.exe 10/19/2006 01:21 PM 20,480 rcmdfmtr.dll 10/19/2006 01:21 PM 40,960 rcmdsa.exe 10/19/2006 12:27 PM 24,576 rmcsnt.exe 10/19/2006 12:27 PM 53,248 Servcsnt.exe 10/19/2006 12:42 PM 32,768 slimsg.dll 10/19/2006 12:59 PM 24,576 slpapi.dll 10/19/2006 12:59 PM 20,480 slpform.dll 10/19/2006 12:16 PM 675,904 snaformat.exe 10/19/2006 02:49 PM 110,592 snapmm.dll 10/19/2006 02:42 PM 118,784 snasm.dll 10/19/2006 02:46 PM 270,336 socketsm.dll 10/19/2006 12:48 PM 73,728 SPELLING.DLL 10/19/2006 02:47 PM 20,480 sxmap.exe 10/19/2006 02:53 PM 32,768 tn3270d.dll 10/19/2006 02:53 PM 229,376 tn3270wn.exe 10/19/2006 02:53 PM 20,480 tn32bind.dll 10/19/2006 02:56 PM 53,248 tn5250d.dll 10/19/2006 02:56 PM 172,032 tn5250wn.exe 10/19/2006 02:54 PM 49,152 tniptkt.dll 10/19/2006 12:58 PM 110,642 tnsmsg.dll 10/19/2006 12:39 PM 20,480 tpstart.exe 10/19/2006 01:28 PM 147,456 uninst.dll 10/19/2006 12:58 PM 20,480 vacgcon.exe 10/19/2006 12:58 PM 61,440 vacgfenu.dll 10/19/2006 12:49 PM 81,920 vacgverf.dll 10/19/2006 12:58 PM 110,592 vacgwin.exe
Directory of %systemroot%\system32
10/19/2006 12:39 PM 24,576 appcmsg.dll 10/19/2006 12:38 PM 20,480 cmnapi32.dll 10/19/2006 01:59 PM 20,480 csloadfx.dll 10/19/2006 02:00 PM 40,960 cslicmon.exe 10/19/2006 12:38 PM 28,672 csvmsg.dll 10/19/2006 02:00 PM 20,480 cs_plusutil.exe 10/19/2006 12:15 PM 24,576 fmt_util.dll 10/19/2006 01:03 PM 20,480 ibmcsprf.dll 10/19/2006 12:17 PM 40,960 Message.dll 10/19/2006 12:14 PM 36,864 nstrc.dll 10/19/2006 12:17 PM 24,576 pcsw32x.dll 10/19/2006 12:40 PM 36,864 pcs_perf.dll 10/19/2006 12:39 PM 24,576 ruimsg.dll 10/19/2006 12:38 PM 65,536 wappc32.dll 10/19/2006 12:21 PM 135,168 wcpic32.dll 10/19/2006 12:48 PM 24,576 winAPPC.dll 10/19/2006 12:21 PM 24,576 wincpic.dll 10/19/2006 12:48 PM 24,576 winCSV.dll 10/19/2006 12:38 PM 65,536 wincsv32.dll 10/19/2006 12:38 PM 32,768 winms32.dll 10/19/2006 12:39 PM 36,864 winnof32.dll 10/19/2006 12:48 PM 24,576 winrui.dll 10/19/2006 12:39 PM 36,864 winrui32.dll 10/19/2006 12:48 PM 24,576 winsli.dll 10/19/2006 12:48 PM 77,824 winsli32.dll 10/19/2006 12:38 PM 28,672 wpdapi32.dll
Directory of %systemroot%\system32\drivers
10/19/2006 02:36 PM 37,244 anydlc.sys 10/19/2006 02:50 PM 11,400 anysosdd.sys 10/19/2006 02:50 PM 342,932 anysosgw.sys 10/19/2006 12:38 PM 1,606,848 appn.sys 10/19/2006 12:39 PM 124,480 appnapi.sys 10/19/2006 12:41 PM 400,224 appnbase.sys 10/19/2006 12:39 PM 32,768 appnnode.exe 10/19/2006 01:24 PM 20,480 cslic.exe 10/19/2006 01:21 PM 45,056 csrcmds.exe 10/19/2006 12:28 PM 36,864 cstrcser.exe 10/19/2006 01:00 PM 16,384 ibmsa.exe 10/19/2006 01:38 PM 28,672 ldlcserv.exe 10/19/2006 01:38 PM 40,960 ldlcserv6.exe 10/19/2006 12:41 PM 102,592 llc2.sys 10/19/2006 01:40 PM 77,536 pdlnacom.sys 10/19/2006 01:41 PM 15,856 pdlnadci.sys 10/19/2006 01:41 PM 39,920 pdlnafac.sys 10/19/2006 01:40 PM 92,464 pdlnampa.sys 10/19/2006 01:41 PM 39,472 pdlnaoem.sys 10/19/2006 01:35 PM 19,456 pdlnatcm.sys 10/19/2006 01:35 PM 17,920 pdlnatdl.sys 10/19/2006 01:36 PM 62,976 pdlnatnm.sys 10/19/2006 01:36 PM 65,024 pdlnatsn.sys 10/19/2006 01:41 PM 72,368 pdlnawac.sys 10/19/2006 01:34 PM 6,768 pdlncbas.sys 10/19/2006 01:35 PM 160,384 pdlncfwk.sys 10/19/2006 01:36 PM 12,288 pdlnctdl.sys 10/19/2006 01:36 PM 12,800 pdlndint.sys 10/19/2006 01:38 PM 64,512 pdlndldl.sys 10/19/2006 01:38 PM 71,680 pdlndldl6.sys 10/19/2006 01:37 PM 71,168 pdlndlpb.sys 10/19/2006 01:37 PM 18,944 pdlndoem.sys 10/19/2006 01:37 PM 53,248 pdlndqll.sys 10/19/2006 01:37 PM 67,072 pdlndsdl.sys 10/19/2006 01:37 PM 51,712 pdlndtdl.sys 10/19/2006 01:33 PM 8,592 pdlnebas.sys 10/19/2006 01:34 PM 50,480 pdlnecfg.sys 10/19/2006 01:38 PM 67,760 pdlnemap.sys 10/19/2006 01:34 PM 12,768 pdlnemsg.sys 10/19/2006 01:34 PM 19,968 pdlnepkt.sys 10/19/2006 01:39 PM 59,520 pdlnshay.sys 10/19/2006 01:39 PM 22,608 pdlnslea.sys 10/19/2006 01:39 PM 54,416 pdlnsv25.sys 10/19/2006 01:40 PM 58,752 pdlnsx25.sys 10/19/2006 01:06 PM 38,944 qeldrvr.sys 10/19/2006 01:14 PM 53,248 rapiserver.exe 10/19/2006 12:15 PM 20,480 trcboot.exe
Directory of
DRIVE_LETTER:\Program Files\IBM\Trace Facility
where DRIVE_LETTER is the installation drive of CS/WIN
or of PCOMM if PCOMM 5.7 CSD3 or above is installed.
10/19/2006 11:56 AM 1,456 appnf.bat 10/19/2006 11:56 AM 11,109 appnt.bat 11/02/2006 08:04 AM 36,864 cstrace.exe 10/19/2006 12:28 PM 32,768 cstrccom.dll 10/19/2006 12:27 PM 28,672 fmteng.dll 10/19/2006 12:27 PM 28,672 pcsfmtpi.dll 11/03/2006 07:43 AM 118,784 trcgui.exe
[Return to top of section] [Return to top of document] [Table of Contents]
| New function added in FixPack 4 | |
| Additional RTP_Tuning parameters | |
| 1. |
Previously, RTP_TUNING had the following two parameters:
PATH_SWITCH_ATTEMPTS - Number of path switch attempts to set on new RTP connections. Specify a value in the range 1-255. If you specify 0(zero), Communications Server for Windows uses the default value of 6. SHORT_REQ - Limits the number of times a Status Request is sent before Communications Server for Windows determines that an RTP connection is disconnected and starts Path Switch processing. Specify a value in the range 1-255. If you specify 0(zero), Communications Server for Windows uses the default value of 6. |
| 2. |
Now there are additionally the four path switch times and maximums set for the refifo timer and the short request timer. Path switch time is the length of time in seconds for which Communications Server for Windows attempts to path switch a disconnected RTP connection. This parameter is specified as four separate time limits for each of the valid transmission priorities in order: LOW, MEDIUM, HIGH, and NETWORK. Each these must be in the range 1-65535. The value you specify for each transmission priority must not exceed the value for any lower transmission priority. If you specify 0(zero) for any of these values, Communications Server for Windows uses the corresponding default value as follows: LOW_PATH_SWITCH_TIME = 480 seconds (8 minutes) MEDIUM_PATH_SWITCH_TIME = 240 seconds (4 minutes) HIGH_PATH_SWITCH_TIME = 120 seconds (2 minutes) NETWORK_PATH_SWITCH_TIME = 60 seconds (1 minute)NOTE: The path switch times must be ordered so that LOW > MEDIUM > HIGH > NETWORK. The RTP_TUNING path switch timers (ALL 4) must be greater that the link timeout for the links being used. For example, EEDLC links are tested every "Inactivity timer" and is retried for "Connect retry count" before an error is detected. These parameters are configured under the IBM EEDLC for Ipv4 or IPv6 panel and EEDLC Device. The default values are inactivity timer = 10 seconds and connect retry count = 3. This means that a link failure could take (3 + 1) x 10 = 40 seconds. Prior to detecting the link failure, the path switch attempts will use the failing link and therefore be unsuccessful. When the path switch attempts fail, the sessions being routed over the HPR pipe will be terminated. MAX_REFIFO_TIME - The RTP protocol uses a timer called the Re-FIFO Timer. The value of this timer is calculated as part of the protocol, but this parameter specifies a maximum value in milliseconds beyond which the timer cannot increase. In some situations, setting this maximum value can improve performance. Setting a value of 0 (zero) means that the timer is not limited and can take any value calculated by the protocol. The default value for this parameter is 4000 milliseconds with a minimum value of 250 milliseconds. If a value specified is 1 - 249 milliseconds, 250 milliseconds is used. Previous to this change, there was no limit on the refifo time, but now a limit is set by default. To return to previous behavior, you may set a limit of 0 (zero) as described. MAX_SHORT_REQ_TIME - The RTP protocol uses a timer called the Short Request Timer. The value of this timer is calculated as part of the protocol, but this parameter specifies a maximum value in milliseconds beyond which the timer cannot increase. In some situations, setting this maximum value can improve performance. Setting a value of 0 (zero) means that the timer is not limited and can take any value calculated by the protocol. The default value for this parameter is 8000 milliseconds with a minimum value of 500 milliseconds. If the value specified is 1-499 milliseconds then a value of 500 milliseconds is used. Previous to this change, there was no limit on the short request time or the refifo time, but now a limit is set by default. To return to previous behavior, you may set a limit of 0 (zero) as described. |
| 3. |
Example of RTP_TUNING changing the default path switch times in .acg file.
RTP_TUNING=(
PATH_SWITCH_ATTEMPTS=6 RANGE = 0,255 default = 6
SHORT_REQ=0 RANGE = 0,255 default = 6
LOW_PATH_SWITCH_TIME=240 RANGE = 1,65535 default = 480 seconds
MEDIUM_PATH_SWITCH_TIME=120 RANGE = 1,65535 default = 240 seconds
HIGH_PATH_SWITCH_TIME=100 RANGE = 1,65535 default = 120 seconds
NETWORK_PATH_SWITCH_TIME=60 RANGE = 1,65535 default = 60 seconds
MAX_SHORT_REQ_TIME=8000 RANGE = 0,24000 default = 8000 milliseconds
MAX_REFIFO_TIME=4000 RANGE = 0,12000 default = 4000 milliseconds
)
|
| 4. |
Display RTP_TUNING was also added to csdisplay rtn in the form: Low Path Switch Time 480 Medium Path Switch Time 240 High Path Switch Time 120 Network Path Switch Time 60 Path Switch Attempts 6 Short Request Retry Limit 6 Maximum Short Request Time 8000 Maximum Refifo Time 4000 This csdisplay rtn is also added to the ntcmpd so that this data is gathered with the cmpd data package. |
| EEDLC IPV6 address support | |
|
Now, EEDLC links can be configured with IPv6 address during the link definition.
If the IPv6 address is not in valid format, then the host resolution will fail during
the link start up a and related error message will be logged in the pcwmsg.mlg file.
CSDISPLAY and NODEOPS will now display the IPv6 address on active or defined links.
Existing IPv6 EEDLC link definitions has to be reconfigured after applying the fixpack4, if any were created at fixpack 2 level. A fixpack 2 level IPv6 port will act like EEDLC IPv4 port since the port name is now IBMEE006 for IPv6 links rather than IBMEEDLC. | |
| EEDLC IPV4 and IPv6 will now match incoming links to defined links. | |
| Previously, incoming EEDLC links were always implicit links and did not match to defined links. Now they match the defined link name and use the characteristics of the defined link. This match is also true for connection network links from the node or to the node. | |
| QUERY CONVERSATION added to CSDISPLAY | |
csdisplay L6C will display LU 6.2 conversation information in the form:
Conversation ID 207749121 Local TP name CPIC_DEFAULT_TPNAME Partner TP name APINGD TP ID 0100AE0C00000000 Session ID F15F6CEB62D01E89 Bytes Sent 5471588 Bytes Received 5421616 Conversation state Send LU Name JMCSNT1E Duplex Type Half Duplex This csdisplay l6c is also added to the ntcmpd so that this data is gathered with the cmpd data package. | |
| Support of restricting maximum pacing window size: | |
Communication Server for OS/2 provided both fixed pacing and two way fixed pacing. CS/Windows
does not provide fixed pacing. However, with this new parameter, there is a limit on the maximum
pacing window. The requirement for fixed pacing is to limit the maximum size of the pacing windows and
this can be accomplished by setting the MAX_RECEIVE_PACING_WINDOW in the .ACG file as part of
MODE definition. For example, the "FIXEDPAC" mode can be defined like below:
MODE=(
MODE_NAME=FIXEDPAC
AUTO_ACT=0
COMPRESSION=PROHIBITED
COS_NAME=#CONNECT
ENCRYPTION_SUPPORT=NONE
DEFAULT_RU_SIZE=1
MAX_INCOMING_COMPRESSION_LEVEL=NONE
MAX_NEGOTIABLE_SESSION_LIMIT=3
MAX_OUTGOING_COMPRESSION_LEVEL=NONE
MAX_RU_SIZE_UPPER_BOUND=4096
MIN_CONWINNERS_SOURCE=1
PLU_MODE_SESSION_LIMIT=3
RECEIVE_PACING_WINDOW=2
MAX_RECEIVE_PACING_WINDOW=5
)
The pacing window starts at 2 (RECEIVE_PACING_WINDOW) and has 5 as the maximum value (MAX_RECEIVE_PACING_WINDOW). Note that the send pacing window is adaptive without a specified limit unless the remote node has the mode set with MAX_RECEIVE_PACING_WINDOW. The MAX_RECEIVE_PACING_WINDOW parameter can be set by editing the .acg configuration file. NOTE: The MAX_RECEIVE_PACING_WINDOW parameter can be set by the NOF call. The variable used to define this parameter is max_receive_pacing_win as part of the define MODE verb. | |
| New function added in FixPack 3 | |
| General enhancements | |
| 1. |
An option is provided to NOT publish TN3270 services to the LDAP Active Directory.
By setting the "TN3270AdvToADS" keyword under
HKEY_LOCAL_MACHINE\SOFTWARE\IBM\Communications Server\current\Version\Config with a
DWORD value of "0", the TN3270 advertisements will be disabled.
Steps to disable publishing:
|
| 2. |
A new configuration parameter has been added to allow a port to
be configured to allow only a specific number of implicit inbound
links for LAN connections.
The parameter "
This parameter affects only implicit links, links that are
dynamically created to accept an inbound connection where the
local SAP, remote SAP, and remote MAC address do not match any
explicitly defined links.
.
To limit the total number of inbound links, use the existing
PORT parameter INB_LINK_ACT_LIM=0, which is documented in the
CS/WIN Configuration File Reference.
|
| SNAFORMAT enhancements | |
| 1. |
Option (-h) has been added to SNAFORMAT to disable HPR formating in the summary trace.
By removing the HPR flows you can follow the API flows easier.. You would disble the HPR flows by entering:
|
| Information Bundler enhancements | |
| 1. |
Option -q (Quiet mode) to suppress popups has been added to csntpd.exe.
This option will allow you to remotely capture an information bundler (cspddata.exe) and allevitate the requirement to "press any key to continue" and the popup window indicating the registry has been copied. Option -s Suppress registry collection. This option suppresses the registry collection and hence output information bundler will not collect registry.dat nor csntreg.dat. Note: The default infobundler behavior will be to show popups and collect registry information when ran with no options. |
| EEDLC IPV4 and IPV6 enhancements | |
| 1. |
EEDLC can now be configured to run IPv4 (IBMEEDLC) and IPv6 (IBMEE006),
each protocol using a different DLC: IBMEEDLC for IPV4 and IBMEE006 for IPV6.
The outgoing links must be defined on the correct DLC type.
IPv6 is supported only on the Windows 2003 (SP1) or XP (SP2) and above Operating Systems.
Existing EEDLC definitions from FixPack 2 and earlier, which used a parameter to specify whether the DLC was IPV4 or IPV6, will all be treated as IPV4 definitions because that parameter is no longer used. Links using IPV6 must be reconfigured to the new IBMEE006 DLC. |
| IBMCSADMIN capabilities | |
| 1. |
A user who is a member of the IBMCSADMIN group can manage the SNA
resources and does not require Administrator authority. With previous
releases of Communications Server, only Administrator authority
allowed management of SNA resources.
A user who is not part of either Administrator or IBMCSADMIN groups will not be allowed to control SNA resources, such as starting and stopping the node, running command line traces, etc. |
New function added in FixPack 2 | |
| General enhancements | |
| 1. |
Support for TCP/IP Version 6 has been added in this fixpack. The function is
currently supported only on WINDOWS 2003 or XP.
To configure CS/WIN to run with IPV6 you must select IPV6 in the DLC profile provided that IPv6 is installed in the Operating system. You can configure and run either IPV4 or IPV6 but not both. You can configure only ONE EEDLC dlc per ACG file. You can have separate ACG files to run IPv4 or IPV6. The default is IPV4. |
New function added in FixPack 1 | |
| General enhancements | |
| 1. |
SNA Function addition of LU 6.2 session level timeout based on LU,
partner LU or mode
LU62_timeout as documented in JR16867 (included in CSNT6.1.2 GA) to terminate the lu62 session on completion of the lu62 conversation. The feature was included in CS/2 and now is configurable only in the CSNT ASCII configuration file. The setting is global on all lu62 sessions with the exception of the IBM Service TPs such as the CPSVCMGR session. The lu62_timeout_value is in seconds. LU62_TIMEOUT=( LU62_TIMEOUT_RESOURCE_TYPE=GLOBAL_TIMEOUT LU62_TIMEOUT_VALUE=20 )New in this APAR JR20407, three new options have been added for LU62_TIMEOUT_RESOURCE_TYPE:
LU62_TIMEOUT_RESOURCE_NAME
which specifies the LOCAL_LU name, PARTNER_LU name, or MODE name.
The LU62_TIMEOUT is used only for sessions with the specified
LOCAL_LU, PARTNER_LU or MODE name.
NOTE: LU62_TIMEOUT is configurable only in the ACSII configuration file (.acg).
|
| EEDLC enhancements | |
| 1. |
NEW FUNCTION support of option to not use Host Name on Connection Networks:
Host name support for Enterprise Extender DLC connection networks is supported
in GA code.
However, if there is not a firewall in the network that requires host name resolution to an IP address separately on each end, then the host name would not have to be sent on the LOCATEs and resolved on the receiver. This is the way that EEDLC connection networks operate in CSNT6.1.1. There is now a checkbox under the EEDLC device configuration labeled "Do not Use IPV4 Host Name". The default is not checked. If it is checked, then the connection network A5 control vectors do not include the host name (making shorter LOCATEs) and the remote just uses the IP address that is sent. If host name resolution fails on an EEDLC link and an IP address is present, then attempt to connect using the IP address. |
| 2. |
EEDLC link liveness timer is now always on. The range that the liveness timer can
be set to was increased from 59 seconds to 255 seconds on either the EEDLC device
or on the connection definition. The default remains at 10 seconds.
|
| 3. |
Changed the default effective capacity of EEDLC and LLC2 links from 133 (16 Mb)
to 160 (157 Mb) to improve HPR ramp up performance (throughput is improved).
|
| Command line trace enhancements | |
|
Note: If versions of PCOMM prior to 5.7 CSD3 are installed, you will
not have any of the CS/WIN 612 Trace facility enhancements.
| |
| 1. |
Trace to multiple trace files is supported from the command line (cstrace).
The file size and the number of files can be specified.
Note that the /w and /n functions are new functions and help is not available
for non-English versions.
to copy to multiple nstrcxxx files add /w yyy (where yyy is Kb file size) to the start statement cstrace start
resets traces and writes to nstrc001,nstrc002,nstrc003,nstrc004,nstrc005 each about 4000 KB. When the files are full, tracing continues by cycling through the files. Note that /w cannot be used with /b and /s. |
| 2. |
New function is added to stop trace from the command line based on message ID.
Note that the /m function is a new function and help is not available
for non-English versions.
To stop on message id, run
where PCS4661I (the messageid) is issued to the message log. To disable traces on message ID, run
Tracing then continues until you run
|
| 3. |
Autostart trace option was incorrectly documented as /f instead of /e.
To enable the autostart option use the following command:
To disable the autostart option use the following command:
To turn on/off APPC API and EEDLC tracing, the format of the trace option file should be:
|
| 4. |
APPNT.BAT has been updated describing new functions.
APPNT.bat is a batch file to start traces from the command line.
The default API option is to truncate the data at 128 bytes.
IPSTRACE is on by default.
Increased the trace buffer size.
|
| 5. |
CSTRACE SHUTDOWN is added to APPNF to reset trace flags.
APPNF.bat is a batch file to stop and format traces.
|
| 6. |
SNAFORMAT ENHANCEMENTS:
SNAFORMAT creates summary and detail files on traces with SDLC, EEDLC DLCs (in addition to existing LLC2 capability) and SLI, RUI, CPIC and APPC apis by formatting the nstrc.tlg to nstrc.sum and nstrc.det. |
[Return to top of section] [Return to top of document] [Table of Contents]
To expand SERVER package run SERVER4.EXE which will generate a Server sub-dir including all server package files. There will also be registrychange.exe, servicestest.exe, killpcs_agnt.exe and instfix.bat in current directory but only required for the package installation.
The Trace Facility is installed on the user-designated drive, but the registry is incorrectly updated to reflect the BOOT drive for the new trace service CSTRCSER.EXE. To correct this, modify the registry to reflect the correct drive and path location for the service CSTRCSER.EXE.
Use regedit to update value for the IMAGEPATH key under
\HKLM\SYSTEM\CURRENTCONTROLSET\SERVICES\CSTRCSER\
to the correct CSTRCSER.EXE path location.
If the current versions of PCOMM is prior to 5.7 CSD3 then you will not have any of the CS/WIN 6.1.2 Trace Facility updates or enhancements.
There is a problem with some versions of PCOMM prior to 5.7 CSD3 where using ADD/REMOVE PROGRAMS to remove PCOMM removes the Service APPNNODE from the REGISTRY. CS will NOT run successfully without this registry entry. While this problem has been resolved in later PCOMM versions you can do the following to address the problem.
The recommended procedure in this situation is as follows:
INSTFIX.BAT can be run with the following options to preserve output to a log file, such as for silent install including errors in the log.
INSTFIX > FIX_PACK_4.TXT 2>&1
NOTE 1: INSTFIX.BAT issues
"NET STOP APPNNODE" to stop APPNNODE Services.
"NET STOP LDLCSERV" to stop LDLCSERV Services.
"CSTRACE STOP" and "CSTRACE SHUTDOWN" to stop CSTRCSER trace Service.
NOTE 2: INSTFIX will rename the current or target files being replaced to &file.pre6124, then copy the updated files.
If for some reason you rerun INSTFIX.BAT, you will receive errors during each rename because the &file.pre6123 file will already exist.The original copy of the file will be preserved in &file.pre6124 and available as a backup for restore purposes.
If for some reason you need to restore or backout this fixpack, you would have to manually rename the updated file names and restore the original files.
NOTE 3: INSTFIX.BAT issues VER to determine operating system version.
For Windows 2000, 2003 or XP user, INSTFIX.BAT will copy
APPNBASE.SYS as APPNBASE.SYS
LLC2W2K.sys as LLC2.SYS
For Windows NT user, INSTFIX.BAT will copy
APPNBNT.SYS as APPNBASE.SYS
LLC2NT.sys as LLC2.SYS
NOTE 4: The default value of the registry key
HKEY_LOCAL_MACHINE\SOFTWARE\IBM\Communications Server\CurrentVersion\VersionNumber
will be changed to 6124.
NOTE: If you are running Communications Server on Windows 2000 Server, then only the user who is a member of Administrator group can manage the SNA resources as well you can ignore the below mentioned steps.
If only the Administrator manages the SNA resources in this server, then you can ignore the following steps (A) and (B).
[Return to top of section] [Return to top of document] [Table of Contents]
| New APARs included in FixPack 4 since FixPack 3 | |
| None. | |
APARs included from previous fixpacks | |
| JR19572 | PCOMM 3270 LUA hangs running on SNA API CLIENT. |
| JR19449 | Apar addresses following problems:
|
| JR19788 | SLI BIND or STSN extensions routines not called. |
| JR20241 | Trap in CCS.DLL When SNA API Client processes UNBIND from Host and SLI_CLOSE from application at the same time. |
[Return to top of section] [Return to top of document] [Table of Contents]
| New function added in FixPack 4 | |
| None. | |
| New function added in FixPack 3 | |
| General enhancements | |
| 1. |
A new environment variable to specify LU alias has been added to SNA
API Client. This environment variable can be used when migrating an
application to WTS environment. Many client applications use a hardcoded
Local LU alias. When migrating to a WTS environment, this hardcoded Local
LU alias needs to be mapped to different LU alias for each user i.e. Local
LU alias x for user1 and y for user2. This can be done by configuring the
environment variable "LUALIAS<TPsLUALIAS>".
Follow the steps below for configuring multiple LU aliases in a WTS environment:
where:
Note: This environment variable has to configured under user environment variables. |
New function added in FixPack 2 | |
| Problem determination enhancements | |
| 1. | A new feature to create two message log files (MsgLog.dat) has been included. This is to reduce the size of each Message log file. Infobundler will collect both the Message Log files. |
| 2. |
In FixPack 2, a new feature that would collect debug information
in multiple trace files (i.e, multiple pcatrace.dat) has been included.
Infobundler will collect all the debug trace files. The following notes
document how to use this feature.
There are three batch files included with this new feature. These batch files update the registry with entries required for this feature. The batch files to be used for enabling or disabling this feature are:
If the option needs to be changed from append to replace or vice-versa, close all the applications, close the trace GUI (tracedg.exe), and run the relevant batch file. Run Delete.bat after product (SNA API Client) uninstall. If Delete.bat is not run after product uninstall, some registry keys related to the product will remain in the system. |
New function added in FixPack 1 | |
| Problem determination enhancements | |
| 1. |
Additional DEBUG Trace options:
Additional tracing has been added to capture more diagnostic information to diagnose problems. Now, when selecting ALL API trace option, additional diagnostic trace information is written to a new file called pcatrace.dat which is created in the client installation directory. |
| 2. |
Infobundler is provided with this version to capture key
client files required for problem diagnoses. It should be
run and output sent whenever pursuing a problem with IBM.
To run the infobundler, go to the SNA API Client installation directory (Eg: C:\CSNTAPI) from command line. Run INFOB.exe from command line. i.e, go to command prompt.
It will go through a series of 13 steps and finally collect the information (11 documents mentioned below) in trace.zip. trace.zip will be located in the directory where the traces exist. For any problem reported, run the infobundler and send the trace.zip file to IBM Support. The summary of features of the Infobundler for SNA API Client is as follows:
|
There is no change in client after Fixpack3 release. So, if you are already at fixpack3 or csnt6.1.2.3 refresh level of the client then no update is required.
Some examples follow:
CLINSTFIX c:\CSNTAPI BACKUP (backs up the directory)CLINSTFIX c:\CSNTAPI NOBACKUP (does not backup the directory)CLINSTFIX c:\CSNTAPI (default is NOBACKUP)CLINSTFIX c:\CSNTAPI BACKUP > CLINSTFIX.LOG 2>&1 (log to file)[Return to top of section] [Return to top of document] [Table of Contents]
Uninstallation instructions are in the Quick Beginnings book at http://www.ibm.com/software/network/commserver/windows/library/index.html
To ensure a complete uninstallation of the product, download the cleanup package (JR21546) from http://www.ibm.com/support/docview.wss?rs=2262&uid=swg24009834
If Personal Communications is installed on the same machine as Communications Server, you must uninstall Personal Communications before uninstalling Communications Server.
All applications using Communications Server should be terminated before you attempt to uninstall the product. Attempting to uninstall Communications Server while an application (such as APING or Personal Communications) is running will cause the uninstall to hang until the application is terminated.
[Return to top] [Table of Contents]
Tivoli, Tivoli Ready, Tivoli Management Environment, and TME are trademarks of Tivoli Systems Incorporated in the United States, other countries, or both.
Lotus and Domino are trademarks or registered trademarks of Lotus Development Corporation in the United States, other countries, or both.
Microsoft, Windows, Windows NT, Windows 2000, Windows XP, and Windows 2003 are trademarks or registered trademarks of Microsoft Corporation in the United States, other countries, or both.
Java, the Java logo, and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.