Call Application Statement
This statement calls the specified ABF or Vision Pro application:
This statement has the following parameters:
name
Specifies the ABF or Vision Pro application name.
If you specify the name parameter, you cannot use the executable parameter.
If this is not the name of a file in the current directory, you must specify a full path name.
frame
Specifies the first frame or procedure to be called in the ABF or Vision Pro application. The value is a frame or procedure name.
If the called application was built with a default first frame or procedure, this parameter is optional. If you do not include it, the application begins at the default frame or procedure.
If the called application has no default first frame or procedure or you do not want to start at the default, you must include this parameter.
executable
Specifies the executable file containing the ABF or Vision Pro application.
If you specify the executable parameter, you cannot use the name parameter.
If this is not the name of an application in the current directory, you must specify a full path name.
param
Passes application-specific parameters to the called application. The value is a string of up to 2000 bytes that contains the parameters you want to pass. Use single spaces to separate the parameters.
OpenROAD passes the parameters to the application as a series of parameters to the command that starts the application. Your host system that processes this command may modify these parameters before the application receives them.
To call another OpenROAD application, use the call runimage or call rundbapp statement. To start a second application that uses a different database or database session, use the call system statement.
Call ISQL
Calls Interactive SQL. It has no parameters.
Call QBF
Calls Query-By-Forms (QBF) to use with the specified QBFName, JoinDef, or table. It takes the following parameters:
qbfname
Specifies a QBFName. If the value is blank, the statement starts QBF at the QBFNames Catalog frame.
Equivalent to the -f flag.
joindef
Specifies the name of a JoinDef. If the is blank, the statement starts QBF at the QBF JoinDefs Catalog frame.
Equivalent to the -j flag.
tblfld
Specifies a table name. This parameter runs QBF on the specified table, using a table field to display the data. If the value is blank, the statement starts QBF at the Tables Catalog frame.
Equivalent to the -t flag.
lookup
Specifies a QBFName, JoinDef name, or a table name, which are checked in that order.
Equivalent to the -l flag.
silent
Suppresses status messages. The value is ignored.
Equivalent to the -s flag.
mode
Lets the application user enter Query-by-Forms directly in the specified mode. The value can be retrieve, append, update, or all.
Equivalent to the -m flag.
table
Specifies the name of the table to query with QBF. The value is a table name. This parameter must be omitted if either the joindef, qbfname, tblfld, or lookup parameter has been used.
flags
Specifies the flags that are to be in effect. The value consists of a list of flags enclosed in single quotes, with items separated by blanks or tabs. All of the flags for the system-level command line (except -u and -G) are allowed.
Call Report
This statement calls Report-Writer to run the specified report. It takes the following parameters:
file
Specifies a file name. This parameter directs the formatted report to the specified file for output.
Equivalent to the -f flag.
silent
Suppresses status messages. The value is ignored.
Equivalent to the -s flag.
report
Specifies a report name. This parameter indicates that a report, rather than a table, is being specified.
Equivalent to the -r flag.
mode
Specifies that a table, rather than a report, is being specified. (The name of the table is the value for the name parameter.) The value can be column, wrap, or block.
Equivalent to the -m flag.
mxline
Sets the maximum output line size to the specified number of characters. The value is an integer.
Equivalent to the -l flag.
mxquer
Sets the maximum length of the query specified in the .query command, after all substitutions for runtime parameters have been made, to the specified number of characters. The value is an integer.
Equivalent to the -q flag.
mxwrap
Sets the specified number as the maximum number of lines to wrap with one of the column C formats or the maximum number of lines that can be used within any block. The value is an integer.
Equivalent to the -w flag.
name
Names a database table or view for which a default report is to be formatted. The value is a table or view name.
param
Passes the parameters for the report. The value is a quoted string containing the parameter string for the report. Each element in a param string must have this form:
pname = 'value'
The elements must be separated by blanks or by tabs. Non-numeric values being passed in an element must be enclosed in standard quotes.
There is one exception: If pname is a character report parameter, the value must be enclosed in double quotes within single quotes (' “ ” '). Embedded double quotes must be dereferenced with a backslash (\).
printer
Specifies a printer name (overrides the default printer).
Equivalent to the -o flag.
copies
Specifies the number of copies to be printed. The value must be a positive integer. This parameter can only be used if you have specified the printer parameter also.
Equivalent to the -n flag.
forcerep
Specifies that the Report-Writer creates headers and footers, even if there is no data for the report. There is no value.
Equivalent to the -h flag.
formfeed
Specifies that the Report-Writer forces form feeds at page breaks, overriding any settings in the report-formatting commands. The value is ignored.
Equivalent to the +b flag.
noformfeed
Specifies that the Report-Writer suppresses form feeds, overriding any settings in the report-formatting commands. The value is ignored.
Equivalent to the -b flag.
pagelength
Sets the page length, in lines, for the report, overriding any .PL commands in the report. The value is an integer.
Equivalent to the -v flag.
sourcefile
Requests that the report specification be read from a source file outside of the Reports Catalog. With this flag, the specified source file is not saved in the database. The value is a file name.
Equivalent to the -i flag.
Note: You cannot use this flag in conjunction with the report (-r) or mode (-m) parameters.
brkfmt
Specifies that breaks and calculations for dates and numbers are based on the displayed data rather than on the internal database values. The value is ignored.
Equivalent to the +t flag (default).
nobrkfmt
Specifies that breaks and calculations for dates and numbers are based on the internal database values rather than on the displayed data. The value is ignored.
Equivalent to the -t flag.
flags
Specifies the flags that are to be in effect. The value consists of a list of flags enclosed in single quotes with items separated by blanks or tabs. All of the flags for the system-level command line (except -u and -G) are allowed.
Call Rundbapp
This statement starts execution of another OpenROAD application. The OpenROAD application that is called must be stored in the database associated with the current session of the calling application. Frames from the calling application are inactive while the called application is executing. This statement takes the following parameters:
application
Specifies the application to be run. The value is the name of the application. (The called application must be stored in the database associated with the current session of the calling application.)
startcomponent
Specifies the frame or procedure in the called application that you want as the entry to the called application. The value is the name of the starting component. If you do not specify a starting component, OpenROAD uses the default starting frame specified in the property sheet for the application.
loadmodule
Specifies the directory location of the 3GL load module for the application. For more information about 3GL load modules, see the Programming Guide. If you do not specify this parameter, no 3GL procedures can be called from the called application.
Note: If you want to execute an application stored in another database, use the call system statement.
Call Rungraph
This statement calls the Visual-Graphics-Editor (VIGRAPH) to display the specified graph that was defined by VIGRAPH. This statement takes the following parameters:
graph
Runs VIGRAPH to display the named graph. The value is the graph name.
device
Causes VIGRAPH to plot the graph in the correct format for the specified device type. The value is the device name.
Equivalent to the -d flag.
file
Causes VIGRAPH to send the graph output to the specified file. The value is a file name.
Equivalent to the -f flag.
table
Causes VIGRAPH to plot the graph with data from the named table. The value is a table name.
Equivalent to the -t flag.
plevel
Causes VIGRAPH to plot the graph at the specified presentation level. The value is an integer from one to five.
Equivalent to the -p flag.
prompt
Causes VIGRAPH to display a message that the graph has been plotted. There is no value.
Equivalent to the -n flag.
flags
Specifies the flags that are to be in effect. The value consists of a list of flags enclosed in single quotes with items separated by blanks or tabs. All the flags for the system-level command line are allowed.
Call Runimage
This statement starts execution of another OpenROAD application stored in an image file. The called application runs in the same database connection as the calling application. While the called application is executing, no frames in the calling application are active. This statement takes the following parameters:
filename
Specifies the name of the image file that contains the application to be run. The value is the file name.
startcomponent
Specifies the name of the starting frame or procedure for the called application. The value is the name of the starting component. If not specified, the default starting frame specified in the property sheet for the application is used.
loadmodule
Specifies the directory location of the 3GL load module for the application. For more information about 3GL load modules, see the Programming Guide. If you do not specify this parameter, no 3GL procedures can be called from the called application.
Note: To execute an application that uses another database, use the call system statement.
Call SQL
This statement calls the SQL Terminal Monitor. This statement takes the following parameter:
flags
Specifies the flags that are to be used. The value consists of a list of flags enclosed in single quotes with items separated by blanks or tabs. You can use the following flags: +a|-a, +d|-d, +s|-s.