On Wed, 5 Feb 1997 18:05:59 EST Paul Schwartz said:
>The following was an e-mail I received from a technician here trying to install
>the new 2.1.6 version of ADSM for NT.
>If anyone has any thoughts, please let me know:
>
>The biggest problem I've encountered with 2-1-6, so far, is that about 75% of
>the time, the installation doesn't complete correctly. Specifically, it
>doesn't
>complete all necessary modifications of the registry, so that the scheduler
>service isn't startable. This is occurring on what should be virtually
>identical
>HP-LH servers, so I'm mystified as to why it's happening. A manual backup &
>restoration will run, however, so I know that the software itself is sound.
>
>It may be that I can manually complete the entries, and everything will work...
>I'll test this when I have some time. For now, though, I've decided to go
>ahead
>and install the older version, since I know that it works, and we're under the
>gun to get ADSM working in the districts (the local NT backups seem to be
>getting more flakey every day).
>
>
>Thanks,
>Paul Schwartz
>Alliant Foodservice
>71421.1614 AT compuserve DOT com
Hello Paul
I hope IBM is listening and can respond.
I think that we found out a little more about your problem today. I will
put forth my theory, please let us know if this is what you are seeing.
If one is using ptf 5 or 6 and one has the password=generate line in the
dsm.opt file, then the line mode client (dsmc.exe) will store the passwd in
the registry for future use. The updatepw.exe and dsmcsvci.exe will also
store the passwd in the registry.
We found that if we had the nodename parm in the dsm.opt file these two
sets of programs dsmc & (updatepw & dsmcsvci) would agree on where the
password is stored. If the nodename parm is not in the dsm.opt file then
they would not. You could store the passwd in the registry with dsmc
and the dsmc program would use it with no problems. But the showpw.exe
program would show random characters. If one then used the updatepw.exe
program, the showpw command would work. But then the dsmc program would
report a problem with the password. One could let the dsmc program store
it then, but then the showpw command would be messed up. (the showpw
command seems to reflect what the dsmcsvc (scheduler) program requires.
This seems related to but not the same as apar IC16093.
The GUI (dsm.exe) client does not use the stored password so is not
affected by this problem.
We had found that not using the nodename made the install much much easier.
We have found the install procedure of ptf 5 and 6 to be much much better
then the earlier releases.
While trying to work this out we tried the ptf 6 level of the windows32 client.
The problem is that many of our users have audio cd-roms in their
machines. With an audio-cd rom, ptf 6 abends with a divide by zero fault
as reported by Melinda. (apar IC16240).
Both of these bugs make the use( or better said--failure) of adsm
a surprise to the end-user.
I think that these two bugs should be fixed before the 3 month+
window when the next ptf (.7) is due out.
IBM if you can not ( or may not) release ptf .7 for the windows32 client
before the next quarterly window. Can you make these fixes available to us
on a request (could be a test directory on index.storsys.ibm.com) basis?
Thanks len
PS Melinda if you are reading this. Can you post your comment on products
with a high apar rate from your History of VM talk?
-------------------------------------------------------------------------
Leonard Boyle, Mainframe support snolen AT vm.sas DOT com
Leonard Boyle, Mainframe support snolen AT vm.sas DOT com
SAS Institute Inc. ussas4hs@ibmmail
Room E206 (919) 677-8000 ext 6241
203 SAS Campus Drive
Cary NC 27513
|
