TPF Family Products: Drivers
Tab navigation
- z/TPF 1.1 & z/TPFDF 1.1 - selected tab,
- TPF 4.1
| Driver | Last Updated |
|---|---|
| API5
Driver
The API5 driver executes test cases for APIs such as Macros, C function interfaces, and grouped functional interfaces. |
added 16 Sept 2005 |
| CHER
Driver
The CHER driver exercises and tests TPF's I-stream SHARING ability by manipulating program AFFINITY values. |
added 21 Nov 2006 |
| CORO
Driver
The CORO test driver uses and verifies the commit rollback support on the z/TPF system. |
added 26 June 2006 |
| DEB5
Driver
The DEB5 driver is used to build, maintain, and modify a subsystem user unique database. |
added 13 June 2006 |
| HOTx
driver
The HOTX driver tests the TPF DASD supports by creating a 'hot record' to blast channels and to test cache. |
added 15 May 2006 |
| KPTS
driver
The KPTS driver is used to test the C APIs and assembler macros that provide support for >4K keypoints. |
added 19 April 2006 |
| LISH
driver
The Lodic/Input List Shutdown Driver is used as a test tool to create background activity in a TPF system. |
added 16 Sept 2005 |
| MEM5
driver
The MEM5 driver tests ECB and system heap test cases. |
added 8 Aug 2006 |
| MPIF
Driver
The MPIF driver generates communications across a channel-to-channel (CTOC) device. |
added 5 June 2006 |
| MQ
Series Driver (MQS1) for TPF
The MQS1 driver is a generic test driver that tests various capabilities of MQ Series support on TPF. |
Updated 26 June 2006 |
| POOL
Driver (z/TPF)
The Pool driver allows users of systems to cycle through available pools quickly. |
added 16 Sept 2005 |
| SOLD
Driver
The SOLD driver is used to test intra- and inter-module calls between various shared objects. |
added 26 June 2006 |
| SIPC
Driver (z/TPF)
The SIPC driver tests IPC by generating IPC traffic as well as background activity. |
added 16 Sept 2005 |
| Tape
Driver for z/TPF
The TAPE Driver is intended to be used as a test tool to exercise the TPF tape macros. |
Updated 11 Feb 2008 |
| TRAG
Driver
The TRAG driver verifies an ECB will use its first tracegroup buffer (IBM_DEFT) after exceeding its number of allocated tracegroup buffers. |
added 19 April 2006 |
