If it gives you any consolation, I've "Been there, Done that, bought the T
shirt...."
Yes you can get around it..... ADSM stores all of the stuff you put in the
"include" statements in the registry. Therefore, you need to go into REGEDIT
to fix the problem. Perhaps I braver (stupider?) than most, but it was not a
big deal to fix. Here is what I did....
1. Go to the STart button (assuming you are running NT 4; I am not up to
date with 3.51), and select "RUN" from the list. In the dialog box enter
REGEDIT, and hit enter.
2. You should see the Registry Editor show up. Go to "EDIT" on the pull
down list, select it, and from the list, select "FIND".
3. In the Find dialog box, you want to look for the string "ADSM". enter
this, and hit enter. For my machine, the second occurance was the winner -
it was under
HKEY_CURRENT_USER\software\IBM\ADSM\CurrentVersion\AdminClient\ADSM
If you have the correct item, on the right side of the RegEdit box, you
should see a series of keys and values. You didn't say which value was bad,
so I can't help you too much here - how I usually screw myself up is by
getting a date way out of range - forcing it to search for a whole year, etc.
To change the value, highlight the tag you want to change, then go up and
select edit - MODIFY should be available. Select this, and a dialog box will
appear with the old value in it. Simply change the value, and end your
regedit session via the normal EXIT procedure. When you start the Admin
client the next time, the change will be in effect.
******
As I am thinking about this, I remember a bug we have discovered. If I
remember correctly, it was more appropriate to the Admin client under Win95,
rather than NT, though. The problem was that the amount of data retrieved by
some searches caused the video buffers to be blown out - in other words, we
could select all of the data, but we couldn't display it all. Things that
gave us real trouble were things like display the tape pool (where we had
6000+ tapes.) We got around it 2 different ways...... first was trying the
above REGEDIT process - we identified the keywords that in this case needed
to be added (it was a new user, and he had never successfully been able to
set the value in the first place). The other way was to set the monitor to
16 colors - this gave us more area to work with, and prevented us from
blowing the buffers in the first place. We then did the function, set the
limit, and then set the user back to 256 colors. This wasn't pretty, (16
colors), and required a couple of boots to get it straight, but the client
was limited by his administrator - couldn't do a regedit.
We APARed the situation, and if I remember, it was accepted. What we wanted
was the ability to set the scope of the search via the include BEFORE the
first search was performed.
Hope this helps
Jerry Lawson
jlawson AT thehartford DOT com
______________________________ Forward Header __________________________________
Subject: Admin Scheduler Event Filter
Author: INTERNET.OWNERAD at SNADGATE
Date: 10/6/97 10:12 AM
--- Message Part 1.1: Text Body Part ------------------------------
---------------------- Forwarded by Virginia L Hysock/HI/CSC on 10/06/97
---------------------- Forwarded by Virginia L Hysock/HI/CSC on 10/06/97
09:19 AM ---------------------------
09:19 AM ---------------------------
(Embedded image moved to file: PIC17324.PCX)
Virginia L Hysock/HI/CSC
10/06/97 08:47 AM
To: LISTSERV AT VM.MARIST DOT EDU
cc:
Subject: Admin Scheduler Event Filter
Hello,
I have a perplexing problem, and I can't imagine I'm the only one who
has come up against it (if so, it's
pretty embarassing!). I have apparently entered a grossly incorrect filter
in querying the Admin Scheduled
Events gui, hanging my admin client. I am forced to close out the session,
and re-enter. I have attempted
to just let it run out, but it continues to use up all virtual memory on my
NT machine.
I have also tried deleting all events, then querying, but have had the
same result. Any ideas on a filename
where this filter may be stored on my machine - or any other way to change
the filter without first getting into
the screen?
Thanks for any help,
Ginny
--- Message part 1.2: PCDATA --------------------------------------
==> Message part 1.2 is a PCDATA file that has been sent separately.
==> Message part 1.2 is a PCDATA file that has been sent separately.
==> Subject: Admin Scheduler Event Filter
==> Document Name: PIC17324.PCX
|
