Does the TCPaccess Communications Server support the use of OSA-E5 devices?
The TCPaccess Communications Server has been End of Life since March 1 2012.
For this reason no further code changes are possible, and no further certifications of any hardware, software or other devices are being performed.
As of this writing, we fully support the use of OSA-E3 devices and are aware of customers utilizing OSA-E4 devices with no reported problems.
We now also have multiple customers utilizing OSA-E5 1Gbe devices in QDIO (OSD) mode with no reported problems.
As noted above, the OSA-E5 device will not be certified, and are aware that changes have been made, but no customers using these devices have reported any impact to connectivity or other problems.
Two types of OSA-E5 devices are available:
OSA-E5 1Gbe 1000 Base T – this device can run in both LCS and QDIO mode.
OSA-E5 10 Gbe Fiber – this device runs only in QDIO mode
Up to this point, all OSA-E devices genned to utilize LCS mode have functioned over TCPaccess with no problem, even when QDIO mode failed. We therefore expect this to be the case with OSA-E5 1Gbe 1000 Base T as well, but cannot provide a guarantee that it will work in your environment.
Up to this point, the OSA-E5 1Gbe in QDIO mode is functioning without problems at customer sites, but we cannot provide a guarantee that it will work in your environment.
We strongly recommend against utilizing the OSA-E5 10 Gbe Fiber device. Due to increased speed in both the device and associated hardware, it may overrun the TCPaccess Communications Server, resulting in slower throughput or other unexpected problems. As no code changes are possible, this could potentially result in severe, unresolvable connectivity problems between your mainframe and network.
An upgrade to and implementation of either of the OSA-E5 devices is fully at your own risk as we cannot guarantee their functionality in your environment, and any code based problems cannot be corrected.
In case of questions or problems, CA technical support is available to assist with configuration and connectivity issues on the TCPaccess CS side.
Configuration or implementation problems with the OSA itself should be resolved with the assistance of IBM.