Information Server site has its own MRI parameter file. Another MRI parameter file is for requests from remote systems. Usually, you do not use the default configuration values.
Although you can edit the parameter file and add the appropriate parameter values, it is more convenient and safer to use MRIDBA to create entries in the local or remote parameter files. SeeConfiguration Parameter Descriptionsfor a
description of each of the possible parameters included in a parameter file. To set up a local or a remote parameter file
1. After executing mridba from the command line, on the DBA Menu, tab to Set up MRI files and press NumEnter.
2. On the MRI files menu, tab to Set up local parameter file or Set up remote parameter file and press NumEnter. 3. The system retrieves the appropriate parameter file and displays the Set up parameter file menu.
4. Fill in the fields as follows:
Default database Windows Server ⇒⇒⇒⇒ ⇒⇒⇒⇒
(Optional) Type the default database for MRI access. If you configure a default database for MRI, it must also be registered through MRIDBA in the Network Configuration report (1C2).
⇐ ⇐⇐
⇐ ⇐⇐⇐⇐ Windows Server 2200 ⇒⇒⇒⇒ ⇒⇒⇒⇒
(Optional) Type the default database for MRI access. If you configure a default database for MRI, it must also be registered through MRIDBA in the Network Configuration report (1C202).
⇐ ⇐⇐
⇐ ⇐⇐⇐⇐ 2200
Maximum users per database Enter the maximum number of active MRI users allowed per database name for your site. The default is 10.
Maximum users per system Enter the maximum number of active MRI users allowed per system for your site. This value should equal or exceed the maximum active users per database parameter. The default is 50. It is not recommended that this number exceed 200, as doing so could cut into system resources, which may lead to undesired results.
Maximum active databases Enter the maximum number of active MRI database names for your site. The default is 10.
UNIX OS Windows Client Windows Server ⇒⇒ ⇒⇒⇒⇒⇒⇒
Local/remote MRI access? If you are setting up a local file, type Y to allow users on your site to access MRI. If you are setting up a remote file, type Y to allow users on remote systems to access MRI. Typing N prevents users from accessing MRI on both local and remote systems. Oracle SID (Optional) Type the default Oracle database system
Oracle DLL (Optional) Enter the specific Oracle dynamically linked library (DLL) for the Oracle level installed on your system. MRI currently looks for oci.dll. MS SQL DLL (Optional) Enter the specific MS SQL dynamically
linked library (DLL) for the MS SQL level installed on your system. MRI currently looks for NTWDBLIB.dll. Sybase DLL (Optional) Enter the specific Sybase dynamically
linked library (DLL) for the Sybase level installed on your system. MRI currently looks for LIBSYB.dll.
⇐ ⇐ ⇐
⇐ ⇐⇐⇐⇐ UNIX OS Windows Client Windows Server Windows Server ⇒⇒ ⇒⇒⇒⇒⇒⇒
UDL Location Enter the directory location of the UDL files if different than the default location. The default location is system drive:\program files\common files\system\ole db\data links\.
Maximum ODBC disconnects before MRIM restarts
(Optional) For local databases, enter the maximum number of allowed disconnects before MRIM restarts. Once the number of disconnects exceeds this value, the pooled MRIM frees all of its resources, restarts itself, and exits. Exiting is the only way to get rid of the driver memory leaks that accumulate with every disconnect when one of a few specific versions of some ODBC drivers are being used. SeeConfiguring Database Access Connection Poolingfor additional information about pooled MRIMs.
For example, if you set this value to 125 and you connect to MRI from an Access database through an ODBC driver, each prestarted MRIM accumulates 1 MB of lost memory before exiting the system. If the ODBC driver is for a FoxPro or DBase database, the accumulated memory loss is 0.5 MB.
The default is 0. Maximum ODBC connections to
keep open (Optional)
For a local database, enter the maximum number of unique ODBC connections (restarted or pooled MRIMs) to keep open. Keeping multiple ODBC connections open provides the following benefits:
• Improves system performance.
• Reduces memory loss if your ODBC driver has a memory leak on connect/disconnect cycles (for example, Access, FoxPro, or DBase databases).
Because your system can lose available memory each time ODBC disconnects from a database, you should minimize the number of times you connect and disconnect from an ODBC data source. For example, one version of the Microsoft Access ODBC Driver loses 8 K of memory each time you
disconnect. The ODBC DSN, user-id, and password are compared to determine unique database connections.
You can specify 0 to 20 open connections. The default is 0.
Disconnect Pooled ODBC Connection if ODBC Error occurs?
To mark a pooled ODBC connection to disconnect when an error occurs, enter Y in this field. The actual connection will not be disconnected until an @LGF is executed on this data source. Enter N if the connection should remain open regardless of what type of error is returned from the ODBC driver.
The default is N. Justification for A, F, and I variables
on the @SQL command.
This parameter sets the justification of numeric data fetched into A, F, and I type Business Information Server variables via the @SQL command.
• R = Right justify data.
• N = No change to the justification.
• L = Left Justify the data. The default is N.
⇐ ⇐ ⇐
Creating Storage Space
UNIX OS Windows Client Windows Server ⇒⇒⇒⇒ ⇒⇒⇒⇒Use the Create storage space menu on the DBA Menu to create storage or table space. To create a storage space
1. After executing mridba from the command line, on the DBA Menu, tab to Create storage space and press NumEnter.
The Create storage space menu appears.
Create storage space Enter the following information.
Database Name -> Database user-id -> Password -> Storage Space ->
Place cursor here and press NumEnter ->
2. To create storage or table space, fill in the fields as follows and press NumEnter. Database Name
Type the database in which the storage or table space is to be created. Database User-id
Type a valid database user-id. Password
Type the database password. Storage Space
Type the storage or table space name.
3. Move your cursor to Place cursor here and press NumEnter. Press NumEnter to complete this procedure.
⇐ ⇐ ⇐