Message delivery

A message can be delivered some time after the ROUTE command is issued, depending on the scheduling options in the 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 processed. 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. 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.
  • 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.


dfhp32j.html | Timestamp icon Last updated: Monday, 5 June 2017