UBE Performance ' SQL Package Location

Once the Table Conversions are completed, change the jde.ini setting on the Enterprise Server that controls where SQL Packages are created. The applicable setting is:

[DB SYSTEM SETTINGS]
sqlPackageLibrary=value

where value controls the location where JD Edwards EnterpriseOne will place SQL packages on your IBM i-based Enterprise Server.

This is shipped with a value of 2 in order for Table Conversions to work correctly. You must change this value to 0 or 1 otherwise you will see a negative performance impact on UBEs. Values are listed in this table:

Value	Action
0	Indicates the system to create packages in the library defined in this jde.ini section: [INSTALL] DefaultSystem=e1_system where for JD Edwards EnterpriseOne Release 9.2 the default value for `e1_system` is E920SYS.
1	Indicates the system will create packages in QRECOVERY and that UBE packages will be named Rnnnnn. Caution: You will need to delete any old UBE SQL packages in QRECOVERY. Please note that no UBEs can be running on the server while you are deleting these packages.
2	Indicates the system will create packages in QRECOVERY and that UBEs are assigned unique names (job number). For example, a UBE name will be in the format T123456. Note: You can use this setting for normal daily operations. However it will make the startup for your frequently run UBEs a little slower as they will not be able to use existing SQL packages.

Value

Action

Indicates the system to create packages in the library defined in this jde.ini section:

[INSTALL] 
DefaultSystem=e1_system

where for JD Edwards EnterpriseOne Release 9.2 the default value for e1_system is E920SYS.

Indicates the system will create packages in QRECOVERY and that UBE packages will be named Rnnnnn.

Caution: You will need to delete any old UBE SQL packages in QRECOVERY. Please note that no UBEs can be running on the server while you are deleting these packages.

Indicates the system will create packages in QRECOVERY and that UBEs are assigned unique names (job number). For example, a UBE name will be in the format T123456.

Note: You can use this setting for normal daily operations. However it will make the startup for your frequently run UBEs a little slower as they will not be able to use existing SQL packages.