JD Edwards EnterpriseOne Initialization for Windows

This initialization occurs when you start JD Edwards EnterpriseOne programs such as queue kernel, runbatch, and so on:

• The environment is passed as a command line argument to the program (such as porttest, queue kernel) or retrieved by jdenet_k from the QEnv key in the [NETWORK QUEUE SETTINGS] section of the JDE.INI file.

• This environment might be translated to a different environment, based on the settings in the [SERVER ENVIRONMENT MAP] section of the JDE.INI file.

• The environment that is used must be a valid entry in the Library ListMaster File table (F0094) and must have a valid corresponding path code in the Environment Detail - OneWorld table (F00941).

• These JDE.INI settings in the [DB SYSTEM SETTINGS] section specify where the JD Edwards EnterpriseOne server startup tables, such as the Data Source Master (F98611) and Object Configuration Master (F986101) tables, are located:

  • Base Datasource

  • Object Owner

  • Server

  • Database

  • Load Library

  • Type

• Using this information, the F986101 table opens in the specified database on the server.

• When an override exists for a given table, BSFN, or the current user, that data source (OMDATP field in the F986101 table) is used for the given object or user and environment. Otherwise, the data source in which OMOBNM=DEFAULT for the given environment is used. Ignore any inactive records (that is, OMSTSO=NA). We strongly recommend that you do not have any default records (OMOBNM=DEFAULT) for batch applications (OMFUNO=UBE). These records might prevent report interconnections (such as one report calling another report) from starting correctly.

• Each unique data source in the F986101 table should correspond to one entry in the F98611 table.

• The corresponding information in the F98611 table must be correct. In particular, the OMDLLNAME field must display the correct DLL for the database to which the data source points.

• For an Oracle database, the OMDATB field from the F98611 table maps to an entry in the tnsnames.ora file. This tnsnames.ora file must be set up correctly (check with an Oracle database administrator).

• For an DB2 for Linux, UNIX, and Windows database database, the OMDATB field from the F98611 table maps to an entry in the ODBC data source. This datasource must be set up correctly (check with a DB2 for Linux, UNIX, and Windows database database administrator).

• For a Microsoft SQL Server, Microsoft Access, or Client Access database, the OMDATB field from the F98611 table maps to a data source specified in the ODBC Data Source Administrator applet in the Windows Control Panel. This data source must be set up correctly. If multiple users plan to sign on to this Windows platform and run JD Edwards EnterpriseOne or PORTTEST, the data sources must be defined on the System DSN tab. Otherwise, User Data Sources can be used.

  If you are using Microsoft Windows 2000 to open the ODBC Data Source Administrator, from the Start menu, select Programs, then Administrative Tools, and then Data Sources (ODBC).

• This information pertains to the setup of SQL Server ODBC drivers, using the ODBC Data Source Administrator applet:

  • The data source name must match the name in the F98611 table.

  • The description can be anything that you want.

  • The server is the name of the database server.

  • The network address includes the database server name, a comma, and a port in which the database user listens.

  • Network Library should be set to Default.

  • Click the Options button for more settings.

  • The database name is usually set to JDE. You can set it to Default.

  • The language name should be set to Default.

  • The Generate Stored Procedure for Prepared Statement option should be turned off.

  • The Use ANSI Quoted Identifiers option should be turned on.

  • The Use ANSI Nulls, Padding and Warnings option should be turned on.

  • The Convert OEM to ANSI characters option should be turned off.

• This information pertains to the setup of Client Access ODBC drivers, using the ODBC Data Source Administrator applet:

  • On the General tab the data source name must match the name in the F98611 table. The system is the name of the database server.

  • On the Server tab, the default libraries should be the IBM i library, and the commit mode should be Commit immediate (*NONE).

  • On the Format tab, the naming convention should be System naming convention (*SYS).

  • On the Other tab, if the data that you are transferring using this data source contains a Binary Large Object (BLOB), translation should be set to Do not translate CCSID 65535. If the data that you are transferring using this data source does not contain a BLOB, translation should be set to Translate CCSID 65535.