What about EXECUTE * PIPE LITERAL / |STATE .... EXECUTE *, yes, that's something I like very much, only VM permits things like this I guess
2009/5/13 Glenn Knickerbocker <n...@bestweb.net> > Not sure how I didn't stumble on this sooner, since I use EXECUTE * PIPE > STATE etc. against long lists in FILELIST all the time: > > > pipe state STRING * Q|cons > > PIPDST060E Delimiter missing after string "* Q". > > PIPSCA003I ... Issued from stage 1 of pipeline 1. > > PIPSCA001I ... Running "state STRING * Q". > > Ready(00060); > > This problem actually already existed with the handful of fileids that > exactly match any two keywords, and is resolved in that case by > supplying the filemode: > > > pipe state format quiet|cons > > Ready; > > pipe state format quiet *|cons > > FORMAT QUIET A1 V 1 1 1 5/13/09 14:50:23 > > Ready; > > > pipe state noformat quiet > > Ready; > > pipe state noformat quiet * > > Ready(28); > > With STRING, there's no way around it but to move the fileid to the > input file. Guess it's time to write myself a PIPSTATE EXEC. > > ¬R > -- Kris Buelens, IBM Belgium, VM customer support
