On Thu, Apr 4, 2024, 11:31 Dave Wade <dave.g4ugm@...> wrote:
Bertram,
?
Well OPERATOR is a funny beast. Many things behave differently, or usually behave differently. Its generally the first logged on user so it receives certain messages which can interfere with other thing.
It has ¡°TERM MODE CP¡± set by default so commands are passed to CP not another user.
I think that is why you get the odd behaviour with ¡°def stor¡± which will always cause a reset so you always need to re-ipl cms.
If there is no OS loaded the default on OPERATOR you won¡¯t get a message about a disabled wait because your VM is already in that state.
Thank you very much.? I hesitated to report a bug here because of my last experience.? I discovered an issue with the CP Define Storage command when issued by the OPERATOR userid.? A person said one shouldn't be issuing this command on the OPERATOR userid.? I could issue this command on OPERATOR on VM/370 R6 PLC 29.? I was a student operator (Ohio University) and had my own copy of VM (VM under VM/370 BSEPP) again at OU as a student.? I was able to define storage on both systems for the OPERATOR userid.
?
I want differences fixed.? All users should be able to define storage regardless of their name or purpose.? I fear (am concerned) that this points to a more significant issue.? After all, why should CP work differently just because the username is different?? It just doesn't make sense.
?
Bertram Moshier
WB8ERT
?
?
?
?
?
On Thu, Apr 4, 2024 at 5:13?AM Dave Wade <dave.g4ugm@...> wrote:
Bertram,
Its ok to just put it on here. There is a GITHUB site but not sure who owns it.