thread_name.ini and process_name.ini
All existing thread_name.ini files work as long as no Java UPoCs or another GJD thread is added to the engine process.
thread_name.ini should contain only the "include" directive when a Java UPoC is used in a process that has at least one GJD in the JVM section of process_name.pni. This also applies when there is more than one GJD in the process. If this is not finished and the UPoC code starts before the GJD code, then the UPoC works but the GJD creates an error.
When the thread_name.ini contains the JVM parameters (a single GJD in the process), the class path values can now contain one or more path/*.jar entries.
The process_name.pni should be placed in the site directory. It requires only the JVM section as it is not used by GJD protocol threads. The entries that are defined in the prior version can be used. The class path should contain entries for all GJD protocol drivers that are used in the process. UPoC-specific items are not stated as long as all UPoC class and jar files are located in the java_uccs directories. They are added to the class path by default.
The start directory can be specified; only one can be specified. Its use is the same as in the prior version except that all Java drivers share that one directory. That is, it can be specified using the relative path "dot" format when defining class path entries.