| Newsgroups |
gmane.comp.emulators.hercules390.general |
| Message-ID |
<[email protected]> |
Le 4/17/2019 à 5:42 PM, Grant Taylor gtaylor-gHMVqx8RTmrtC6uA/[email protected]
[hercules-390] a écrit :
> Please excuse my naive n00b questions as I try to understand the high
> level behind this.
Never be afraid to ask
>
> On 4/17/19 2:06 AM, 'Dave Wade' [email protected] [hercules-390] wrote:
>> On VM everyone has a virtual reader, so files arrive on the reader.
> Are these virtual readers attached to guest VMs used somewhat like an inbox?
CP (the VM Hypervisor) maintains 3 queues for each defined virtual
machine : The Reader Queue, The Printer Queue, The Punch Queue. Each of
these queues contain sets of cards and/or printed lines. They are each
grouped in spool file which contain the cards/prints and some metadata.
View each "spool file" as a box - with a box ID (Spool ID), a
label(Tag), a class (a 1 character information), and is located in
someone's drawer (spool queue).
>
> Was it possible for anyone add cards to any other guest VM's hopper
> (inbox)? (Even if that's not what was actually done.)
You use the CP SPOOL <PRT|PUN> TO <userid> to indicate the disposition
of the next "punch" or "print" output. <userid> can be yourself or "*"
in which case it is sent to your own reader queue. <userid> can be
"SYSTEM" in which case it becomes eligible for actual physical punching
(and put on the Punch queue) or printing (put on the print queue) -
under certain conditions. When sending files via RSCS you simply do a
'CP SPOOL PUN TO RSCS' then punch your file.
>
>> To send you tag the file with the name of the remote node and userid
>> you want to send to and spool it the RSCS machines reader.
> It sounds like you would prepend a data set (file) with a card that
> indicated where you wanted the data set (file) to be sent to and then
> drop it in RSCS's hopper (inbox).
You use the spool file Tag (Using the CP TAG Command) to give that
information. RSCS looks at the spool file "TAG" metadata and then reacts
accordingly. The TAG is an arbitrary string. When using RSCS when
transfering a file through an NJE link, the tag basically contains the
remote node to send it to followed by information to be relayed to the
remote node for disposition.
>
> I presume that RSCS would read the prepended card to learn where the
> associated data set (file) was supposed to go, and would then magically
> transfer (copy / punch / ???) the card and the data set (file) to the
> receiving guest VM's hopper (inbox).
Specification of disposition of a transfered file using NJE is included
in the NJE protocol. RSCS then knows what to do with the received file
(to which VM User to send it to).
So basically, RSCS uses CP spool files metadata, no need for additional
cards ;)
On a side note, the CP Virtual reader is a bit magic and can turn
"virtually printed files" into magical 132 columns cards and read them !
This allows transfering printer listings to other users, other nodes,
RSCS managed printers, RSCS managed RJE printers, etc..
--Ivan
[Non-text portions of this message have been removed]