IBM Communications Server for Windows
Version 6.4 FixPack 1
Readme

© Copyright International Business Machines Corp. 2009
All Rights Reserved
Licensed Material - Property of IBM
US Government Users Restricted Rights - Use, duplication or
disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
Table of Contents
1 About this update
2 National Language Support (NLS)
3 Server update information
4 Client update information
5 Uninstall information
6 Web site and support information
7 Notices and trademarks

1 About this update

Section Table of Contents
1.1 New in this fixpack
1.2 Product fix history
1.3 Files included

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/Windows Version 6.4 FixPack 1 is an upgrade that includes FixPack 1 updates. It is not a full install, and requires that CS/Widnows V 6.4 GA level should be installed to install fixpack1. Only fixpacks greater than FixPack 1 should be installed after this installation.

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] [Table of Contents]

1.1 New in this fixpack

For details on new functions, see the "New function" subsections of the Server and Client update information sections. In addition, all APAR fixes since GA up to and including FixPack 1 are included.

[Return to top of section] [Return to top of document] [Table of Contents]

1.2 Product fix history

This update includes fixes to the CS/Windows 6.4 from GA.

Check the web sites listed in section 6 for the latest information about this product.

Notes:

  1. This fixpack will be a pre-requisite of all future CS/Windows 6.4 APARs.
  2. This fixpack should only be applied to CS/Windows 6.4 at GA level .Only fixpacks greater than FixPack 1 should be installed after this installation.

[Return to top of section] [Return to top of document] [Table of Contents]

1.3 Files included

The Fixpack1 release includes the following files:

README.HTM This ReadMe.htm is included in JR33995.EXE, JR34488.EXE and R34492.EXE package, which describe about the fixes, new functions, and install instructions.
JR33995.EXE Self extracting executable that contains Server.exe and nlspack.exe for FixPack1 files to be installed on the CS/Widnows 6.4 Server install.
JR34488.EXE Self extracting executable that contains Client.exe and nlspack.exe for FixPack 1 files to be installed on the CS/Widnows 6.4 API Client install.
JR34492.EXE Self extracting executable that contains FixPack 1 files to be installed for CS/Windows 6.4.0 Remote Admin Client install.

nlspack.exe:

    Self extracting executable that contains FixPack 1 language files to be installed on the CS/Windows 6.4 Server and API-Client installation. The English version of this module is installed as part of the server or client install by default. If CS/Windows 6.4 was installed on non-English language machine, you must install the appropriate version of this NLS package after the server and client installation.

[Return to top of section] [Return to top of document] [Table of Contents]

2 National Language Support (NLS)

Section Table of Contents
2.1 Files included
2.2 Install instructions

[Return to top] [Table of Contents]

2.1 Files included - NLS

nlspack.exe: Includes the language packages for all the languages, which CS/Windows 6.4 supports. Run the appropriate self extracting language pack with the -d option, so that the language files will be extracted with proper directory structure. CS/Windows supported on the following languages:

CHS : Simplified Chinese
CHT : Traditional Chinese
DEU : German
ESP : Spanish
FRA : French
ITA : Italian
JPN : Japanese
KOR : Korean
PTB : Brazilian Portuguese

[Return to top of section] [Return to top of document] [Table of Contents]

2.2 Install instructions - NLS

The NLS update can be integrated into and installed as part of the server or client update or can be installed separately after the server or client update by running instfix.bat present in the nlspack.exe.

2.2.1 Integrated with server or client update
2.2.2 Separate, after server or client update

[Return to top of section] [Return to top of document] [Table of Contents]

2.2.1 Integrated with server or client update

Instructions to update the server package with the NLS updates:

  1. Replace the pcsnops.exe, adminstrings.dll and pcstrcres.dll in the server package with those included in the respective language pack of nlspack.
    Example: If you are installing the fixpack on French Operating system then replace those modules from nlspack present under ..\FRA\ directory.
  2. Copy the file PCCFGXXX.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.
  3. Update the server INSTFIX.BAT file with an appropriate rename and copy statement for the pccfgxxx.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.

Instructions to update the API client package with the NLS updates:

  1. Replace the setco.exe, testlu62.exe and tracedg.exe in the client update package with those included from the appropriate sub-directory of this package.
  2. Update the client INSTFIX.BAT file with an appropriate rename and copy statement present in the client.exe. See existing rename and copy statements in INSTFIX.BAT for format.

[Return to top of section] [Return to top of document] [Table of Contents]

2.2.2 Separate, after server or client update

Server Install instructions:

  1. Install the server updates first, following the instructions in section 3.
  2. Stop the CS/Windows node and all applications that use CS/Windows.
  3. Copy nlspack.exe of Server, which is present in JR33995.EXE to a temporary directory.
  4. Run the nlspack.exe, which will extract all the language packs.
  5. Choose the appropriate NLS package based on the CS/Windows language that is installed, and Run the respective language pack.
    Example: If you wanted to install Simplified Chinese language pack then Run chs.exe -d
    This will create a sub-directory chs and extract all the files under chs directory for Simplified Chinese language.
  6. Review the comments in the INSTFIX.BAT file for specific usage instructions. For example:
    • INSTFIX chs (no parameters; environment variables will be used to locate the installation location)
    • INSTFIX chs> nlsfp1.txt 2>&1 (silent install)
    • INSTFIX chs "C:\Program Files\IBM\Communications Server" (specify the directory)
    • INSTFIX chs "C:\Program Files\IBM\Communications Server" > nlsfp1.txt 2>&1 (silent install, specify directory)
  7. Reboot and start the CS/Windows node.

NOTE:
INSTFIX.BAT checks if a PCOMM version less than 5.7 CSD3 is installed and if true, does not update the Trace Facility. CS/Windows 6.4 would use the Trace Facility installed by PCOMM. If you have installed PCOMM 5.7 CSD3 or PCOMM 5.8 on CS/Windows 6.4, PCOMM will not install its Trace Facility. In this case, NLS_INSTFIX will update the CS/Windows 6.4 Trace Facility.

If versions of PCOMM prior to 5.7 CSD3 are installed, you will not have any of the CS/Windows 6.4 Trace Facility updates or enhancements.

Client Install instructions:

  1. Install the client updates first.
  2. Stop the all applications that use API-CLIENT.
  3. Copy nlspack.exe of API Client, which is present in JR34488.EXE to a temporary directory.
  4. Run the nlspack.exe, which will extract all the language packs.
  5. Choose the appropriate NLS package based on the API Client language that is installed, and Run the respective language pack.
    Example: If you wanted to install Simplified Chinese language pack then Run chs.exe -d
    This will create a sub-directory chs and extract all the files under chs directory for Simplified Chinese language.
  6. Review the comments in the INSTFIX.BAT file for specific usage instructions. For example:
    • INSTFIX chs "C:\Program Files\IBM\CS SNA API Client" (specify the directory)

[Return to top of section] [Return to top of document] [Table of Contents]

3 Server update information
Section Table of Contents
3.1 APARs included
3.2 Files updated - server
3.3 New function - server
3.4 Install instructions - server

[Return to top] [Table of Contents]

3.1 APARs included


APARS included from FixPack 1
JR33070SLOW PERFORMANCE RUNNING LU62 TRANSACTIONS ON SNA API CLIENT.
JR33954ERROR WHEN ATTEMPTING TO CONFIGURE EICON CONNECTION.

[Return to top of section] [Return to top of document] [Table of Contents]

3.2 Files updated - server

The server update of this fixpack will replace existing files with those in these lists.

Directory of "C:\Program Files\IBM\Communications Server" (Communications Server installation directory) 

09/10/2009  13:36            45,056 adminapi.dll
09/10/2009  13:36           397,312 adminserver.dll
09/10/2009  13:32            69,632 adminstrings.dll
09/10/2009  13:23            77,824 adRAPIClient.dll
09/10/2009  13:37            40,960 adRAPIStubs.dll
09/10/2009  13:22            53,248 adRapiUtil.dll
09/10/2009  13:58            36,864 anutil.dll
09/10/2009  13:58            24,576 anyloadr.exe
09/10/2009  13:58            24,576 anytrace.dll
09/10/2009  13:58            24,576 anytrc.dll
09/10/2009  13:58            24,576 anytrfmt.dll
09/10/2009  14:08            32,768 anyws2in.dll
09/10/2009  14:07            36,864 anyws32.dll
09/10/2009  14:06            24,576 anywsipc.dll
09/10/2009  13:31            49,152 cscm.dll
09/10/2009  13:44            36,864 csdisplay.exe
09/10/2009  13:58            24,576 ipc.dll
09/10/2009  13:59           118,784 ippmm.dll
09/10/2009  13:41            45,056 ldlc.dll
09/10/2009  14:06           163,840 mptncmm.dll
09/10/2009  13:02           155,648 msgbrwsr.exe
09/10/2009  13:50           460,288 ocdconvt.dll
09/10/2009  13:21           286,720 pccfgenu.dll
09/10/2009  13:21            94,208 Pcscapi.dll
09/10/2009  13:14            32,768 pcscca.exe
09/10/2009  13:27         1,290,240 pcscfg.exe
09/10/2009  13:01           151,552 pcsmfcx.dll
09/10/2009  13:39           442,368 pcsnops.exe
09/10/2009  13:02            45,056 rasbut.exe
09/10/2009  12:57           684,139 snaformat.exe
09/10/2009  14:09           114,688 snapmm.dll
09/10/2009  14:06           122,880 snasm.dll
09/10/2009  14:07            24,576 sxmap.exe
09/10/2009  14:11            36,864 tn3270d.dll
09/10/2009  14:11           249,856 tn3270wn.exe
09/10/2009  13:28            20,480 vacgcon.exe
09/10/2009  13:28           110,592 vacgwin.exe
09/10/2009  16:36            65,536 wappc32.dll
09/10/2009  13:45            49,152 winaping.exe
09/10/2009  16:36            65,536 wincsv32.dll
09/10/2009  13:12            32,768 winms32.dll
09/10/2009  13:13            36,864 winnof32.dll

Directory of %snaroot%\properties\version where "%snaroot%" is the installation folder of CS/Windows. 

29/09/2009  15:24               161 IBM_Communications_Server_for_Windows.6.4.0.swtag
29/09/2009  15:24               208 PTF_V6.4.0.1_for_Communication_Server_Windows.6.4.0.1.fxtag

Directory of %systemroot%\system32\drivers 

09/10/2009  14:00            38,512 anydlc.sys
09/10/2009  13:11         1,621,913 appn.sys
09/10/2009  13:13           124,956 appnapi.sys
09/10/2009  13:05           400,157 appnbase.sys
09/10/2009  13:53            28,672 ldlcserv.exe
09/10/2009  13:53            40,960 ldlcserv6.exe
09/10/2009  13:06           103,193 llc2.sys
09/10/2009  13:53            64,512 pdlndldl.sys
09/10/2009  13:53            72,704 pdlndldl6.sys
09/10/2009  13:52            70,656 pdlndlpb.sys
09/10/2009  13:52            53,248 pdlndqll.sys
09/10/2009  13:52            67,584 pdlndsdl.sys
09/10/2009  13:54            59,392 pdlnshay.sys
09/10/2009  13:54            22,464 pdlnslea.sys
09/10/2009  13:54            54,304 pdlnsv25.sys
09/10/2009  13:55            58,768 pdlnsx25.sys
09/10/2009  13:32            40,576 qeldrvr.sys

Directory of %snaroot%\Trace Facility where "%snaroot%" is the installation folder of CS/Windows. 

09/10/2009  13:03           122,880 trcgui.exe

[Return to top of section] [Return to top of document] [Table of Contents]

3.3 New function - server

New function added in FixPack 1
Active LUs Display
1.

Option to display Active LU 0 to 3:

Csdisplay can display all the LU's used by the LUA application or by the TN3270 Sessions with the new option of ALU. To check the active LUA & TN3270E session, type "csdisplay ALU" from the command Windows prompt.

Example output of the "csdisplay ALU" as follows: 

1) When there is one LUA SSCP-LU and one LUA LU-LU Session active.


csdisplay ALU


LU Name BASELU0A
PU Name PUNAME
NAU Address 10
Session Type SSCP-LU

LU Name BASELU02
PU Name PUNAME
NAU Address 2
Session Type LU-LU


Total number of configured LU's 25
Number of active LUs 9
Number of SSCP connected LUs 1
Number of active LU Application Sessions 1
Number of active TN3270 Sessions 0

2) When there is one SSCP-LU TN3270 and one LU-LU TN3270 Session type.

csdisplay ALU

LU Name BASELU02
PU Name PUNAME
NAU Address 2
Session Type TN3270E SSCP-LU, 9.122.19.75

LU Name BASELU03
PU Name PUNAME
NAU Address 3
Session Type TN3270E LU-LU, 9.122.19.75


Total number of configured LU's 25
Number of active LUs 9
Number of SSCP connected LUs 0
Number of active LU Application Sessions 0
Number of active TN3270 Sessions 2

3) When there is no SSCP Connected LU's or active LUA Application Seesions or active TN3270 Session.

csdisplay ALU

None

Note : Even, if there are 25 configured LU's, 9 active SSCP-LU's and no LUA or TN3270 LU's active then the output for this command will be NONE.

Snaformat enhance to format the Control Vector (X'82')
1. The snaformat tools is been updated to format the CV'82' Subarea characteristics subfields, the formated trace will be presented in the .det file.

[Return to top of section] [Return to top of document] [Table of Contents]

3.4 Install instructions - server

Installing the fixpack on the system:
  1. Download JR33995.EXE in Binary format into a temporary directory.

  2. Run the JR33995.EXE, which will extract Server.exe and nlspack.exe
  3. Run Server.EXE with -d option to extract all server files. There are executables included in this package, those are required for fixpack installation. The instfix.bat in current directory is required only for the fixpack installation.
    1. If you have SNA API Client Services (Split-stack API Client/Server), copy API_Client.EXE in the client workstation and see section 4 for install instructions.
    2. nlspack.exe contains non-English language updates. Customers running non-English versions of CS/Windows also need to install NLSPACK package seperately. To install the language pack refer section 2 for NLS install instructions.

  4. New function updates have been included with this fixpack package. See section 3.3 for more details on the new updates.
    1. INSTFIX.BAT checks if a PCOMM version less than 5.7 CSD3 is installed and if true, does not update the Trace Facility. CS/Windows 6.4 would use the Trace Facility installed by PCOMM. If you have installed PCOMM 5.7 CSD3 and above on CS/Windows 6.4, PCOMM will not install its Trace Facility. In this case, INSTFIX will update the CS/Windows 6.4 Trace Facility.

      If versions of PCOMM prior to 5.7 CSD3 are installed, you will not have any of the CS/Windows 6.4 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/Windows 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:

      1. Remove PCOMM using Add or Remove Programs
      2. Remove CS/Windows 6.4
      3. Re-install CS/Windows 6.4
      4. Install PCOMM 5.8 (or PCOMM 5.7 CSD3 or later)
      5. Apply CS/Windows 6.4 Fixpack1 maintenance upgrade

  5. Stop Communications Server for Windows (including your node, Node Operations, Node Configuration, Log Viewer, and any other CS/Windows components you have started). Note that there may still be CS/Windows-related services running on the machine after stopping these applications, but this is normal and should not affect the installation of this fix pack package.
    1. Stop ALL Window applications on this box since a reboot will be required after running INSTFIX.BAT maintenance installation.
    2. Refer the INSTFIX.BAT for details on various installation options.

    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_1.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.pre6401, then copy the updated files.

    If for some reason you rerun INSTFIX.BAT, you will receive errors during each rename because the &file.pre6401 file will already exist.The original copy of the file will be preserved in &file.pre6401 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: After all the files are copied, INSTFIX.BAT automatically issues
    "SERVICESTEST -c LDLCSERV" command to initialize LDLCSERV service.
    "NET START LDLCSERV" to start LDLCSERV service.

    NOTE 4: The default value of the registry key HKEY_LOCAL_MACHINE\SOFTWARE\IBM\Communications Server\CurrentVersion\VersionNumber will be changed to 6401.

  6. After running INSTFIX.BAT, confirm ALL component parts listed in section 3.2 reflect new dates. If they do NOT, then you must manually copy them after you REBOOT but prior to starting any IBMCS Services. ALL files must reflect updated dates or IBMCS will not function properly.

  7. If you want to restrict the user(Non-Administrator) from controlling SNA resources like Stoping/Starting the node/link etc., you have to run the batch file below and follow the step (B) mentioned below.

    1. Run the batch "AccessControlSettings.bat"

    2. If you are running Windows XP or 2003 and above do the following: (For Windows NT and 2000, skip this step.)
      1. Run regedit to start the registry editor (start->run then type regedit).
      2. Navigate to HKLM\Software\IBM\Communications Server
      3. Right-click on Communications Server and select Permissions.
      4. Click the "Add" button.
      5. Click the "Advanced" button.
      6. Click the "Find Now" button.
      7. Select "IBMCSADMIN" from the resulting list and click the "OK" button.
      8. Click the "OK" button.
      9. Select "IBMCSADMIN" from the list.
      10. Check the appropriate box to allow "Full Control".
      11. Click the "OK" button.
      12. Navigate to HKLM\Software\IBM\OEM_CONFIG and repeat the steps from "3" to "11".
      13. Exit the registry editor.

  8. Shutdown and Restart WINDOWS to reboot the machine.

  9. You can now start IBMCS Node Operations and configure the new available functions.

[Return to top of section] [Return to top of document] [Table of Contents]

4 Client update information
Section Table of Contents
4.1 APARs included
4.2 New function - client
4.3 Install instructions - client
4.4 Files updated - client

[Return to top] [Table of Contents]

4.1 APARs included

New APARs included in FixPack 1 since CSNT6.4 GA
None.

[Return to top of section] [Return to top of document] [Table of Contents]

4.2 New function - client

New function added in FixPack 1
APPC Cancel Conversation support
1. The CANCEL_CONVERSATION verb is a control verb that will cancel a connection between a local LU and partner LU using a specific transaction program (tp_id) and a conversation (conv_id). The definition of the VCB structure for the CANCEL_CONVERSATION verb is as follows: 
    typedef struct cancel_conversation
    {
    unsigned short opcode;     /* verb operation code     */
    unsigned char opext;       /* verb extension code     */
    unsigned char format;      /* format                  */
    unsigned short primary_rc; /* primary return code     */
    unsigned long secondary_rc;/* secondary return code   */
    unsigned char tp_id[8];    /* TP identifier           */
    unsigned long conv_id;     /* conversation identifier */
    } CANCEL_CONVERSATION;
Please refer the Client/Server programming guide for usage of this verb.
[Return to top of section] [Return to top of document] [Table of Contents]

4.3 Install instructions - client

Installing the fixpack on the system:
  1. Be SURE you have downloaded the 6.4 FixPack 1 APAR package (JR34488.exe) in BINARY format.
  2. Create a temporary directory, copy the JR34488.exe, and Run JR34488.exe, which will extract API_Client.exe and nlspack.exe for the API Client
  3. Run API_Client.exe to extract all the API Client's updated files
  4. Stop ALL running SNA API client applications on this machine. Check the Task Manager and stop any running API CLIENT exe's such as ATTMSG.EXE and LU62MGR.EXE.
  5. INSTFIX.BAT is an installation batch file. INSTFIX.BAT will backup the files to a folder called *.pre6401, then install/copy the updated the DLL's and EXE's to the supplied installation folder. View the comments included in INSTFIX.BAT usage instructions.

    Some examples follow:

    • INSTFIX "C:\Program Files\IBM\CS SNA API Client" (to install fixpack)
    • INSTFIX "C:\Program Files\IBM\CS SNA API Client" > CLINSTFIX.LOG 2>&1 (log to file)
  6. nlspack.exe contains non-English language updates. Customers running non-English versions of API Client also need to install NLSPACK package seperately. To install the language pack refer section 2 for NLS install instructions.
  7. After running INSTFIX, shutdown and restart the machine to complete the installation.

[Return to top of section] [Return to top of document] [Table of Contents]

4.4 Files updated - client

The client update of this fixpack will replace existing files with those in these lists.

Directory of "C:\Program Files\IBM\CS SNA API Client" (SNA API Client installation directory) 

09/10/2009  14:19            45,056 AMISC.DLL
09/10/2009  14:19            49,152 ASPRT.DLL
09/10/2009  14:19           126,976 CCM.DLL
09/10/2009  14:18            77,824 CCS.DLL
09/10/2009  14:25           131,072 CSCCFG.EXE
09/10/2009  13:29            98,304 ibmslp.dll
09/10/2009  14:23            61,440 MGRLVL.DLL
09/10/2009  12:55            36,864 nstrc.dll
09/10/2009  14:24            40,960 RESETAPI.EXE
09/10/2009  14:24            32,768 SETCO.EXE
09/10/2009  14:22           102,400 SSET.DLL
09/10/2009  14:25            57,344 TESTLU62.EXE
09/10/2009  14:24            65,536 TRACEDG.EXE
09/10/2009  13:15            36,864 TRNSDT.DLL
09/10/2009  14:19            32,768 WAPPC32.DLL

Directory of "C:\Program Files\IBM\CS SNA API Client\properties\version" 

29/09/2009  15:24               166 IBM_SNA_API_Client_for_Windows.6.4.0.cmptag
29/09/2009  15:24               206 PTF_V6.4.0.1_for_SNA_API_Client_for_Windows.6.4.0.1.fxtag

[Return to top of section] [Return to top of document] [Table of Contents]

5 Uninstall information
Uninstallation of a fixpack is not supported. To revert to a previous level, uninstall the product completely, then install the GA level, then install the desired fixpack level.

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 of document] [Table of Contents]

6 Web site and support information

Product information
For the latest information about the IBM Communications Server family of products, visit the Communications Server Web site at http://www.ibm.com/software/network/commserver. This Web site provides information and links to headline information, specification sheets, frequently asked questions, education, and much more.

Product support
For the latest support information, visit the Communications Server Support Web site at http://www.ibm.com/software/network/commserver/support. This Web site provides information and links to code fixes, tips, newsgroups, maintenance, and much more.

Technical notes
Search the hints and tips in the IBM Support database at http://www.ibm.com/software/network/commserver/windows/support/.

Technical support
For technical assistance or questions, call the IBM support center for your country. For example, in the United States, call 1-800-IBM-SERV.

[Return to top] [Table of Contents]

7 Notices and trademarks

AnyNet, IBM, S/390, WebSphere, and z/OS are trademarks or registered trademarks of IBM Corporation in the United States, other countries, or both.

Tivoli, and Tivoli License Management are trademarks of Tivoli Systems Inc. or IBM Corporation 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, Windows Server 2003, Windows Vista, Windows Server 2008 and Windows 7 are trademarks or registered trademarks of Microsoft Corporation in the United States, other countries, or both.

VMware is a registered trademark of VMware, inc.

[Return to top] [Table of Contents]