I don't really agree with the recommendation to use RACF(BATCH as opposed to using RAC: - with RAC, one gets a returncode for the specific RACF command that was executed - RACF(BATCH gives one global returncode for all stacked commands. A REXX stage can also be written using RAC.
Steve Swift wrote "RACFAST", a RAC compatible module, it sends its output to the console, not to a disk file that is then typed on the console. This would be more suited for use in a PIPE subroutine. I adapted it to the newer RACF releases and enhanced the detection of timeouts (required for lengthy RACF output, like RAC LISTUSER *). I can't check if I placed it on VM's download library (www.vm.ibm.com seems down) 2009/9/20 Rob van der Heij <[email protected]> > > On Sun, Sep 20, 2009 at 3:52 AM, Thomas Kern <[email protected]> wrote: > > > Try putting your RACF command in a PIPELINE. > > > > PIPE some input | CMS RACF whatever | other stages | > RACF OUTPUT A > > If you want to do that, it takes a bit more. Obviously the RACF module > (you probably want "command RACF" instead) does not take input from > the pipeline like that. You could use > spec ,EXEC RAC, 1 1-* nw | command | .. > > But I would recommend to write a RACF stage that stacks the input and > uses "RACF ( BATCH" to run the commands. Once you have this framework, > you may soon find yourself generate RACF commands from the output of > earlier commands. So make sure your stage handles that properly. > > Rob -- Kris Buelens, IBM Belgium, VM customer support
