Morning Jim and thanks for the feedback. I have worked with various outputs from AFP to XEROX and have implemented several report distribution systems (now known as electronic content management systems) and I still don't feel that I know enough about all the various aspects of printing. If you have a guide that you don't mind sharing I wouldn't mind getting a copy.
Thanks and best regards, Gil. -----Original Message----- From: Jim Marshall [mailto:[email protected]] Sent: Wednesday, November 25, 2009 6:38 AM To: [email protected]; Gilbert C Cardenas Cc: Jim Marshall Subject: Re: Monitor lpr printer on Windows from Mainframe >We use VPS to route print from the mainframe to the windows server >and when the server goes down for maintenance etc, the vps printer >goes into an error status cause it can't communicate with the printer. >I can't rely on the network folks to communicate what they are doing to >me so I really need this to be automated. > VPS indeed has an EXIT08 which can redrive the request for connection at some interval. In the VPS LPR/LPD you just code say TCPMRD=15 (min) and the printer will indeed timeout. Without coding it then the printer will never timeout. This is because VPS makes the initial request and waits for a response. Eventually the printer may become available but, unlike SNA where the 3X74 controller would notify VPS, nothing is sent to VPS saying it is now available. I always code some timeout. True if the whole thing is not available again, then you go into a loop and eventually (we hope), the printer becomes available. In VPS 1.8 EXIT08 was implemented in exit code. Oh yes, the exit code needs to be told the TCP/IP error code so it knows to retry this type of error. But in VPS 2.0, the strategy is available in parameters although I have not examined them yet to see how easy it is. Hey this is what one doing printing suffers from in the IP world of printing. As a side bar, if indeed the printer is set for 15 minutes timeout and there is very long print actually printing, since the response does not come to the very end, then even though it is printing, the printer will TIMEOUT and when it restarts, it starts over (thank you LPD protocol). I try to stay away from large printouts and LPR/LPD protocol unless there is no other way. This is why we always TRY to use SOCKET printing, with timeout coded too, but doing checkpointing just like JES2 does (JES3 too). Send me an e-mail offlist and be glad to send you the one I have run for almost 20 years as a guide. I threw in all kinds of extra IP error codes as I tripped over them. jim This e-mail (and any attachments) may contain information that is confidential and/or protected by law. Any review, use, distribution or disclosure to anyone other than the intended recipient(s) is strictly prohibited. If you are not the intended recipient, please contact the sender by reply email and delete all copies of this message. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
