Re: JES to RSCS LPR printer
Thanks everyone, I found the problem I was having. Actually fairly dumb on my part. I changed the DEST to bpzvm.xwc132, and it didn't print. I assumed it didn't work. But what I found is that it was in the RSCS queue with a user-hold. When I released the hold it printed. Now I need to find if there is a VSE DISP= type parameter in z/OS so that it won't go to RSCS with a user-hold. On Thu, Jan 14, 2010 at 1:59 PM, Marcy Cortes marcy.d.cor...@wellsfargo.com wrote: We do that. I'm not a z/OS person, but I think they just use DEST=vmnode.printer Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Mark Pace Sent: Thursday, January 14, 2010 10:19 AM To: IBMVM@LISTSERV.UARK.EDU Subject: [IBMVM] JES to RSCS LPR printer Is it possible to route JES output to an LPR printer defined to RSCS? The LPR printer works great in RSCS, but can't for the life of me make it work with IP Printway in z/OS. I already have RSCS and JES connected, I currently use it to send output to my VM userid, and then print it from my VM userid to the RSCS printer. I would just like to remove the step of logging in to VM and printing. Thanks for any assistance. -- Mark Pace Mainline Information Systems 1700 Summit Lake Drive Tallahassee, FL. 32317 -- Mark Pace Mainline Information Systems 1700 Summit Lake Drive Tallahassee, FL. 32317
Re: JES to RSCS LPR printer
I have had that problem at other places and until the MVS people fixed their side I used my SCHEDULER product to change RSCS prt queues to NOHOLD every 30 minutes so anything hung up would print, eventually. good luck munson Mark Pace mpac...@gmail.com Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 01/15/2010 08:33 AM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: JES to RSCS LPR printer Thanks everyone, I found the problem I was having. Actually fairly dumb on my part. I changed the DEST to bpzvm.xwc132, and it didn't print. I assumed it didn't work. But what I found is that it was in the RSCS queue with a user-hold. When I released the hold it printed. Now I need to find if there is a VSE DISP= type parameter in z/OS so that it won't go to RSCS with a user-hold. On Thu, Jan 14, 2010 at 1:59 PM, Marcy Cortes marcy.d.cor...@wellsfargo.com wrote: We do that. I'm not a z/OS person, but I think they just use DEST=vmnode.printer Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Mark Pace Sent: Thursday, January 14, 2010 10:19 AM To: IBMVM@LISTSERV.UARK.EDU Subject: [IBMVM] JES to RSCS LPR printer Is it possible to route JES output to an LPR printer defined to RSCS? The LPR printer works great in RSCS, but can't for the life of me make it work with IP Printway in z/OS. I already have RSCS and JES connected, I currently use it to send output to my VM userid, and then print it from my VM userid to the RSCS printer. I would just like to remove the step of logging in to VM and printing. Thanks for any assistance. -- Mark Pace Mainline Information Systems 1700 Summit Lake Drive Tallahassee, FL. 32317 -- Mark Pace Mainline Information Systems 1700 Summit Lake Drive Tallahassee, FL. 32317 *** IMPORTANT NOTE*-- The opinions expressed in this message and/or any attachments are those of the author and not necessarily those of Brown Brothers Harriman Co., its subsidiaries and affiliates (BBH). There is no guarantee that this message is either private or confidential, and it may have been altered by unauthorized sources without your or our knowledge. Nothing in the message is capable or intended to create any legally binding obligations on either party and it is not intended to provide legal advice. BBH accepts no responsibility for loss or damage from its use, including damage from virus.
Re: JES to RSCS LPR printer
You will have to send it to an OUTCLASS in JES that is not defined with OUTDISP=(HOLD...), or release the output in the JES queue prior to sending it to RSCS. Check with your JES folks for a class that has OUTDISP=(WRITE,...). From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Mark Pace Sent: Friday, January 15, 2010 8:34 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: JES to RSCS LPR printer Thanks everyone, I found the problem I was having. Actually fairly dumb on my part. I changed the DEST to bpzvm.xwc132, and it didn't print. I assumed it didn't work. But what I found is that it was in the RSCS queue with a user-hold. When I released the hold it printed. Now I need to find if there is a VSE DISP= type parameter in z/OS so that it won't go to RSCS with a user-hold. On Thu, Jan 14, 2010 at 1:59 PM, Marcy Cortes marcy.d.cor...@wellsfargo.commailto:marcy.d.cor...@wellsfargo.com wrote: We do that. I'm not a z/OS person, but I think they just use DEST=vmnode.printer Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDUmailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Mark Pace Sent: Thursday, January 14, 2010 10:19 AM To: IBMVM@LISTSERV.UARK.EDUmailto:IBMVM@LISTSERV.UARK.EDU Subject: [IBMVM] JES to RSCS LPR printer Is it possible to route JES output to an LPR printer defined to RSCS? The LPR printer works great in RSCS, but can't for the life of me make it work with IP Printway in z/OS. I already have RSCS and JES connected, I currently use it to send output to my VM userid, and then print it from my VM userid to the RSCS printer. I would just like to remove the step of logging in to VM and printing. Thanks for any assistance. -- Mark Pace Mainline Information Systems 1700 Summit Lake Drive Tallahassee, FL. 32317 -- Mark Pace Mainline Information Systems 1700 Summit Lake Drive Tallahassee, FL. 32317
JES to RSCS LPR printer
Is it possible to route JES output to an LPR printer defined to RSCS? The LPR printer works great in RSCS, but can't for the life of me make it work with IP Printway in z/OS. I already have RSCS and JES connected, I currently use it to send output to my VM userid, and then print it from my VM userid to the RSCS printer. I would just like to remove the step of logging in to VM and printing. Thanks for any assistance. -- Mark Pace Mainline Information Systems 1700 Summit Lake Drive Tallahassee, FL. 32317
Re: JES to RSCS LPR printer
For some VSE output, we send from POWER to a service virtual machine that uses the form number as printer number, receives it, does some manipulation then sends it off to the printer. But for those that don't require 'adjustment' we send directly to the RSCS printer. -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Mark Pace Sent: January 14, 2010 13:19 To: IBMVM@LISTSERV.UARK.EDU Subject: JES to RSCS LPR printer Is it possible to route JES output to an LPR printer defined to RSCS? The LPR printer works great in RSCS, but can't for the life of me make it work with IP Printway in z/OS. I already have RSCS and JES connected, I currently use it to send output to my VM userid, and then print it from my VM userid to the RSCS printer. I would just like to remove the step of logging in to VM and printing. Thanks for any assistance. -- Mark Pace Mainline Information Systems 1700 Summit Lake Drive Tallahassee, FL. 32317 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 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 be 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 the basis of 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 property of the TTC and must not be altered or circumvented in any manner.
Re: JES to RSCS LPR printer
Mark, We do it all the time. Just define a DESTID in JES and route to the node name of the RSCS queue for the LPR. Works great. From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Mark Pace Sent: Thursday, January 14, 2010 1:19 PM To: IBMVM@LISTSERV.UARK.EDU Subject: JES to RSCS LPR printer Is it possible to route JES output to an LPR printer defined to RSCS? The LPR printer works great in RSCS, but can't for the life of me make it work with IP Printway in z/OS. I already have RSCS and JES connected, I currently use it to send output to my VM userid, and then print it from my VM userid to the RSCS printer. I would just like to remove the step of logging in to VM and printing. Thanks for any assistance. -- Mark Pace Mainline Information Systems 1700 Summit Lake Drive Tallahassee, FL. 32317
Re: JES to RSCS LPR printer
We do that. I'm not a z/OS person, but I think they just use DEST=vmnode.printer Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Mark Pace Sent: Thursday, January 14, 2010 10:19 AM To: IBMVM@LISTSERV.UARK.EDU Subject: [IBMVM] JES to RSCS LPR printer Is it possible to route JES output to an LPR printer defined to RSCS? The LPR printer works great in RSCS, but can't for the life of me make it work with IP Printway in z/OS. I already have RSCS and JES connected, I currently use it to send output to my VM userid, and then print it from my VM userid to the RSCS printer. I would just like to remove the step of logging in to VM and printing. Thanks for any assistance. -- Mark Pace Mainline Information Systems 1700 Summit Lake Drive Tallahassee, FL. 32317
RSCS LPR ??
I have a report that has some simple carraige control in it SKIP to CH 1 (line 2) and CH 12 (line 44). I want to print this report on a LPR printer via RSCS. How do I get the printer detect the CH 12 and skip to CH 1. Thanks
Re: RSCS LPR ??
Tom - I believe that RSCS LPR will only detect ASA control characters. There is no ASA control character for skip to channel 12. To get to line 44 you would have to count lines and print blank lines after the last detail line to get to line 44. /Fran Hensler at Slippery Rock University of Pennsylvania USA for 45 years [EMAIL PROTECTED] +1.724.738.2153 Yes, Virginia, there is a Slippery Rock On Thu, 8 May 2008 12:43:14 -0500 Huegel, Thomas said: I have a report that has some simple carraige control in it SKIP to CH 1 (line 2) and CH 12 (line 44). I want to print this report on a LPR printer via RSCS. How do I get the printer detect the CH 12 and skip to CH 1. Thanks
Re: RSCS LPR ??
I've got a carriage control paper tape punch if you need to use it. Better yet, you send me the tape and I'll punch it. I hate it when someone borrows my punch and doesn't return it. :-) Jim Huegel, Thomas wrote: I have a report that has some simple carraige control in it SKIP to = CH 1 (line 2) and CH 12 (line 44). I want to print this report on a LPR printer via RSCS. How do I get the printer detect the CH 12 and skip to CH 1. Thanks -- Jim Bohnsack Cornell University (607) 255-1760 [EMAIL PROTECTED]
RSCS LPR ??
I have a report that has some simple carraige control in it SKIP to CH 1 (line 2) and CH 12 (line 44). I want to print this report on a LPR printer via RSCS. How do I get the printer detect the CH 12 and skip to CH 1. RSCS LPR exit LPRXONE does handle a skip to channel 1 opcode, converting to the appropriate CR/FF. However, it will ignore a skip to channel 12. Best Regards, Les Geer IBM z/VM and Linux Development
Re: RSCS LPR ??
OK thanks Les.. I guess my question was poorly worded, I don't want to skip to CH 12, just to CH 1.. I should have left the CH 12 stuff out it was confusing.. Tom -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] Behalf Of Les Geer (607-429-3580) Sent: Thursday, May 08, 2008 3:46 PM To: IBMVM@LISTSERV.UARK.EDU Subject: RSCS LPR ?? I have a report that has some simple carraige control in it SKIP to CH 1 (line 2) and CH 12 (line 44). I want to print this report on a LPR printer via RSCS. How do I get the printer detect the CH 12 and skip to CH 1. RSCS LPR exit LPRXONE does handle a skip to channel 1 opcode, converting to the appropriate CR/FF. However, it will ignore a skip to channel 12. Best Regards, Les Geer IBM z/VM and Linux Development
Re: RSCS LPR won't autostart
Looks like that's the problem. AST is not enabled. I have to look into it closer because that config source that's supposedly in place has AST defined. Unfortunately it's on a remote VM which I don't administer and I don't have access to the RSCS config disk. If available, check the RSCS console to find the event which caused AST to be turned off. RSCS displays a message indicating AST was disabled for the link. Conditions that can cause this to occur include someone draining the link, or an unrecoverable error was encountered. Best Regards, Les Geer IBM z/VM and Linux Development
Re: RSCS LPR won't autostart
Looks like that's the problem. AST is not enabled. I have to look into it closer because that config source that's supposedly in place has AST defined. Unfortunately it's on a remote VM which I don't administer and I don't have access to the RSCS config disk.
RSCS LPR won't autostart
I have 2 different RSCS links defined to the same physical LPR (HP 8150). One link is for landscape, one is for portrait (see definitions below). W hen I send a printout to the portrait queue, the link autostarts fine and the document is printed successfully. When I send the same printout to the landscape queue, I get DMTAXM101I File 7431 (7431) enqueued on link ROC815WL and the link never starts. I can stop/restart the link and the document will then print. I have other LPR's defined exactly the same way and they all autostart correctly on both landscape and portrait queues. The links are defined as follows: LINKDEF ROC815W TYPE LPR MANUAL FORM *AST LINKDEF ROC815WL TYPE LPR MANUAL FORM *AST ... PARM ROC815W EXIT=LPRXPSE ITO=0 SEC=NO # HOST=149.24.51.28 #/* HP 8150 Devl WW * / PRINTER=raw # USER=YES # /* allow overrides * / EPARM='FORM=POCP1109' /* Portrait 60 lpp */ PARM ROC815WL EXIT=LPRXPSE ITO=0 SEC=NO # HOST=149.24.51.28 #/* HP 8150 Devl WW * / PRINTER=raw # USER=YES # /* allow overrides * / EPARM='FORM=LACP1012' /* landscape */ Any thoughts on what might be causing this?
RSCS LPR won't autostart
I have 2 different RSCS links defined to the same physical LPR (HP 8150). One link is for landscape, one is for portrait (see definitions below). W hen I send a printout to the portrait queue, the link autostarts fine and the document is printed successfully. When I send the same printout to the landscape queue, I get DMTAXM101I File 7431 (7431) enqueued on link ROC815WL and the link never starts. I can stop/restart the link and the document will then print. I have other LPR's defined exactly the same way and they all autostart correctly on both landscape and portrait queues. When you mention you can stop/restart the link and the document prints fine, that implies the link state is not drained. What state is the link in? Can you trace this? Best Regards, Les Geer IBM z/VM and Linux Development
Re: RSCS LPR won't autostart
Here's the info: ROC815W is the portrait queue, ROC815WL is the landscape queue. sm rscs q sys link name roc815w Ready; Link Line Name Status Type Addr LU Name Logmode Queueing ROC815W inactive LPR ... ... priority 1 link found sm rscs q sys link name roc815wl Ready; Link Line Name Status Type Addr LU Name Logmode Queueing ROC815WL inactive LPR ... ... priority 1 link found sm rscs q roc815wl q Ready; Link ROC815WL inactive sending=0 receiving=0 queued=1 looping=0 held=0 Pos Loc Origin Destination in Q IDID Node Userid Node Userid Status 1 7435 7435 MVM1 BHENRROC815WL SYSTEM waiting 1 file found Is that what you mean by link STATE?
Re: RSCS LPR won't autostart
Yes inactive is the link state, which indicates RSCS never tried to start the link when a file was queue to it. Next, check if autostart is still defined on for the link Issue: sm rscstst1 q links node roc815wl show ast Best Regards, Les Geer IBM z/VM and Linux Development Here's the info: ROC815W is the portrait queue, ROC815WL is the landscape queue. sm rscs q sys link name roc815w Ready; Link Line Name Status Type Addr LU Name Logmode Queueing ROC815W inactive LPR ... ... priority 1 link found sm rscs q sys link name roc815wl Ready; Link Line Name Status Type Addr LU Name Logmode Queueing ROC815WL inactive LPR ... ... priority 1 link found sm rscs q roc815wl q Ready; Link ROC815WL inactive sending=0 receiving=0 queued=1 looping=0 held=0 Pos Loc Origin Destination in Q IDID Node Userid Node Userid Status 1 7435 7435 MVM1 BHENRROC815WL SYSTEM waiting 1 file found Is that what you mean by link STATE?
Re: RSCS: LPR page size
However, printouts can be produced in VSE in two different ways - via SYSLST (system logical unit) or a numbered SYS (e.g., SYS010 - program logical unit). STDOPT affects only SYSLST output. Ok... I found the problem. I was in fact using a numbered sys, which was assigned to a logical printer: // ASSGN SYS005,05E That printer had a * $$ LST card, with an FCB= option, which was defined with a 60 line page. I changed the FCB and the problem was fixed. Thank you all for your help and advice! Shimon -- ** ** Shimon Lebowitzmailto:[EMAIL PROTECTED] VM System Programmer . Israel Police National HQ. http://www.poboxes.com/shimonpgp Jerusalem, Israel phone: +972 2 542-9877 fax: 542-9308 ** **
Re: RSCS: LPR page size
To put it another way, if your program is using a program logical unit (a numbered SYS), STDOPT LINES= won't help. Thank you to Ron and Tom for your suggestions. The program on VSE is an Assembler utility writing to numbered SYS (I don't recall which right now). I was hoping for an easy way to specify lines/page, I will try Les's instructions today or tomorrow. Thanks! Shimon
Re: RSCS: LPR page size
Hi Shimon, If you are printing from CMS to a printer on RSCS (LPR or otherwise) and the CMS file doesn't contain carriage control, isn't CMS the one that is breaking it up into 60 line pieces? You would have to tell CMS it has an 80 line (or whatever) printer when it formats its output. On 3/26/07, Shimon Lebowitz [EMAIL PROTECTED] wrote: I am sending files via RSCS to be printed on an LPR link, without any carriage control. The link is defined with EXIT=LPRXONE. The printed output (on portrait mode paper) is only 60 lines per page. How can I control the page size (in lines) of an LPR link? I would like to increase it considerably. Is this possible when printing w/o CC? Using CC I have filled a page. Thanks! Shimon -- ** ** Shimon Lebowitzmailto:[EMAIL PROTECTED] VM System Programmer . Israel Police National HQ. http://www.poboxes.com/shimonpgp Jerusalem, Israel phone: +972 2 542-9877 fax: 542-9308 ** **
Re: RSCS: LPR page size
Shimon, Would the LINECOUNT parameter for the CMS PRINT command do what you want to do? On 3/26/07, Ron Schmiedge [EMAIL PROTECTED] wrote: Hi Shimon, If you are printing from CMS to a printer on RSCS (LPR or otherwise) and the CMS file doesn't contain carriage control, isn't CMS the one that is breaking it up into 60 line pieces? You would have to tell CMS it has an 80 line (or whatever) printer when it formats its output. On 3/26/07, Shimon Lebowitz [EMAIL PROTECTED] wrote: I am sending files via RSCS to be printed on an LPR link, without any carriage control. The link is defined with EXIT=LPRXONE. The printed output (on portrait mode paper) is only 60 lines per page. How can I control the page size (in lines) of an LPR link? I would like to increase it considerably. Is this possible when printing w/o CC? Using CC I have filled a page. Thanks! Shimon -- ** ** Shimon Lebowitzmailto:[EMAIL PROTECTED] VM System Programmer . Israel Police National HQ. http://www.poboxes.com/shimonpgp Jerusalem, Israel phone: +972 2 542-9877 fax: 542-9308 ** **
Re: RSCS: LPR page size
If you are printing from CMS to a printer on RSCS But I am not. My output is being generated on VSE and going via NJE to RSCS to be printed, using a DEST= parameter on the LST card. The printing itself is being done with NO page size control in the application, just keep spewing out the lines till it's done. Thanks, Shimon
Re: RSCS: LPR page size
If you are printing from CMS to a printer on RSCS But I am not. My output is being generated on VSE and going via NJE to RSCS to be printed, using a DEST= parameter on the LST card. The printing itself is being done with NO page size control in the application, just keep spewing out the lines till it's done. You need to define a PCL command (via the link PREFIX string) to tell the printer how many lines/page for the print output. Remember to use the suffix string to reset the printer for the next print out. Best Regards, Les Geer IBM z/VM and Linux Development
Re: RSCS: LPR page size
The printing itself is being done with NO page size control in the application, just keep spewing out the lines till it's done. You need to define a PCL command (via the link PREFIX string) to tell the printer how many lines/page for the print output. Remember to use the suffix string to reset the printer for the next print out. Les, Does this mean that the pages stopping at 60 lines is being done by the printer itself, and not by RSCS? Thank you, Shimon
Re: RSCS: LPR page size
Hi Shimon, You've tried using // STDOPT LINES=nn in your job to change the default number of lines on the page for your job? On 3/26/07, Shimon Lebowitz [EMAIL PROTECTED] wrote: The printing itself is being done with NO page size control in the application, just keep spewing out the lines till it's done. You need to define a PCL command (via the link PREFIX string) to tell the printer how many lines/page for the print output. Remember to use the suffix string to reset the printer for the next print out. Les, Does this mean that the pages stopping at 60 lines is being done by the printer itself, and not by RSCS? Thank you, Shimon
Re: RSCS: LPR page size
From what's been written, I presume that the carriage control that VSE uses would be preserved if it existed. Using // STDOPT LINES= is a way to influence VSE's production of carriage control characters. However, printouts can be produced in VSE in two different ways - via SYSLST (system logical unit) or a numbered SYS (e.g., SYS010 - program logical unit). STDOPT affects only SYSLST output. To complicate matters even further, if your program is a COBOL program and is using DISPLAY (UPON SYSLST) then there will be no page breaks, regardless of STDOPT LINES. Ordinarily reports aren't written with DISPLAY, but it has been done. To put it another way, if your program is using a program logical unit (a numbered SYS), STDOPT LINES= won't help. The only way you can control the page breaks from the VSE side is from within your program. - Tom. At 03:27 PM 3/26/2007, you wrote: Hi Shimon, You've tried using // STDOPT LINES=nn in your job to change the default number of lines on the page for your job? Tom Cluster County of Sonoma Santa Rosa, CA (707) 565-3384 (Tuesdays and Wednesdays only)
Re: RSCS: LPR page size
The printing itself is being done with NO page size control in the application, just keep spewing out the lines till it's done. You need to define a PCL command (via the link PREFIX string) to tell the printer how many lines/page for the print output. Remember to use the suffix string to reset the printer for the next print out. Les, Does this mean that the pages stopping at 60 lines is being done by the printer itself, and not by RSCS? Well, RSCS is not counting lines for LPR printers. It will generate form feeds if the (any) control characters in the print job request such. Do you know if the VSE job contains CC? If not, then the printer is determining lines per page. In either case, RSCS is not. Best Regards, Les Geer IBM z/VM and Linux Development
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
Re: Stuck RSCS LPR printers procedure
Hi Mike, Don't do use a START command. It will process the queued files, then ignore any subsequent arrivals. Instead do a DEFINE printerid ASTART. This will start the printer for all currently queued file, and leave it ready to process new arrivals. 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.
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.
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
Re: Stuck RSCS LPR printers procedure
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.
Re: Stuck RSCS LPR printers procedure
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
Re: Stuck RSCS LPR printers procedure
Hi Mike, That's it. Nice and simple (like me). Peter -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Horlick, Michael Sent: February 7, 2007 12:04 To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Stuck RSCS LPR printers procedure 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. 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.
Stuck RSCS LPR printers procedure
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. Please see url: http://www.vm.ibm.com/related/rscs/lprsetup.html Especially step 11, advanced topics, item 3. How to avoid hung LPR links using the TIMEOUT= and FILEHOLD= parameters, in conjunction with a notify link and RSCS events. FYI, see the z/VM 5.3 RFA for a new Function Level (530) of RSCS as a priced feature of z/VM with IPLA pricing. Best Regards, Les Geer IBM z/VM and Linux Development
Re: RSCS LPR Printer Name w/spaces
Here is my solution to send print from RSCS to a Windows printer named: 'eSCRIP-SAFE Printer on https://x.xxx-.us/printers/default' I have determined the the real printer name on Windows is eSCRIP-SAFE Printer and does not include the URL that it is printing to. I have also determined that RSCS truncates the PRINTER= name at the first space. It doesn't matter whether the printer name is enclosed in single quotes: PRINTER='ESCRIP-SAFE Printer' This is correct according to Alan Altmark who wrote to me: However, using blanks in LPR queue names violates RFC 1179 (LPR), since blanks are significant to the protocol for 'query' and 'remove' functions. The vendor and I have tried to change the .inf file for installation to not have an embedded space. It seemes that Windows XP SP2 is adding the word Printer to the name. So my solution is to use a third party LPD program called RPM (Remote Print Manager) from Brooks Internet Software: http://www.brooksnet.com/ This LPD server allows me to use my own name for the receiving queue so I chose TRANSCRIPT. RPM then prints to any Windows printer no matter how it is named. /Fran Hensler at Slippery Rock University of Pennsylvania USA for 43 years [EMAIL PROTECTED] +1.724.738.2153 Yes, Virginia, there is a Slippery Rock -- On Tue, 12 Dec 2006 11:54:31 EST Fran Hensler said: I have set up an RSCS LPR link that prints to a Hummingbird LPD server on a PC. The PRINTER name has no spaces and is 27 characters. This is working just fine. Now I want to do the same thing but the printer name has embedded spaces. When I click on properties for the printer I do not get an option to rename the printer. It is a network printer. I enclosed the printer name in single quotes but I get a NAK when I try to print to it. PRINTER='eSCRIP-SAFE Printer on https://x.xxx-.us/printers/default' Does anyone know how I could either rename this printer to remove spaces or how to make RSCS print to printer name with embedded spaces. /Fran Hensler at Slippery Rock University of Pennsylvania USA for 43 years [EMAIL PROTECTED] +1.724.738.2153 Yes, Virginia, there is a Slippery Rock
Re: RSCS LPR Printer Name w/spaces
Fran Hensler wrote: I enclosed the printer name in single quotes but I get a NAK when I try to print to it. PRINTER='eX- Printer on https://xxx.xx-.us/printers/default' Does anyone know how I could either rename this printer to remove spaces or how to make RSCS print to printer name with embedded spaces. On Tue, 12 Dec 2006 12:14:37 -0500 David Boyes said: Have the machine that has access to the printer share it as a name that does not have spaces in it. The Windows LPD will honor shared names as well as the original name. David - Your solution worked great when testing on a local network printer but when I tried to share the IPP printer I got this message Sharing is not supported for this type of printer I tried creating a short cut but that doesn't work either. So I'm going to try and get the vendor to change the spaces in the printer name to underscores. I might also open a PMR and ask IBM to support printer names with embedded spaces in the name. /Fran Hensler at Slippery Rock University of Pennsylvania USA for 43 years [EMAIL PROTECTED] +1.724.738.2153 Yes, Virginia, there is a Slippery Rock
Re: RSCS LPR Printer Name w/spaces
On Thursday, 12/14/2006 at 08:36 EST, Fran Hensler [EMAIL PROTECTED] wrote: Your solution worked great when testing on a local network printer but when I tried to share the IPP printer I got this message Sharing is not supported for this type of printer I tried creating a short cut but that doesn't work either. So I'm going to try and get the vendor to change the spaces in the printer name to underscores. I might also open a PMR and ask IBM to support printer names with embedded spaces in the name. While you get it straightened out, you can use TCPSNIFF (VM download library?) to act as an LPR proxy, changing RSCS-specifed underscores to blanks on the way to the printer. However, using blanks in LPR queue names violates RFC 1179 (LPR), since blanks are significant to the protocol for 'query' and 'remove' functions. Alan Altmark z/VM Development IBM Endicott
RSCS LPR Printer Name w/spaces
I have set up an RSCS LPR link that prints to a Hummingbird LPD server on a PC. The PRINTER name has no spaces and is 27 characters. This is working just fine. Now I want to do the same thing but the printer name has embedded spaces. When I click on properties for the printer I do not get an option to rename the printer. It is a network printer. I enclosed the printer name in single quotes but I get a NAK when I try to print to it. PRINTER='eX- Printer on https://xxx.xx-.us/printers/default' Does anyone know how I could either rename this printer to remove spaces or how to make RSCS print to printer name with embedded spaces. /Fran Hensler at Slippery Rock University of Pennsylvania USA for 43 years [EMAIL PROTECTED] +1.724.738.2153 Yes, Virginia, there is a Slippery Rock
Re: RSCS LPR Printer Name w/spaces
I enclosed the printer name in single quotes but I get a NAK when I try to print to it. PRINTER='eX- Printer on https://xxx.xx- .us/printers/default' Does anyone know how I could either rename this printer to remove spaces or how to make RSCS print to printer name with embedded spaces. Have the machine that has access to the printer share it as a name that does not have spaces in it. The Windows LPD will honor shared names as well as the original name.
Re: RSCS LPR Printer Name w/spaces
I enclosed the printer name in single quotes but I get a NAK when I try to print to it. PRINTER='eX- Printer on https://xxx.xx- .us/printers/default' Does anyone know how I could either rename this printer to remove spaces or how to make RSCS print to printer name with embedded spaces. Have the machine that has access to the printer share it as a name that does not have spaces in it. The Windows LPD will honor shared names as well as the original name. Did you trace the RSCS link to see what was actually sent as the printer queue name? Did it include the entire string with the start/end quote? Best Regards, Les Geer IBM z/VM and Linux Development
Re: RSCS LPR Printer Name w/spaces
Fran Hensler wrote: Does anyone know how I could either rename this printer to remove spaces or how to make RSCS print to printer name with embedded spaces. On Tue, 12 Dec 2006 12:14:37 -0500 David Boyes said: Have the machine that has access to the printer share it as a name that does not have spaces in it. The Windows LPD will honor shared names as well as the original name. David - Your solution works great. Thank you. /Fran Hensler at Slippery Rock University of Pennsylvania USA for 43 years [EMAIL PROTECTED] +1.724.738.2153 Yes, Virginia, there is a Slippery Rock
Re: RSCS LPR Printer Name w/spaces
Your solution works great. Thank you. You're welcome. Side note, though: that's an IPP-driven printer...8-) Remember to vote yes to add IPP support for RSCS in the next requirements go-round at your favorite user group.
