Kristina,
I,ve seen this happen before, here it concerned a Novell client
(V3105/6) communicating with a version V3.1.?.5 ADSM NT server.
I was experiencing the exact same problem, I couldn't get the client
into prompted mode. I reported the problem to IBM, after which I made
a trace. IBM came back with an answer. Your server was surely set to
polling mode only, because thats what the trace told them. This was
not true and had to convince them otherwise.
After some diddling with the DSM.OPT settings I found out I could get
the client in prompted mode if I set the SCHEDMODE PROMPTED setting
before any other SCHED?????? setting (like SCHEDLOGNAME etc..).
I reported this to IBM, heard nothing for a time, in the mean time
migrated to a higher server level (NT ADSM V3.1.2.13) and now coming
to the climax ... the problem has .... you guessed it, gone.
In conclusion that the new server software had solved the problem I
closed the problem report with IBM.
hope this will help a bit,
regards, Walter Ridderhof
______________________________ Reply Separator _________________________________
Subject: Betr: The SCHEDMODE option?
Author: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> at inet-1
Date: 3/23/99 6:37 AM
The prompted schedmode isn't always available. It depends on the
COMMMethod you're using. If you're using shared memory then all the
client can do is go into polling mode. The client will tell you this
in the shcedule log file. I've only seen the prompted schedule work if
TCP/IP is used. Look in the schedule log file of the client. If the
server forces on prompted scheduling mode and the client can't comply
it will say so in the output.
Prompted scheduling mode isn't available with a v3 client and a v2
server regardsless of the communication method.
Another reason can be that the option is put in the wrong option file.
The schedmode option has to bo placed in the dsm.sys file and not the
dsm.opt file
Regards,
Maarten Doeswijk
____________________________ Antwoord-separator ________________________________
Onderwerp: The SCHEDMODE option?
Auteur: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> in inet-1
Datum: 22-3-99 15:59
I have a problem with options in ADSM on AIX. There's an option that
decides if the clients are to use
polling or promted mode whith the ADSM scheduler (SCHEDMODE).
Default mode is polling, and if you set schedmode on the AIX client (in the
dsm.sys file) to promted and has the same
mode on the server the scheduler function stops working on AIX. This
function works just fine with Windows NT cilents though.
The problem I have on AIX clients is that when the server and the client
both are set to schedmode promted - the client doesn't recieve a schedule
from the ADSM server, and the adsm_sched.log tells that the ADSM server
does not support polling.
According to the ADSM documentetation both of these options should be
possible to apply on any of my platforms;
eg both NT AS/400 and AIX.
At the moment the only way to get the scheduler to work on the AIX clients
is to let them have polling schedmode.
So I had to set the options on the server to any so that the NT clients
could continue with promtede mode.
The question is : Has anyone seen this before and could give me a hint??
My qustomer's wish is that all clients should run in promted mode so
the server has full control over the ADSM clients
Thanks
Hälsningar/Regards
Kristina Ahlström
Systemteknik/Systems Engineer
----------------------------------------------------
Rowika AB, F O Petersons gata 9, SE - 421 31 Västra Frölunda Rowika AB, F O
Petersons gata 9, SE - 421 31 Västra Frölunda
mailto:kristina.ahlstrom AT rowika DOT se
Tel: +46 31 709 82 30 Fax: +46 31 709 45 45
Internet: http://www.rowika.se
|
