Yep! Can't read my own execs... :) Thanks. On Tue, Oct 12, 2010 at 1:29 PM, Ron Schmiedge <ron.schmie...@gmail.com> wrote: > And by CP SET VMOUT you meant CP SCREEN VMOUT of course... > > > On Tue, Oct 12, 2010 at 10:35 AM, Bruce Hayden <bjhay...@gmail.com> wrote: >> There are a few options. The easy one is to turn highlighting on and >> off, which will make that part white: >> 'CP SET VMOUT DEFAULT' /* Must be default for this to work */ >> hi = '1DC8'x >> lo = '1D40'x >> Say 'There has been an 'hi'error'lo >> >> The other way that works for entire lines is to set the VMOUT setting. >> 'CP SET VMOUT RED' >> say 'This is an error' >> 'CONWAIT' /* Wait for output to display */ >> 'CP SET VMOUT DEFAULT' >> >> Finally, there is a lot of flexibility in full screen CMS, but the >> operators woud have to run with fullscreen on. >> >> On Tue, Oct 12, 2010 at 12:14 PM, Karl Kingston <karlkings...@ongov.net> >> wrote: >>> Does anybody have any tricks on how to do highlighting in a rexx "SAY" >>> statement? What about setting colors for an extended attributes? >>> >>> I'm working on writing an Rexx exec to let our operators know which of our >>> z/Linux machines are up, are supposed to be up, and are down. So if I can >>> do colors, that would be nice. But at the very least, I need hilighting. >>> >>> Thanks >>> >> >> >> >> -- >> Bruce Hayden >> z/VM and Linux on System z ATS >> IBM, Endicott, NY >> >
-- Bruce Hayden z/VM and Linux on System z ATS IBM, Endicott, NY
