As soon as I saw that "CMS GLOBALV" I sort of gasped, and was sure Kris would immediately respond. :)
It does seem easy enough to create a GLOBALV EXEC and then open an APAR when the compiler fails. Shimon On Wed, Jun 25, 2014 at 9:14 PM, Rob van der Heij <[email protected]> wrote: > Or maybe have a GLOBALV EXEC on your A-disk that does not produce more than > 1 line of output... ;-) > > If this is how they access the GLOBALV variables, I'm not sure I want to > sit next to them at dinner (sharp steak knifes etc) > > > On 25 June 2014 20:08, Glenn Knickerbocker <[email protected]> wrote: > > > On 6/25/2014 8:08 AM, Jonathan Scott wrote: > > > PIPE ( ENDCHAR ? ) > > > CMS GLOBALV SELECT CENV LIST > > > | DROP FIRST 1 > > > | STRIP LEADING BLANK 1 > > > | APPEND LITERAL > > > | JOIN * H00 > > > | STORAGE 06B7CC28 300 E0 > > > | COUNT BYTES > > > | STORAGE 06B7C7F0 11 E0 > > > > D'oh! I don't know why it didn't occur to me that the compiler module > > would be CALLING Pipelines. That makes the PUSH workaround make sense. > > > > ¬R > > >
