Five authorization exit routines run in the BDT address space. Their function is to examine each command and file-to-file transaction, to determine whether the user is allowed to issue it, and to send an appropriate return code back to the calling module. These exit routine are:

• BDTUX25—authorizes users submitting commands to the BDT address space. If TQI is not enabled, it also authorizes users submitting file-to-file transactions. BDTUX25 runs when a command or file-to-file transaction enters the BDT address space. If the exit routine is not coded, BDT rejects the command or transaction. If TQI is enabled, transactions skip BDTUX25 and use BDTUX29 instead.
• BDTUX26—authorizes users submitting file-to-file transactions at the global node. BDTUX26 runs in the global BDT node before a BDT job number is assigned and the job is placed on the BDT work queue.
• BDTUX27—authorizes users submitting file-to-file transactions at local BDT nodes. If coded, it runs on both ends of a transfer just before the dynamic application programs (DAPs) for the transfer are scheduled. The assignment of the DAPs on both ends of a transfer is the final step before the actual transfer of the data. BDTUX27 runs on both sides to make authorization checks before the transfer is actually made.
• BDTUX29—authorizes users submitting file-to-file transactions when TQI is enabled. It runs for file-to-file transactions only, not for commands. BDTUX29 must check the authorization of the user requesting the transaction.
• BDTUX31—authorizes users to submit INQUIRY and MODIFY commands concerning specific transactions (both file-to-file and SNA NJE). Information about the owner of the transaction, the origin of the command, and the type of command entered are given to BDTUX31 to determine if information about the transaction should be displayed.