Here is a little EXEC I use: /* */
trace Off smsg RSCS drain ZVMUAFC sleep 2 sec smsg RSCS delete ZVMUAFC sleep 2 sec 'smsg rscs define ZVMUAFC TYPE TCPNJE Q PRI NODE ZVMUAFC DP 5 CL * ASTART RETRY' sleep 2 sec 'smsg RSCS start ZVMUAFC PARM STREAMS=2 BUFF=8192 COMP=MAX ITO=100 OPT=YES MAXD=10 TCP=TCPIP02 HOST=192.168.75.191' EXit Thank you, Scott -----Original Message----- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Schuh, Richard Sent: Thursday, August 12, 2010 1:50 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: RSCS Messages Had to change an IP address while the system was up. It normally is ASTART but that would not work in this case, it would go to the address in the config file when RSCS started. I guess I will look for an opportune moment and recycle RSCS. Regards, Richard Schuh > -----Original Message----- > From: The IBM z/VM Operating System > [mailto:ib...@listserv.uark.edu] On Behalf Of peter.w...@ttc.ca > Sent: Thursday, August 12, 2010 11:42 AM > To: IBMVM@LISTSERV.UARK.EDU > Subject: Re: RSCS Messages > > Then don't start a link, define it with autostart. We do this > from time to time here, with no unwanted messages. Example: > > SMSG RSCS STOP PRT577 > SMSG RSCS DEFINE PRT577 ASTART > > This actually works better then a STOP/START combination > because with START the link will process any queued work, > then stop. It will need another START when more work arrives. > With ASTART, it will process the currently queued work PLUS > anything that comes later. > > Peter > > -----Original Message----- > From: The IBM z/VM Operating System > [mailto:ib...@listserv.uark.edu] On Behalf Of Schuh, Richard > Sent: August 12, 2010 14:29 > To: IBMVM@LISTSERV.UARK.EDU > Subject: Re: RSCS Messages > > Logging off has no effect - messages resume as soon as the > user logs back on. However, logging RSCS off and back on > would work :-) I get the same response to the SET LINK NOMSG > as to the SETMSG command. > > Regards, > Richard Schuh > > > > > -----Original Message----- > > From: The IBM z/VM Operating System > > [mailto:ib...@listserv.uark.edu] On Behalf Of Dale R. Smith > > Sent: Thursday, August 12, 2010 10:51 AM > > To: IBMVM@LISTSERV.UARK.EDU > > Subject: Re: RSCS Messages > > > > On Thu, 12 Aug 2010 09:12:27 -0700, Schuh, Richard > <rsc...@visa.com> > > wrot= > > e: > > > > >When a user starts a link via SMSG command, it becomes a > > special pal of > > >= > > > > RSCS and receives messages about that link forever or until RSCS is > > recycled, whichever comes first. Is there any other way of causing > > RSCS t= o quit sending the messages? I tried the SETMSG ALL OFF > > command and found = > > > > out that I was not subscribed for any messages :-( > > > > > > > > >Regards, > > >Richard Schuh > > > > > > > Have you tried: SMSG RSCS SET linkid NOMSG ? > > I think logging off/on the user getting the messages will stop them > > also.= > > > > > > -- > > Dale R. Smith > > > > > 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. > Confidentiality Note: This e-mail, including any attachment to it, may contain material that is confidential, proprietary, privileged and/or "Protected Health Information," within the meaning of the regulations under the Health Insurance Portability & Accountability Act as amended. If it is not clear that you are the intended recipient, you are hereby notified that you have received this transmittal in error, and any review, dissemination, distribution or copying of this e-mail, including any attachment to it, is strictly prohibited. If you have received this e-mail in error, please immediately return it to the sender and delete it from your system. Thank you.
