Hello Steve,
?
Thank you very much for taking your time at looking into that topic. ?On my side, I can add this:
?
1. I already use HercPrt with DOS/360, despite the absence of an end separator page, I am using the same method Fish uses for VM/370 (which has no end separator page), it is a reasonable trade-off;
?
2. it would be easy for me to "train" HercPrt to recognize an end separator page, I just did not know how to create one, but you just showed me how;
?
3. using a dedicated printer for DOS/360 avoids the problem of handshaking but leave us without one advantage of running DOS in a virtual machine, that is spooling the output (punched or printed) to other virtual machines, without manual intervention. When I use DOS/VS under VM/370, I submit jobs from a CMS virtual machine and I use a "special" print class for them. This class is handled by one LST task connected to a virtual printer, itself spooled to the CMS virtual machine. This way I can submit a job to the DOS/VS virtual machine, get back the output in the virtual reader of the CMS virtual machine, examine it with the SFBROWSE command and then decide whether or not I print it. I can also use a "regular" print class if I want the output printed right away. However, this can only work if handshaking is implemented. Otherwise, one has to manually close the spool device;
?
4. as far as I am concerned, don't worry about modifying the code of POWER II, I prefer to work with DOS/VS anyway (meaning no offense :-) ). However, I feel I should add that I truly had a lot of fun building DOS/360 following the instructions of your website. I learn along the way and I do play with my DOS/360 system from time to time. I think the community is lucky to have a man of your expertise to help anyone interested in DOS/360.
?
Cheers,
?
Rene FERLAND, Montreal
?
Ren¨¦ Ferland