Running without TQI

The use of TQI is optional.

Running without TQI improves system performance. BDT runs faster because there is no message delay. Less resources are needed because a TQI address space is not used. Less I/O takes place because messages are not written to and read from DASD.

However, running without TQI has these disadvantages:

JES2 users can submit commands and file-to-file transactions only if they are at a processor with a BDT address space. (JES3 users do not have this restriction.)
BDT must be running when users submit commands and file-to-file transactions. If BDT is down, requests will be lost because they cannot be held on a checkpoint data set until BDT is started or restarted.
Users can receive messages associated with their commands and file-to-file transactions only if they are at a processor with a BDT address space.

If you choose to run without TQI, the following is necessary:

You must code TQIEN=N and TQIREQ=N on the IEFSSNxx member of SYS1.PARMLIB. (TQIEN=Y and TQIREQ=Y are the defaults. TQIEN and TQIREQ are described on page Step 1. Define BDT As an MVS Secondary Subsystem—SYS1.PARMLIB Member IEFSSNxx.)
You must not allocate the TQI checkpoint data set, the TQI bit-map data set, or any message data sets in the BDT start procedure. (The BDT start procedure is described on page Step 1. Write a BDT Start Procedure.)
You must code TQIAUTO=NO on the OPTIONS initialization statement. (TQIAUTO=YES is the default. TQIAUTO is described on page OPTIONS—Define Operating Characteristics of the BDT Subsystem.)