For those of you using the Minisoft ODBC driver.

I have noticed something strange with the listener job. It is streamed as
MSJOB,MGR.MINISOFT and this is how the job name shows up in the showjob
listing. Then, after the listener has been running for a time, the job name
will change to MANAGER.SYS.

Has anyone else seen this?

Also, I recently spoke with tech support at Minisoft about the way their
driver opens every file listed in your DSN when your client application
connects. If any of the files listed in the DSN are not present, say a text
file that is created by a nightly job that crashed, then the connection will
fail even if you do not reference the missing file. The tech responding with
"how else would we do it"?

To me this seems like alot of overhead, especially if your app is stateless
and reconnects for every data access. I now must create multiple DSN's, so
that a missing file does not prevent all connections, which can require an
app to perform multiple connects and again increase overhead.

Am I wrong in thinking that the files should not be opened until they are
first referenced? Just curious as I am sure Minisoft will not change this.