Kbase 16501: Report Builder V7 vs V8 - .pf's, .ini's, and -Mm
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
8/21/2003 |
|
Status: Verified
FACT(s) (Environment):
Progress 7.x
FACT(s) (Environment):
Progress 8.x
SYMPTOM(s):
Report Builder
Trying to specify startup parameters
Unable to find server with protocol "TCP" in /etc/services. (777)
Server has -Mm parm <size> and client has <size>. They must match. (1150)
CAUSE:
Problems can occur due to incorrect location of start-up parameters
FIX:
Version 7.x:
In version 7.x, Report Builder does not read command line parameters. It does not read start-up parameters from an icon that is either used to start Progress or start Report Builder directly. It also does not read start-up parameters from a 4GL call to run Report Builder (prorb.exe).
Version 7.x Report Builder reads from and writes to an initialization file that must be called "Progress.ini". It uses standard Progress search rules to locate the .ini file (looks first in the working directory, then Windows directory, then DLC/BIN, then your path).
Progress, including Report Builder Version 7.3c and later, reads from the Startup.pf parameter file located by default in c:\DLC. You might change the name and/or location of this file by creating an environmental variable (PROSTARTUP) and include it in the [Startup] section of the Progress.ini file.
Do not set the variable at the DOS level because it is then ignored by Progress (Progress first looks to the .ini file). If PROSTARTUP is not defined in the .ini file, it is taken to be the default.
A Version 7.x Report Builder bug occurs when database connection parameters are used in the Startup.pf. Doing so might cause the following error:
unable to find server demosv1 in /etc./services (777).
Even though the bug is fixed in Version 8.x, it is still not recommended to put database connection parameters in Startup.pf.
It is important to keep track of what .ini file and .pf files are being used by each part of Progress. Because Report Builder is a separate executable, it might use a different .ini file.
For example, you might specify one .ini on the command line that invokes Progress. However, Report Builder continues to use the default Progress.ini because it does not read command line parameters.
There is a special case involving the Message Buffer Size parameter (-Mm):
This is a session-wide parameter and not a database connection parameter. The client and the server must have matching values for -Mm. This parameter can be specified in Startup.pf.
In version 7.x, you can also specify this value in the [ReportBuilderDefaults] section of the Progress.ini. To do this, create a line called EngineParameters.
For example:
EngineParameters=-Mm 512.
Version 8.x:
In version 8.x, Report Builder does read parameters from the command line of the icon or 4GL command to run. However, it still does not read from the command line for the Progress icon (_prowin.exe).
This means it is possible to specify an .ini file for Report Builder to use by specifying -ininame on the Report Builder icon.
In Version 8.x, there is an additional environment variable (RBSTARTUP) that defines a file that holds optional parameters that only Report Builder reads from. By default, this file is called rbstart.pf and is located in C:\DLC.
Report Builder automatically searches that location for the rbstart.pf file at start-up. If RBSTARTUP is not defined in the Progress.ini, Report Builder searches for the default rbstart.pf.
Report Builder reads parameters from both the rbstart.pf and the startup.pf and puts them together. Therefore, parameters can be specified in either place. It is also possible to specify another parameter file to read from within any parameter file currently being read by using (-pf) in your list of parameters.
(Do not specify Report Engine-specific parameters in the startup.pf because these are not understood by the rest of Progress.)
In Version 8.x, Report Builder no longer reads the EngineParameter line in the ReportBuilderDefaults section of the Progress.ini. Instead, -Mm can be specified in any of the parameter files that Report Builder reads. It can also be specified on the Report Builder command line.
If you get the following message:
.Error 1150, server and client -Mm do not match
make sure you know exactly what .ini and .pf files are being read. The last value read overrides a previously specified value if they are for the same parameter. The message means the values are in conflict with each other.
One sure way to avoid this conflict is to specify -Mm in the Startup.pf. In this way, everything is sure to have the same -Mm value.
Since -Mm is not a database connection parameter, do not include it in the Other Connect Statement Parameters box of the database connection dialog box..