|
Launch-Time Do-Not-Send Checking |
  
|
|
Launch-Time Do-Not-Send Checking |
|
Purpose
The lookup checks for phone number, e-mail address or e-mail domain name at launch time for all outbound operations, and if found in the specified index file the outbound operation will be marked for failure. The benefits of this approach are described in the introduction to this section.
Commands Used
The following commands may be placed in System, Owner or Jobtype UJP files, from which they will migrate to the Job Instance Properties in the usual way on job creation. The commands may also be placed in the FST file used for launches using FFBC.
Each command specifies an index file to be used (containing entries to be checked against), together with an optional outcome override and other keyword parameters. When you use these commands to specify global, per-client or per-job lookup files, you should normally disable the legacy Do-Not-Send lookups described in later sections. For global lookups, this can be done selectively by assigning a value of NONE to system variables DNS_PATH, DNS_MAIL_PATH and DNS_DOMN_PATH when the new commands have been implemented and tested. The user-specific lookups are disabled by removing the $dns_file command and the system variables USER_DNS_MAIL and USER_DNS_DOMN.
The sequence in which files are checked is System, Owner and then Jobtype, with the commands originating in each file being checked in the reverse sequence to that in which they appear. All the white-list items are checked first and a match causes further checking to be skipped. White-list matches also prevent items from being excluded by legacy do-not-send commands and variable specifications.
In a Job Administration type FEB2 broadcast (separate columns for fax phone and e-mail), a match on either the e-mail or the phone column will exclude the item.
The outcome code is determined by the file in which a match is first found.
Default Failure Outcome codes
Phone lookup failures: 188
E-Mail lookup failures: 189
Domain lookup failures: 190
Resubmit Failed
Since these checks are, by definition, performed at job launch time, resubmitting an item which has failed the check will cause it to be transmitted. This differs from the processing of the legacy do-not-send lookups, where the lookup is repeated for a resubmitted item. To guard against unwanted accidental transmission, outcome codes 188-190 are never resubmitted as a result of using the JOBADMIN Resubmit Failed dialog and entering class 'Z'. You can still resubmit these items by entering the outcome code in the JOBADMIN Resubmit Fail dialog or by using the right-click menu of the JOBADMIN job item status list.
Override Failure Outcome codes
The outcome code number specified on the $dns_phone or $dns_email command, if any, will override the default values shown above. In the case of an index containing both e-mail addresses and domain names, the specified outcome code will be incremented by one for domain matches.
If you use the override outcome code on the command, failed items will NOT be protected from accidental transmission if you ignore the warning and enter 'Z' on the JOBADMIN Resubmit Fail dialog.
Topic url: http://www.copia.com/support/refmanual/index.html?launch_time_do_not_send.htm