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:[email protected]] On
Behalf Of Schuh, Richard
Sent: August 12, 2010 14:29
To: [email protected]
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:[email protected]] On Behalf Of Dale R. Smith
> Sent: Thursday, August 12, 2010 10:51 AM
> To: [email protected]
> Subject: Re: RSCS Messages
> 
> On Thu, 12 Aug 2010 09:12:27 -0700, Schuh, Richard 
> <[email protected]> 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.

Reply via email to