Enterprise Extender connections with TPX

Products

• TPX - Session Management

Issue/Introduction

Does TPX support Enterprise Extender connections?

We are converting our VTAM TRL to Enterprise Extender connections.

Environment

TPX - Session Mangement

z/OS

Resolution

Enterprise Extender (EE) interacts with TPX through APPN with VTAM, providing an extension to TCP/IP networks. TPX requires VTAM LU2 over SNA to function.

TPX relies on the standard VTAM/SNA architecture to establish sessions, and VTAM handles the translation or extension to the Enterprise Extender environment

Key interaction details include:

1. No Direct Link: There is no direct connection between TPX and Enterprise Extender and no configurations are required in TPX to support VTAM EE.
2. VTAM Requirement: Connectivity is only established via VTAM / APPN..
3. Disaster Recovery (DR) Troubleshooting: In case of migration to another CEC where TPX can no longer reach an application, the EE connection may need to be recycled to restore access.

To display Enterprise Extender (EE) details and troubleshoot connectivity for TPX, the following VTAM display commands are used:

• /D NET,EE,LIST=DETAIL – Displays detailed information about Enterprise Extender connections..
• /D NET,NETSRVR,SCOPE=ALL – Displays network node server information.
• /D NET,ADJSSCPS – Displays adjacent system services control point information.
• /D NET,ID=ISTADJCP,E – Displays information about adjacent control points.
• /D NET,ID=ISTCDRDY,SCOPE=ALL – Displays the status of dynamic CDRSCs.
• /D NET,RSCLIST,ID=*,IDTYPE=CDRSCS – Lists cross-domain resources.
• /D NET,ID=tso-applid,E – Displays the status of a specific application ID.

If TPX can no longer reach an application after a migration or environment change, the EE connection may need to be recycled to restore connectivity, however be careful when recycling the EE because it will impact all network-reliant applications, especially in the production system.