$retry_tosend [USR, UJP]
Specify TOSEND Directory for Retries
This command is used to specify that a different TOSENDx directory is to be used for retries after the first attempt has failed. This allows the priority of retry attempts to be increased or reduced. The directory specified by the first parameter on this command will be used for all subsequent automated retries of the transmission. The number specified must be non-zero and must not be higher than the number of extra TOSEND directories specified on the $request_dir command.
Important note: this command affects all outbound operations done with this user profile, including broadcasts and server operations.
For special applications an override for this command may also be placed in an individual FS file as an override to that in the user profile. This is done automatically when a Retry Action is specified in a custom SMR file to specify a TOSEND queue for retries after a specific outcome code has occurred.
The parameters on this command are used as follows:
|tosend||the number of the TOSENDx directory to be used for retries. A value of -1 in this parameter leaves normal retries unchanged and allows this command to be used just to specify an mtosend parameter.|
|mtosend||the number of the TOSENDx directory to be used when job items are manually resubmitted after failure. This directory is also selected when the 'P' prefix is used in a $retry_delays item.|
Default: The same TOSENDx directory will be used for all attempts.
Use TOSEND3 for all retries:
$retry_tosend 3 ; use TOSEND3 for retries
Use TOSEND3 for automatic retries and TOSEND11 for manual retries:
$retry_tosend 3 11
Use TOSEND3 for initial automatic retries and TOSEND11 for manual retries and the third and subsequent retries:
$retry_tosend 3 11
$retry_delays F "5 5 P5 P5 P5"