Just a word of caution on output redirection of administrative
commands.... IBM has changed the format between maintenance releases (on
MVS at least, don't know about AIX, etc.)... very frustrating when you
do some post-processing on these redirected files. On more than 1
occasion I've put maintenance on the ADSM server only to find the format
of a report has changed from column oriented to 1 field per line or vice
versa.  I haven't put any maintenance on our Version 2 server so can't
say if this problem still exists....

Tim Pittson
tpittson AT himail.hcc DOT com

>----------
>From:  Dwight Cook[SMTP:decook AT AMOCO DOT COM]
>Sent:  Monday, May 06, 1996 9:29 AM
>To:    Multiple recipients of list ADSM-L
>Subject:       Re: ADSM Reporting Capabilities
>
>     I can answer the one real fast...
>     ADSM V2R1L0.2 under aix... if from the command line you use output
>     redirection it alters the output format... that is from dsmadmc
>you
>     say " q fil f=d" you get all file spaces in that one node per
>screen
>     but if you use "q fil f=d > filespace.list then filespace.list
>     contains column oriented report w/ one filespace per line (node
>data
>     is together but no total line...
>
>     hope this helps...
>     later
>          Dwight
>
>
>
>______________________________ Reply Separator
>_________________________________
>Subject: ADSM Reporting Capabilities
>Author:  ADSM-L at unix,mime/dd.RFC-822=ADSM-L\@VM\.MARIST\.EDU
>Date:    5/3/96 6:38 AM
>
>
>Many times I have come accross instances where the reports
>that can be generated using the admin client cannot be generated
>from the command line utilities.
>
>For instance, from the command line the "query filspace" command
>does not represent the details that I require.  Upon issuing a
>"query filespace format=detailed" changes the format - it is no
>longer in columnar format, it is now going down the page.  What
>I want to do is generate the report available from the admin
>GUI interface on a scheduled basis and mail the results to the
>users that are affected (IE: drive utilization, date of last
>backup, etc).  The file produced from the GUI interface is
>ideal:  one line (record) per node, and a fixed length of 520
>bytes.  How can I do this via the command line?
>
>Another instance:
>I was trying to find an easy way to produce a report which
>simply contains the scheduling classes and the nodes that
>belong to it - is there an easier way that selecting each
>class one by one?
>
>One way to solve my reporting problems would be to get an
>engine that can access the Database that ADSM uses - or at
>least the file layout of the records.  Has anyone else come
>across this problem, or better yet - Anyone have a solution?
>
>
>
>
>Bryan King
>Network Specialist
>ISM Manitoba
>Winnipeg, Canada
>204-946-6640
>bking AT ism DOT ca
>