IP Services: Relink NMI applications using the 64-bit TMI copy buffer function
Description
Starting with z/OS V2R1, the interface between the 64-bit TMI copy buffer function (EZBTMIC4) and the TCP/IP stack is changed. Applications that use the real-time TCP/IP network monitoring network management interface (NMI) and statically link to this function must either relink or change to dynamic linking or loading of the function.
Table 1 provides more details about this migration action. Use this information to plan your changes to the system.
| Element or feature: | Communications Server. |
|---|---|
| When change was introduced: | z/OS V2R1. |
| Applies to migration from: | z/OS V1R13. |
| Timing: | Before installing z/OS V2R2. |
| Is the migration action required? | Yes, if your application statically links to the 64-bit TMI copy buffer function (EZBTMIC4). No change is required for applications that use the 32-bit TMI copy buffer function (EZBTMIC1) or that dynamically link or load EZBTMIC4. |
| Target system hardware requirements: | None. |
| Target system software requirements: | None. |
| Other system (coexistence or fallback) requirements: | None. |
| Restrictions: | None. |
| System impacts: | None. |
| Related IBM Health Checker for z/OS check: | None. |
Steps to take
If your application statically links to the 64-bit TMI copy buffer function (EZBTMIC4), relink your application, or change your application to dynamically link to the 64-bit TMI copy buffer function (EZBTMIC4).
Reference information
For more information, see "EZBTMIC1 or EZBTMIC4: Copy TCP/IP Management Interface Data Buffer" in z/OS Communications Server: IP Programmer's Guide and Reference.