SESSION
Purpose
The SESSION control file entry applies to base AON functions.
The SESSION control file entry is used to identify sessions that are to be actively monitored by AON⁄SNA.
Syntax
- alias
- The 1 - 8 character name used to identify the session. Also, use the alias name in an ACTMON statement. Choose names to avoid conflicts with real resources.
- lu_name
- The names used to identify the pair of logical units. The names can be network qualified, as in network_name.luname.
Usage notes
- The Advanced Peer-to-Peer Networking architecture uses the SESSION control file entry.
- The session must also have an ACTMON control file entry.
Examples
- The following example defines a session called TEST1 between LU
NT6DI005 and application NTV6D in network USIBMNT.
SESSION TEST1,LU1=USIBMNT.NTV6D, LU2=NT6DI005 - The following example defines three sessions. An ACTMON statement
for these entries is also required if these sessions are actively
monitored.
SESSION RJE1,LU1=RALSNDS1,LU2=RALSNDS8 SESSION RJE2,LU1=RALSNDS1,LU2=RALSNDS7 SESSION RJE3,LU1=RALSNDS1,LU2=RALSNDS6
