| |
|
| GBIND AMRU flow |
Page |
| |
|
| ACTLU: Sending an ACTLU request for a logical unit (LU) |
Figure 1 |
| ACTPU: Sending an ACTPU request for a communication controller
or physical unit (PU) |
Figure 2 |
| BIND: Sending a BIND request to a secondary logical unit (SLU) |
Figure 3 |
| Virtual and explicit route: Activating a virtual route (VR)
and the associated explicit route (ER) |
Figure 4 |
| |
|
| Resource activation flow |
Page |
| |
|
| Activating a CDRM |
|
| CDRM with COLD response, activating |
Figure 15 |
| CDRM with ERP response, activating |
Figure 14 |
| CDRM with a virtual route-based transmission group, activating |
Figure 16 |
| Activating a cross-network SSCP-SSCP session |
|
| Back-to-back gateway NCPs request sessions |
Figure 17 |
| Gateway VTAM requests
session |
Figure 18 |
| Non-gateway VTAM requests
session |
Figure 19 |
| Activating an NCP major node |
|
| Channel-attached communication controller, activating |
Figure 1 |
| Link-attached communication controller, activating |
Figure 2 |
| Activating resources controlled by a host or NCP major node |
|
| Link: Activating a link |
Figure 3 |
| Link station: Activating a cross-subarea link station |
Figure 5 |
| Logical unit (LU): Activating a logical unit |
Figure 12 |
| Application program: Activating an application program and
processing an OPEN ACB request |
Figure 13 |
| Physical unit (PU): Activating a physical unit type 2.0 |
Figure 7 |
| Physical unit (PU): Activating a physical unit type 2.0 with
load required |
Figure 8 |
| Physical unit (PU): Moving a dynamically added physical unit |
Figure 10 |
| Physical unit (PU): Moving a SYSGENed physical unit |
Figure 9 |
| SSCP takeover of peripheral node logical units (LUs) |
Figure 11 |
| Switched connection, establishing |
Figure 6 |
| Switched link with takeover, activating |
Figure 4 |
| |
|
| Session establishment flow |
Page |
| |
|
| Failed session establishment |
|
| Failure (CDINIT rejection) of session initiation by a secondary
logical unit (SLU) for single gateway VTAM and
single gateway NCP |
Figure 26 |
| Failure (CINIT rejection) of setup procedure initiated by a
secondary logical unit (SLU) for single gateway VTAM and single gateway NCP |
Figure 28 |
| Failure (SETCV failure) of session initiation by a secondary
logical unit (SLU) for single gateway VTAM and
single gateway NCP |
Figure 27 |
| Gateway VTAM |
|
| Default partitioning of gateway VTAM responsibility
spanning three networks |
Figure 19 |
| Multiple gateway VTAMs and back-to-back gateway NCPs |
Figure 2 |
| PLU availability for autologon, notification of |
Figure 25 |
| Requests initiated by primary logical units (PLUs) |
|
| Dependent PLU initiating cross-domain session with independent
SLU |
Figure 8 |
| Independent PLU initiating cross-domain session with independent
SLU |
Figure 7 |
| Independent PLU requesting session with independent SLU through
a single gateway VTAM and single
gateway NCP |
Figure 10 |
| OPNDST ACQUIRE |
Figure 3 |
| PLU initiating request for single gateway VTAM and single gateway NCP |
Figure 9 |
| PLU initiating request setup queued for single gateway VTAM and single gateway NCP |
Figure 11 |
| SIMLOGON |
Figure 4 |
| SIMLOGON(RELREQ) |
Figure 5 |
| SIMLOGON(RELREQ): Session is pending active or already in progress |
Figure 6 |
| Requests initiated by secondary logical units (SLUs) |
|
| Dependent SLU initiating cross-domain session with application
logical unit (LU) |
Figure 16 |
| INIT SELF |
Figure 14 |
| LOGON |
Figure 12 |
| Predesignated control of gateway NCP by middle host |
Figure 19 |
| REQSESS |
Figure 13 |
| Sending an unformatted request to the SSCP |
Figure 15 |
| Single gateway connecting three or more networks |
Figure 18 |
| Single gateway VTAM and
single gateway NCP |
Figure 17 |
| Requests initiated by third parties |
|
| CLSDST PASS |
Figure 21 |
| CLSDST PASS with NOTIFY |
Figure 22 |
| Request spanning three networks |
Figure 23 |
| VARY LOGON or LOGAPPL processing |
Figure 24 |
| |
|
| Deactivation or session termination flow |
Page |
| |
|
| CLOSE ACB processing |
Figure 16 |
| Deactivating an application program |
Figure 17 |
| Deactivating a CDRM |
|
| Forced |
Figure 20 |
| Forced, without affecting active sessions |
Figure 22 |
| Forced or immediate, VTAM releases
before V3R4.1 |
Figure 23 |
| Immediate |
Figure 19 |
| Immediate, without affecting active sessions |
Figure 21 |
| Normal |
Figure 18 |
| Deactivating a logical unit (LU), single network |
|
| Forced |
Figure 2 |
| Immediate |
Figure 1 |
| VARY NET,TERM Cleanup |
Figure 14 |
| VARY NET,TERM Unconditional |
Figure 13 |
| With Giveback |
Figure 3 |
| Deactivating a logical unit (LU), multiple networks |
|
| Independent PLU sends BFCLEANUP for independent SLU |
Figure 4 |
| Independent PLU sends UNBIND for independent SLU |
Figure 5 |
| PLU sends UNBIND for multiple gateway VTAMs and single gateway
NCP |
Figure 6 |
| PLU sends UNBIND for single gateway VTAM and single gateway NCP |
Figure 7 |
| SLU requests TERMINATE SELF (CLEANUP) for single gateway VTAM and single gateway NCP |
Figure 9 |
| SLU requests TERMINATE SELF for multiple gateway VTAMs and
back-to-back gateway NCPs |
Figure 8 |
| SLU requests TERMINATE SELF for single gateway VTAM and single gateway NCP |
Figure 10 |
| Type 2.1 nodes, active termination |
Figure 11 |
| Deactivating a physical unit (PU) acting as an adjacent link
station for independent logical unit (LU) sessions |
Figure 12 |
| Queued session, terminating |
Figure 15 |
| Route failure |
|
| Route failure in intermediate network causes termination of
LU-LU sessions |
Figure 25 |
| Route failure in intermediate network causes termination of
SSCP-SSCP sessions |
Figure 26 |
| SSCP-SSCP session termination causes LU-LU sessions to be broken |
Figure 24 |
| |
|
| Error and SSCP management services flow |
Page |
| |
|
| Error recovery processing (ERP) |
|
| Hard INOP |
Figure 2 |
| Soft INOP |
Figure 1 |
| LPDA-2 processing |
|
| Unsolicited LPDA-2 test on permanent link error with two link
segments |
Figure 6 |
| Unsolicited LPDA-2 test on thresholds reached for an LPDA-2
physical unit (PU) with one link segment |
Figure 4 |
| Unsolicited LPDA-2 test on thresholds reached for an LPDA-2
physical unit (PU) with two link segments |
Figure 5 |
| SSCP management services processing |
|
| FORWARD and DELIVER Routing |
Figure 3 |
| XRF processing |
|
| Secondary logical unit (LU) initiate with USERVAR (LOGON) |
Figure 9 |
| Third-party initiate (CLSDST PASS) |
Figure 10 |
| XRF primary and backup sessions, establishment of |
Figure 7 |
| XRF session switch (takeover) |
Figure 8 |
z/OS Communications Server: SNA Diagnosis Vol 1, Techniques and Procedures
Copyright IBM Corporation 1990, 2014