ADSM-L

Re: Format of output file using select statements

2003-01-07 11:29:25
Subject: Re: Format of output file using select statements
From: Andrew Raibeck <storman AT US.IBM DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 7 Jan 2003 09:25:08 -0700
>> One of the challenges to machine-readable output
>> from dsmadmc is all the extra stuff it wraps
>> around the output ...

We are looking at addressing this in a future release, so that only the
data itself is displayed.

Best regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.eyebm DOT com (change eye to i to reply)

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.




Matt Simpson <msimpson AT UKY DOT EDU>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
01/07/2003 06:27
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: Format of output file using select statements



At 23:33 -0600 1/6/03, Roger Deschner wrote:
>Neither of these formats, which were designed to be human-readable, are
>particularly easy for re-digestion by a computer program of any kind -
>especially when a field is split across lines.

One of the challenges to machine-readable output from dsmadmc is all
the extra stuff it wraps around the output, e.g:
--
Tivoli Storage Manager
Command Line Administrative Interface - Version 5, Release 1, Level 1.0
(C) Copyright IBM Corporation 1990, 2002 All Rights Reserved.

Session established with server UKCCSERVER1: Solaris 7/8
   Server Version 4, Release 2, Level 3.0
   Server date/time: 01/07/03   08:15:20  Last access: 01/07/03   08:14:44

(stuff I really want)

ANS8002I Highest return code was 0.
--

People here have suggested various ingenious combinations of
tail/awk/grep to strip out the garbage, and they work fairly well.
But that seems a little Rube Goldbergish, and I'm a little worried
that it might break if something in the output changes.  I think I
already know the answer (No), but does anybody know of a way to keep
that stuff from appearing in the output, instead of finding it and
throwing it away afterwards?


--


Matt Simpson --  OS/390 Support
219 McVey Hall  -- (859) 257-2900 x300
University Of Kentucky, Lexington, KY 40506
<mailto:msimpson AT uky DOT edu>
mainframe --   An obsolete device still used by thousands of obsolete
companies serving billions of obsolete customers and making huge obsolete
profits for their obsolete shareholders.  And this year's run twice as
fast
as last year's.