If you want to use different optfiles for different sessions, you can
use the 'default' optfile to communicate with your adsm scheduler
server. If you don't use incremental schedules but commands
like "dsmc inc -optfile", you can use different optfiles with scheduled
sessions.

In Windows 3.1 adsm scheduler is not really a service, daemon or
whatever you call it, but a foreground user program. This might
explain some differences.

I'm afraid I don't have a better idea.