At 02:41 PM 1/30/2001, Dave Darnell wrote:
>Chuck,
>
>I'm sure the MiniSoft guys will answer soon,
>
>We noticed that the logon changes when we use MiddleMan and a process is
>spawned in a session with a different logon.  The listener does an
>AIFCHLOGON (sp?) before spawning the process so that the process and session
>will belong to the proper group.account. (MiniSoft- am I getting this
>right?)

Yes, to verify (enforce) security we use AIFCHANGELOGON.  Several years ago
we did this using some parameters which modified the JS table for every
execution.  This was great for debugging.  This lead to many problems at
large production sites.  Especially those with automation tools that could
not find the appropriate job to stop at night for backups.

We have addressed this issue in two ways.

First calls made to AIFCHANGELOGON no longer modify the system JS table. If
this behavior is still seen, then some NMPRG file needs to be
updated.  Please contact us ASAP.

Second, MSJOB can now be controlled from either a Win32 based workstation
or from the MPE command line.  The utility MSJOBCMD will run from a job or
session and either conditionally or unconditionally stop the job or any
single port listener in the job.  MSJOBCMD sets some civars based upon what
action was taken.

<http://www.minisoft.com/middleman/mdmconsl.htm#msjobcmd>

>As far as the DSNs, how about multiple User DSNs with one to few files each
>instead of one monolithic DSN per data source?

"Never say never"

We understand this is an issue to some sites.  We try to address it by
suggesting more DSNs with fewer entries.

neal
800-682-0200
<www.minisoft.com>