Immediate, immnonurgent, immnormal, immurgent, periodic, period Channel Options

From MsgServerDocWiki

Channel service periodicity (immediate, immnonurgent, immnormal, immurgent, periodic, period)

IMPORTANT NOTE: All of these channel options are obsolete and have no effect in the Sun Java System Messaging Server. While the code default is still immnormal, the normal Messaging Server configuration sets immnonurgent on the defaults channel for self-documentation purposes, as immnonurgent corresponds (more or less) to the actual behavior of Messaging Server, regardless of what is set.

If a channel is capable of master-mode operations (as specified with the master channel option), such operations may be initiated either by a periodic service job or on demand as delivery is needed. The channel option periodic inhibits initiation of delivery jobs on demand for the channel it is associated with regardless of priority. The immediate channel option, which is the default, specifies that jobs should run on demand for messages of appropriate urgency; what appropriate urgency means is controlled via the channel options described below.

• immurgent enables immediate delivery processing on messages with a priority setting of urgent. Messages with a lower priority will wait for periodic processing.
• immnormal enables immediate delivery for messages with normal or urgent priority. immnormal is the default.
• immnonurgent enables immediate delivery for urgent, normal, and non-urgent messages.

Thus the default behavior (immediate immnormal) enables immediate processing for all but non-urgent or lower priority messages.

Delivery via periodic service jobs is always possible unless the channel is marked with the slave channel option. Channels capable of master-mode operation are periodically checked for pending messages by periodic service jobs. These jobs runs at fixed intervals --- usually every four hours, though you may change this interval, if desired. On OpenVMS systems, the interval is changed by setting the system logical PMDF_POST_INTERVAL; if used, PMDF_POST_INTERVAL should be set to a string of the form DD HH:MM:SS (e.g., "0 00:30:00"). With PMDF on UNIX systems, the interval is determined in the crontab entry for the post job; see the appropriate edition of the PMDF Installation Guide. On NT systems, the interval is determined by the Scheduler.

Not all channels may need service at the same intervals. For example, a channel may see little traffic and be expensive to service (i.e., it costs money to place a connecting phone call on a master-only periodic PhoneNet channel). Servicing such a channel at longer intervals than that of a single period between periodic jobs may lower the cost of operation without significantly affecting the quality of service. In another case, one particular channel may see very heavy traffic and may require frequent service, while other channels need servicing much less often. In this situation it may be appropriate to service the heavily used channel more often than any other.

The period channel option can be used to control how often a channel is serviced. This option requires a single integer argument. The channel is then serviced by every Nth service job. The default value of the period channel option is 1, which means that every periodic service job will check the channel for pending messages.