# Chapter 2. Overview of the OS/2 PCM Compatibility Testkit

The OS/2 PCM Compatibility Testkit is a set of automated test cases that verify that your hardware is compatible with OS/2 Warp. The OS/2 PCM Compatibility Testkit Version 4.6 tests the networking capabilities of the system. Personal computer manufacturers must establish network compatibility before a system can be added to the list of compatible systems.

This chapter describes:

- The high-level flow of the test process

- The skills required to use the OS/2 PCM Compatibility Testkit

- What you get with the OS/2 PCM Compatibility Testkit

- The test environment, including the hardware and software required to create the environment

- Which tests you need to run for your specific hardware and software configuration

## Using the Testkit

A good way to create your test environment is to start with systems that you know are compatible with OS/2 Warp and run all the tests in that environment. If a test case fails in an environment that is known to be compatible with OS/2 Warp, troubleshooting is not complicated by having a new system that may or may not be compatible with OS/2 Warp.

The steps involved in using the OS/2 PCM Compatibility Testkit are:

1. Obtaining the necessary hardware and operating system software

2. Connecting and configuring the machines to create a stable test environment (see Chapter 3, "Building the Test Environment")

3. Testing your machine in the stable environment by doing the following:

- If you want your system listed as a compatible server:

1. Test your machine in the role of an additional server and gather results.

2. Test your machine in the role of a domain controller and gather results.

- If you want your system listed as a compatible client:

1. Test your machine in the role of client 1 and gather results.

2. Test your machine in the role of client 2 and gather results.

(See Chapter 6, "Using Your System in the Stable Test Environment" for detailed information.)

Note: | If your system supports different LAN adapters, you can have your system listed with up to two different LAN adapters by testing with different LAN adapters when moving a system from one role to another. If you change LAN adapters, be sure to list both in the system hardware configuration PCM_HDW on panel 3.

1. Submitting the results to the OS/2 PCM Compatibility Test Program Office

2. Receiving email or fax confirmation from the OS/2 PCM Compatibility Test Program Office that your hardware has passed the test and will be added to the lists of compatible systems

This document provides detailed instructions to guide you through these procedures.

## OS/2 PCM Compatibility Testkit Materials

The OS/2 PCM Compatibility Testkit Version 4.6 consists of:

- A PCM Version 4.6 Testkit CD containing the software, documentation, and file templates needed to perform the compatibility tests

- Viewable and printable documentation about the OS/2 PCM Compatibility Testkit

- A license agreement for OS/2 PCM Compatibility Testkit

- A Welcome Letter, which includes instructions for printing this document

## Which Tests are Required

To be placed in the list of compatible systems your hardware must pass:

- The base test suite, which tests whether your machine is compatible with the OS/2 operating system in a non-networked environment

- The network test suite, which tests the networking features of OS/2

See Chapter 8, "PCM Base Test Case Details" and Chapter 9, "LAN Test Case Details" for a complete listing of the test cases.

### Base Tests

You must perform the OS/2 base compatibility tests on all systems, whether they are designated as client or server systems. The OS/2 base compatibility tests consist of:

- Required tests, which must be run on all systems. These tests include installation and initialization of OS/2, batch testing, stress testing, hardware interface tests, and special function tests, such as multimedia.

- Additional tests, which test specific hardware interfaces. You need to run these tests only if your system's shipped configuration supports these features:

- Advanced Power Management

- Symmetric MultiProcessing (SMP)

- PCMCIA

- Speech Recognition

- Capability to boot from partition the begins or extends beyond 8.3GB (cylinder 1024).

- Journaled File System (JFS) - required for OS/2 Warp Server for e-business.

These tests will be required for compatibility only if the system that is being tested will support the specific function.

Running the entire set of base tests takes approximately one and one half days. This includes time for setup and results processing.

### Network Tests

In addition to the base tests, your hardware must pass the network tests, which verify networking functions. A system may be tested as a client system, as a server system, or both.

#### Testing as a Server

If you want your system included in the list of compatible server systems, you must test it in both the additional server and domain controller roles as shown in Figure 3. You must submit a test results diskette showing that your system has passed the base tests and the network tests. Base system testing must be done only once using the additional server role. Network testing must be done for both the additional server and domain controller roles.

#### Testing as a Client

If you want your system included in the list of compatible client systems, you must test it in both client 1 and client 2 roles as shown in Figure 3. You must submit a test results diskette showing that it has passed the base tests and the network tests. Base system testing must be done only once using the client 1 role. Network testing must be done for both the client 1 and client 2 roles.

#### Testing as Both Client and Server

If you want your system included in both lists, compatible client systems and compatible server systems, you must perform all the tests and submit two test results diskettes, one from server testing and another from client testing.

Base testing is required in both client and server roles because the OS/2 base differs between the client and server products.

#### Duration of the Tests

The network tests take approximately two days to complete, including setting up the test environment, running the test cases, and collecting the results.

You should allow at least four days for the network tests to allow time to resolve problems and to rerun test cases after you fix problems discovered during the tests. This document describes an environment that can eliminate or minimize setup problems. If you choose to use a different configuration, troubleshooting might be more difficult.

## The Test Environment

The test environment consists of a network of systems configured as shown in the following figure:

Figure 3. The OS/2 PCM Compatibility Testkit Test Environment

The systems in this environment are:

- The domain controller

This server system controls access by users, manages the resources of your network, and controls the sharing of resources.

- An additional server

This system handles other server functions, such as file access, remote connections, and network printing.

The test cases require both domain and server tests to verify that your system correctly handles the handshaking between the domain and server systems.

- Client 1 and client 2

These systems act as requesters of services provided by the domain controller and the additional server, and test the peer-to-peer networking features of OS/2 Warp Version 4.

To set up this environment, you need:

- Two server systems (see "Server Hardware Requirements")

- Two client systems (see "Client Hardware Requirements")

- One printer (network or locally attached to the additional server) and the appropriate OS/2 driver

Note: | PCM compatibility testing requires only two client systems in the test environment. However, to meet certain requests from your customers, you may need to test server systems with more than two clients. See Appendix G, "Testing with Additional LAN Clients" for more information.

- Four LAN adapter cards with the appropriate driver and NIF files (see "Selecting LAN Adapter Cards")

- Two modems that are supported by LAN Distance (see "Finding a Supported Modem")

- Two analog phone lines.

Note: | If analog phone lines are not available, you can choose to test with a Null Modem cable instead of using modems.

- Ethernet hub or token ring MAU and category 5 cabling

- Three to four blank 3.5" high-density diskettes

### Server Software Requirements

Installation materials (CD and diskettes) for the server operating system. This can be any of the following:

- OS/2 Warp Server for e-business

- Convenience package for OS/2 Warp Server for e-business

### Server Hardware Requirements

The minimum hardware for each server is:

- System unit uses at least an Intel® 486 processor

- System unit has at least 32 MB RAM

- Hard drive with at least 1 GB capacity (at least 3 drives for RAID setup, and 1 additional drive for OS/2 Warp Server for e-business JFS volume spanning testcase).

- CD-ROM drive

- OS/2 boot partition with a minimum of 500 MB free space, which includes a minimum of 50 MB for swapper.dat. This also includes space for the network test cases, but not for the base test cases.

- For additional server, a PCMTEST partition with at least 230 MB free space for base test cases. This may be the boot partition or another local (non-network) drive.

- For domain controller, a SADUMP partition of at least 20 MB larger than installed memory. This can be the same space allocated for the PCMTEST partition.

- A Journaled File System (JFS) partition. To test volume spanning, two physical disks are required.

- The printer device driver for the printer in your test environment.

- If your machine supports multimedia, you need the appropriate multimedia hardware:

- Sound card

- Speakers

- CD-ROM drive

- An audio (music) CD

### Client Software Requirements

You may install one of these operating systems on a client system:

- OS/2 Warp Version 4

- Convenience Package for OS/2 Warp Version 4

### Client Hardware Requirements

The minimum hardware for each client is:

- System unit uses at least an Intel 486sx processor. If you plan to run the speech recognition tests, the system unit must have at least an Intel Pentium® processor, 90 MHz or faster.

- System unit has at least 16 MB RAM

- Hard drive with at least 1 GB capacity

- OS/2 boot partition with a minimum of 400 MB free space, which includes a minimum of 50 MB for swapper.dat. The networking test cases are installed on the boot drive.

- At least 230 MB free space for installing the base test cases. This may be the boot partition or another local (non-network) drive.

- CD-ROM drive

- Printer support should be installed even if no printer is attached.

- If your system supports multimedia, you need the appropriate multimedia hardware:

- Sound card

- Speakers

- CD-ROM drive

- An audio (music) CD

- If your system supports speech recognition, you need:

- A microphone compatible with OS/2 Warp Version 4

- Sound card

- Speakers

### Selecting LAN Adapter Cards

- The LAN adapter cards should be either all token ring or all Ethernet. It is helpful if all four adapters are the same kind or at least use the same driver. Using the same driver will save some setup time later on. However, it is possible to mix adapter cards, as long as they are all of the same type, either all Ethernet or all token ring.

- Use one of the adapters supported by OS/2, information on supported adapters can be found in the online guides:

- For OS/2 Warp Server products, see the MPTS Configuration Guide.

- For OS/2 Warp 4, see the Network Adapters and Protocol Services Guide.

Note: | Additional information on LAN Adapters supported can be found on the WEB at: http://service.software.ibm.com/os2ddpak/html/index.htm.

- The choice of LAN adapter for the additional server is of particular importance because that adapter is used by the Remote Connection Server. Select an adapter from the list of Tested and Approved adapters that passed the Remote Connections testing. If you are using a Token Ring as the LAN type and the adapter being used uses the IBMTOK driver, then you have an adapter that should work.

- For LAN adapter cards not listed, check with the adapter manufacturer for driver availability, and any setup or configuration requirements that may be needed for OS/2 and LAN Distance.

### Finding a Supported Modem

Use a modem that is supported by LAN Distance. A list of supported modems is provided in the online IBM Remote Access Guides.