z/OS Communications Server

SNA Network Implementation GuideVersion 2 Release 3

SC27-3672-30

IBM

Note:Before using this information and the product it supports, be sure to read the general information under Notices on page829.

This edition applies to Version 2 Release 3 of z/OS (5650-ZOS), and to subsequent releases and modifications untilotherwise indicated in new editions.

Last updated: March 21, 2018

Copyright IBM Corporation 2000, 2018.US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv

Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xix

About this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiWho should read this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiHow this document is organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiHow to use this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxii

How to contact IBM service . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiiConventions and terminology that are used in this information . . . . . . . . . . . . . . . . . xxiiiHow to read a syntax diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxivPrerequisite and related information . . . . . . . . . . . . . . . . . . . . . . . . . . xxvi

Summary of changes for SNA Network Implementation Guide . . . . . . . . . . . xxxiChanges made in z/OS Communications Server Version 2 Release 3. . . . . . . . . . . . . . . . xxxiChanges made in z/OS Communications Server Version 2 Release 2, as updated June 2017 . . . . . . . . xxxiiChanges made in z/OS Version 2 Release 2, as updated September 2016 . . . . . . . . . . . . . . xxxiiChanges made in z/OS Version 2 Release 2, as updated March 2016 . . . . . . . . . . . . . . . xxxiiChanges made in z/OS Version 2 Release 2 . . . . . . . . . . . . . . . . . . . . . . . xxxiiiChanges made in z/OS Version 2 Release 1, as updated September 2014 . . . . . . . . . . . . . . xxxiiiz/OS Version 2 Release 1 summary of changes . . . . . . . . . . . . . . . . . . . . . . xxxiii

Chapter 1. Post-installation considerations for z/OS Communications Server . . . . . . 1Defining Communications Server SNA to z/OS. . . . . . . . . . . . . . . . . . . . . . . . 1Using automatic restart manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Starting z/OS Communications Server SNA . . . . . . . . . . . . . . . . . . . . . . . . . 2

Chapter 2. VTAM networking concepts . . . . . . . . . . . . . . . . . . . . . . 5VTAM functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5VTAM nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Nodes with APPN function only. . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Nodes with subarea function only . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Nodes with both subarea and APPN function . . . . . . . . . . . . . . . . . . . . . . . 10

Network accessible units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Physical unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Logical unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Network control sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14SSCP-SSCP sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14CP-CP sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

User sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15How VTAM locates resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Locating resources in a subarea network. . . . . . . . . . . . . . . . . . . . . . . . . 16Locating resources in an APPN network . . . . . . . . . . . . . . . . . . . . . . . . . 17

Route selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Routing in a subarea network . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Routing in an APPN network . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Subarea addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21APPN addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Controlling network data flow using pacing . . . . . . . . . . . . . . . . . . . . . . . . 21Pacing concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Pacing window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Copyright IBM Corp. 2000, 2018 iii

Chapter 3. Implementing a VTAM network. . . . . . . . . . . . . . . . . . . . . 25Using start options and configuration lists . . . . . . . . . . . . . . . . . . . . . . . . . 27

Start options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Configuration lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Identifying resources to VTAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Coding concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Sift-down effect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Using MVS system symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Verifying a VTAM network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Verifying a multiple-domain subarea network . . . . . . . . . . . . . . . . . . . . . . . 47Verifying a multiple-network environment . . . . . . . . . . . . . . . . . . . . . . . . 48Verifying a VTAM APPN network . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Chapter 4. Connecting an APPN node to VTAM . . . . . . . . . . . . . . . . . . 51Connections through boundary function-based transmission groups . . . . . . . . . . . . . . . . 52Multiple connections with parallel transmission groups. . . . . . . . . . . . . . . . . . . . . 52Channel connections between APPN nodes . . . . . . . . . . . . . . . . . . . . . . . . . 53

Multipath channel connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Composite network node channel connections . . . . . . . . . . . . . . . . . . . . . . . 60

Leased connections between APPN nodes . . . . . . . . . . . . . . . . . . . . . . . . . 61IBM 3172 Nways Interconnect Controller connections between APPN nodes . . . . . . . . . . . . . . 62

Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Using a connection network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64IBM Open Systems Adapter connections between APPN nodes . . . . . . . . . . . . . . . . . 70

APPN multiple network connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Peripheral subnetwork boundaries. . . . . . . . . . . . . . . . . . . . . . . . . . . 94Extended subnetwork boundaries . . . . . . . . . . . . . . . . . . . . . . . . . . . 94APPN multiple network connectivity support . . . . . . . . . . . . . . . . . . . . . . . 95

Virtual-route-based transmission groups . . . . . . . . . . . . . . . . . . . . . . . . . . 98Defining a VR-based TG. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100VR-based TG recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Selecting the network node server for end nodes . . . . . . . . . . . . . . . . . . . . . . 103Creating a network node server list . . . . . . . . . . . . . . . . . . . . . . . . . . 103Activating, replacing, and displaying a network node server list . . . . . . . . . . . . . . . . 104Using the NNSPREF start option . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Chapter 5. Connecting a subarea node to VTAM . . . . . . . . . . . . . . . . . 107Connecting two VTAMs using channels . . . . . . . . . . . . . . . . . . . . . . . . . 107

Channel-to-channel adapter connection . . . . . . . . . . . . . . . . . . . . . . . . . 107Multipath channel connections . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Connecting two VTAMs through communication controllers. . . . . . . . . . . . . . . . . . . 110Nonswitched SDLC subarea connection . . . . . . . . . . . . . . . . . . . . . . . . 110Switched SDLC subarea connection . . . . . . . . . . . . . . . . . . . . . . . . . . 112X.25 subarea connection (NPSI support) . . . . . . . . . . . . . . . . . . . . . . . . 114Token-ring connection (NTRI support) . . . . . . . . . . . . . . . . . . . . . . . . . 115Sample NCP definition statements for token-ring connection . . . . . . . . . . . . . . . . . 115

Connecting two VTAMs using an external communication adapter . . . . . . . . . . . . . . . . 116Sample configuration with Ethernet or Ethernet-type LAN . . . . . . . . . . . . . . . . . . 116Sample configuration with a token-ring local area network . . . . . . . . . . . . . . . . . . 118

Connecting an NCP to VTAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119Channel-attached NCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120Channel-attached NCP to a VTAM data host . . . . . . . . . . . . . . . . . . . . . . . 124NCP definition statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Connecting an NCP to another NCP. . . . . . . . . . . . . . . . . . . . . . . . . . . 131Recovery operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132Defining a link-attached NCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132Enhanced remote controller support . . . . . . . . . . . . . . . . . . . . . . . . . . 133NCP switched SDLC connections. . . . . . . . . . . . . . . . . . . . . . . . . . . 134

iv z/OS V2R3.0 Communications Server: SNA Network Implementation Guide

Chapter 6. Using Enterprise Extender (EE) . . . . . . . . . . . . . . . . . . . . 137Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

Benefits of Enterprise Extender . . . . . . . . . . . . . . . . . . . . . . . . . . . 138Availability of Enterprise Extender . . . . . . . . . . . . . . . . . . . . . . . . . . 138Hardware requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139EE reliability and strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139Using EE and extended border node (EBN) as a replacement for SNI. . . . . . . . . . . . . . . 140EE implementation considerations . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Designing the EE network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141Distinctions between an EE network and an EE connection network . . . . . . . . . . . . . . . 142Characteristics of EE connections . . . . . . . . . . . . . . . . . . . . . . . . . . . 142Static VIPA considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143IP multipath considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144Class of Service preservation dependencies . . . . . . . . . . . . . . . . . . . . . . . 144Comparing host name and IP address definitions . . . . . . . . . . . . . . . . . . . . . 145

Configuring the EE network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146Preservation of SNA transmission priority . . . . . . . . . . . . . . . . . . . . . . . . 148Network address translation (NAT) considerations . . . . . . . . . . . . . . . . . . . . . 148Steps for configuring and activating an EE network . . . . . . . . . . . . . . . . . . . . 149

Configuring the EE connection network . . . . . . . . . . . . . . . . . . . . . . . . . 166Connection network concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170EE connection network rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171Contrasting local and global networks . . . . . . . . . . . . . . . . . . . . . . . . . 171Benefits of defining multiple Enterprise Extender virtual routing nodes . . . . . . . . . . . . . . 172Defining an EE connection network in the EE XCA major node. . . . . . . . . . . . . . . . . 175

EE security considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177SNA session level encryption (SLE) . . . . . . . . . . . . . . . . . . . . . . . . . . 177IP security (IPSec) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177Using EE with network address translation (NAT) . . . . . . . . . . . . . . . . . . . . . 179IP filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179IDS for Enterprise Extender . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179OEM security products - EE proxy solutions . . . . . . . . . . . . . . . . . . . . . . . 181

Tuning the EE network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181Tuning Enterprise Extender-specific buffer pools . . . . . . . . . . . . . . . . . . . . . 181Timers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182HPR ALIVE timer optimization for Enterprise Extender . . . . . . . . . . . . . . . . . . . 185Enterprise Extender LDLC keep-alive reduction . . . . . . . . . . . . . . . . . . . . . . 186Enterprise Extender improved packet loss tolerance . . . . . . . . . . . . . . . . . . . . 187Disconnect and inactivity summary . . . . . . . . . . . . . . . . . . . . . . . . . . 187Customizing IP type of service . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

Advanced coding considerations for EE . . . . . . . . . . . . . . . . . . . . . . . . . 189EE connection network reachability awareness . . . . . . . . . . . . . . . . . . . . . . 189TCP/IP MTU size for EE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198Running EE in constrained or virtualized environments . . . . . . . . . . . . . . . . . . . 200RTP transmission stall operator awareness and recovery support . . . . . . . . . . . . . . . . 201Load balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202Transmission group profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202Dynamic reconfiguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203Dial usability - DWACT, DWINOP, KEEPACT, REDIAL, and REDDELAY . . . . . . . . . . . . . 203Customization for EE connection network PUs . . . . . . . . . . . . . . . . . . . . . . 204Cross-subnet routing with global VRNs . . . . . . . . . . . . . . . . . . . . . . . . 205

Troubleshooting EE problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208

Chapter 7. OSA-Express. . . . . . . . . . . . . . . . . . . . . . . . . . . . 215OSA-Express overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215Defining an OSA-Express device to z/OS Communications Server using QDIO . . . . . . . . . . . . 217OSA routing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219

OSA-Express virtual MAC (VMAC) routing . . . . . . . . . . . . . . . . . . . . . . . 219Primary and secondary routing . . . . . . . . . . . . . . . . . . . . . . . . . . . 221

Outbound priorities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223MTU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223

Contents v

Chapter 8. Sharing NCP peripheral nodes (CMC configurations) . . . . . . . . . . 225Channel-attached NCPs in a CMC configuration . . . . . . . . . . . . . . . . . . . . . . 226Link-attached NCPs in a CMC configuration . . . . . . . . . . . . . . . . . . . . . . . . 228Controlling resource ownership in a CMC configuration . . . . . . . . . . . . . . . . . . . . 228Problem determination in a CMC configuration . . . . . . . . . . . . . . . . . . . . . . . 229

Chapter 9. Defining resources dynamically. . . . . . . . . . . . . . . . . . . . 231Defining switched resources dynamically . . . . . . . . . . . . . . . . . . . . . . . . . 231

Dynamic PU definition (DYNPU operand) . . . . . . . . . . . . . . . . . . . . . . . 231Dynamic switched definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231

Dynamic configuration of channel-attached devices. . . . . . . . . . . . . . . . . . . . . . 234Installation and preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236Defining your configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237Building resource definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237Using the default naming convention . . . . . . . . . . . . . . . . . . . . . . . . . 238Customizing the command lists . . . . . . . . . . . . . . . . . . . . . . . . . . . 238

Dynamic reconfiguration and change of operands . . . . . . . . . . . . . . . . . . . . . . 239Dynamic reconfiguration and dynamic change requirements . . . . . . . . . . . . . . . . . 241Using the VARY ACT,UPDATE technique . . . . . . . . . . . . . . . . . . . . . . . . 243Using the VARY DRDS technique . . . . . . . . . . . . . . . . . . . . . . . . . . 246Using the MODIFY DR technique . . . . . . . . . . . . . . . . . . . . . . . . . . 248Dynamic reconfiguration of independent LUs . . . . . . . . . . . . . . . . . . . . . . 249Dynamic reconfiguration of frame-relay resources . . . . . . . . . . . . . . . . . . . . . 249Implicit dynamic reconfiguration . . . . . . . . . . . . . . . . . . . . . . . . . . . 251Dynamic reconfiguration examples . . . . . . . . . . . . . . . . . . . . . . . . . . 251Line backup through dynamic reconfiguration . . . . . . . . . . . . . . . . . . . . . . 255

Chapter 10. Defining peripheral nodes. . . . . . . . . . . . . . . . . . . . . . 259Defining type 2.1 peripheral nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . 259

Nonnative network type 2.1 connections . . . . . . . . . . . . . . . . . . . . . . . . 260Attaching peripheral nodes to VTAM . . . . . . . . . . . . . . . . . . . . . . . . . . 261

Local non-SNA connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261Local SNA connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262Loop-adapter-attached connection . . . . . . . . . . . . . . . . . . . . . . . . . . 264External communication adapter (XCA) connections . . . . . . . . . . . . . . . . . . . . 264

Attaching peripheral nodes to NCP . . . . . . . . . . . . . . . . . . . . . . . . . . . 267Defining type 2.1 peripheral nodes . . . . . . . . . . . . . . . . . . . . . . . . . . 267Nonswitched SDLC connection . . . . . . . . . . . . . . . . . . . . . . . . . . . 268Switched SDLC connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268Defining switched resources used by multiple VTAMs . . . . . . . . . . . . . . . . . . . 273NCP/Token Ring interconnection (NTRI) . . . . . . . . . . . . . . . . . . . . . . . . 274BSC connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276

Chapter 11. Defining LUs . . . . . . . . . . . . . . . . . . . . . . . . . . . 279Independent LUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279

Characteristics of independent LUs . . . . . . . . . . . . . . . . . . . . . . . . . . 279Defining independent LUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281Multiple connections between a type 2.1 node and a subarea node . . . . . . . . . . . . . . . 285Dynamic selection of session connections . . . . . . . . . . . . . . . . . . . . . . . . 287Connecting independent LUs through NCPs . . . . . . . . . . . . . . . . . . . . . . . 287Authorized transmission priority for LEN connections. . . . . . . . . . . . . . . . . . . . 288Restrictions on using independent LUs . . . . . . . . . . . . . . . . . . . . . . . . . 289Dependent logical units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289

Chapter 12. Establishing and controlling SNA sessions . . . . . . . . . . . . . . 293Multicultural support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294

Multicultural support for user USS messages and commands . . . . . . . . . . . . . . . . . 294Defining USS tables for use with the LANGTAB operand . . . . . . . . . . . . . . . . . . 294Defining USS messages to the MVS message service . . . . . . . . . . . . . . . . . . . . 295Multicultural support for the language passed to application programs . . . . . . . . . . . . . . 295

vi z/OS V2R3.0 Communications Server: SNA Network Implementation Guide

Model name table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296Associated LU table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297Selecting session parameters for the logon mode table . . . . . . . . . . . . . . . . . . . . . 298Automatic logons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305

Coding for automatic logon . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305Operator commands for automatic logon . . . . . . . . . . . . . . . . . . . . . . . . 306Reallocation of autologon sessions . . . . . . . . . . . . . . . . . . . . . . . . . . 306

Session management exits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310Session authorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311Session accounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312

Session-level pacing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312Fixed session-level pacing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313Adaptive session-level pacing . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314Setting initial pacing values . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315Sample configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320

Logon and logoff requests from dependent logical units . . . . . . . . . . . . . . . . . . . . 327Unformatted logon requests using mixed-case passwords . . . . . . . . . . . . . . . . . . . 328

Chapter 13. Network routing . . . . . . . . . . . . . . . . . . . . . . . . . . 331Network routing and resource location for APPN nodes . . . . . . . . . . . . . . . . . . . . 331

Types of searches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332Minimizing broadcast searches . . . . . . . . . . . . . . . . . . . . . . . . . . . 335Network search overhead caused by duplicate resource definitions . . . . . . . . . . . . . . . 338Avoiding congestion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339Checkpointing of the TRS database and the directory database . . . . . . . . . . . . . . . . . 339APPN Class of Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340APPN network routing through a composite network node (CNN) . . . . . . . . . . . . . . . 349Using the SAMAP table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352

Network routing for subarea nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . 355Physical paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356Logical paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358How session traffic is assigned to a specific route . . . . . . . . . . . . . . . . . . . . . 360How to plan routes in your network . . . . . . . . . . . . . . . . . . . . . . . . . 364How VTAM handles network and subarea addressing. . . . . . . . . . . . . . . . . . . . 367Virtual route pacing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372Parallel sessions using parallel transmission groups . . . . . . . . . . . . . . . . . . . . 375Dynamic path update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376

Chapter 14. Application programs . . . . . . . . . . . . . . . . . . . . . . . 379Naming an application program . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379Model application program definitions . . . . . . . . . . . . . . . . . . . . . . . . . . 380

Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381Coding guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381How VTAM finds the best match. . . . . . . . . . . . . . . . . . . . . . . . . . . 383Example of using model application program definitions . . . . . . . . . . . . . . . . . . . 385Resource state requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386

Authorizing application facilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386Passing and validating logon requests . . . . . . . . . . . . . . . . . . . . . . . . . 386Overriding dial number digits for dial or token-ring connections . . . . . . . . . . . . . . . . 387Acquiring LU sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387Enabling parallel sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387Authorizing privileged paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387

Data compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388Types of compression. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388Implementing data compression . . . . . . . . . . . . . . . . . . . . . . . . . . . 389Compression level negotiation. . . . . . . . . . . . . . . . . . . . . . . . . . . . 390Summary of data compression . . . . . . . . . . . . . . . . . . . . . . . . . . . 392

Security features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393Cryptography facility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393Message authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402

Contents vii

SLU authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403VTAM application security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404Confidential data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4043270 Intrusion Detection Services . . . . . . . . . . . . . . . . . . . . . . . . . . . 405

Logon mode parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427Using user variables (USERVAR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428

Application workload balancing with USERVAR . . . . . . . . . . . . . . . . . . . . . 428Classes of USERVARs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429Types of USERVARs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430Processing USERVARs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430USERVAR propagation and routing . . . . . . . . . . . . . . . . . . . . . . . . . . 432Defining your network with USERVARs . . . . . . . . . . . . . . . . . . . . . . . . 433Dynamic USERVAR update session failure . . . . . . . . . . . . . . . . . . . . . . . 433

Generic resources function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435High availability using extended recovery facility . . . . . . . . . . . . . . . . . . . . . . 435

Security features in an XRF environment . . . . . . . . . . . . . . . . . . . . . . . . 436LU 6.2 in an XRF Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . 437

Persistent LU-LU sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437Single node persistent sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439VTAM common network services. . . . . . . . . . . . . . . . . . . . . . . . . . . . 440Cross-memory application programming interface (API) . . . . . . . . . . . . . . . . . . . . 440Allocating private storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440Communicating with start-stop devices. . . . . . . . . . . . . . . . . . . . . . . . . . 441LU 6.2 application programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441

Enabling LU 6.2 support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441LU 6.2 sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441LU 6.2 session limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444Managing LU 6.2 sessions with operator commands . . . . . . . . . . . . . . . . . . . . 445LU 6.2 security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446LU 6.2 sync point services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447Selective termination of idle LU 6.2 sessions . . . . . . . . . . . . . . . . . . . . . . . 448Selective termination of idle network management sessions . . . . . . . . . . . . . . . . . . 449APING support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450High-performance data transfer (HPDT) . . . . . . . . . . . . . . . . . . . . . . . . 452

Communications storage manager (CSM) . . . . . . . . . . . . . . . . . . . . . . . . . 453

Chapter 15. CMIP application programs . . . . . . . . . . . . . . . . . . . . . 455VTAM topology agent CMIP application program . . . . . . . . . . . . . . . . . . . . . . 455Implementing CMIP services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455What the topology agent does . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456How data flows between the topology manager and the topology agent. . . . . . . . . . . . . . . 457Associations and using the directory definition file for CMIP services . . . . . . . . . . . . . . . 457

Controlling associations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458Determining security for associations . . . . . . . . . . . . . . . . . . . . . . . . . 458Updating the directory definition file . . . . . . . . . . . . . . . . . . . . . . . . . 460

Chapter 16. Functions provided by VTAM in a sysplex. . . . . . . . . . . . . . . 463Setting up the sysplex environment for VTAM and TCP/IP functions . . . . . . . . . . . . . . . 464

Sysplex subplexing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466Coupling facility structure attributes. . . . . . . . . . . . . . . . . . . . . . . . . . 466Determining the size of the coupling facility structure . . . . . . . . . . . . . . . . . . . . 469Sample CFRM coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469Connecting to and allocating storage for coupling facility structures . . . . . . . . . . . . . . . 471Structure rebuild . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471Coupling facility duplexing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472Coupling facility storage shortages . . . . . . . . . . . . . . . . . . . . . . . . . . 472Dynamic altering of structures. . . . . . . . . . . . . . . . . . . . . . . . . . . . 473

Dynamic definition of VTAM-to-VTAM connections . . . . . . . . . . . . . . . . . . . . . 473Generic resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476

viii z/OS V2R3.0 Communications Server: SNA Network Implementation Guide

||

Generic resources requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . 476Generic resource mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478Partner LU mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479Initiating sessions with generic resource members . . . . . . . . . . . . . . . . . . . . . 482Implementation considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . 484Coupling facility failures for generic resource configuration . . . . . . . . . . . . . . . . . . 485Removing a generic resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486Routine maintenance for VTAM nodes . . . . . . . . . . . . . . . . . . . . . . . . . 492

Multinode persistent sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492Multinode persistent session configuration requirements . . . . . . . . . . . . . . . . . . . 495Using multiple coupling facility structures for multinode persistent sessions . . . . . . . . . . . . 498Establishing multinode persistent sessions . . . . . . . . . . . . . . . . . . . . . . . . 498Coupling facility failures for multinode persistent session configuration . . . . . . . . . . . . . . 502Failure recovery processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503MNPS planned and forced takeover processing . . . . . . . . . . . . . . . . . . . . . . 505What to do if recovery does not occur or complete . . . . . . . . . . . . . . . . . . . . . 509

TSO generic resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511Sysplex-wide security associations . . . . . . . . . . . . . . . . . . . . . . . . . . . 512

Coupling facility failures for sysplex-wide security associations . . . . . . . . . . . . . . . . 512Failure of a TCP/IP stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512Failure of a VTAM node. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512Rebuild of the sysplex-wide security associations structure (EZBDVIPA). . . . . . . . . . . . . . 512Disconnect from the EZBDVIPA structure . . . . . . . . . . . . . . . . . . . . . . . . 513Modifying the number of lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513

Sysplexports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514Coupling facility failures for Sysplexports . . . . . . . . . . . . . . . . . . . . . . . . 514Failure of a TCP/IP stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514Failure of a VTAM node. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515Rebuild of the Sysplexports structure (EZBEPORT) . . . . . . . . . . . . . . . . . . . . . 515Disconnect from the EZBEPORT structure . . . . . . . . . . . . . . . . . . . . . . . . 515

Chapter 17. Implementing an APPN network . . . . . . . . . . . . . . . . . . . 517Coding considerations for APPN resources . . . . . . . . . . . . . . . . . . . . . . . . 517Maximum APPN Locate size considerations . . . . . . . . . . . . . . . . . . . . . . . . 519Enabling control sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519

CP-CP sessions between two VTAM nodes . . . . . . . . . . . . . . . . . . . . . . . 520Defining adjacent APPN nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . 520Defining the logon mode for CP-CP sessions . . . . . . . . . . . . . . . . . . . . . . . 521

High-Performance Routing (HPR) . . . . . . . . . . . . . . . . . . . . . . . . . . . 521What is High-Performance Routing?. . . . . . . . . . . . . . . . . . . . . . . . . . 521What is Rapid Transport Protocol? . . . . . . . . . . . . . . . . . . . . . . . . . . 522What is automatic network routing?. . . . . . . . . . . . . . . . . . . . . . . . . . 523How does HPR switch paths? . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524HPR implementation overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 525Setting session paths using HPRNCPBF . . . . . . . . . . . . . . . . . . . . . . . . 533

Chapter 18. Implementing a combined APPN and subarea network . . . . . . . . . 535Start options defining a combined subarea and APPN environment . . . . . . . . . . . . . . . . 538

SORDER start option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539SSEARCH start option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539CDRSCTI start option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539IOPURGE start option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539

Dependent LUs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540Dependent LU server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540Dependent LU server support across subnetwork boundaries . . . . . . . . . . . . . . . . . 544

Defining CDRSCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545Shared NCPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545SSCP takeover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546Establishing and controlling sessions . . . . . . . . . . . . . . . . . . . . . . . . . . 549Controlling searches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 549

Contents ix

||

Using SORDER to control network search order . . . . . . . . . . . . . . . . . . . . . . 549Using SSEARCH to limit subarea network searches . . . . . . . . . . . . . . . . . . . . 550Using the CDRSCTI start option to reduce broadcast searches of APPN . . . . . . . . . . . . . . 551Using the DISJOINT operand to define disjoint subarea networks . . . . . . . . . . . . . . . . 551

APPN and subarea Class of Service resolution . . . . . . . . . . . . . . . . . . . . . . . 553Resolving logon mode names to subarea and APPN Classes of Service . . . . . . . . . . . . . . 555Defining APPN and subarea Classes of Service in logon mode tables . . . . . . . . . . . . . . . 557Defining APPNTOSA and SATOAPPN class of service mapping tables . . . . . . . . . . . . . . 557

Adding and moving nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557

Chapter 19. Implementing a subarea network. . . . . . . . . . . . . . . . . . . 559Start options defining other domains . . . . . . . . . . . . . . . . . . . . . . . . . . 560

Defining the location of cross-domain resource managers by coding adjacent SSCP tables . . . . . . . . 560Defining the location of cross-domain resource managers dynamically . . . . . . . . . . . . . . 561Specifying timeout values for locating cross-domain resources . . . . . . . . . . . . . . . . . 561

Identifying VTAMs in other domains (CDRMs) . . . . . . . . . . . . . . . . . . . . . . . 562Identifying resources in other domains . . . . . . . . . . . . . . . . . . . . . . . . . . 564

Dynamic definition of cross-domain resources . . . . . . . . . . . . . . . . . . . . . . 565Static definition of cross-domain resources. . . . . . . . . . . . . . . . . . . . . . . . 566Model definition of cross-domain resources . . . . . . . . . . . . . . . . . . . . . . . 568Adjacent SSCPs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571CDRM owner verification for cross-domain resources . . . . . . . . . . . . . . . . . . . . 578Changing ownership of cross-domain resources . . . . . . . . . . . . . . . . . . . . . . 579Shadow resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 579

Chapter 20. Connecting multiple subarea networks . . . . . . . . . . . . . . . . 581Defining a multiple-network environment . . . . . . . . . . . . . . . . . . . . . . . . . 581SNI configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584Start options defining other networks . . . . . . . . . . . . . . . . . . . . . . . . . . 585

Start options for gateway VTAMs . . . . . . . . . . . . . . . . . . . . . . . . . . 585GWSSCP start option for nongateway VTAMs . . . . . . . . . . . . . . . . . . . . . . 585Configuration lists for gateway VTAMs . . . . . . . . . . . . . . . . . . . . . . . . 586

Connecting networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 586Defining a gateway VTAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587Defining a gateway NCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 588

Converting a non-SNI NCP to a gateway NCP . . . . . . . . . . . . . . . . . . . . . . 589Defining native networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 590Defining nonnative networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592Dynamic network identification . . . . . . . . . . . . . . . . . . . . . . . . . . . 593

Defining cross-domain resource managers . . . . . . . . . . . . . . . . . . . . . . . . . 597Defining cross-domain resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . 600

Session initiation request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 601Name assumption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 602Predefined cross-domain resources without network specification . . . . . . . . . . . . . . . . 604Predefined cross-domain resources with network specification . . . . . . . . . . . . . . . . . 605Dynamic cross-domain resources . . . . . . . . . . . . . . . . . . . . . . . . . . . 606

Defining adjacent SSCPs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 609Types of adjacent SSCP tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . 609Deciding whether to code adjacent SSCP tables . . . . . . . . . . . . . . . . . . . . . . 609Sample of adjacent SSCP tables for a multiple-network environment . . . . . . . . . . . . . . . 610Request routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 613Dynamically defined CDRSCs and adjacent SSCP tables . . . . . . . . . . . . . . . . . . . 614Alias name translation and adjacent SSCP tables . . . . . . . . . . . . . . . . . . . . . 614

Cross-network routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 614Network address structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . 614Network naming conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 615Controlling paths for interconnected networks . . . . . . . . . . . . . . . . . . . . . . 616Handling class of service tables . . . . . . . . . . . . . . . . . . . . . . . . . . . 618Address translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 620Resource name translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 622

x z/OS V2R3.0 Communications Server: SNA Network Implementation Guide

Alias selection function of the session management exit routine . . . . . . . . . . . . . . . . 623NetView alias name translation facility . . . . . . . . . . . . . . . . . . . . . . . . . 624

Establishing and controlling SNA sessions . . . . . . . . . . . . . . . . . . . . . . . . . 630Nonnative network type 2.1 connections . . . . . . . . . . . . . . . . . . . . . . . . 630Automatic logon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 631

Operating VTAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 632Gateway NCP and VTAM interaction . . . . . . . . . . . . . . . . . . . . . . . . . 632Using the NetView program for network management . . . . . . . . . . . . . . . . . . . 632

Application programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633Defining the NetView program . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633

Chapter 21. Operating VTAM . . . . . . . . . . . . . . . . . . . . . . . . . . 635Starting the domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635

Configuration restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 636Information recorded by configuration restart . . . . . . . . . . . . . . . . . . . . . . 640

Activating resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 640Order of activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 641Resources automatically activated by VTAM . . . . . . . . . . . . . . . . . . . . . . . 642Activating application programs . . . . . . . . . . . . . . . . . . . . . . . . . . . 646

Monitoring the domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 646Using the DISPLAY command. . . . . . . . . . . . . . . . . . . . . . . . . . . . 646Monitoring I/O problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 646Suppressing messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647Message flooding prevention . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647Other methods of controlling messages . . . . . . . . . . . . . . . . . . . . . . . . . 648Displaying and testing routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 648Defining operator messages and commands . . . . . . . . . . . . . . . . . . . . . . . 649Multiple console support (MCS) in VTAM. . . . . . . . . . . . . . . . . . . . . . . . 649

Controlling the domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 650Establishing and terminating sessions with operator commands . . . . . . . . . . . . . . . . 650Dynamic table replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 650

Deactivating resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 651Order of deactivation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 651Automatic deactivation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 652Normal deactivation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 652Immediate deactivation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 652Forced deactivation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 652Forced reactivation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 652

Halting VTAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 653Canceling VTAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654Automatic operations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654

Program operators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654CNM application programs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 655Collecting session awareness (SAW) data . . . . . . . . . . . . . . . . . . . . . . . . 656

Operating VTAM in a multiple-domain subarea network . . . . . . . . . . . . . . . . . . . . 658Links and link stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 658Discontiguous domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 661Backing up resource owners . . . . . . . . . . . . . . . . . . . . . . . . . . . . 662Sharing an NCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663

Chapter 22. Operating with an NCP . . . . . . . . . . . . . . . . . . . . . . . 665Loading an NCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 665

NCP load process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 665Identifying the communication controller . . . . . . . . . . . . . . . . . . . . . . . . 666Selecting a load station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 667Loading from the host or from external storage . . . . . . . . . . . . . . . . . . . . . . 668Reloading an NCP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 668Scheduled automatic reloading of a communication controller . . . . . . . . . . . . . . . . . 668Renaming NCP load modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . 671Loading or purging a load module on a communication controller disk . . . . . . . . . . . . . . 673

Contents xi

Activating an NCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 673Automatic activation of adjacent link stations . . . . . . . . . . . . . . . . . . . . . . 674Reactivating a failed NCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 677Activating links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 677Loading and activating an NCP over a switched link . . . . . . . . . . . . . . . . . . . . 679Enabling communication controller channels for activation . . . . . . . . . . . . . . . . . . 680

Monitoring an NCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 681Sending line errors to VTAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . 681Displaying NCP storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 682Testing a nonswitched SDLC line . . . . . . . . . . . . . . . . . . . . . . . . . . . 682

Deactivating an NCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 683Deactivating links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 683Dumping an NCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 684

Selecting a dump station for a static dump of an NCP. . . . . . . . . . . . . . . . . . . . 685Selecting a dump file for an NCP dump . . . . . . . . . . . . . . . . . . . . . . . . 686Selecting the disposition of an NCP dump. . . . . . . . . . . . . . . . . . . . . . . . 686Other communication controller dumps . . . . . . . . . . . . . . . . . . . . . . . . 687Selecting a dump file for a MOSS or CSP dump . . . . . . . . . . . . . . . . . . . . . . 687

IBM Communication Controller for Linux on z Systems considerations . . . . . . . . . . . . . . . 688Defining and activating XCA-attached CCL NCPs . . . . . . . . . . . . . . . . . . . . . 689Loading XCA-attached CCL NCPs . . . . . . . . . . . . . . . . . . . . . . . . . . 689Monitoring and managing XCA-attached CCL NCPs . . . . . . . . . . . . . . . . . . . . 691Dumping XCA-attached CCL NCPs . . . . . . . . . . . . . . . . . . . . . . . . . . 691

Chapter 23. Tuning VTAM for your environment . . . . . . . . . . . . . . . . . 693Introduction to tuning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 693

Tuning tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 694Estimating active sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 694Common storage areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 694Buffer pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 694NCP slowdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 694Coattailing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 695

Tuning tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 695Monitoring common storage areas . . . . . . . . . . . . . . . . . . . . . . . . . . 695Analyzing slowdown. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 697Gathering tuning information with the performance monitor interface . . . . . . . . . . . . . . 697Gathering tuning statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 698Analyzing tuning statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 714Determining the amount of coattailing in your system. . . . . . . . . . . . . . . . . . . . 715Migrating from user-replaceable constants . . . . . . . . . . . . . . . . . . . . . . . . 715

Estimating the number of active sessions . . . . . . . . . . . . . . . . . . . . . . . . . 715EAS operand for application programs . . . . . . . . . . . . . . . . . . . . . . . . . 715EAS operand for independent logical units . . . . . . . . . . . . . . . . . . . . . . . 716

Common storage areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 716Common service area limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 716Common service area 24-bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . 716

DISPLAY STORUSE pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 717Buffer pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 724

Types of buffer pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 724Buffer pool allocation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 726HOT I/O detection/termination . . . . . . . . . . . . . . . . . . . . . . . . . . . 733

Controlling NCP slowdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735Maximizing coattailing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735

Controlling outbound coattailing . . . . . . . . . . . . . . . . . . . . . . . . . . . 736Controlling inbound coattailing . . . . . . . . . . . . . . . . . . . . . . . . . . . 737Coattailing for SNA controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . 738Coattailing for channel-to-channel operations. . . . . . . . . . . . . . . . . . . . . . . 745

Session-level pacing tuning considerations. . . . . . . . . . . . . . . . . . . . . . . . . 746Input/output buffers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 747Application program data space . . . . . . . . . . . . . . . . . . . . . . . . . . . 747CSM storage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 747

xii z/OS V2R3.0 Communications Server: SNA Network Implementation Guide

Appendix A. TSO/VTAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . 749Defining TSO to VTAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 749

Defining the TCAS application to VTAM . . . . . . . . . . . . . . . . . . . . . . . . 750Defining TSO/VTAM session parameters . . . . . . . . . . . . . . . . . . . . . . . . 754Defining an interpret table for compatible logons . . . . . . . . . . . . . . . . . . . . . 759

Defining TSO to MVS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 759Writing a procedure to start TSO/VTAM time sharing. . . . . . . . . . . . . . . . . . . . 759Creating a TSOKEY00 PARMLIB member . . . . . . . . . . . . . . . . . . . . . . . . 759Defining TCAS program properties . . . . . . . . . . . . . . . . . . . . . . . . . . 760

Implementing TSO/VTAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 760Translation tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 760Coding TSO/VTAM exit routines. . . . . . . . . . . . . . . . . . . . . . . . . . . 760Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 760Performance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7613270 large screen considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . 761TSO considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 762Multicultural support for TSO/VTAM user messages . . . . . . . . . . . . . . . . . . . . 762Operating VTAM under TSO . . . . . . . . . . . . . . . . . . . . . . . . . . . . 763

Appendix B. Storage estimate worksheets . . . . . . . . . . . . . . . . . . . . 765General information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 766APPN interchange node or network node . . . . . . . . . . . . . . . . . . . . . . . . . 767APPN migration data host and end node . . . . . . . . . . . . . . . . . . . . . . . . . 769Subarea data host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 770Subarea communication management configuration . . . . . . . . . . . . . . . . . . . . . 771APPL EAS storage estimates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 773

Appendix C. Communications storage manager . . . . . . . . . . . . . . . . . 775CSM installation and definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . 776Initializing CSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 776Monitoring CSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 776CSM problem diagnosis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 777

Appendix D. Logon manager . . . . . . . . . . . . . . . . . . . . . . . . . . 779How the logon manager operates . . . . . . . . . . . . . . . . . . . . . . . . . . . 779Installing the logon manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 780Starting the logon manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 780Defining the logon manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 780

Sample logon manager configuration . . . . . . . . . . . . . . . . . . . . . . . . . 781Defining the logon manager and TPF applications to VTAM. . . . . . . . . . . . . . . . . . 782Defining the logon manager configuration. . . . . . . . . . . . . . . . . . . . . . . . 783

Monitoring logon manager resources . . . . . . . . . . . . . . . . . . . . . . . . . . 787Halting the logon manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 787

Appendix E. Cryptographic keys . . . . . . . . . . . . . . . . . . . . . . . . 789Filing SLU keys for single-domain cryptographic sessions . . . . . . . . . . . . . . . . . . . 789

Single-domain cryptographic sessions that use PCF/CUSP . . . . . . . . . . . . . . . . . . 790Single-domain cryptographic sessions that use ICSF/MVS . . . . . . . . . . . . . . . . . . 790

Filing CDRM keys for cross-domain cryptographic sessions . . . . . . . . . . . . . . . . . . . 791Cross-domain cryptographic sessions in which both hosts use PCF/CUSP . . . . . . . . . . . . . 791Cross-domain cryptographic sessions in which both hosts use ICSF/MVS . . . . . . . . . . . . . 792Cross-domain cryptographic sessions in which the hosts use different cryptographic services. . . . . . . 794Changing the cryptographic capability of a logical unit . . . . . . . . . . . . . . . . . . . 796

Appendix F. Command lists: Dynamic configuration of channel-attached devices . . . 799ISTDINFO: VTAM device information services . . . . . . . . . . . . . . . . . . . . . . . 799

Dependencies and restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 799Output variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 799Output tokens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 800

Contents xiii

ISTDEFIN: VTAM device information services . . . . . . . . . . . . . . . . . . . . . . . 803Dependencies and restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 803Output variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 804Output tokens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 804

Appendix G. Message translation using the MVS Message Service . . . . . . . . . 807Overview of MMS support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 807Internal translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 807

Selecting internal translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 807Defining messages for internal translation . . . . . . . . . . . . . . . . . . . . . . . . 808

External translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 808Selecting external translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 808Defining messages for external translation. . . . . . . . . . . . . . . . . . . . . . . . 809

Skeleton file use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 809

Appendix H. Forcing an APPN route in a VTAM network . . . . . . . . . . . . . . 811

Appendix I. Border node connection types. . . . . . . . . . . . . . . . . . . . 817

Appendix J. VTAM restricted materials . . . . . . . . . . . . . . . . . . . . . 821

Appendix K. Architectural specifications. . . . . . . . . . . . . . . . . . . . . 823

Appendix L. Accessibility . . . . . . . . . . . . . . . . . . . . . . . . . . . 825

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 829Terms and conditions for product documentation . . . . . . . . . . . . . . . . . . . . . . 831IBM Online Privacy Statement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 831Policy for unsupported hardware. . . . . . . . . . . . . . . . . . . . . . . . . . . . 832Minimum supported hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . 832Policy for unsupported hardware. . . . . . . . . . . . . . . . . . . . . . . . . . . . 832Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 833

Bibliography. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 835

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 839

Communicating your comments to IBM . . . . . . . . . . . . . . . . . . . . . 861

xiv z/OS V2R3.0 Communications Server: SNA Network Implementation Guide

Figures

1. Pacing flow outbound pacing . . . . . . . . . . . . . . . . . . . . . . . . . . . 222. Pacing flow inbound pacing . . . . . . . . . . . . . . . . . . . . . . . . . . . 223. Pacing flow receiving early pacing response . . . . . . . . . . . . . . . . . . . . . . 234. VTAM network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275. Configuration list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386. MPC connection between two VTAM network nodes . . . . . . . . . . . . . . . . . . . 567. Type 2.1 channel connection between a composite network node and a network node . . . . . . . . 618. Leased connection between two composite network nodes . . . . . . . . . . . . . . . . . . 629. Two network nodes connected using an IBM 3172 Nways Interconnect Controller . . . . . . . . . . 63

10. VTAM attachment to a LANNo meshed connection definitions . . . . . . . . . . . . . . . 6511. VTAM attachment to a LANMeshed connection definitions provide optimal route calculation . . . . . 6612. VTAM attachment to a connection network reduces required connection definitions (token ring) . . . . . 6713. VTAM attachment to a connection network also enables optimal route calculation (token ring). . . . . . 6814. Basic ATM configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7115. VTAM connection to the IBM Open Systems Adapter . . . . . . . . . . . . . . . . . . . 7216. Definition of VTAM connection to the IBM Open Systems Adapter . . . . . . . . . . . . . . . 7317. Port on the IBM Open Systems Adapter through which the ATM network is accessed. . . . . . . . . 7418. Definition of port on the IBM Open Systems Adapter through which the ATM network is accessed . . . . 7519. TGs that route data across the ATM network . . . . . . . . . . . . . . . . . . . . . . 7520. Definition of a TG over a PVC . . . . . . . . . . . . . . . . . . . . . . . . . . . 7621. TG over an SVC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7722. Definition of a TG over an SVC . . . . . . . . . . . . . . . . . . . . . . . . . . . 7923. Multiple nodes communicating across an ATM network. . . . . . . . . . . . . . . . . . . 8324. ATM configuration with a connection network . . . . . . . . . . . . . . . . . . . . . . 8325. Definitions in VTAMLST for the VTAM in HOST1 . . . . . . . . . . . . . . . . . . . . 8526. Definitions in VTAMLST for the VTAM in HOST2 . . . . . . . . . . . . . . . . . . . . 8627. Definitions in VTAMLST for the VTAM in HOST3 . . . . . . . . . . . . . . . . . . . . 8728. APPN subnetworks through APPN multiple network connectivity support . . . . . . . . . . . . 9329. VR-based TG between composite network nodes . . . . . . . . . . . . . . . . . . . . . 9930. Multiple contiguous VR-based TGs . . . . . . . . . . . . . . . . . . . . . . . . . 10031. VR-based TGs in a communication management configuration . . . . . . . . . . . . . . . . 10232. Parallel transmission groups in multiple domain environment with NCP . . . . . . . . . . . . 10933. Attaching domains using NCP-to-NCP token-ring connection . . . . . . . . . . . . . . . . 11534. XCA multiple domain configuration with Ethernet or Ethernet-type LAN . . . . . . . . . . . . 11735. XCA multiple domain configuration . . . . . . . . . . . . . . . . . . . . . . . . . 11836. Channel-attached 3720 Communication Controller . . . . . . . . . . . . . . . . . . . . 12137. Parallel transmission groups between VTAM and NCP . . . . . . . . . . . . . . . . . . 12338. Example NCP to VTAM data host connection . . . . . . . . . . . . . . . . . . . . . . 12539. Defining, loading, and activating a link-attached NCP . . . . . . . . . . . . . . . . . . . 13240. Comparison between an EE network and a SNA network. . . . . . . . . . . . . . . . . . 14041. How EE and EBN work together . . . . . . . . . . . . . . . . . . . . . . . . . . 14142. How ToS settings affect IP traffic . . . . . . . . . . . . . . . . . . . . . . . . . . 14543. Four types of EE connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . 14744. VRN connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16645. VTAM routing with an SATF . . . . . . . . . . . . . . . . . . . . . . . . . . . 16746. VTAM routing meshed connections . . . . . . . . . . . . . . . . . . . . . . . . . 16847. VTAM attachment to a connection network . . . . . . . . . . . . . . . . . . . . . . 16948. VTAM optimal route calculations . . . . . . . . . . . . . . . . . . . . . . . . . . 17049. Defining multiple EE VRNs. . . . . . . . . . . . . . . . . . . . . . . . . . . . 17250. EE connection network reachability awareness in a mixed-release environment . . . . . . . . . . 19351. Connection network reachability example 1 . . . . . . . . . . . . . . . . . . . . . . 19752. Connection network reachability example 2 . . . . . . . . . . . . . . . . . . . . . . 19853. Global VRN with extended border nodes . . . . . . . . . . . . . . . . . . . . . . . 20654. OSA-Express virtual MAC routing . . . . . . . . . . . . . . . . . . . . . . . . . 22055. QDIO primary and secondary routing . . . . . . . . . . . . . . . . . . . . . . . . 222

Copyright IBM Corp. 2000, 2018 xv

56. Example of communication management configuration . . . . . . . . . . . . . . . . . . 22657. Creating resources in dynamic switched major node . . . . . . . . . . . . . . . . . . . 23258. Dynamic configuration of channel-attached device . . . . . . . . . . . . . . . . . . . . 23659. DR ADD operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25260. DR DELETE operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25361. DR MOVE operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25462. Sample implicit dynamic reconfiguration . . . . . . . . . . . . . . . . . . . . . . . 25563. Line backup through dynamic reconfiguration . . . . . . . . . . . . . . . . . . . . . 25664. Nonnative network type 2.1 connection . . . . . . . . . . . . . . . . . . . . . . . . 26165. Local SNA devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26366. XCA connection in a single-domain environment . . . . . . . . . . . . . . . . . . . . 26567. Major elements of PATH definition statements for switched major node . . . . . . . . . . . . . 27168. Independent LU with multiple connections to VTAM . . . . . . . . . . . . . . . . . . . 28669. Definition building for dynamically defined dependent LUs . . . . . . . . . . . . . . . . . 29170. Macroinstructions for logon mode table . . . . . . . . . . . . . . . . . . . . . . . . 30071. How session parameters are obtained from a logon mode table . . . . . . . . . . . . . . . . 30472. Automatic logon to A50ACCTS application program . . . . . . . . . . . . . . . . . . . 30573. Automatic logon reallocation . . . . . . . . . . . . . . . . . . . . . . . . . . . 30874. Fixed-session pacing (one- and two-stage) . . . . . . . . . . . . . . . . . . . . . . . 31375. Adaptive session pacing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31476. Pacing windows for SNA LUs . . . . . . . . . . . . . . . . . . . . . . . . . . . 31777. Pacing windows for non-SNA LUs . . . . . . . . . . . . . . . . . . . . . . . . . 31878. Same domain application program-to-application program session . . . . . . . . . . . . . . . 32079. Same domain application program-to-local device session. . . . . . . . . . . . . . . . . . 32180. Application program-to-application program over APPN host-to-host connection . . . . . . . . . . 32281. Application program-to-application program over CTCA connection . . . . . . . . . . . . . . 32382. Application program-to-local SNA device over CTCA connection . . . . . . . . . . . . . . . 32483. Application program-to-local SNA device over AHHC connection . . . . . . . . . . . . . . . 32584. Application program-to-application program with VR from intermediate host-to-SLU host. . . . . . . 32785. Routing example through a CNN node . . . . . . . . . . . . . . . . . . . . . . . . 34986. CNN route calculation example . . . . . . . . . . . . . . . . . . . . . . . . . . 35087. Composite network node route calculation example. . . . . . . . . . . . . . . . . . . . 35188. Composite network node route BIND reroute example. . . . . . . . . . . . . . . . . . . 35189. Typical CNN session path . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35290. APPN view of CNN session path . . . . . . . . . . . . . . . . . . . . . . . . . . 35391. SAMAP session routing concept . . . . . . . . . . . . . . . . . . . . . . . . . . 35392. SAMAP example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35593. One explicit route in each direction . . . . . . . . . . . . . . . . . . . . . . . . . 35794. Two explicit routes in each direction . . . . . . . . . . . . . . . . . . . . . . . . . 35895. Virtual route and explicit route associations and transmission priority . . . . . . . . . . . . . 35996. Class of Service substitution . . . . . . . . . . . . . . . . . . . . . . . . . . . 36297. Class of Service hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36398. Element and subarea address incompatibility in multiple-domain environment . . . . . . . . . . 36999. Local flow control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373

100. Parallel sessions using parallel transmission groups . . . . . . . . . . . . . . . . . . . . 375101. Sample single-domain network . . . . . . . . . . . . . . . . . . . . . . . . . . 377102. Data compression yield . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391103. Encryption facility specifications . . . . . . . . . . . . . . . . . . . . . . . . . . 395104. Encryption facility in an APPN environment . . . . . . . . . . . . . . . . . . . . . . 399105. Encryption facility in multiple-network environment . . . . . . . . . . . . . . . . . . . 400106. 3270 IDS protection overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 406107. Candidate application assessment process . . . . . . . . . . . . . . . . . . . . . . . 410108. Sample of typical SNA 3270 network configuration . . . . . . . . . . . . . . . . . . . . 411109. Sample extended recovery facility network. . . . . . . . . . . . . . . . . . . . . . . 431110. Application program backup using persistent LU-LU sessions - part 1 . . . . . . . . . . . . . 439111. Application program backup using persistent LU-LU sessions - part 2 . . . . . . . . . . . . . 439112. Application program backup using persistent LU-LU sessions - part 3 . . . . . . . . . . . . . 440113. Example of flows between client and server for DISPLAY APING command . . . . . . . . . . . 451114. Generic resource mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478115. Partner LU mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480116. Session establishment with generic resource members . . . . . . . . . . . . . . . . . . . 481

xvi z/OS V2R3.0 Communications Server: SNA Network Implementation Guide

||||||

117. Application program backup using multinode persistent sessions . . . . . . . . . . . . . . . 494118. Multinode persistent session network example . . . . . . . . . . . . . . . . . . . . . 497119. Session routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500120. Path switch processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501121. HPR=(RTP,ANR) and TG capabilities . . . . . . . . . . . . . . . . . . . . . . . . 526122. HPR over composite network nodes . . . . . . . . . . . . . . . . . . . . . . . . . 527123. HPR Over APPN host-to-host channel connections . . . . . . . . . . . . . . . . . . . . 528124. Multiple HPR routes between HPR session endpoints . . . . . . . . . . . . . . . . . . . 529125. Using VR-based TGs for non-HPR endpoints . . . . . . . . . . . . . . . . . . . . . . 530126. Session involving HPR and APPN routes . . . . . . . . . . . . . . . . . . . . . . . 531127. Interchange node using HPR routing between subarea and APPN . . . . . . . . . . . . . . . 532128. Sessions traversing APPN and subarea networks. . . . . . . . . . . . . . . . . . . . . 533129. Example of communication management configuration . . . . . . . . . . . . . . . . . . 535130. Communication management configuration after conversion . . . . . . . . . . . . . . . . . 536131. VTAM functioning as a dependent LU server . . . . . . . . . . . . . . . . . . . . . . 541132. Switched major node for a dependent LU server . . . . . . . . . . . . . . . . . . . . . 542133. DLUS located in different APPN subnetwork than DLUR or PLU . . . . . . . . . . . . . . . 544134. PLU exists in or through a subarea network . . . . . . . . . . . . . . . . . . . . . . 545135. SSCP takeover when adjacent CP does not support CP name change . . . . . . . . . . . . . . 546136. SSCP takeover when adjacent CP is another composite network node. . . . . . . . . . . . . . 548137. Disjoint hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552138. Hosts with subarea connection . . . . . . . . . . . . . . . . . . . . . . . . . . . 553139. LOGMODE resolution example . . . . . . . . . . . . . . . . . . . . . . . . . . 553140. Class of Service resolution at multiple nodes . . . . . . . . . . . . . . . . . . . . . . 556141. Multiple-domain network . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559142. Major and minor nodes in multiple-domain environment . . . . . . . . . . . . . . . . . . 563143. Example of adjacent SSCP table connection . . . . . . . . . . . . . . . . . . . . . . 574144. Multiple-network environment. . . . . . . . . . . . . . . . . . . . . . . . . . . 583145. Backup of a gateway NCP - part 1 . . . . . . . . . . . . . . . . . . . . . . . . . 596146. Backup of a gateway NCP - part 2 . . . . . . . . . . . . . . . . . . . . . . . . . 596147. Multiple-network configuration: CDRM major nodes . . . . . . . . . . . . . . . . . . . 599148. Example of three interconnected networks . . . . . . . . . . . . . . . . . . . . . . . 602149. Example of two interconnected networks . . . . . . . . . . . . . . . . . . . . . . . 604150. Multiple-network configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 610151. Multiple-network paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 616152. COS resolution in a multiple-network environment . . . . . . . . . . . . . . . . . . . . 619153. COS tables and routing in an SNI back-to-back configuration . . . . . . . . . . . . . . . . 620154. Address translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 621155. Example of name translation . . . . . . . . . . . . . . . . . . . . . . . . . . . 627156. Nonnative network type 2.1 connections . . . . . . . . . . . . . . . . . . . . . . . 631157. Restoring resource definitions with configuration restart and NODELST files . . . . . . . . . . . 637158. Effects of NCP deactivation on cross-subarea links and link stations . . . . . . . . . . . . . . 658159. NCP generation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 666160. Activating NCPs and link stations: Through another NCP . . . . . . . . . . . . . . . . . 675161. Activating NCPs and link stations: Through host link station . . . . . . . . . . . . . . . . 675162. Automatic activation of link stations . . . . . . . . . . . . . . . . . . . . . . . . . 676163. Loading and activating NCP using switched link . . . . . . . . . . . . . . . . . . . . 679164. Loading over a channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 681165. Example of an MPC channel-to-channel, QDIO, and Hipersockets tuning statistics report . . . . . . . 705166. Buffer pool after initial allocation and after one expansion . . . . . . . . . . . . . . . . . 728167. How VTAM uses input buffers. . . . . . . . . . . . . . . . . . . . . . . . . . . 732168. How VTAM uses output buffers . . . . . . . . . . . . . . . . . . . . . . . . . . 733169. Effect of DELAY time on coattailing - example 1 . . . . . . . . . . . . . . . . . . . . . 739170. Effect of DELAY time on coattailing - example 2 . . . . . . . . . . . . . . . . . . . . . 739171. Effect of DELAY time on coattailing - example 3 . . . . . . . . . . . . . . . . . . . . . 740172. General I/O buffer format . . . . . . . . . . . . . . . . . . . . . . . . . . . . 742173. Using multiple I/O buffers to transfer single message . . . . . . . . . . . . . . . . . . . 743174. Multiple-buffer considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . 744175. Sample Logon Manager Configuration . . . . . . . . . . . . . . . . . . . . . . . . 781176. Cryptography in multiple-domain environment (Both hosts use PCF/CUSP) . . . . . . . . . . . 792177. Cryptography in multiple-domain environment (Both hosts use ICSF/MVS) . . . . . . . . . . . 794

Figures xvii

178. Cryptography in multiple-domain environment (Hosts use different cryptographic services) . . . . . . 796179. Sample network showing default route . . . . . . . . . . . . . . . . . . . . . . . . 811180. Sample network using default for UPARM1 . . . . . . . . . . . . . . . . . . . . . . 812181. Sample network using TG profile on some links . . . . . . . . . . . . . . . . . . . . . 813

xviii z/OS V2R3.0 Communications Server: SNA Network Implementation Guide

Tables

1. LU types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162. Pacing types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213. MVS static system symbols that can be used in VTAM . . . . . . . . . . . . . . . . . . . 414. HPDT Packing - packing buffer size, CSM pools size, and waste per packing buffer . . . . . . . . . 605. Comparison between static and dynamic definitions . . . . . . . . . . . . . . . . . . . 1466. SNA priorities and corresponding port numbers and default ToS values . . . . . . . . . . . . . 1887. Connection conditions and results . . . . . . . . . . . . . . . . . . . . . . . . . 1998. Troubleshooting EE problems . . . . . . . . . . . . . . . . . . . . . . . . . . . 2089. OSA-Express support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

10. Definitions for dynamically configured devices . . . . . . . . . . . . . . . . . . . . . 23711. Dynamic reconfiguration operations for valid major nodes . . . . . . . . . . . . . . . . . 24112. Rules for multiple definition of resources . . . . . . . . . . . . . . . . . . . . . . . 24913. Example of model name table . . . . . . . . . . . . . . . . . . . . . . . . . . . 29614. Example of associated LU table . . . . . . . . . . . . . . . . . . . . . . . . . . 29815. How session parameters are identified . . . . . . . . . . . . . . . . . . . . . . . . 30016. Correspondence of methods to letters . . . . . . . . . . . . . . . . . . . . . . . . 31617. Same domain application program-to-application program sessionPLU to SLU flow . . . . . . . . 32118. Same domain application program-to-application program SessionSLU to PLU Flow . . . . . . . . 32119. Same domain application program-to-local device sessionPLU to SLU flow . . . . . . . . . . . 32220. Same domain application program-to-local device sessionSLU to PLU flow . . . . . . . . . . . 32221. Application program-to-application program over APPN host-to-host connectionPLU to SLU flow 32322. Application program-to-application program over APPN host-to-host connectionSLU to PLU flow 32323. Application program-to-application program over CTCA connectionPLU to SLU flow . . . . . . . 32424. Application program-to-application program over CTCA connectionSLU to PLU flow . . . . . . . 32425. Application program to local SNA device over CTCA connectionPLU to SLU flow . . . . . . . . 32526. Application program-to-local SNA device over CTCA connectionSLU to PLU flow . . . . . . . . 32527. Application program-to-local SNA device over AHHC connectionPLU to the SLU . . . . . . . . . 32628. Application program-to-local SNA device over AHHC connectionSLU to PLU flow . . . . . . . . 32629. Application program-to-application program with VR from intermediate host-to-SLU hostPLU to SLU

flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32730. Application program-to-application program with VR from intermediate host-to-SLU hostSLU to PLU

flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32731. Default registration values for resources . . . . . . . . . . . . . . . . . . . . . . . 33632. COSAPPN #CONNECT class of service LINEROW values . . . . . . . . . . . . . . . . . 34133. ISTACST2 #CONNECT class of service LINEROW values . . . . . . . . . . . . . . . . . . 34234. ISTACST3 #CONNECT class of service LINEROW values . . . . . . . . . . . . . . . . . . 34335. ISTINCLM APPNCOS values based on LOGMODE operand values . . . . . . . . . . . . . . 34536. Default TG characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34737. #CONNECT Class of Service LINEROW values . . . . . . . . . . . . . . . . . . . . . 34738. Adjacent node subarea requirements for multiple-domain environment . . . . . . . . . . . . . 37039. Endpoint node subarea requirements for multiple-domain environment . . . . . . . . . . . . . 37040. Sample model application program names . . . . . . . . . . . . . . . . . . . . . . . 38241. Compression values for example of data compression yield . . . . . . . . . . . . . . . . . 39142. DES-TDES24 encryption options . . . . . . . . . . . . . . . . . . . . . . . . . . 39643. Resource verification reduction matrix . . . . . . . . . . . . . . . . . . . . . . . . 44444. Structure attributes used to compute structure size . . . . . . . . . . . . . . . . . . . . 46745. Structure attributes defined by VTAM . . . . . . . . . . . . . . . . . . . . . . . . 46846. VTAM to VTAM connection example . . . . . . . . . . . . . . . . . . . . . . . . 47547. Start options and node type relationship . . . . . . . . . . . . . . . . . . . . . . . 51748. Network resource list example . . . . . . . . . . . . . . . . . . . . . . . . . . . 62949. Loading a 3745 from VTAM . . . . . . . . . . . . . . . . . . . . . . . . . . . 69050. Loading a CCL or 3745 from VTAM . . . . . . . . . . . . . . . . . . . . . . . . . 69151. Record format for SNA controller . . . . . . . . . . . . . . . . . . . . . . . . . . 69952. Record format for channel-to-channel adapters . . . . . . . . . . . . . . . . . . . . . 70153. Record format for multipath channel connections (XCF) . . . . . . . . . . . . . . . . . . 702

Copyright IBM Corp. 2000, 2018 xix

54. Record format for multipath channel connections (channel) . . . . . . . . . . . . . . . . . 70555. Record format for TCP connections . . . . . . . . . . . . . . . . . . . . . . . . . 71056. Record format for RoCE connections . . . . . . . . . . . . . . . . . . . . . . . . . 71257. DISPLAY STORUSE pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71758. VTAM buffer pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72459. Number of buffers per page . . . . . . . . . . . . . . . . . . . . . . . . . . . 73060. I/O buffer size and number of buffers per page . . . . . . . . . . . . . . . . . . . . . 73161. Coding the device-specific hexadecimal data of PSERVIC . . . . . . . . . . . . . . . . . . 75662. Worksheet for APPN interchange node or network node storage . . . . . . . . . . . . . . . 76763. Summary of worksheet, APPN interchange node or network node storage . . . . . . . . . . . . 76964. Worksheet for APPN migration data host and end node . . . . . . . . . . . . . . . . . . 76965. Summary of APPN migration data host and end node . . . . . . . . . . . . . . . . . . . 76966. Worksheet for subarea data host . . . . . . . . . . . . . . . . . . . . . . . . . . 77067. Summary of subarea data host . . . . . . . . . . . . . . . . . . . . . . . . . . . 77068. Worksheet for subarea communication management configuration . . . . . . . . . . . . . . . 77169. Summary of subarea communication management configuration . . . . . . . . . . . . . . . 77270. Buffer pools in CSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77571. Connection type for selected VTAM and partner node combinations . . . . . . . . . . . . . . 81772. User replaceable or modifiable modules. . . . . . . . . . . . . . . . . . . . . . . . 82173. VTAM message modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 821

xx z/OS V2R3.0 Communications Server: SNA Network Implementation Guide

About this document

This document provides an understanding of the major concepts involved inimplementing a VTAM network and describes how to:v Install VTAMv Define network resources to VTAMv Replace user tables and exit routinesv Tune VTAM for a specific environmentIt also provides guidance for using VTAM resource definition statements andmacroinstructions. Use this document when installing, upgrading, or otherwisechanging a VTAM network.

The information in this document includes descriptions of support for both IPv4and IPv6 networking protocols. Unless explicitly noted, descriptions of IP protocolsupport concern IPv4. IPv6 support is qualified within the text.

The z/OS Communications Server: SNA Resource Definition Reference contains abrief description and shows the exact coding format of each VTAM definitionstatement, start option, and user table. It serves as a reference document for systemprogrammers who are already familiar with the major concepts involved inimplementing a VTAM network.

Who should read this documentSystem programmers who are familiar with the basic concepts oftelecommunication, Systems Network Architecture (SNA), and VTAM.

For an overview of the new functions in VTAM, see the z/OS CommunicationsServer: New Function Summary.

How this document is organizedThe z/OS Communications Server: SNA Network Implementation Guide isdivided into the following sections:

The first section describes subarea and Advanced Peer-to-Peer Networking (APPN)concepts for VTAM.

The second section presents an overview of VTAM implementation issues commonto all VTAM networks.

The third section describes:v Various ways of connecting VTAM as an APPN node in the networkv Enterprise Extender connectionsv Types of subarea connections to VTAMv VTAM as a data hostv Methods for VTAM resources to be defined dynamicallyv Details about how to define PUs to VTAMv Details about how to define independent and dependent LUs to VTAM

Copyright IBM Corp. 2000, 2018 xxi

The fourth section describes:v Major concepts involved in establishing sessions.v Major concepts involved in routing data through a VTAM network; both routing

considerations for APPN and subarea nodes are covered.

The fifth section describes:v Concepts and functions available for VTAM application programs. For detailed

information about implementation of VTAM application programs, see z/OSCommunications Server: SNA Programming and z/OS Communications Server:SNA Programmer's LU 6.2 Guide.

v Concepts involved in implementing a VTAM application using the CommonManagement Information Protocol (CMIP). See the z/OS CommunicationsServer: CMIP Services and Topology Agent Guide for detailed information aboutimplementing a CMIP application program.

The sixth section describes how to incorporate VTAM functions and enhancementsused in a sysplex environment.

The seventh section presents the major concepts in implementing an APPNnetwork and describes:v How to implement VTAM as an APPN node in the networkv Considerations for implementing a combined APPN and subarea network

The eight section presents the major concepts involved in implementing a subareanetwork and describes:v Major concepts in implementing a basic subarea network environmentv Major concepts in implementing a multiple-network environment using the SNA

network interconnection (SNI)

The ninth section describes VTAM operator control functions including the basictasks available to the VTAM operator for controlling the VTAM domain and howto control a domain that includes NCP subarea nodes.

The tenth section describes how you can adjust VTAM to provide optimal servicefor your environment.

The provide additional information for this document.

How to use this documentTo use this document, you should be familiar with the basic concepts oftelecommunication, SNA, and VTAM.

How to contact IBM serviceFor immediate assistance, visit this website: http://www.software.ibm.com/support

Most problems can be resolved at this website, where you can submit questionsand problem reports electronically, and access a variety of diagnosis information.

xxii z/OS V2R3.0 Communications Server: SNA Network Implementation Guide

http://www.software.ibm.com/supporthttp://www.software.ibm.com/support

For telephone assistance in problem diagnosis and resolution (in the United Statesor Puerto Rico), call the IBM Software Support Center anytime (1-800-IBM-SERV).You will receive a return call within 8 business hours (Monday Friday, 8:00 a.m. 5:00 p.m., local customer time).

Outside the United States or Puerto Rico, contact your local IBM representative oryour authorized IBM supplier.

If you would like to provide feedback on this publication, see Communicatingyour comments to