© Copyright IBM Corporation 1999, 2002. All rights reserved.

Java^TM Communications API for OS/2, Version 2.0.1 is supported on the following OS/2 products:

• IBM® OS/2 Warp® 4 with FixPak 5 or higher for single-byte character set (SBCS) countries or regions
  or FixPak FX00505 for double-byte character set (DBCS) countries or regions
• IBM OS/2 Warp Server for e-business
• Convenience Package for OS/2 Warp 4
• Convenience Package for OS/2 Warp Server for e-business
• Convenience Package 2 for OS/2 Warp 4
• Convenience Package 2 for OS/2 Warp Server for e-business
• WorkSpace On-Demand Version 2.0, with the latest FixPak

Note: For information on the Double Byte Character Set (DBCS) FixPak equivalents, see the FixPaks section.

Contents

1.0 OVERVIEW

Java Communications API for OS/2 enables Java applications to have a platform-independent way of performing serial and parallel port communications for technologies such as voice mail, fax, and smartcards. After writing serial or parallel port communications for your application, you can then include those files with your application. You can also include Java Communications API for OS/2 with your application for redistribution.

Java Communications API for OS/2 supports EIA232 (RS232) serial ports and IEEE 1284 parallel ports and is supported on systems with the Runtime Environment that is a part of the IBM OS/2 Warp Developer Kit, Java 2 Technology Edition, 1.3.0 or later.

Using Java Communications API for OS/2, you can:

• List ports on a system.
• Open and claim ownership of ports.
• Resolve port ownership contention between applications.
• Perform asynchronous and synchronous access of I/O ports through event notification.
• Receive bean-style events describing state changes on the port.

1.1 FixPaks

The following considerations apply:

For information about downloading a particular FixPak, visit the IBM FixPak Web site at:

      http://ps.software.ibm.com/pbin-usa-ps/getobj.pl?/pdocs-usa/otherservices.html

2.0 INSTALLING JAVA COMMUNICATIONS API FOR OS/2

Complete the following steps to install Java Communications API for OS/2:

1. Place the Java Communications API for OS/2 ZIP file (javacomm.zip) in the [x:\javadir] directory, where [x:\javadir] is the drive and directory where you installed the Developer Kit and is one of the following as appropriate:
   • JAVA13 for Version 1.3.0 of the Developer Kit. By default, JAVA13 is the name of the directory.
   • JAVA131 for Version 1.3.1 of the Developer Kit. By default, JAVA131 is the name of the directory.
2. Unzip the ZIP file by typing the file name at a command prompt (from within the [x:\javadir] directory). The following list shows the files and the subdirectories into which the files are unzipped.

   comm.jar in [x:\javadir]\jre\lib\ext\ javacomm.prp in [x:\javadir]\jre\lib ibmcomm.dll in [x:\javadir]\jre\bin syslevel.jcm in [x:\javadir]\jre\bin

3. Restart the computer.

3.0 UNINSTALLING JAVA COMMUNICATIONS API FOR OS/2

To uninstall Java Communications API for OS/2, complete the following steps:

1. Go to the Developer Kit directory and delete the following files:

          [x:\javadir]\jre\lib\ext\comm.jar
          [x:\javadir]\jre\lib\javacomm.prp
          [x:\javadir]\jre\bin\ibmcomm.dll
          [x:\javadir]\jre\bin\syslevel.jcm

   where [x:\javadir] is the drive and directory where you installed the Developer Kit and is one of the following as appropriate:
   • JAVA13 for Version 1.3.0 of the Developer Kit. By default, JAVA13 is the name of the directory.
   • JAVA131 for Version 1.3.1 of the Developer Kit. By default, JAVA131 is the name of the directory.
   
   
   
2. Restart the computer.

4.0 DOCUMENTATION

For a general overview of JAVACOMM, see the following Web site:

http://java.sun.com

Click Products & APIs and scroll down to the Optional Packages section. The documents at this Web site contain links to many other Web-based information sources.

5.0 KNOWN LIMITATIONS

Parallel Port communications

• On the OS/2 platform, there is no output buffer. Java Communications API for OS/2 writes directly to the parallel port. Therefore the following method returns 0:
  
  ParallelPort.getOutBufferFree
  
  
• There is no NotifyOnBuffer event because this event gets triggered when the output buffer is empty.
• OS/2 does not support suspend() and restart().
• OS/2 does not support getMode() and setMode(). getMode() returns LPT_MODE_ANY. setMode() throws an exception.

Serial Port communications

• OS/2 does not support ReceiveFraming or ReceiveThresholds.
• OS/2 does not support opening the CommPort passing in a file descriptor.

6.0 NOTICES

© Copyright IBM Corporation 1999, 2002. All rights reserved.

U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

7.0 TRADEMARKS

The following terms are trademarks of International Business Machines Corporation in the U.S., or other countries, regions, or both:

      IBM
      OS/2
      OS/2 Warp

Java is a trademark of Sun Microsystems, Inc. in the U.S. and other countries or regions. The Java technology is owned and exclusively licensed by Sun Microsystems, Inc.

Other company, product, and service names may be trademarks or service marks of others.

THIS DOCUMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE AND MERCHANTABILITY WITH RESPECT TO THE INFORMATION IN THIS DOCUMENT. BY FURNISHING THIS DOCUMENT, IBM GRANTS NO LICENSES TO ANY PATENTS OR COPYRIGHTS.