Tom,
   may be my description of the problem was too short, so I'll try to
explain it in more deatil but I'll refer to my numbered steps in my former 
message.


On Wed, 21 May 1997, Tom Brooks wrote:
>  Could you provide more a specific message for "scheduler has been stopped"?

As of step 1 You can see that its dealing with CLIENTS on HP-UX 9.05
systems. 
There is no evidence in the server's ACTLOG about any ANSnnnn-message as
You can see from today's happening "Scheduler has been stopped" 
(not on the "rzhp735b" but on the "rzbcosv2". I was unlucky not having 
chosen the 98% failing rzbcosv2-machine as an example but the 75% failing
rzhp735b ).

adsm> q actlog begint=13:00 s=rzbcosv2

Date/Time            Message                                                   
------------------------------------------------------------------------------
---
21.05.1997 13:25:21  ANR2561I Schedule prompter contacting  
RZBCOSV2(sessio21.05.1997 13:25:21  ANR2561I Schedule prompter contacting  
RZBCOSV2(session   
                      3447) to start a scheduled operation.                    
21.05.1997 13:25:23  ANR0400I Session 3448 started for node RZBCOSV2(HPUX).   
21.05.1997 13:25:25  ANR0403I Session 3448 ended for node RZBCOSV2 (HPUX).     
21.05.1997 13:25:25  ANR0400I Session 3449 started for node RZBCOSV2(HPUX).   
21.05.1997 13:25:26  ANR0480W Session 3449 for node RZBCOSV2 (HPUX)terminated 
                      - connection with client severed.                        
21.05.1997 14:39:35  ANR0400I Session 3456 started for node RZBCOSV2(HPUX).   
21.05.1997 14:39:38  ANR0403I Session 3456 ended for node RZBCOSV2 (HPUX).     

> Without the ANRnnnn or ANSnnnn it is not clear if this message is from the
> client or server side. Please provide the exact message text also. Did
> this occur during server initialization?

So I draw the conclusion, that it has nothing to do with server
initialization. The 2 lines ( time-stamped 14:39:.. are due to a restart
on the rzbcosv2 done via
        nohup /usr/adsm/dsmc sched -quiet

The message text is just as it is at the end of my step 2, i.e. a plain
time-stamped
"19.05.1997 17:15:02 Scheduler has been stopped "
in the DSMSCHED.LOG-file

>
> Tom Brooks
> ADSM Development
> 

Hope this helps clarifying matters.

-- 
MfG / Ciao         - - - - - - - - - - - - - - - - - - - - - - - - - - - -
MfG / Ciao         - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Peter Dümpert                                   Email: p.duempert AT tu-bs DOT 
de
Rechenzentrum der Technischen Universität       Fax  : ++49/531/391-5549
D 38092 Braunschweig                            Tel  : ++49/531/391-5535