E-Mail Special Action Specification

$action_email pathname [code] [domain|combined] [EmptyOK] [WSDelim]

This command is used to specify a list file which is pre-loaded by the COPIAFACTS engine, to specify special actions to be performed for specific e-mail addresses or domains.  Multiple commands may be specified to arrange for different types of action.

Job Administration users should not normally use this command: instead use $action_email commands in SYSTEM.UJP to specify actions at launch time.

For more information, see Destination-Specific Processing.

The parameters on this command are used as follows:

pathnameThe pathname of the look-up file to be used.  Currently supported file extensions are:
.NDXa character-mode index file created and maintained by the PIN utility.
.TXTa list of entries to be matched
The timestamp of the file will be checked each time a fresh scan of the TOSEND folders is started (typically every 20 seconds) and the file will be reloaded if it has changed.
codeA code which will be used as the default numeric action code for matched items. In a 'combined' index/list, the supplied code will be incremented by one for domain-name matches.  If not supplied, only the action code from the list will be returned.
domainA keyword which indicates that the index/list contains only domain names to be matched
combinedA keyword which indicates that the index/list contains both e-mail addresses and domain names
EmptyOKA keyword which indicates that the index/list may be empty.  This suppresses the check that ensures that at least one entry has been loaded from the file. Failure to load any entries could be a symptom of a corrupted file.
WSDelimA keyword which indicates that any number of white spaces may separate the phone number and the action code in a loaded TXT list.

The NDX file may contain a positive numeric data value for each entry, and the TXT file may contain a positive numeric data value separated from the address/domain entry by a single TAB character (or any whitespace, if WSDelim is used).  If present, this will override the default numeric action code.

The action codes from the list(s) in which the item is matched will be returned, separated by semi-colons, in the ACTION_CODES variable as the FS file is processed, along with any action codes already present from the FS file.  However only the original ACTION_CODES content will be written back to the FS file variable.

Action codes less than 1000 are reserved for system use, and it is recommended that only 4-digit codes are used for user applications..

Example:

A domain matched in two lists might acquire a string "1234;2041" in the variable ACTION_CODES. The pre-process commands used to perform the appropriate actions would then be:

$if 1234 $in @ACTION_CODES

  ...

$endif

$if 2041 $in @ACTION_CODES

  ...

$endif