IP Services: Replace configuration of TCP/IP legacy device types

Description

Support for the DEVICE and LINK profile statements for the following TCP/IP legacy device types are removed from IBM Communications Server in z/OS V2R2:
  • ATM
  • CDLC
  • CLAW
  • HYPERchannel
  • SNALINK (LU0 and LU6.2)
  • X.25
Because support will be eliminated for the ATM device type, the following associated TCP/IP profile statements will no longer be supported:
  • ATMARPSV
  • ATMLIS
  • ATMPVC
  • Start of changeTRANSLATE NSAPEnd of change
Start of changeBecause support will be eliminated for the CDLC, SNALINK (both LU0 and LU6.2), and X.25 device types, the following server applications will no longer be supported:
  • NCPROUTE
  • SNALINK LU0
  • SNALINK LU6.2
  • X.25 NPSI
End of change
Start of changeBecause support will be eliminated for the CLAW and HCH device types, the following TCP/IP profile statement parameters will no longer be supported:
  • IPCONFIG CLAWUSEDOUBLENOP and STOPONCLAWERROR
  • TRANSLATE HCH
End of change

If you are using these Start of changelegacy device typeEnd of change profile statements, migrate to a later interface type, such as OSA-Express QDIO or HiperSockets.

Note: This only affects device types that are configured to the TCP/IP stack.

As of z/OS V2R2, ZOSMIGV2R1_CS_LEGACYDEVICE migration health check is removed.

Table 1 provides more details about this migration action. Use this information to plan your changes to the system.

Table 1. Information about this migration action
Element or feature: z/OS® Communications Server.
When change was introduced: z/OS V2R2. This change was also announced in the Statement of direction: IBM zEnterprise System, z/OS, and z/VM enhancements shorten time to value, deliver enhanced security, and improve data access 114-009 February 24, 2014.
Applies to migration from: z/OS V2R1 and z/OS V1R13.
Timing: Before installing z/OS V2R2.
Is the migration action required? Yes, if you are using any of these legacy device types, you must migrate from these device types to more recent types, such as OSA-Express QDIO and HiperSockets™.
Target system hardware requirements: None.
Target system software requirements: None.
Other system (coexistence or fallback) requirements: None.
Restrictions: None.
System impacts: TCP/IP configuration error messages are issued if any of the affected profile statements are configured to the TCP/IP stack.
Related IBM® Health Checker for z/OS check: The ZOSMIGV2R1_CS_LEGACYDEVICE migration health check determines whether you are using any legacy device statements in your TCP/IP profile. This check is available on the following releases:
  • z/OS V1R13 with APARs PI12977 and OA44669 applied.
  • z/OS V2R1 with APARs PI12981 and OA44671 applied.

If any of these device type profile statements are processed, warning message EZZ0717I is issued.

Steps to take

Start of changeIf your current configuration includes functions for which support has been eliminated, perform the following steps:End of change
  1. Migrate to a later TCP/IP interface type, such as OSA-Express QDIO or HiperSockets.
  2. Start of changeReview your TCP/IP IPCONFIG and TRANSLATE profile statements for unsupported parameters.End of change
  3. Start of changeVerify you are not using the unsupported server applications.End of change
Start of changeYou should alsoEnd of change remove any customization for the ZOSMIGV2R1_CS_LEGACYDEVICE health check in your IBM Health Checker for z/OS HZSPRMxx parmlib member.

Reference information

For information about configuring OSA-Express QDIO and HiperSockets interfaces, see Considerations for networking hardware attachment in z/OS Communications Server: IP Configuration Guide.

Parent topic: Communications Server actions to perform before installing z/OS V2R2