Paul,
I experienced this as well, but attributed it to running the v3 clients against
a v2 server.  Apparently that is not the case.  Just to note, in addition to the
NT4 clients, I experienced this on Netware and now it appears Unix as well.   I
circumvented the problem by switching the schedule mode from server prompting to
client polling.  Once this was done, things have been running normally.

Steve Fletcher
Giant of Maryland, Inc.




Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

To:   ADSM-L AT VM.MARIST DOT EDU
cc:    (bcc: Steve Fletcher/GIANTMD/US/Ahold)
Subject:  ADSM V3 Client Problems with Scheduler Service




We have installed ADSM V3.1.0.7 client on a number of NT4 machines but we
are having problems with Server Prompted backups.  We currently have as live
an MVS V2 ADSM server.  However, the problem also occurs using our test ADSM
V3.1 level 30 MVS server.  The MVS ADSM server shows message "ANR2561I
Schedule prompter contacting TOMP01 (session xxxx) to start a scheduled
operation".  This message is repeated every 40 seconds.  On the NT4 client
DSMSCHED.LOG we see the message "TCP/IP accepted connection from server"
repeated at the intervals.  When the ADSM Central Scheduler Service is
re-cycled on the NT4 client machine, the backup "bursts into life"!!
However, when the next backup window starts we again have the problem until
the Scheduler Service is re-cycled again.

I have been speaking to the UK IBM Support Centre but noone else has
reported this problem to them.

We are using Interlink TCP/IP.

What are we doing wrong?  Does anyone have any ideas?  This is holding up
our conversion to ADSM V3 clients for NT.  We do not have any problem with
NT4 ADSM V2 clients.  We have re-installed the ADSM Scheduler Service code.

Paul Tomes
TSG
Abbey Life Assurance
Tel ++44-1202-407568