Syntax
SENDLISTSTATIC expression { <download_file> | FILE extract_file }
<download_file> := { file_name | expression } [ ON expression ]Parameters
SendListStatic can be abbreviated as SLSTA.
expression
The name of the listbox to download is specified. This can be a literal, String attribute or String expression. The listbox name is contained as the value of the attribute or expression.
A common convention for the format of the listbox name is one of the following forms (where <item> is the variable the list box applies to):
<ispec>.<item>
Indicates that the list box applies only to users of the specified ispec.
*.<item>
Indicates that the list box applies to users of all ispecs.
download_file
The name of the file to download is specified. This external text file contains the complete list box data that creates a static list box.
Refer to SendMessage for more information on the format of value-description pairs in the file.
ON expression
The On command option is not supported for applications deployed on Windows.
For MCP-based systems, the expression can be a variable or literal containing the pack that has the file stored in it. The default is the Dictionary pack for the system.
FILE extract_file
The existing extract file to use as a definition is specified. This extract file must have been previously defined using a Determine Actual or Extract logic statement with the RetainAs command option, or referenced by a SetTitle logic statement in a report.
Description
For Windows-based systems
The SendListStatic logic statement populates a static list box with multiple value-description (expression) pairs from a specified file. It is intended for use with the Component Enabler or the NOF interface.
The specified file is downloaded from the host application when the user interface containing the specified list box is accessed for the first time by a particular user, and on subsequent occasions, if the timestamps on the file dictate that this is necessary.
Refer to SendListDynamic for more information on populating dynamic list boxes.
For MCP-based systems
For Reports run from a NOF terminal or program for an MCP-based system, the SendListStatic command sends data to the NOF terminal or program. Otherwise, the data is submitted to the Workstation Driver Program (WDP).
For Ispecs in an MCP-based system, executing the SendListStatic command from a T27 style, IBM 3270 or OLTP terminal is ignored unless contained in the System Global Logic STARTUP (in which case the data is submitted to WDP). NOF input results in the data being sent to the NOF terminal or program.
When processing an OLTP-originated transaction, the SendListStatic command is ignored. No user indication is given.
Restrictions
The following restrictions apply to use of the SendListStatic logic command:
It is ignored in OLTP-originated transactions.
It has an effect only in ispecs or reports initiated by a user station, or in standalone reports.
Examples
Example 1
This example creates and downloads an extract file.
LookUp From Glb.Spaces Areas
Extract Frame10 As FileA RetainAs "AreaFile" : Frame10 defines format
End
SendListStatic "*.AreaCode" File FileA : Closes file and downloads
Example 2
This example uses the Cust ispec with Branch and CusTyp list boxes.
In logic, a static listbox for Branch is to be downloaded from the BranchLbx file, and a list box for CustTyp is to be downloaded from the CusTypLbx file. The Branch list box is used by other ispecs, but the CusType list box is specific to Cust.
SendListStatic "*.Branch" BranchLbx SendListStatic "Cust.CusTyp" CusTypLbx