Frequently Asked Questions: PCI-X Coprocessor
On this FAQ page you may find answers to some of the questions you have concerning the coprocessor hardware and its IBM software.
- Which Windows operating systems are supported?
- Which Linux operating systems are supported?
- How can I maximize CCA throughput?
- What does a CCA return code/reason code of 12/338 mean?
- What should I know about Coprocessor batteries?
- Why do I have to wait for the 4764 card to be ready to use when it is powered on or reset, or when the device driver is loaded?
- What is the meaning of the "8xxxxxxx" return codes from CLU?
- How can I verify the integrity of an IBM 4764 Cryptographic Coprocessor?
- Can I use the Java programming language to build applications to use with the CCA API?
- Which Windows operating systems are supported?
Microsoft Windows Server 2003, Standard Edition (32-bit) is the only supported Windows operating system. - Which Linux operating systems are supported?
The following Linux operating systems are supported:- SUSE Linux Enterprise Server 9 from Novell (32-bit)
- SUSE Linux Enterprise Server 10 from Novell (32-bit) for Release 3.30.04 or later
- Red Hat Linux Enterprise 5.2, Server Edition (32-bit) for Release 3.30.05 or later
- How can I maximize CCA throughput?
A technical note describes how you can utilize additional multi-threading and key-caching capabilities of the CCA software to enhance throughput. - What does a CCA return code/reason code of 12/338 mean?
CCA return code 12, reason code 338, will arise when an application attempts to use CCA but the coprocessor has not been loaded with the CCA code. While other conditions can give rise to 12/338, this is often the source of difficulty. Be sure that the Coprocessor code loading is complete by following the instructions in Chapter 4 of the CCA Support Program Installation Manual and the README file accompanying your CCA software. To determine what software is loaded in your coprocessor, use the CLU utility ST or VA commands as also described in Chapter 4 of the manual. - What should I know about Coprocessor batteries?
See What should I know about Coprocessor batteries? - Why do I have to wait for the 4764 card to be ready to use when it is powered on or reset, or when the device driver is loaded?
Any time the 4764 card is reset, it goes through an extensive set of power-on self test (POST) functions which carefully test all parts of the card. This includes special tests required for a device that is certified under FIPS 140 at Level 4. Because the 4764 is a complex device and contains cryptographic hardware that must be carefully tested, these tests can take up to 2-3 minutes to run. The card is not available for use by application programs until the POST tests have completed execution. On most servers, this will not be a problem because the 4764 POST runs at the same time that the server itself is booting, and the 4764 is usually available before the server is ready to run application programs.
The user can cause the 4764 to be reset by explicitly loading the host device driver, or by running the CLU program. In either case, the card will begin executing POST and will not be usable for several minutes afterwards. You can write an application program to poll the card in order to determine when it is ready by periodically sending a CCA command like a Crypto_Facility_Query status request and waiting until it returns with a successful return code. - What is the meaning of the "8xxxxxxx" return codes from CLU?
See Understanding the 8xxxxxxx return codes. - How can I verify the integrity of an IBM 4764 Cryptographic Coprocessor?
See Validating the IBM 4764. - Can I use the Java programming language to build applications to use with the CCA API?
See Building Java applications to use with the CCA API.