Decades ago I did some work with 3270 printers.? A printer is nothing more than another I/O addressable device.? Printing a 3270 monitor's screen contents was a local control unit function.? It was part of the CU's configuration.? The "print key" on a local monitor would send data to the configured printer attached to the same control unit.? That is one flavor of printing.? While it looks like this, the use of a CP command is different.
toggle quoted message
Show quoted text
There is nothing stopping an application, VM/370 in this context, from sending content to any printer.? I did a bunch of that in CICS/VS "in the day".? The functionality is similar.? The user presses a monitor key and the screen appears at a printer. However, they are implemented entirely differently.? VM has to do the sending and it is not part of the 3270 control unit definition. I would concur that the issue would appear to be in the VM/370 implementation.? It is not an issue with the "device" or "control unit" emulation software doing the printing. It has been a long time.? There may have been some control characters recognized by the printer that were not recognized by monitors.? I only mention that, because to adjust the CP function for printing a monitor's buffer may require use of those characters.? A 3270 component description might be needed to adjust this. I realize there are no concrete answers here, but this may help in first understanding the underlying issue and perhaps fixing it. Harold Grovesteen On 5/23/24 18:27, Fish Fish wrote:
Dave Wade wrote:Fish wrote:Oh well. It was worth a shot.Dave Wade wrote:No, but I have now and it makes no different.... |