> that was.weird, output wrapping and I don't think showing up in SECUSER

If I remember correctly, a 3215 is 132 character print which is why messages 
are wrapping. I'm guessing that 3270 mode does not print some message 
attributes but in 3215 mode enables them because of the free space. Issue a 
console command to remove these if you don't like the wrapping.
> they're from the z/OS console.

Actually, your z/OS has this defined as a terminal under a control unit. This 
terminal could be just as easily be for VTAM. z/OS doesn't care. Issue V 
xxx,console and z/OS allocates the device to the system instead of VTAM.
VM and z/OS may interact a little more but to deal with the missing CU or 
change from 3270 to 3215 but it's just a terminal connected to the console 
address space.
> SECUSER isn't getting the output.
Are you using #CP DISCONNECT or using PA1 with DISCONNECT? I think PA1 puts the 
terminal into CP mode and stops messages from passing to the VM terminal which 
means CP doesn't receive any messages to forward to SECUSER. My guess is that 
you will see messages being queued to that console. There's a D C command to 
see if message are queueing up. 
As a suggestion, get it working with a CMS user and a looping REXX exec. Once 
that's working, z/OS should work the same. 
    On Thursday, July 20, 2023 at 08:40:44 PM PDT, Phil Smith III 
<[email protected]> wrote:  
 
 Jon Perryman kindly offered more thoughts. I've been doing VM for over forty 
years, though focused on z/OS for the last fifteen, so I am very familiar with 
PROP and SECUSER and like that. I agree that this is a VM thing, but I'm 
suspecting that it may have to do with some virtual device not existing, or a 
CP TERMINAL setting. I did try CP TERMINAL CONMODE 3215 but that was.weird, 
output wrapping and I don't think showing up in SECUSER (I did need to get the 
system up so other folks could use it, so my tinkering was limited, alas).

You wrote, in part:
> You want messages from the VM terminal routed somewhere in VM
Right. But they aren't messages from the "VM terminal" per se: they're from the 
z/OS console. Now, that's running on z/VM, so there's some VM terminal-ness in 
there, but it's not quite as simple as "Set up PROP", since, as noted, SECUSER 
isn't getting the output.

I guess I'm kinda looping here. I don't mean to sound argumentative-I really 
appreciate the input, I just don't see how to apply it (yet)! We'll see what I 
get from the VM list, and I will close the loop here if/when I get it resolved. 
Meanwhile, keep those ideas comin'.!




----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
  

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to