If the 370 has one or more printers, there would be a program per printer and a print queue server. Gates to the print queue server would be available to those with the right to use a queued printer. The printer programs would run in real time with the printer. If it is important to segregate the printers, one set of printers with one set of users, this may be done by providing one print queue server for each such set.
We currently think that we will print only thru printers attached to Tymnet. This will not involve kernel logic.
PRINTERF(0,sb,m,sb ==> c;PRINTER)
Return codes
3 Outboard error with standard error string as follows
CCW
CSW
VOLID
SENSE
>4 catastrophic error, do not return until intervention
"Distribution string" is what would be used to construct the banner. The first 8 characters of the distribution string are used as the parameters to a CP SPOOL 00E xxxxxxxx command. This will cause the print output to go into a VM reader if the first 8 characters identify a VM user and Gnosis is running under VM. The output will go to the real VM printer if the distribution string is not a valid VM userid.
Since there is no banner and since files spooled to readers lose carriage control information, files "printed" to a VM reader are transmitted "as is". This can be used to transfer text files from Gnosis to CMS.
This key is found as USER.PUB.PRINT
Return codes
x'10000000' suggest to try again
x'20000000' more than 16 waiters