TRANSFER Installation and Management Guide

Using the SCHEDULER QUEUE SAMPLES Screen
TMANAGER
10–14 13198 Tandem Computers Incorporated
Remote Shipment entries occur only if there was a failure while processing a
submit entry that required shipment to a remote node. The count for Remote
Shipment work goes up and down depending on whether remote systems are
available. If a remote system is not available, the entry is placed in the NET queue
for retry later.
Remote shipment requests in the NET queue are entries that have been tried
previously when the remote system was not available. TSCHED moves entries
from the NET queue to the READY queue based on parameters given to TSCHED
at start time. Remote Shipment work requests in the READY queue are entries
ready for remote shipment.
Items are removed from the HELD queue at CHECKSESSIONHOUR if you
specify the UNHOLD parameter as TRUE in the PATHWAY configuration for the
A-TSCHED server. For more information about the CHECKSESSIONHOUR
parameter, see Section 7, “Customizing a TRANSFER System” and “Idle Sessions”
in Section 11,“Managing a TRANSFER System.”
The count of entries for the type-of-work Invalid Code should always be zero.
If you do have Invalid Code entries, however, you need to shutdown your
TRANSFER system and do the following:
1. Use the FUP PURGEDATA command on the READY, TIME, and NET files
(including their alternate key files) to delete all entries from the queues.
2. Run the XIINIT utility to recreate the control record in each scheduler file.
3. Run TCHECK to adjust any inconsistences in the TRANSFER database.
4. Start TRANSFER.
5. Run TSRBLD to rebuild the queue files.
For more information about the XIINIT, TCHECK, and TSRBLD utilities, refer to
Section 11, “Managing a TRANSFER System.”