Am actually taking a different angle to try to get this to work.

Apparently, the JDBC.pod has documentation on starting the server It says the below

"Place the dbd_jdbc.jar file, log4j-1.2.13.jar, and your database's JDBC driver on the machine where you wish to run the server.

=item 2

Add dbd_jdbc.jar, log4j-1.2.13.jar, a log4j.properties file, and your database's JDBC driver to your classpath. Follow any other instructions which came with your JDBC driver. For example, a type 2 JDBC driver may require that the database's native libraries be added to your path or library path."

So - my class path is C:\jars

And, in my class path do I have the dbd_jdbc.jar? Yes, I have that file. Do I have the log4j-1.2.13.jar? File log4j-1.2.13.jar? Yes, I do have that file. The last item, do I have the JDBC driver? That, I do not know - so, at this point, I need to look into the JDBC driver next.

Another source I found stated:

"No, the error you’re encountering specifically mentions the org.apache.logging.log4j.LogManager class, which is part of Log4j 2.x. If you’re using Log4j 1.x, it won’t contain this class. Make sure to use a Log4j 2.x version and include the corresponding JAR file in your project."

So - will look into this Log4j 2.x version

Well, some good news(well crossing my fingers at least), I ensured that the following jar files in the log4j-1.2.13.jar, log4j-core-2.17.1.jar, log4j-api-2.17.1.jar, and log4j2.properties in the jars folder, which is the CLASSPATH, then when I ran "java -Djdbc.drivers=foo.bar.Driver -Ddbd.port=12345 com.vizdom.dbd.jdbc.Server" It did not error out.

The Teradatadriver is terajdbc4.jar - which I have on my C:\jars folder. Which makes sense I have, because I can connect to JDBC with Teradata using Java as a programming language fine - so, I must have had the driver to do that. So, need to explore more the JDBC.pod documentation.