This is a good solution but it does (from my understanding per IBM) require
multiple client connection licenses on the server.  The server will complain if
you register more nodes than it is licensed for.

Chuck Tomlinson 793-0730 wrote:

> Automatic digest processor <LISTSERV AT VM.MARIST DOT EDU>  writes:
> ------------------------------
> >Date:    Fri, 17 Jul 1998 14:20:22 -0500
> >From:    "Clendenny, Ronald D." <rdclendenny AT CAL.AMEREN DOT COM>
> >Subject: Re: Multiple opt files.
> >
> >Along similar lines, I need to run different pre and post commands at
> >different times of day for the same client.  Since the pre and post
> >commands are in the dsm.sys file, of which there is only one.  How can
> >this be done?
> >
> >Ron Clendenny
> >Callaway Nuclear Plant
> >Fulton, Missouri
> ><rdclendenny AT cal.ameren DOT com>
>
> Well I did not see a response to this yet so I will take a shot at it.  Since
> you are using the dsm.sys file I assume that this is a unix system.  I sure
> you have found out that the dsm.sys/dsm.opt is read only when the scheduler
> daemon is started.  One thing that I have done was to create multiple server
> stanzas in the dsm.sys file for the same ADSM server.  Each server stanza
> could have a different pre/post command.  Then you run multiple 'dsmc sched'
> process (one for each stanza).   When I did this I also gave each scheduler
> daemon a different node name.  That may not work for you but this might point
> in the right direction.  Here is an example:
>
> dsm.sys:
> DEFAULTserver Main1
> SErvername Main1
>         TCPS            adsmserver.domain.com
>         TCPPort         1500
>         TCPCLIENTPort   1501
>         ....
>         ....
>         PRESCHECDULECMD precmd1.sh
>         POSTSCHEDULECMD postcmd1.sh
> SErvername SameSrv2
>         TCPS            adsmserver.domain.com
>         TCPPort         1500
>         TCPCLIENTPort   1502
>         ....
>         ....
>         PRESCHECDULECMD precmd2.sh
>         POSTSCHEDULECMD postcmd2.sh
> SErvername SameSrv3
>         TCPS            adsmserver.domain.com
>         TCPPort         1500
>         TCPCLIENTPort   1503
>         ....
>         ....
>         PRESCHECDULECMD precmd3.sh
>         POSTSCHEDULECMD postcmd3.sh
>
> Well you get the idea.  I even went as far as to assign each stanza a
> different SCHEDLOGname so that I could log each one separately.  As mentioned
> before, I used different NODENAME's for each stanza and set them here as well.
>
> You then create multiple dsm.opt files.  Then when starting the scheduler
> daemon just set the environment variable DSM_CONFIG to the location of the
> dsm.opt file to use.  Example:
>
> dsm_1.opt:
> SErvername Main1
>         ...
>         ...
>
> dsm_2.opt:
> SErvername SameSrv2
>         ...
>         ...
>
> dsm_3.opt:
> SErvername SameSrv3
>         ...
>         ...
>
> In Kron shell you can just do the following to start the scheduler daemon (we
> will assume that the dsm.sys and all the dsm*.opt files are in
> /usr/lpp/adsm/bin directory).
> export DSM_CONFIG=/usr/lpp/adsm/bin/dsm_1.opt ; dsmc sched
> export DSM_CONFIG=/usr/lpp/adsm/bin/dsm_2.opt ; dsmc sched
> export DSM_CONFIG=/usr/lpp/adsm/bin/dsm_3.opt ; dsmc sched
>
> I originally did this on an AIX system that had 4 Lotus Notes servers running
> on it and had to back each one up separately because it was an HA environment.
> But that is a different story....
>
> Chuck T.
> ----------------------------------------------------------------
> Disclaimer: These are my views and not those of my employer.
>
>  Charles (Chuck) N. Tomlinson               IBM Global Services, Austin, Texas
>  Phone: (512) 823-0730  Tie Line: 793-073   Storage Management Division
>  http://w3.austin.ibm.com/~chuckt           Email: chuckt AT austin.ibm DOT 
> com



--
Steffan Rhoads
Steffan Rhoads
Lead Technical Consultant
Think Enterprise Solutions
10 Holland
Irvine, California  92618-2504
srhoads AT westernmicro DOT com