OK folks, I solved it!
I was doing the CP CLOSE PRT from the 1st level operator console. ?That did not work but when I tried it from the 2nd level operator console as #CP CLOSE PRT, that did it.
I wonder why it won't work from the 1st level console as Bob indicated it should?
And thank you for LINED character change suggestion for the 2nd level operator. ?I implemented that.
To say that I generally know what I'm doing, I think it more accurate to say I'm generally learning what I forgot and what I never knew.
Thanks.
On Thu, 2024-10-24 at 10:13 -0400, Jeff Henry wrote:
I used to do it the other way around. I'd change the guest machine's first-level LINEND character to something other than #. That way, when I habitually typed #CP something on the 2nd level machine, I wouldn't accidentally do something to the (production) first-level system. Oh, and on a related note - don't give the guest machine anything other than class G in the first-level directory.
On Thu, Oct 24, 2024 at 9:41?AM Ross Patterson via <ross.patterson=
[email protected]> wrote:
So I tried something else.? I attached 00F to the 2nd level VM and now printing works flawlessly with no extra steps or closes.
Sure, that'll work fine.
You sound like you generally know what you're doing on VM, so I hesitate to ask, but have you changed the LINEND character on your second-level CP's OPERATOR user?? One of the big gotchas running CP in a VM is which CP gets the command when you type #CP at the virtual console.? Old timers like me used to put something like TERM LINEND $ in the second-level OPERATOR's PROFILE EXEC, so #CP whatever went to first-level and $CP whatever went to?second-level.
Ross
--
Jeff Henry
