|
$listfile [UJP] |
  
|
|
$listfile [UJP] |
|
Specify Filename of Broadcast List
$listfile filename [OMIT]
This command is use to specify the name of a broadcast list, and also to select whether items from that list are to be included in a specific broadcast.
This command normally originates in the Owner Job Properties or Jobtype Job Properties file and is copied into a Job Instance Properties file as the job instance is created.
Currently the following list types are supported:
| .TLS, .TAB, .TXT | The list is an ASCII file in which fields are delimited by TAB characters. Because of the variability of CSV specifications, we strongly recommend the use of this type of ASCII file in preference to those with other delimiters. |
| .XLS | The list is in the first or only worksheet of an Excel file. The default is now set to use a custom interface in F7EXCEL.DLL to read Microsoft Excel files, so that Excel is no longer required to be installed on the machine that is using the list to launch a job. This interface does not support XLS files from Excel 95 or earlier. To force the use of Excel (2000 or later), assign a non-empty value to the variable USE_EXCEL. Excel 2007 .XLSX broadcast lists are supported (and do not require the USE_EXCEL variable) if Excel 2007 is installed: the Microsoft Office Compatibility Pack is not currently supported for this purpose. |
| .DBF | The list is in a standard dBase DBF file. |
| .LST, .CSV | These extensions, and any others apart from the those listed above, denote an ASCII file in which fields are delimited either by the system-defined list-separator character or by a space. This means that fields containing embedded blank space must be enclosed in double-quotes. The list separator is that defined in Windows regional settings. If the list separator is '|' then blank space is not a separator character and double quotes are unnecessary. To prevent the use of a space as a delimiter in unquoted fields when other delimiters are defined, define NO_SPACE_DELIMITER to a non-empty value in job properties. |
Other ASCII-file extensions, as well as those shown above, may be forced globally to be processed as either CSV or TAB types by setting the FORCE_CSV and FORCE_TAB system variables in the configuration file. To vary the settings for individual owners, omit this $var_def from the configuration file and place it instead in SYSTEM.UJP and/or individual owner or jobtype properties.
The parameters on this command are used as follows:
| filename | The full pathname of the file to be used. Except in the presence of a $var_def command defining NO_LIST_GROUP as a non-empty value, a filename part starting with the word 'GROUP' is taken as the name of an ASCII file containing list pathnames, one per line. |
| OMIT | A keyword indicating that the list is to be excluded for the job instance (in an instance UJP only). |
There can be a maximum of 256 $listfile commands in an instance UJP file. Since the instance UJP file is built from the system, owner and jobtype UJP files, this limits the number of list files you can include in each.
Position Requirements: The sequence of the $listfile commands is significant since lists can be selected by sequence number in Job IVR. Lists can also be selected in custom IVR by assigning a string of 0/1 digits to the JOBLISTS system variable. See also the $job_options keyword 'abslist'.
Default: none
Example:
$listfile @FFJOBS\copia\presslist.TXT
$listfile @FFJOBS\copia\GROUP007.TXT
Topic url: http://www.copia.com/support/refmanual/index.html?$listfile.htm