This chapter describes how to run an application that uses Application Server.
Before you can run your application with Application Server, you might need to set up the environment. See the topic To set up AppTrack and the licensing environment in the Help.
Runnable programs can be:
The syntax for invoking a linked system executable file varies slightly from that for invoking a dynamically loadable program and is described later in this chapter.
If there is problem with the application, your application supplier might suggest that you run FaultFinder to produce a report on the problem. See the section FaultFinder in this chapter.
To run a linked executable program, enter the following command line at the command prompt:
program-name [program-params]
where the parameters are:
| program-name | The name of an executable file. If the program-name does not contain an explicit path then the directories specified by the PATH environment variable are searched. |
| program-params | Zero or more parameters that are required by the program. Each parameter is a string, separated from adjoining parameters by one or more spaces. |
To run dynamically loadable programs (that is, callable shared objects, .gnt files or .int files) enter the following command line at the system prompt:
run [switch-param] program-name [program-param]
where the parameters are:
| switch-param | One or more programmable and run-time switches that control events in a program at run time. Your application supplier will tell you which switches to specify. |
| program-name | The name of a dynamically loadable program, which is an .int file, a .gnt file or a callable shared object. If versions of the program exist as an .int file, a .gnt file, or a callable shared object, and you do not specify a filename extension in the run command, then by default, the callable shared object version is run in preference to the .gnt file, and the .gnt file in preference to the .int file. |
| program-param | One or more parameters that are required by the program. Each parameter is a string, separated from adjoining parameters by one or more spaces. |
A run-time system error message is returned on a program that is syntactically correct but that encounters problems during the actual running of the program. For example, you could receive such an error if you try to access a file in the wrong mode or if you use a corrupt file.
If you try to run a program, but the run is not successful, you should be aware that the program counter (pc) values for native code generated files, callable shared objects and system executable files are undefined.
FaultFinder is an aid to debugging production applications. It enables you to obtain a text-based report on the state of an application at the time an application terminates abnormally. The report is a snapshot of the application at the time of failure and identifies items such as open files, file buffers, loaded programs, and so on.
You run FaultFinder when your application supplier requests a FaultFinder report. When you have generated the report, you need to send it to your application supplier for them to interpret.
FaultFinder is controlled by environment variables. To turn on FaultFinder set the environment variable faultfind_level to a positive value. Then, if the application terminates abnormally, the run-time system automatically invokes FaultFinder which in turn generates the report.
The following environment variables control the operation and output of FaultFinder:
| faultfind_level=n | Turns on FaultFinder and enables tracing of events. n can be any positive value less than or equal to 1024 and enables the last n events to be traced. The default value is 0. |
| faultfind_outfile="[>>]"filename | The file to which the analysis is written. If filename contains the string %p, this string is replaced by the process ID of the program that started FaultFinder. The default filename is ffnd_out.%p in the current working directory. If you specify >>, the output is appended to filename, if it already exists, otherwise a new file named filename is created. |
| faultfind_recsize="record_size" | A numeric value that specifies the internal cache size used to store read/write data for the operation traceback log. All read/write data is stored and reported. By using this tunable you might improve performance. The default value is 64 and the maximum is 1024. |
For example
set faultfind_level=5 set faultfind_outfile="applflt.log" set faultfind_recsize=1024
The Consolidated Tracing Facility (CTF) is a tracing infrastructure that enables you to quickly and easily produce diagnostic information detailing the operation of Micro Focus software components.
For more information, see the topic Consolidated Tracing Facility