Short retry count (SHORTRTY)
This attribute specifies the maximum number of times that the channel is to try allocating a session to its partner.
The short retry count attribute can be set from zero through 999 999 999.
- Cluster sender
- Cluster receiver
If the initial allocation attempt fails, the
count is decremented and the channel retries the remaining number of times with
an interval, defined in the short retry interval attribute, between each
attempt. If it still fails, it retries
long retry count number
of times with an interval of
long retry interval between each
attempt. If it is still unsuccessful, the channel closes down.
On z/OS®, a channel cannot enter retry if the maximum number of channels (MAXCHL) has been exceeded.
On IBM® i, UNIX, and Windows systems, in order for retry to be attempted a channel initiator must be running. The channel initiator must be monitoring the initiation queue specified in the definition of the transmission queue that the channel is using.
If the channel initiator (on z/OS ) or the channel (on Multiplatforms) is stopped while the channel is retrying, the short retry count and long retry count are reset when the channel initiator or the channel is restarted, or when a message is successfully put at the sender channel. However, if the channel initiator (on z/OS ) or queue manager (on Multiplatforms) is shut down and restarted, the short retry count and long retry count are not reset. The channel retains the retry count values it had before the queue manager restart or the message being put.
- When a channel goes from RETRYING state to RUNNING state, the short retry count and long retry count are not reset immediately. They are reset only when the first message flows across the channel successfully after the channel went into RUNNING state, that is; when the local channel confirms the number of messages sent to the other end.
- The short retry count and long retry count are reset when the channel is restarted.