Re[2]: WIN 95 ADSM GUI Question

Hello,
I am resending this message as I did not get
a reply stating the message was delivered.


-----------------------------------------------------------------
Rejean Larivee
Rejean Larivee
IBM ADSM Level 2 Support


---------------------- Forwarded by Rejean Larivee/Quebec/IBM on 11/24/98
03:04 PM ---------------------------
03:04 PM ---------------------------


Rejean Larivee
11/24/98 10:30 AM

To:   ADSM-L AT VM.MARIST DOT EDU
cc:
From: Rejean Larivee/Quebec/IBM @ IBMCA
Subject:  Re[2]: WIN 95 ADSM GUI Question


Hello,
you guessed right. The ADSM admin GUI "properties"
are stored on the client machine, not on the adsm server.
These are stored in the registry under.
HKEY_USERS\.Default\Software\IBM\ADSM\CurrentVersion\AdminClient\xxx
where xxx is the ADSM server name.

Since you mentionned you change the include options
for the activity log in the GUI, you would be interested in
the following "value names" :
  alog_fdate     (activity log-from date, aka begindate)
  alog_tdate     (activity log-to date, aka enddate)
  alog_ftime      (activity log-from time, aka begintime)
  alog_ttime      (activity log-to time, aka endtime)

Suppose you changed the begindate and begintime for
the activity log query via the "view/include" menu pull-down to :
   10/24/1998 at 8:58.
then the alog_fdate and alog_ftime "values" would be set
as follow in the registry :
  alog_fdate  10/24/1998
  alog_ftime   08:58
These values would be set as soon as you hit the "INCLUDE"
 or "APPLY" button from  the "Activity Log - Include" window.
Now, if you had let the operation complete normally and if you
had close the GUI "normally", the alog_fdate and alog_ftime
would have been reset to "*". But because, you cancelled the
GUI, the values were not reset and therefore when you clicked
on the "activity log" icon, the alog_fdate an alog_ftime were
pulled from the registry.
Now, you "coud" and I am certainly not saying you "should"
edit the registry and update the values manually before
restarting the ADSM GUI. All you need to do is reset the
values back to "*" for alog_fdate and alog_ftime. The next
time you would start the GUI and click on the "activity log" icon,
it would default to displaying the last hour of activity log.
Again, I do not recommend you edit the registry because
of risk of corruption in the registry. However, if you feel
comfortable with this, the procedure will work.

Good day !

-----------------------------------------------------------------
Rejean Larivee
Rejean Larivee
IBM ADSM Level 2 Support



---------------------- Forwarded by Rejean Larivee/Quebec/IBM on 11/24/98
09:36 AM ---------------------------
09:36 AM ---------------------------


ADSM-L AT VM.MARIST DOT EDU on 11/23/98 05:58:09 PM

Please respond to ADSM-L AT VM.MARIST DOT EDU

To:   ADSM-L AT VM.MARIST DOT EDU
cc:
Subject:  Re[2]: WIN 95 ADSM GUI Question


     I would never have guessed adsm was storing these requests on the
     server.  My thought was that the client was storing the requests in
     some file and that if I found out what the name of that file was I
     could just delete it.
     james.sporer AT doit.wisc DOT edu



______________________________ Reply Separator
_________________________________
Subject: Re: WIN 95 ADSM GUI Question
Author:  "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>  at IPNET
Date:    11/23/98 11:07 AM


I ran into this before also,  I let the command run and finish.  But I was
told that you can delete the ADSM User id on the server.
All the actions for that id would be deleted.  Then create a new user id.

This may be faster if you have the rights to create a new id.







james.sporer AT CCMAIL.ADP.WISC DOT EDU on 11/23/98 10:53:57 AM

Please respond to ADSM-L AT VM.MARIST DOT EDU

To:   ADSM-L AT VM.MARIST DOT EDU
cc:    (bcc: Joe Schilling/BOMC/TIME_INC/US)
Subject:  WIN 95 ADSM GUI Question




     By mistake I requested a huge volume of data from the activity log
     using the gui admin client with the include option.  After waiting a
     couple of minutes for the output I decided to cancel the gui session
     and start over requesting what I actually wanted.  When I click on the
     activity log after restarting it still requests the same data from the
     activity log.  Obviously the activity log request is getting stored
     some place and reexecuting every time I click on activity log.  I even
     went so far as to reinstall the admin gui but couldn't get rid of the
     request.  The only way I was able to get rid of the queued activity
     log command was to let it complete.  Has anybody else run into this
     and is there a way to get rid of that stored command in the GUI?
     james.sporer AT doit.wisc DOT edu