You have a very good point. In our case, most of the reports come from CICS and are just a few pages.
I will however check the number of blocks for the file currently being stuck and if it is greater than a certain number of blocks then the procedure will not do the commands. Thanks Mike -----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Aria Bamdad Sent: February 7, 2007 11:51 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Stuck RSCS LPR printers procedure How do you know that the printer is stuck? If the job has been in the queue or partly sent by RSCS, it could be that the printer needs intervention, like needing paper or toner. Doing what you do will cause these jobs to restart and hang again! Aria. On Wed, 7 Feb 2007 11:48:10 -0500 you said: > >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
