So just
STOP printerid DEFINE printerid ASTART (no other operands). ? Mike ________________________________ From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: February 7, 2007 11:48 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Stuck RSCS LPR printers procedure Hi Mike, Didn't look at the first part carefully. You can replace the DRAIN, FLUSH, START and CHANGE with a simple STOP and DEFINE sequence. That's how we handle it. Peter -----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Horlick, Michael Sent: February 7, 2007 11:36 To: IBMVM@LISTSERV.UARK.EDU Subject: Stuck RSCS LPR printers procedure Greetings, I am trying to set up some automation to try to retry "stuck" LPR printing. Currently, every 30 minutes we check the RSCS queues for files that are older than 2 hours old and if there are some to have our help desk do the following commands on a stuck printer. DRAIN printerid FLUSH printerid spid HOLD START printerid FORM * CHANGE printerid spid NOHOLD Now I've decided to have the procedure which detects the stuck printer do the commands to try to fix it and if the status doesn't change the next time it is called to e-mail our clients help desk. While checking out the RSCS book I see that maybe the RSCS STOP command , followed by the START command can do the equivalent. Is there a difference or a better way? Regards Mike Horlick ________________________________ The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review retransmission dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient or delegate is strictly prohibited. If you received this in error please contact the sender and delete the material from any computer. The integrity and security of this message cannot by guaranteed on the Internet. The Sender accepts no liability for the content of this e-mail or for the consequences of any actions taken on basis of the information provided. The recipient should check this e-mail and any attachments for the presence of viruses. The sender accepts no liability for any damage caused by any virus transmitted by this e-mail. This disclaimer is the property of the TTC and must not be altered or circumvented in any manner.
