ADSM-L

Re: Reply to questions

1994-11-21 17:18:40
Subject: Re: Reply to questions
From: Leonard Boyle <SNOLEN AT VM.SAS DOT COM>
Date: Mon, 21 Nov 1994 17:18:40 EST
On Wed, 16 Nov 1994 13:33:01 PST "Brett Walker (408)256-0265 Fax:" said:
>Re: Note from you attached below
>
>
>Currently the GUI's don't work this way; however, we are looking at
>ways of re-vamping the directory tree dialog, and this is one of the
>many things we're looking at (including selecting an entire sub-tree
>easily).
>
>Brett Walker
>ADSM Client Development

Brett

It is good news that you are looking at improving the gui interface.
I have another request in this general area.

Currently if one uses the line mode client, one gets volumes of information
about the job. But if one uses the gui interface one gets one line with a
status of saved, failed or marked inactive. One does not get any detail
on why a failure occured or stats on the job. With the mac client you
also have to be watching the screen - because you can not scroll back to
see any status messages that scrolled off the top of the window.

1) Could the gui interface include the full information provided with the
   line-mode client. Now you might not want to include this by default.
   But either have an option before the run or better yet, Always
   save the data and give the end-user an option to view the more detailed
   log. Maybe write the data to a file and use a local system editor to view
   the data. The site could configure the editor or view used locally.

2) Create an option or command to allow one to save the information from
   a gui session into a file.

3) Create an option that reports on the objects other then files that are
   saved.


Currently if someone uses the gui interface and all goes well then  no
problem. But if there is something that is not quite right, there is no
easy way for the user to save the data for an analyst to review later.

Some of these problems might not be seen as errors to ADSM, so they would
not be recorded in the error log. For example if one changed the include
statements in a way which caused many files to be marked inactive when one
did not wish to do so.

I also think about another option which is a little more off the wall.
If adsm could transfer the log file up to the server as a final part of
any action, then it could be the basis of automating the monitoring of the
system. Adsm could store the logs away under a virtual node. Since the
files are text then a site could retrieve the files at will to any platform and
process them with a program to generate status and exception reports.
This assumes that adsm would allow the cross platform restores of text files,
Should be doable. And for the 370/390 platforms we would need a adsm client.
Or at least a partial client. With VM this might be easy if the virtual node
was a sfs userid.

Thanks len
-------------------------------------------------------------------------
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
<Prev in Thread] Current Thread [Next in Thread>