Brian Westerman wrote: >So you are using TCP to get to them inside the ICC, but they >are technically local 3270 terminals. I think you can make >some of them printers if you want, but that seems like a waste.
I recently worked with an organization that configured an OSA-ICC TN3270E printer session, and it makes sense for them. They did this because one of the TCP/IP products available for z/VSE, the one they use, includes a TN3270E server that is limited to display terminal sessions and does not support printer sessions. This particular organization uses the TCP/IP product's TN3270E server for display sessions, but they also have a line printer they need to continue running. Previously, historically, the line printer was coax attached to an IBM 3174 Establishment Controller. The same line printer is now connected via OSA-ICC's TN3270E server and continues to behave like a terminal-attached printer, with IBM Personal Communications in the middle handling the emulation. Direct would have been nice, and technically the printer can directly connect via a TN3270E printer session (it has a built-in TN3270E client), but for some weird reason when the line printer operates using a different connection it unavoidably changes "personalities" and won't interpret the same data stream the same way. That's how the printer is designed, not something that can be changed. So rather than reconfigure z/VSE's output to adjust the print data stream, they inserted IBM Personal Communications in the middle to accept the original data stream then handle some very light reformatting before passing it on to the printer via LPR/LPD protocol. This arrangement works! - - - - - - - - - - Timothy Sipples I.T. Architect Executive Digital Asset & Other Industry Solutions IBM Z & LinuxONE - - - - - - - - - - E-Mail: [email protected] ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
