Re: Redirecting Output In Scripts
2001-07-03 10:25:36
Subject: |
Re: Redirecting Output In Scripts |
From: |
Richard Sims <rbs AT BU DOT EDU> |
Date: |
Tue, 3 Jul 2001 07:28:08 -0400 |
...
>SELECT NODE_NAME,VOLUME_NAME FROM VOLUMEUSAGE > 'DM.PROD.ADSMP.VOLUSAGE'
...
>However, in the TSM server on AIX, a similar command defined as a script and
>then run issues an ANR2907E Unexpected SQL operator token - '>'.
A frequently asked question...
Admin Ref manual chapter 3, Redirecting Command Output addresses this.
And from my notes at http://people.bu.edu/rbs/ADSM.QuickFacts :
> Redirection character in the server
administrative command line interface,
if at least one space on each side of
it, saying to replace the specified
output file. There is no "escape"
character to render this character
"un-special", as a backslash does in
Unix. Thus, you should avoid coding
" > " in an SQL statement: eliminate at
least one space on either side of it.
Richard Sims, BU
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- Redirecting Output In Scripts, Robin Lowe
- Re: Redirecting Output In Scripts,
Richard Sims <=
- Re: Redirecting Output In Scripts, Cook, Dwight E
- Re: Redirecting Output In Scripts, Martin, Jon R.
- Re: Redirecting Output In Scripts, Ford, Phillip
- Re: Redirecting Output In Scripts, Poland, Neil
- Re: Redirecting Output In Scripts, Nicholas Cassimatis
- Re: Redirecting Output In Scripts, Sheets, Jerald
- Re: Redirecting Output In Scripts, James Thompson
|
|
|