Suggestion time. My auditors always had me use two different userids. My primary only had 'normal' access while my secondary user had full class-A access and was the one listed in RSCS, etc. as an authorized user. (I was the System's Programming manager in a small shop and my duties included being the security manager also.) The auditor received a report of any logons to that ID so I had to log what function I performed using that userid. Just like not giving root access to your normal linux id.
Anyway, you might want to set up a secondary userid for yourself and such a userid could have been used to pull back the RSCS messages. Tony Thigpen -----Original Message ----- From: Schuh, Richard Sent: 08/12/2010 04:18 PM > Having the operator do anything other than a simple START, including "PARM > anything" requires an approval process. That said, a scan of the config file > reveals that an id that rarely logs on is authorized. I will use it as my > surrogate. Thanks for the idea. > > Regards, > Richard Schuh > > > >> -----Original Message----- >> From: The IBM z/VM Operating System >> [mailto:ib...@listserv.uark.edu] On Behalf Of Tony Thigpen >> Sent: Thursday, August 12, 2010 1:02 PM >> To: IBMVM@LISTSERV.UARK.EDU >> Subject: Re: RSCS Messages >> >> Force it back to operator by stoping/starting the link from operator. >> >> Based on what I have seen, if the user logs off *AND* RSCS >> tries to send another message while the user is logged off, >> then it reverts back to the operator automatically. >> >> Tony Thigpen >> >> -----Original Message ----- >> From: Schuh, Richard >> Sent: 08/12/2010 12:12 PM >>> 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 to 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 >>> >>> >>> >> > >
