We have just explained how BMS determines the terminals eligible to receive
your routed message. Actual delivery occurs later in time, much later in some
cases, depending on the scheduling options in your ROUTE command (INTERVAL,
TIME, AFTER and AT). You can request delivery immediately, after an interval
of time has elapsed, or at a particular time of day.
When the appointed time arrives, BMS attempts to deliver the message to
every terminal on the eligible terminal list. All the following conditions
must be met for the message to be delivered to any particular terminal:
- The terminal must be defined as a type supported by BMS, and the same
type as when the ROUTE command was processed8. (Where
there is a long delay between creation and delivery of a message, it is possible
for the terminal defined with a particular TERMID to change characteristics
or disappear, especially in an autoinstall environment.)
- The terminal must be in service and available (that is, there cannot be
a task running with the terminal as its principal facility).
- The terminal must be eligible for automatic transaction initiation, or
the terminal operator must request delivery of the message with the CSPG transaction.
Note:
If several messages accumulate for delivery to a particular terminal,
there is no guarantee that the operator will view them in any particular order.
In fact, the CSPG transaction allows the operator to control delivery order
in some situations. If a specific sequence of pages is required, you must
send them as one message.
- If the delivery list entry restricts delivery to a particular operator
or to operators in certain classes, the operator signed on at the terminal
must qualify. (See Message destinations for the OPCLASS and LIST specifications
that produce these restrictions.)
- The purge delay must not have expired, as explained in the next section.
If BMS cannot deliver a message to an eligible
terminal, it continues to try periodically until one of the following conditions
occurs:
- A change in terminal status allows the message to be sent.
- The message is deleted by the destination terminal operator.
- The purge delay elapses.
The purge delay is the period of time allowed for delivery of a message
once it is scheduled for delivery. After this interval elapses, the message
is discarded. The purge delay is
a system-wide value, set by the PRGDLY option in the system initialization
table. Its use is optional; if the systems programmer sets PRGDLY to zero,
messages are kept indefinitely.
When BMS purges a message in this fashion, it sends an error message to
the terminal you specify in ERRTERM. (If you use ERRTERM without a specific
terminal name, it sends the message to the principal facility of the task
that originally created the message. If you omit ERRTERM altogether, no message
is sent.)
A 3270 terminal need not have exactly the same extended attributes that it
had at the time the ROUTE command was issued, because BMS removes unsupported
attributes from the data stream at the time of delivery.
[[ Contents Previous Page | Next Page Index ]]