Terminal reconnect protocols

The reconnect protocol used for terminals with RNR activated depends on the kind of work in progress and the types of terminals in use at the time of the outage.

The following table shows the reconnect protocol used for each type of terminal following a session outage. All terminals are assumed to have RNR activated. If a session cannot be reconnected, error message DFS2050 or DFS2055 is sent to the Master Terminal Operator.
Table 1. Rapid Network Reconnect protocols
Terminal type Connect protocol Terminal subtype Message generated
SLU1 SNA CLEAR

SNA SDT
  • Static sessions
  • ETO printers
 DFS36501
ETO non-printers DFS3649
SLU2 SNA CLEAR

SNA SDT

 Static sessions DFS3650
Static sessions DFS3649
NTO SNA CLEAR

SNA SDT

 Static sessions DFS3650
ETO sessions DFS3649
SLU0

(Non-SNA 3284 and 3286)

 SNA UNBIND

SNA BIND

 Static sessions DFS3650
ETO sessions DFS3649
SLU0

(Finance and SLUP)2

 SNA CLEAR

SNA STSN

SNA SDT

 ETO sessions No message
ISC

(Primary Half-Session)

 SNA UNBIND

SNA BIND

SNA STSN

SNA SDT

   No message
ISC SNA UNBIND   No message
ETO w/ ALOT=03 UNBIND

UNBIND

   No message
Notes:
  1. Message DFS3649 indicates that signon is required. Message DFS3650 indicates that no signon is required.
  2. Reconnect is available only for Single-Node Persistent Sessions.
  3. Signon data must be supplied as logon user data or by the DFSLGNX0 exit.