|
BPCS 6.02 Mixmode AS400 V4R2 RISC We currently have an inhouse written shipping label generated from RPG code that is printing via an AS400 dumb terminals comm port to a SATO label printer . This custom job extracts shipping data from BPCS and prints on the label. Here's my issue. I have a new warehouse facility across town with T1 connection back to our AS400. All network addressed PC's there running green screen emulation via Client Access. I want to hook up another Sato printer there and run the same custom program. I'm having trouble getting the SATO printer to print from the custom program through Client Access. I've also tried using a print server instead of client access. I can't install dumb terminals in the new facility unless I buy a remote controller which I don' t really want to do. THe Sato printer has both a serial and parallel interface. It looks like the special Sato coding that's in the RPG is getting cooked during the passing to the printer therefore the Sato doesn't know what to do. Obviously, we don't have alot of experience with this type of connection to barcode printers but we have installed HP lazer printers by the dozens and have had no problems. I wondering if my AS400 device description is causing the data stream to be corrupted before it hits the printer. I realize this is a border line question for a BPCS list so I apologize now and I'm not slamming anyone with this. Thanks Rick Carter 270-745-9532 +--- | This is the BPCS Users Mailing List! | To submit a new message, send your mail to BPCS-L@midrange.com. | To subscribe to this list send email to BPCS-L-SUB@midrange.com. | To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com. | Questions should be directed to the list owner: dasmussen@aol.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.