gtps2m4kACF/SNA Data Communications Reference

PU 5 and PU 2.1 LEN Session Activation

The following sections show examples of session activation when the TPF system is connected as a PU 5 node or PU 2.1 low-entry networking (LEN) node. See APPN Session Activation for session activation flows when the TPF system is connected to the network as an APPN node.

CDRM-CDRM Session Activation

The following sections show examples of session activation based on your configuration.

Across a CTC Connection (TPF to TPF, or TPF to VTAM)

To activate the CDRM-CDRM session from the TPF system, enter the following:

   ZNETW ACT ID=rrrrrrrr

Where:

rrrrrrrr
The name of the remote CDRM.

Figure 120. CDRM-CDRM Session Started by the TPF System




Here are the flows when activated by the remote SSCP:

Figure 121. CDRM-CDRM Session Started by the Remote SSCP




Across an NCP Connection (TPF to VTAM)

To activate the CDRM-CDRM session from VTAM, enter the following:

   V NET,ACT,ID=rrrrrrrr

Where:

rrrrrrrr
The name of the TPF CDRM.

Figure 122. CDRM-CDRM Session Started by VTAM




The CDRM-CDRM session can be activated from the TPF side. The ACTCDRM request sent by TPF will be rejected by the gateway NCP, but then that NCP will forward the request to VTAM who will drive the session. Here are the flows for this case:

Figure 123. CDRM-CDRM Session Started from the TPF side




Session Activation Between TPF APPL (PLU) and Remote APPL (SLU)

To activate the APPL-APPL session from the TPF system, enter the following:

  ZNETW ACT ID=ssssssss LOGON=pppp CDRM=cccccccc

Where:

ssssssss
The name of the remote APPL

pppp
The name of the TPF APPL

cccccccc
The name of remote CDRM.

Figure 124. APPL-APPL Session Started by TPF (PU 5)




Note:
If the normal flow sequence numbers in the RVT (RV2SISEQ and RV2SOSEQ) are both zero, then CLEAR and STSN are not sent; only SDT is sent on the LU-LU session following the BIND. This applies to all the flow diagrams in this section.

Here are the flows when the session is started from the remote side:

Figure 125. APPL-APPL Session Started by Remote LU (PU 5)




If the remote SSCP is VTAM, then it is possible that the CDINIT request sent (step #1) is a CDINIT Queue Only request. In this case a CDINIT Dequeue request must be sent before CDCINIT. Here are the flows:

Figure 126. APPL-APPL Session Started by Remote LU (PU 5) and is Queued




For PU 2.1 LEN, the session can only be started from the remote side and requires the use of the Logon Manager in VTAM. Here are the flows:

Figure 127. APPL-APPL Session Started by Remote LU (PU 2.1 LEN)




Note:
If the normal flow sequence numbers in the RVT (RV2SISEQ and RV2SOSEQ) are both zero, then CLEAR and STSN are not sent; only SDT is sent on the LU-LU session following the BIND.

Session Activation for Host-Node SLU Session

To activate the host-node SLU session from the TPF system, enter the following:

  ZNETW ACT ID=ssssssss LOGON=pppp CDRM=cccccccc

Where:

ssssssss
The name of the remote APPL

pppp
The name of the TPF APPL

cccccccc
The name of the remote CDRM.

This message brings up a session between the remote APPL and each TPF SLU-thread of APPL pppp that is not already in session.

Figure 128. Host-Node SLU Session Started by TPF (PU 5)




Note:
The remote PLU may not send CLEAR and STSN following the BIND. It is possible that only SDT is sent on the LU-LU session following the BIND.

For remote initiated PU 5 sessions, the only difference in the flows is that the remote side sends the CDINIT request (step #1 in the previous figure). Also, the remote side may send a CDINIT Queue Only request, in which case a CDINIT Dequeue request must also be sent by the remote side before the TPF system can send CDCINIT.

For PU2.1 LEN, the session can only be started from the remote side. Here are the flows:

Figure 129. Host-Node SLU Session Started by Remote LU (PU 2.1 LEN)




FMMR-FMMR Session Activation

To activate the FMMR-FMMR session, enter the following:

  ZNETW ACT ID=rrrrrrrr LOGON=llllllll CDRM=cccccccc

Where:

rrrrrrrr
The name of the remote FMMR

llllllll
The name of the local FMMR

cccccccc
The name of the remote CDRM.

For FMMR-FMMR sessions, the PLU is the FMMR whose LU name is greater. Here are the flows when initiated from the side owning the FMMR PLU:

Figure 130. PU 5 FMMR-FMMR Session Initiation from the PLU




Here are the flows when initiated from the side owning the FMMR SLU:

Figure 131. PU 5 FMMR-FMMR Session Initiation from the SLU




For PU 2.1 LEN, the session must be started from VTAM and use the Logon Manager. Here are the flows:

Figure 132. PU 2.1 LEN FMMR-FMMR Session Initiation




Session Activation between TPF APPL and Remote 3270

Here are the flows for when the remote terminal logs on to the TPF APPL:

Figure 133. 3270 Session Started by Remote Terminal (PU 5)




Here are the PU2.1 LEN flows for when the remote terminal logs on to the TPF APPL:

Figure 134. 3270 Session Started by Remote Terminal (PU 2.1 LEN)




Session Activation for PU 5 LU 6.2 Sessions (Started by TPF PLU)

The following are the flows when the TPF system is the primary LU (PLU) and activates a new session (parallel or single) in a PU 5 environment. The session is activated by an ALLOCATE verb. In step #5, a FLUSH verb is issued causing the buffered ATTACH (FMH5) to be transmitted to the remote LU.

Figure 135. PU 5 LU 6.2 Session Started by TPF PLU




Here are the flows when the session is started from the remote side:

Figure 136. PU 5 LU 6.2 Session Started by Remote SLU




Session Activation for PU 5 LU 6.2 Sessions (Started by TPF SLU)

The following are the flows when a TPF secondary LU (SLU) thread activates a new single session in a PU 5 environment. The session is activated by an ALLOCATE verb. In step #6, a FLUSH verb is issued causing the buffered ATTACH (FMH5) to be transmitted to the remote LU. This example assumes the TPF system is the contention winner.

Figure 137. PU 5 LU 6.2 Session Started by TPF SLU




Here are the flows when the session is started from the remote side. If the remote LU started the session with an ALLOCATE request, the flow is step #5A; otherwise, the flow is step #5B.

Figure 138. PU 5 LU 6.2 Session Started by Remote PLU




Session Activation for PU 2.1 LEN LU 6.2 Sessions

The following are the flows when the TPF system activates a new session (parallel or single) that is not using an SLU thread and is in a PU 2.1 LEN environment. The session is activated by an ALLOCATE verb. In step #4, a FLUSH verb is issued causing the buffered ATTACH (FMH5) to be transmitted to the remote LU.

Figure 139. PU 2.1 LEN LU 6.2 Session Started by TPF




The following flows show a single session being started by a remote SLU (dependent LU).

Figure 140. PU 2.1 LEN LU 6.2 Session Started by Remote SLU




Note:
If the remote LU is an independent LU, then it sends a BIND directly to the TPF system.

PU 5 and PU 2.1 Session Deactivation

The following sections show examples of session deactivations.

CDRM-CDRM Session Deactivation

The following sections show different ways to deactivate a CDRM-CDRM session.

Normal CDRM-CDRM Session Deactivation

To deactivate the CDRM-CDRM session from the TPF system, enter the following:

   ZNETW ACT ID=rrrrrrrr

Where:

rrrrrrrr
The name of the remote CDRM.

Figure 141. Normal CDRM-CDRM Session Deactivation




Note:
Either SSCP can send CDTAKED. After all initiating and active LU-LU sessions have been ended, the SSCP receiving the CDTAKED request sends CDTAKEDC first. Next, the SSCP that sent CDTAKED sends a CDTAKEDC followed by a DACTCDRM.

Immediate CDRM-CDRM Session Deactivation

To deactivate the CDRM-CDRM session from the TPF system, enter the following:

   ZNETW ACT ID=rrrrrrrr,I

Where:

rrrrrrrr
The name of the remote CDRM.

Figure 142. Immediate CDRM-CDRM Session Deactivation




Note:
Either SSCP can send CDTAKED. After all initiating and active LU-LU sessions have been ended, the SSCP receiving the CDTAKED request sends CDTAKEDC first. Next the SSCP that sent CDTAKED sends a CDTAKEDC followed by a DACTCDRM.

To deactivate the CDRM-CDRM non-disruptively, enter the following:

   ZNETW ACT ID=rrrrrrrr,I,SAVESESS

Where:

rrrrrrrr
The name of the remote CDRM.

In this case, the flows are identical except that active LU-LU sessions are not ended (step #2); only the LU-LU sessions that are in the process of being activated are ended.

Forced CDRM-CDRM Session Deactivation

To deactivate the CDRM-CDRM session from the TPF system, enter the following:

   ZNETW ACT ID=rrrrrrrr,F

Where:

rrrrrrrr
The name of the remote CDRM.

Figure 143. Forced CDRM-CDRM Session Deactivation




Note:
Either SSCP can send CDTAKED. There are no CDTAKEDC exchanges here. DACTCDRM is sent immediately after receiving a CDTAKED response, and then the LU-LU sessions are ended. For active LU-LU sessions, UNBIND is the only command that flows (a CDSESSEND cannot be sent because the CDRM-CDRM session no longer exists). LU-LU sessions that are in the process of being activated are cleaned up without any flows between the LUs.

To deactivate the CDRM-CDRM non-disruptively, enter the following:

   ZNETW ACT ID=rrrrrrrr,F,SAVESESS

Where:

rrrrrrrr
The name of the remote CDRM.

In this case, the flows are identical except that active LU-LU are not ended (step #3); only the LU-LU sessions that in the process of being activated are ended.

Session Deactivation for TPF APPL (PLU) and Remote APPL (SLU)

The following sections show different ways to deactivate an APPL-APPL session.

Normal Deactivation of APPL-APPL Session

To deactivate an APPL-APPL session normally from the TPF system, enter the following:

   ZNETW INACT ID=ssssssss

Where:

ssssssss
The name of the remote APPL.

To deactivate all sessions with the TPF APPL, enter the following:

  ZNETW INACT ID=pppp

Where:

pppp
The name of the TPF APPL.

Figure 144. Normal APPL-APPL Session Deactivation




Notes:

  1. Responses to normal data traffic can flow before step #5. Because the CHASE command is normal flow, once a response to CHASE has been received the LU knows it is not waiting for any more responses to normal flow traffic. The remote LU does not have to send a CHASE request, so step #2 is optional.

  2. For PU2.1 sessions, no CDSESSENDs are sent (skip step #7).

Immediate APPL-APPL Session Deactivation

To deactivate an APPL-APPL session immediately from the TPF system, enter the following:

   ZNETW INACT ID=ssssssss,I

Where:

ssssssss
The name of the remote APPL.

To deactivate all sessions with the TPF APPL, enter the following:

   ZNETW INACT ID=pppp,I

Where:

pppp
The name of the TPF APPL.

Figure 145. Immediate APPL-APPL Session Deactivation




Note:
For PU2.1 sessions, no CDSESSENDs are sent (skip step #3).

Forced APPL-APPL Session Deactivation

To deactivate an APPL-APPL session with force from the TPF system, enter the following:

   ZNETW INACT ID=ssssssss,F

Where:

ssssssss
The name of the remote APPL.

To deactivate all sessions with the TPF APPL, enter the following:

   ZNETW INACT ID=pppp,F

Where:

pppp
The name of the TPF APPL.

Figure 146. Forced APPL-APPL Session Deactivation




Note:
For PU2.1 sessions, no CDSESSENDs are sent (skip step #2).

Host-Node SLU Session Deactivation

The following sections show different ways to deactivate a host-node SLU session.

Normal Deactivation of Host-Node SLU Session

To deactivate a host-node SLU session normally from the TPF system, enter the following:

   ZNETW INACT ID=ssssssss

Where:

ssssssss
The name of the TPF SLU thread.

To deactivate all sessions with the remote APPL, enter the following:

   ZNETW INACT ID=pppppppp

Where:

pppppppp
The name of the remote APPL.

Figure 147. Normal Host-Node SLU Session Deactivation




Notes:

  1. Responses to normal data traffic can flow before step #4. Because the CHASE command is normal flow, once a response to CHASE has been received the LU knows it is not waiting for any more responses to normal flow traffic. The remote LU does not have to send a CHASE request, so step #3 is optional.

  2. For PU2.1 sessions, no CDSESSENDs are sent (skip step #6).

Immediate Deactivation of Host-Node SLU Session

To deactivate a host-node SLU session immediately from the TPF system, enter the following:

   ZNETW INACT ID=ssssssss,I

Where:

ssssssss
The name of the TPF SLU thread.

To deactivate all sessions with the remote APPL, enter the following:

   ZNETW INACT ID=pppppppp,I

Where:

pppppppp
The name of the remote APPL.

Figure 148. Immediate Host-Node SLU Session Deactivation




Note:
For PU2.1 sessions, no CDSESSENDs are sent (skip step #2).

Forced Host-Node SLU Session Deactivation

To deactivate a host-node SLU session with force from the TPF system, enter the following:

   ZNETW INACT ID=ssssssss,F

Where:

ssssssss
The name of the TPF SLU thread.

To deactivate all sessions with the remote APPL, enter the following:

   ZNETW INACT ID=pppppppp,F

Where:

pppppppp
The name of the remote APPL.

Figure 149. Forced Host-Node SLU Session Deactivation




Note:
For PU2.1 sessions, no CDSESSENDs are sent (skip step #2).

FMMR-FMMR Session Deactivation

The following sections show different ways to deactivate an FMMR-FMMR session.

Normal or Immediate Deactivation of FMMR-FMMR Session

To deactivate an FMMR-FMMR session normally from the TPF system, enter the following:

   ZNETW INACT ID=rrrrrrrr

To deactivate an FMMR-FMMR session immediately from the TPF system, enter the following:

   ZNETW INACT ID-rrrrrrrr,I

Where:

rrrrrrrr
The name of the remote FMMR.

To deactivate all FMMR sessions, enter the following:

   ZNETW INACT ID=llllllll

or

   ZNETW INACT ID-llllllll,I

Where:

llllllll
The name of the local FMMR.

Figure 150. Normal or Immediate FMMR-FMMR Session Deactivation




Note:
For PU2.1 sessions, no CDSESSENDs are sent (skip step #2).

Forced FMMR-FMMR Session Deactivation

To deactivate an FMMR-FMMR session with force from the TPF system, enter the following:

   ZNETW INACT ID=rrrrrrrr,F

Where:

rrrrrrrr
The name of the remote FMMR.

To deactivate all FMMR sessions, enter the following:

   ZNETW INACT ID=llllllll,F

Where:

llllllll
The name of the local FMMR.

Figure 151. Forced FMMR-FMMR Session Deactivation




Note:
For PU2.1 sessions, no CDSESSENDs are sent (skip step #2).

LU 6.2 Session Deactivation

If you deactivate an LU 6.2 session normally, the session ends after the active conversation, if any, finishes. The other types of deactivation cause the session to end without waiting for an active conversation to finish.

Normal LU 6.2 Session Deactivation

To deactivate LU 6.2 sessions normally for a particular remote LU, enter the following from the TPF system:

   ZNETW INACT ID=ssssssss

or

   ZNCNS RESET LU=ssssssss,MODE=nnnnnnnn

Where:

ssssssss
The name of the remote LU

nnnnnnnn
The mode name.

To deactivate all LU 6.2 sessions normally between remote LUs and a specific TPF/APPC local LU, enter the following:

   ZNETW INACT ID=pppp

Where:

pppp
The name of the local TPF/APPC LU.

Figure 152. Normal LU 6.2 Session Deactivation




Note:
For PU2.1 sessions, no CDSESSENDs are sent (skip step #4).

Immediate LU 6.2 Session Deactivation

To deactivate all LU 6.2 sessions immediately for a particular remote LU, enter the following from the TPF system:

   ZNETW INACT ID=ssssssss,I

Where:

ssssssss
The name of the remote LU.

To deactivate all LU 6.2 sessions immediately between remote LUs and a specific TPF/APPC local LU, enter the following:

   ZNETW INACT ID=pppp,I

Where:

pppp
The name of the TPF APPL.

Figure 153. Immediate LU 6.2 Session Deactivation




Note:
For PU2.1 sessions, no CDSESSENDs are sent (skip step #2).

Forced LU 6.2 Session Deactivation

To force the deactivation of all LU 6.2 sessions with a particular remote LU, enter the following from the TPF system:

   ZNETW INACT ID=ssssssss,F

Where:

ssssssss
The name of the remote LU.

To force the deactivation of all LU 6.2 sessions between remote LUs and a specific TPF/APPC local LU, enter then following:

   ZNETW INACT ID=pppp,F

Where:

pppp
The name of the TPF APPL.

Figure 154. Forced LU 6.2 Session Deactivation




Note:
For PU2.1 sessions, no CDSESSENDs are sent (skip step #2).

APPN Session Activation

The following sections show examples of session activations when the TPF system is connected to the network as an APPN end node (EN).

CP-CP Session Activation

This section contains the flows for activating CP-CP sessions between the TPF system and its network node server (NNS).

Figure 155. CP-CP Session Activation




Note:
The CP-CP sessions are not considered active until step 4 completes.

APPN LU-LU Session Activation

This section contains the flows for activating LU-LU sessions between the TPF system and remote LUs in an APPN network.

Legend for acronyms in the flow diagrams:

APPL
Application LU

CP
Control point LU

M1
PCID modifier in the original LOCATE request

M2
PCID modifier used in the subprocedure

NNS
Network node server

PLU
Primary logical unit

RSCV
Route selection control vector (control vector X'2B')

SC
Session characteristics (control vectors X'31' and X'65')

Sessst
Session started notification

SLU
Secondary logical unit

TGs
Transmission groups (pairs of control vectors X'46' and X'47').

Session Started by a TPF PLU

The following diagram shows the flows for sessions that are started by a TPF PLU.

Figure 156. Session Started by TPF PLU (APPN)




Session Started by a TPF SLU

The following diagram shows the flows for sessions that are started by a TPF SLU.

Figure 157. Session Started by TPF SLU (APPN)




Session Started by a Remote SLU When RSCV is Provided

The following diagram shows the flows for sessions that are started by a remote SLU when the RSCV is provided.

Figure 158. Session Started by Remote SLU (APPN), RSCV Provided




Session Started by a Remote SLU When RSCV is Not Provided

The following diagram shows the flows for sessions that are started by a remote SLU when the RSCV is not provided.

Figure 159. Session Started by Remote SLU (APPN), RSCV Not Provided




Session Started by a Remote SLU When the Session is Queued

The following diagram shows the flows for sessions that are started by a remote SLU when the session is queued.

Figure 160. Session Started by Remote SLU (APPN), Session Queued




Session Started by a Remote PLU

The following diagram shows the flows for sessions that are started by a remote PLU.

Figure 161. Session Started by Remote PLU (APPN)




Session Started by a Remote PLU When the Session is Queued

The following diagram shows the flows for sessions that are started by a remote PLU when the session is queued.

Figure 162. Session Started by Remote PLU (APPN), Session Queued




LU-LU Session Activation for Printer Sharing

This section contains the flows for establishing an LU-LU session with a shared printer. The TPF system can either request the session with the printer or be asked to release its session with the printer.

Legend for acronyms in the flow diagrams:

CP
Control point LU

I/Q
Initiate or queue

NNS(SLU)
Network node server for the SLU

NNS(TPF)
Network node server for the TPF system

PLU
Primary logical unit

Relreq
Release session request

RSCV
Route selection control vector (control vector X'2B')

SC
Session characteristics (control vectors X'31' and X'65')

Sessst
Session started notification

SLU
Secondary logical unit

TGs
Transmission groups (pairs of control vectors X'46' and X'47').

Session Requested by the TPF System (Printer Available)

The following diagram shows the flows when the TPF system requests a session with a shared printer that is available.

Figure 163. Printer Sharing, Request by TPF, Printer Available




Session Requested by the TPF System (Printer In Use)

The following diagram shows the flows when the TPF system requests a session with a shared printer that is in use.

Figure 164. Printer Sharing, Request by TPF, Printer In Use




TPF System Requested to Release the Shared Printer

The following diagram shows the flows when the TPF system is requested to release the session with a shared printer.

Figure 165. Printer Sharing, TPF Requested to Release the Printer




APPN LU-LU Session Deactivation

This section contains the flows for deactivating LU-LU sessions in an APPN network. For active LU-LU sessions, the control points (CPs) are not involved except for the case where normal deactivation is done by a SLU. See PU 5 and PU 2.1 Session Deactivation for the other deactivation flows.

Legend for acronyms in the flow diagrams:

APPL
Application LU

CP
Control point LU

NNS
Network node server

PLU
Primary logical unit

SLU
Secondary logical unit.

Figure 166. Normal Deactivation by Remote SLU (APPN)




APPN-Subarea Migration Flows

This section contains the flows for establishing LU-LU sessions between the TPF system in an APPN network and remote LUs in a subarea (PU 5) network.

Legend for acronyms in the flow diagrams:

BF
Boundary function within the NCP

CDRM
Cross-domain resource manager

CP
Control point LU

INN
Interchange network node

NNS
Network node server

PLU
Primary logical unit

RSCV
Route selection control vector (control vector X'2B')

SC
Session characteristics (control vectors X'31' and X'65')

Sessst
Session started notification

SLU
Secondary logical unit

TGs
Transmission groups (pairs of control vectors X'46' and X'47').

SLU Initiated, SLU in APPN, PLU in Subarea

The following diagram shows the flows for sessions that are initiated by the SLU. The SLU is in an APPN network and the PLU is in a subarea network.

Figure 167. SLU Initiated, SLU in APPN, PLU in Subarea




SLU Initiated, SLU in APPN, PLU in Subarea (PLU Location Unknown)

The following diagram shows the flows for sessions that are initiated by the SLU. The SLU is in an APPN network and the PLU is in a subarea network but the PLU location is unknown.

Figure 168. SLU Initiated, SLU in APPN, PLU in Subarea (PLU Location Unknown)




PLU Initiated, SLU in APPN, PLU in Subarea

The following diagram shows the flows for sessions that are initiated by the PLU. The SLU is in an APPN network and the PLU is in a subarea network.

Figure 169. PLU Initiated, SLU in APPN, PLU in Subarea




SLU Initiated, PLU in APPN, SLU in Subarea (SC Provided)

The following diagram shows the flows for sessions that are initiated by the SLU. The PLU is in an APPN network and the SLU is in a subarea network. Session characteristics are provided.

Figure 170. SLU Initiated, PLU in APPN, SLU in Subarea (SC Provided)




SLU Initiated, PLU in APPN, SLU in Subarea (SC Not Provided)

The following diagram shows the flows for sessions that are initiated by the SLU. The PLU is in an APPN network and the SLU is in a subarea network. Session characteristics are not provided.

Figure 171. SLU Initiated, PLU in APPN, SLU in Subarea (SC Not Provided)




PLU Initiated, PLU in APPN, SLU in Subarea (SC Provided)

The following diagram shows the flows for sessions that are initiated by the PLU. The PLU is in an APPN network and the SLU is in a subarea network. Session characteristics are provided.

Figure 172. PLU Initiated, PLU in APPN, SLU in Subarea (SC Provided)




PLU Initiated, PLU in APPN, SLU in Subarea (SC Not Provided)

The following diagram shows the flows for sessions that are initiated by the PLU. The PLU is in an APPN network and the SLU is in a subarea network. Session characteristics are not provided.

Figure 173. PLU Initiated, PLU in APPN, SLU in Subarea (SC Not Provided)




More on SNA Command Flow

For additional information about SNA command flows, see the following publications: