1 declare 2 1 server_socket_table(0:255) static aligned, /* SST */ 3 2 gender fixed binary(8), 4 2 socket_usage fixed binary(8), 5 2 byte_size fixed binary(8), 6 2 unused_brother fixed binary(8), 7 2 event_channel fixed binary(71), 8 2 connection_channel fixed binary(71), 9 2 listener_id_no fixed binary(35), 10 2 link_segment_ptr pointer, 11 2 link_subscript_or_mode fixed binary(17), 12 2 type_for_transfer fixed binary(8), 13 2 ncp_index bit(36) unaligned, 14 2 foreign_socket_id bit(41) unaligned; 15 16 17 /* 18 The SST contains information about all of the auxiliary sockets used by RSEXEC requests. 19 The local pin number is passed to foreign users as the HANDLE; this is used to index the 20 SST array on subsequent references. Some less than obvious SST fields are : 21 22 socket_usage : state or usage of this socket, from above list 23 24 unused_brother : since Multics always views sockets as pairs, the 25 use of net_pin_manager_ results in the allocation 26 of two pins. However, RSEXEC requests only ask for 27 sockets one at a time. Thus, one of each pair allocated 28 by Multics is ignored; unused_brother is its pin number. 29 30 listener_id_no : each RSEXEC conversation is assigned a unique integer 31 identifier so that sockets belonging to that conver- 32 sation can be found. 33 34 link_segment_ptr : if this socket is in use for a link, this field 35 points to the <user>.ARPAnet_msgs segment involved in 36 this link. 37 38 link_subscript_or_mode : 39 if socket is used for a link, this is the index of this 40 link in the ULT.link array. If used for file transfer, 41 this field is the mode specification. 42 43 type_for_transfer : if socket is used for file transfer, this is the type 44 specification. 45 46 */