PDA

View Full Version : Printer Answer Interpreter



B.Myrick
01-01-1995, 02:00 AM
I have a new project I want to do. I have several printers in the plant that print pick lists, bills of lading, etc, that fail every now and then. End of forms, not lined up, etc. Nothing really special. What I would like to do is: Determine what outq the user is assigned to; Determine the CPxxxxx message; Display a User friendly message with limited options; Convert the User's option to the appropriate I, C, G, Etc. and answer the message. Has anybody out there done something along these lines? I'm sure an API is going to be required. Or I can print to an *OUTFILE, but that's the old way and not that innovative. All help is appreciated. Bret "I'm still learning" Myrick

David Abramowitz
06-20-2000, 11:49 AM
Most warehouse operations operate uniquely, so my experience might not be of help. Are your printers used exclusively for a single form? e.g. Printer PRT12 for pick lists only Printer PRT14 for Blue Bar only etc. Dave

B.Myrick
06-20-2000, 12:48 PM
Dave, Yes. One is Pick Slips only and the other is dedicated to Bills of Lading. They each are loaded with the one form and nothing else. If I figure this out or someone has the answer already (pray pray pray), then I can utilize it later on my bluebar only or laser printer only which use *STD. Thanks, Bret

David Abramowitz
06-20-2000, 06:45 PM
In a similar situation, we solved the problem with user training, and a buncha phone calls. WRKSPLF *ALL is periodically monitored by a human being, and so is DSPMSG QSYSOPR. Through initial diligence it has actually worked out well. Despite having remote PDCs, no printer is ever stuck in a jam, or without forms for more than a few minutes. This company is relatively small, and personnel are amenable to changing the paper in the printer, etc. Sometimes, , , sometimes, establishing manual procedures can work just as well if not better than automated ones. Dave

B.Myrick
06-21-2000, 06:40 AM
Thanks Dave. I agree with the manual procedures be implemented. I would just as soon see the printer be canceled by the system, and have a job that simply re-starts the writer. Don't know how I am going to procede yet, but your answer backs up what I was thinking. Later, Bret