Here is a brief piece I use to discuss printing off the AS400 / iSeries
There are differences when printing with Ethernet attachment versus Twinax on an AS/400 / iSeries . The main difference is that the host data stream is different. With Twinax the data stream is SCS (SNA Character Stream) with the Ethernet attachment the data stream is TCP/IP - ASCII. The AS/400 Host Print Transform can be configured to handle to transform from SCS to ASCII. As with most ASCII environments, there is no intelligence in the data stream. So, the operator of other software must be used to operate the printer in an ASCII environment.
Improved Options to support TCP/IP ASCII printing are:
1. Use SNMP communications instead of TCP/IP.
2. Use TN3270 / TN5250 support - SNA over Ethernet.
3. Use IPDS - AFP
1. SNMP - Allows the ASCII printer to be defined as a device rather than a Remote OUTQ. This does give some management over the device but not much management capability over the print jobs i.e.. backspace, restart etc..
2. TN5250 - Allows for support of SNA over Ethernet. Gives the printer operator the same basic capabilities as direct Twinax attachment.
3. IPDS / AFP - Allows for a more advanced data stream. Full error recovery down to the last printed page; forward and backspace capability; advanced functions like barcode, graphics, overlays, logos etc...
If what the customer is printing is critical, do they need to guarantee that it printed?
A consistent problem I have discussed with customers who use ASCII printers from their AS400 is the ability to manage the print and make sure it prints.
Host Print Transform which is standard in the OS of the iSeries offers the SCS to ASCII transform, but a couple of the limitations I know about are:
1) Limitations include no page range printing.
2) Controlling the output can also be a problem because of the lack of control over the sending of spool files. Once a spooled file has started sending, a user may have a tough time stopping the printing from the operating system side. Putting the spool file on hold or deleting it may not be successful.
3) No Guarantee that what you are printing actually prints.
4) No Error Recovery between the printer and AS400
5) IPDS is the only way to accomplish this completely
6) Ethernet/TelNet capabilities on the 6500 from the iSeries emulates the Twinax better than any other options.
If you need assistance in configuring any print device to your AS400, please let me know
There are differences when printing with Ethernet attachment versus Twinax on an AS/400 / iSeries . The main difference is that the host data stream is different. With Twinax the data stream is SCS (SNA Character Stream) with the Ethernet attachment the data stream is TCP/IP - ASCII. The AS/400 Host Print Transform can be configured to handle to transform from SCS to ASCII. As with most ASCII environments, there is no intelligence in the data stream. So, the operator of other software must be used to operate the printer in an ASCII environment.
Improved Options to support TCP/IP ASCII printing are:
1. Use SNMP communications instead of TCP/IP.
2. Use TN3270 / TN5250 support - SNA over Ethernet.
3. Use IPDS - AFP
1. SNMP - Allows the ASCII printer to be defined as a device rather than a Remote OUTQ. This does give some management over the device but not much management capability over the print jobs i.e.. backspace, restart etc..
2. TN5250 - Allows for support of SNA over Ethernet. Gives the printer operator the same basic capabilities as direct Twinax attachment.
3. IPDS / AFP - Allows for a more advanced data stream. Full error recovery down to the last printed page; forward and backspace capability; advanced functions like barcode, graphics, overlays, logos etc...
If what the customer is printing is critical, do they need to guarantee that it printed?
A consistent problem I have discussed with customers who use ASCII printers from their AS400 is the ability to manage the print and make sure it prints.
Host Print Transform which is standard in the OS of the iSeries offers the SCS to ASCII transform, but a couple of the limitations I know about are:
1) Limitations include no page range printing.
2) Controlling the output can also be a problem because of the lack of control over the sending of spool files. Once a spooled file has started sending, a user may have a tough time stopping the printing from the operating system side. Putting the spool file on hold or deleting it may not be successful.
3) No Guarantee that what you are printing actually prints.
4) No Error Recovery between the printer and AS400
5) IPDS is the only way to accomplish this completely
6) Ethernet/TelNet capabilities on the 6500 from the iSeries emulates the Twinax better than any other options.
If you need assistance in configuring any print device to your AS400, please let me know
Tags:
AS400 Printing Tips
Leave a comment