| My customer has VMS 7.1 with the appropriate DECnet+ 7.1 and also
experiences the problem stated in .0
Of course he was able to workaround the problem, but doesn't find
it very comfortable (problem is known for a long time...and not fixed)
I have looked into 815 - ECO 1 (v 1.3.3) doesn't seem to fix it and
for 1.3.5 you only provided the system image, which obviously also
doesn't fix the problem. It would be nice to have a formal kit, which
can be installed by customers without any workarounds.
The customer also wanted me to let you know, that he would prefer the
way, how DECserver installation is being done. They create an EXTRA
NCL script, where the decserver mop clients are created, while
the wanrouter installation modifies the mop client startup.
When he does a Net$config for some other reason, it easily happens,
that he destroys the client database, if he says yes to the question
"replace ... ncl script", which does not happen for DECservers.
If you need a IPMT for this request, please let me know.
thanks and best regards
eva
|
|
Unfortunatly there is not much we can do about re-engineering the kitinstal
for VMS V7. We just don't have the time or the manpower. We would have
liked to generate a full kit for V1.3.5 but if we waited until we had the
time it might never happen.
� The customer also wanted me to let you know, that he would prefer the
� way, how DECserver installation is being done. They create an EXTRA
� NCL script, where the decserver mop clients are created, while
� the wanrouter installation modifies the mop client startup.
Sounds good. The problem is that the load-host configurator was written
long before DECnet/OSI had this "feature". It would be difficult to change
the load-host configurator (we don't have anyone left to work on it).
� When he does a Net$config for some other reason, it easily happens,
� that he destroys the client database, if he says yes to the question
� "replace ... ncl script", which does not happen for DECservers.
But I thought net$config saved your previous configuration?. If not then
you can restore your WR90 MOP client information using
"@sys$manager:decrou$host_config update network". I think this should
restore all the WR90 clients (you then have to do
@SYS$COMMON:[SYSMGR]NIS$HOST_CONFIG update network to update any DECNIS
system).
Its not fullproof since if you've customized the script you've lost those
changes.
Sorry not much help,
Mark
|