I think you are correct Rob, an application program (ie WAKEUP) must establish it's ability to receive SMSG's before anyone can send one. Just setting SMSG ON is not enough.
-----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] Behalf Of RPN01 Sent: Friday, December 05, 2008 11:34 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SMSG Authorization Wouldn't the EREP program actually have to be waiting and understand SMSG messages, otherwise, what do you expect it to do with the message once received? Of course, I could be blowing smoke, and EREP does indeed have features to do this that I'm unaware of or have forgotten. (Getting old is such a pain...) -- Robert P. Nix Mayo Foundation .~. RO-OE-5-55 200 First Street SW /V\ 507-284-0844 Rochester, MN 55905 /( )\ ----- ^^-^^ "In theory, theory and practice are the same, but in practice, theory and practice are different." On 12/5/08 11:26 AM, "Howard Rifkind" <[EMAIL PROTECTED]> wrote: I'm trying to SMSG the EREP guest and although I have set SMSG on the command comes back stating that the EREP guest isn't authorized. Is there anyway around this to get EREP authorized for SMSG? Will IUCV do it? so I can get EREP to execute a REXX exec from a command issued from a different virtual machine guest. Thanks. _____________ LEGAL NOTICE Unless expressly stated otherwise, this message is confidential and may be privileged. It is intended for the addressee(s) only. Access to this E-mail by anyone else is unauthorized. If you are not an addressee, any disclosure or copying of the contents of this E-mail or any action taken (or not taken) in reliance on it is unauthorized and may be unlawful. If you are not an addressee, please inform the sender immediately, then delete this message and empty from your trash.
