ADSM-L

Re: Central Logging of Client

1996-03-19 08:59:18
Subject: Re: Central Logging of Client
From: Bob Douglas <bob.douglas AT COMPUTING-SERVICES.OXFORD.AC DOT UK>
Date: Tue, 19 Mar 1996 13:59:18 +0000
>ADSM Development is looking into a design for centralized logging of client
>errors so they could be queried by administrators, and we would like to get
>some customer input to the design.  The initial requirement is for
>centralized logging pertaining to scheduled commands with potential to expand
>that to all ADSM client commands, whether scheduled or not.  We're interested
>in hearing what you would like to see reported from the clients to the server
>and what type of queries would be the most valuable to you.  We would also
>appreciate any other input you would like to provide to help make this design
>as crisp as possible.  Thank you very much.
>
>ADSM Development:
>  Bonnie Vining  dancer AT vnet.ibm DOT com
>  Don Warren     dwarren AT vnet.ibm DOT com
>

Since restriction to central logging of client information related
to scheduled commands is only the initial phase of the enhancement,
I ignore this restriction below.

As background, we run a heterogeneous network with a central server
providing facilities to many (thousands) of independent clients.
Client administrators run their client systems with no reference
to central server administrators (apart from when they encounter
problems within ADSM).

(1) Client logging to server

    The version of ADSM client software in use.

    Any Error or Severe Error category messages; optionally, any
    Warning category messages; if an option to log Information
    category messages centrally is provided, it must be possible
    to suppress this.

    Failure messages that could not be reported on the client.
    An example of such a failure (which we have seen) would be
    the partition filling which holds a client's dsmsched.log
    file.

(2) Client queries available to the server

    The client operating system version. For example, it is
    useful to be able to find out (without asking the client
    administrator) whether a client is running Windows 3.1
    or Windows 95 (or Solaris 2.4 or 2.5, etc, etc).

    Similarly the ADSM version in use.

    To list or display client configuration files: dsm.sys,
    dsm.opt, incl.excl, preferences file.

    To list or display client log files (dsmsched.log and
    dsmerror.log), with (at least) begindate/begintime and
    enddate/endtime options.

Regards,
Bob Douglas
<Prev in Thread] Current Thread [Next in Thread>