If I remember well: RAC writes its output to disk as RACF OUTPUT A and then the disk file is typed at the console. I inherited a RACFAST tool from Steve Swift that avoids this detour via the A-disk. So, if the use of a RACF command is more than an example but key: use FILELIST first.
Another side note: when inserting a > stage to collect the data flowing through the pipe, remember that null records are possible in a pipe, but not on disk. I.e. the null records will not end in the disk file. Use "|PAD 1 x|> fn ft fm" to have these null records in the file too. 2008/2/7, David Boyes <[EMAIL PROTECTED]>: > > I am frustrated with commands generating data that fills multiple > screens > > and not have the ability to scroll back and forth in the results > > Thus I thought I'd try something with PIPEs and came up with this: > > [snip] > > This seemed like it would work but the file is empty when xedit opens > it. > > Try SET FULLSCREEN ON at the CMS command line. Not all commands use the > right I/O stuff to be pipe-friendly (particularly stuff brought over > from MVS like RACF). > > I don't care for fullscreen CMS much, but others like it. > -- Kris Buelens, IBM Belgium, VM customer support
