If you add the TRANSMIT and RECEIVE commands to the table of authorized commands, the TSO/E default allows all users to use those commands. By writing exits, you can limit the use of TRANSMIT and RECEIVE to specific users. You can also use exits to restrict the nodes to which a user can send transmitted data, to allow users to receive data sets intended for other users, and to allow users to transmit and receive data set types that TRANSMIT and RECEIVE do not support.

TSO/E allows you to decide on an installation-wide basis whether transmitted data will be encrypted. You can require all transmitted data to be encrypted, you can allow the user to decide whether to encrypt data, or you can disallow encryption altogether. If you allow encryption, you can use TRANSMIT and RECEIVE exits to selectively prevent encryption or decryption. You can also use exits to modify the encryption and decryption options the user specifies, or to use your own encryption algorithm instead of the one TSO/E invokes by default. By default, TSO/E users are not notified when they have a transmission to receive. You can use exits to provide that notification. JES2 and JES3 provide exits for notifying the receiver that a transmission has arrived. JES2, JES3, and TSO/E all provide exits for notifying the sender that an acknowledgment is available to receive.

Periodically you might need to delete from the JES spool those data sets that have been sent to incorrect user IDs, or to users who have not logged on for a given period of time. JES2 and JES3 provide exits you can use for that purpose.

TSO/E enables you to collect statistics on network usage and to report those statistics. Two TSO/E exits that you can write collect the statistics. SMF macros, that you code in those exits, report the statistics.

For more information, see Customizing TRANSMIT and RECEIVE.