ADSM-L

Re: Client ver 3.7.2 - no SA software

2000-11-15 10:03:33
Subject: Re: Client ver 3.7.2 - no SA software
From: Zoltan Forray/AC/VCU <zforray AT VCU DOT EDU>
Date: Wed, 15 Nov 2000 09:20:11 -0500
I guess I should have clarified my environment.

This is OS/390 2.5.  There is no dsmaccnt.log.

And as I mentioned to Maria, I am not going through a proxy. I go directly
to the OS/390 box.




                    "France, Don G
                    (Pace)"               To:     ADSM-L AT VM.MARIST DOT EDU
                    <don.france-ed        cc:
                    s AT EDS DOT COM>            Subject:     Re: Client ver 
3.7.2 - no SA software
                    Sent by:
                    "ADSM: Dist
                    Stor Manager"
                    <ADSM-L AT VM DOT MAR
                    IST.EDU>


                    11/15/00 01:20
                    AM
                    Please respond
                    to "ADSM: Dist
                    Stor Manager"






Yep... we see the same phenomenon for some customer environments.  Maria's
suggestion may fix your browser-admin experience.

Just a suggestion, though - sounds like you're wanting to do some "more
than
casual" administering - so, I recommend a couple things:  (a) use the
dsmaccnt.log file to extract the 4961 info (and other session stats) and/or
(b) use the admin command-line interface and run server scripts or macros
to
accomplish frequently-repeated tasks... some folks run shell scripts which
perform daily queries using dsmadmc and store the results in a flat file
which might then be displayed via an internal web page.


Don France

Technical Architect - Unix Engineering/P.A.C.E.
San Jose, CA
mailto:dfrance AT pacbell DOT net
PACE - http://www.pacepros.com
Bus-Ph:   (408) 257-3037


 -----Original Message-----
From:   Maria Paz Gimeno [mailto:mpgimeno AT IBERCOM DOT ES]
Sent:   Friday, November 10, 2000 3:42 AM
To:     ADSM-L AT VM.MARIST DOT EDU
Subject:        RV:      Re: Client ver 3.7.2 - no SA software

The problem with speed in the admin web interface could be related to your
proxy,
if you have one.
We have a similar problem in a customer, the administrative web interface
was very slow,
and when we removed for the TSM server address to go thought the proxy,
the response time was much much faster.
It is just one idea
Regards
Maria

<Prev in Thread] Current Thread [Next in Thread>