Ah. So SECUSER follows the MSG setting and OBSERVER goes where CPCONIO goes. Interesting. We were both wrong, uh right ;-) At least CPCONIO is not as tough as VMCONIO.
On 13 April 2015 at 16:29, Bruce Hayden <[email protected]> wrote: > No, I'm not sure, but it won't take much experimenting to verify. I am > fairly certain that SECUSER output is its own message class, but OBSERVER > output is just CP output. So how that is set up can also change how you > get the output. > > On Mon, Apr 13, 2015 at 10:16 AM, Rob van der Heij <[email protected]> > wrote: > > > On 13 April 2015 at 16:01, Bruce Hayden <[email protected]> wrote: > > > > > > > You will have to set CPCONIO to IUCV to capture the > > > SECUSER output from the LLICPDM user. > > > > > > > > Are you sure Bruce? Wasn't SCIF output always to IUCV as soon as you > > connect to *MSG service? > > > > I think you'd set CPCONIO if you're a *server* and want to associate all > > CMS and CP output with the request you service. And only with care or > > you're likely to bite yourself in the tail... PROP goes to great lengths > > for example to avoid the feedback loop. > > > > Rob > > > > > > -- > Bruce Hayden > z/VM and Linux on z Systems ATS > IBM, Endicott, NY >
