¿ªÔÆÌåÓý

  1. H390-Vm
  2. Topics

VM Guest Printing

 

I have a VM system and a VM under VM guest system.? My printer output from a user under the guest system is vanishing.
?
In Hercules, I have 00e output going to a file.?? The CP directory entry for the VM guest includes:
?
USER VMTEST PPPPP 8M 16M G ? ? ? ? ? ? ? ? ? ?
?OPTION ECMODE REALTIMER BMX VIRT=REAL STFIRST
?IPL 6A1 ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?
?CONSOLE 009 3215 ? ? ? ? ? ? ? ? ? ? ? ? ? ??
?SPOOL 00E 1403 A ? ? ? ? ? ? ? ? ? ? ? ? ? ??
?SPOOL 00C 2540 READ * ? ? ? ? ? ? ? ? ? ? ? ?
?SPOOL 00D 2540 PUNCH A
?
Suppose I dial my guest system and logon as a user.? I can print a file and I see it show up on the operator console of the VM guest:
?
16:13:46 PRT ?00E OUTPUT OF DAN ? ? ?FILE ?= 0027 RECDS= 000005 COPY= 01 ?A PRT
?
After seeing the message, a Q PRT by the Operator shows no files.
?
There is also no output added to my redirected listing file.? I do know that this works from the top level VM.
?
I must be missing something, but it is surely not obvious to me.? Please enlighten me.
?
Thanks.? ? ? ? ? ? ? ? ? ??

 

On Wed, Oct 23, 2024 at 17:21 Daniel L. Srebnick via <dan=[email protected]> wrote:
Suppose I dial my guest system and logon as a user.? I can print a file and I see it show up on the operator console of the VM guest:
?
16:13:46 PRT ?00E OUTPUT OF DAN ? ? ?FILE ?= 0027 RECDS= 000005 COPY= 01 ?A PRT
?
After seeing the message, a Q PRT by the Operator shows no files.
?
There is also no output added to my redirected listing file.?

Your second-level user wrote a file to its virtual printer.? The second-level CP created a second-level SPOOL file to collect and store that print data.? When the file was closed, the second-level CP wrote the SPOOL file's contents to a printer.? That printer is actually a first-level virtual printer, so the first-level CP created a?first-level?SPOOL file to collect and store the print data that the second-level CP wrote.? If your?first-level?CP doesn't have a STARTed printer accepting print files, it will just sit in the first-level SPOOL until you #CP START one.

A first-level Q PRT should show this.

Ross
 

Therein lies the mystery.

My first level printer IS started and nothing is in the queue, nor is it being written to the associated file.


On Wed, 2024-10-23 at 19:00 -0400, Ross Patterson wrote:
On Wed, Oct 23, 2024 at 17:21 Daniel L. Srebnick via <dan=[email protected]> wrote:
Suppose I dial my guest system and logon as a user.? I can print a file and I see it show up on the operator console of the VM guest:
?
16:13:46 PRT ?00E OUTPUT OF DAN ? ? ?FILE ?= 0027 RECDS= 000005 COPY= 01 ?A PRT
?
After seeing the message, a Q PRT by the Operator shows no files.
?
There is also no output added to my redirected listing file.?


Your second-level user wrote a file to its virtual printer.? The second-level CP created a second-level SPOOL file to collect and store that print data.? When the file was closed, the second-level CP wrote the SPOOL file's contents to a printer.? That printer is actually a first-level virtual printer, so the first-level CP created a?first-level?SPOOL file to collect and store the print data that the second-level CP wrote.? If your?first-level?CP doesn't have a STARTed printer accepting print files, it will just sit in the first-level SPOOL until you #CP START one.

A first-level Q PRT should show this.

Ross
 

On Wed, Oct 23, 2024 at 19:03 Daniel L. Srebnick via <dan=[email protected]> wrote:
Therein lies the mystery.

My first level printer IS started and nothing is in the queue, nor is it being written to the associated file.

If the second-level CP is still logged on, and you haven't done a #CP CLOSE PRT from its virtual console, then the first-level SPOOL file is still open, and won't appear in the PRT queue yet.

Folks that used to run second-level systems with virtual printers often had a?second-level OS mod to do a CLOSE vdev-addr via DIAG 8 after printing their SPOOL's files.? But VM/370 R6 CP doesn't do that by default.

Ross
 

I understand what you're saying, but...
?
The output appears on the second level CP for a moment and then is gone:
?
18:51:41 PRT ?00E OUTPUT OF DAN ? ? ?FILE ?= 0020 RECDS= 000005 COPY= 01 ?A PRT
Q PRT
18:51:56?
18:51:56 NO PRT FILES
?
If I issue a CP CLOSE PRT it does nothing because the output seems to be going into the ether...shouldn't the files show up via a
Q PRT until I issue the CLOSE?
 

Daniel,
?
How is your printer defined in the directory of the first level machine hosting the second level system?? It's been a long (really long) time, but I vaguely recall that you had to define the printer (Device 00E) on the first level machine correctly, or possibly couple the printer on the hosting first level VM to another device on a first level VM (RSCS comes to mind).?? The basic gist of it is that the system printer at the second level is DEV 00E at the first level, and that you have to track it down from there.
?
I wish I had a working example to look at..... sigh..... I know I've done it once or twice.? Those were the days!
?
Jim
 

Daniel,
?
You have to issue the CP CLOSE PRT from the virtual machine console (first level) userid that is hosting the 2nd level VM system.
?
At that point, if your first level system printers are stopped (e.g., device 00e or 00f) then you should see the output in a CP Q PRT ALL command, sitting in the first level spool.? If the printers are started then you will see a message on the first level operator console that the output is bring printed and it should be available in your disk file.
?
Regards,
Bob
?
 

Hi Bob:

That did not work either. ?The spooled file is there at level 2 as long as the printer is drained. ?Starting it and the output vanishes.

So I tried something else. ?I attached 00F to the 2nd level VM and now printing works flawlessly with no extra steps or closes.



On Thu, 2024-10-24 at 05:47 -0700, Bob Polmanter wrote:
Daniel,
?
You have to issue the CP CLOSE PRT from the virtual machine console (first level) userid that is hosting the 2nd level VM system.
?
At that point, if your first level system printers are stopped (e.g., device 00e or 00f) then you should see the output in a CP Q PRT ALL command, sitting in the first level spool.? If the printers are started then you will see a message on the first level operator console that the output is bring printed and it should be available in your disk file.
?
Regards,
Bob
?
 

On Thu, Oct 24, 2024 at 09:08 Daniel L. Srebnick via <dan=[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
 

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:
On Thu, Oct 24, 2024 at 09:08 Daniel L. Srebnick via <dan=[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
 

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:
On Thu, Oct 24, 2024 at 09:08 Daniel L. Srebnick via <dan=[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
 

Dan,
?
From the first level's operator's console, you'd be closing the operator's virtual printer.? To close the VM hosting the second level machine from the operator's console, you'd have to "send" the command to it:
?
CP SEND LEVEL2VM #CP CLOSE PRT
?
I still have a some VM/SP Rel 5 manuals, so I checked, and there doesn't appear to be a Class D version of the CLOSE command, where you could specify userid and device.
?
Gosh, am I rusty.....
?
Jim

1 - 12 of 12