Re: Re: upcoming talks about hercules

Le 4/18/2019 à 7:06 AM, Grant Taylor gtaylor-gHMVqx8RTmrtC6uA/[email protected] 
[hercules-390] a écrit :
> Do the reader, printer, and punch have their own spool file? Or do 
> they share one spool file? (Per guest VM.) 
The spool file space is global in the system. Then each spool file 
within that file space contains metadata to indicate to whom it belongs 
to and to which of the 3 queues it is assigned to. Therefore transfering 
a spool flie (using the CP TRANSFER command for example) is an immediate 
command (no data is copied.. it's just a matter of changing the 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).
> Is it correct to say that each guest VM has a spool queue with the three
> aforementioned spool files therein?
No... The RDR queue is meant to (eventually) be read by the user. The 
PRT and PUN queues are actually meant to send the spool file to the 
system for actual printing/punching - but are still in your queue should 
you still want to delete it, transfer it and whatnot before it is 
actually processed by the system. For example if you *really* want to 
print an output to a real printer (or what VM/370 thinks is a real 
printer) but it will only print print spool files of class "T" but you 
printed your output class "A", it won't print and it will remain in your 
print queue.... But you can change this by changing the class of the 
spool file in the print queue using the CP command "CHANGE" and Voila ! 
.... (well not quite.. the Printer needs to be loaded with the proper 
form - but that's another story).
>
> Is "*" a synonym for the current user?  (In this context.)
Absolutely !
>
> I can see how something like that could make the JCL user agnostic.  The
> user that runs the JCL job gets the output sent to the "*" user ID.
> Hypothetically.
There is no such thing as a JCL in VM ;) But yes.. for EXECs in CMS it's 
a great shortcut to say 'myself' !
> <snipped />

> Interesting.
>
> Can those magical 132 column cards then be executed like normal 80
> column cards?
>
VM/CMS Users do not execute jobs from the card reader ! They just 
receive the files on CMS format Minidisks (there is ONE notable 
exception which is the CMSBATCH utility/user but it's (IMHO) one of the 
dirtiest hack ever !)

Unless of course the virtual machine is running something else than CMS.

....

Oh and missed the part about RSCS routing. RSCS uses store and forward 
and has a path table, so you don't have to specify the path yourself 
(and can't use source routing) - you only have to give a final 
destination... This is not part of stock VM/370 R6 RSCS but there are 
user modification to RSCS that will do that. Newer versions of RSCS 
(when they split RSCS from VM/370 and made it a separate system product 
had it though). If there is a path loop due to misconfiguration it will 
get detected.

PS : this should go to another mailing list... there is a H390-VM group 
that discusses just that (the subtilities of running VM under Hercules). 
And people are usually fine with giving VM hints to newbies ;)

--Ivan




[Non-text portions of this message have been removed]