So... where does the command issuer run... e.g. as a TSO user, as a batch job, other?
If they have the proper privilege on z/OS, they could issue the JES2 command: $Nn#;nodename userid 'message text here' Where the '#' is the JES2 node number of your target z/VM system. The message would appear at the target as a message sent by RSCS (which can easily be trapped by PROP or other automation tools). We've used that technique for years here in a sort of cludge. A home-built VM:Operator "RO VMOPER" macro accepts a command for z/OS, sends the command via RSCS over NJE to z/OS (CP SMSG RSCS MSG mvs_nodename SYSTEM arguments), where they are trapped by z/OS automation, tested for authorization, executed as a z/OS operator command (NETVIEW is heavily involved), and the command responses trapped and sent back to z/VM using the $NM# command as a if they were a rexx stem. The "RO VMOPER" macro had been waiting for the reply, traps the "stem", and does what it is told to do. Someday we'll get a "round tuit" and re-write that cludge to use something more modern (like rexx sockets perhaps). Mike Walter Aon Corporation The opinions expressed herein are mine alone, not my employer's. "Hughes, Jim" <jim.hug...@doit.nh.gov> Sent by: "The IBM z/VM Operating System" <IBMVM@LISTSERV.UARK.EDU> 06/06/2011 01:09 PM Please respond to "The IBM z/VM Operating System" <IBMVM@LISTSERV.UARK.EDU> To IBMVM@LISTSERV.UARK.EDU cc Subject Re: Sending messages to z/OS from z/VM using RSCS I am looking for something which sends a message our z/VM prop machine which in turn executes a rexx procedure. ____________________ Jim Hughes Consulting Systems Programmer Mainframe Technical Support Group Department of Information Technology State of New Hampshire 27 Hazen Drive Concord, NH 03301 603-271-5586 Fax 603.271.1516 Statement of Confidentiality: The contents of this message are confidential. Any unauthorized disclosure, reproduction, use or dissemination (either whole or in part) is prohibited. If you are not the intended recipient of this message, please notify the sender immediately and delete the message from your system. ==>-----Original Message----- ==>From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On ==>Behalf Of Mike Walter ==>Sent: Monday, June 06, 2011 2:06 PM ==>To: IBMVM@LISTSERV.UARK.EDU ==>Subject: Re: Sending messages to z/OS from z/VM using RSCS ==> ==>Jim, ==> ==>From TSO you can use: XMIT (or TRANSMIT) node.userid ==>That places you into EDIT on a file permitting multiple lines to be ==>entered, after which you press PF3 to send the file. ==>The message appears as a reader file on the node.userid on the target VM ==>system. ==> ==> ==>See: ==>http://publib.boulder.ibm.com/infocenter/zos/v1r11/index.jsp?topic=/c om.i ==>bm.zos.r11.ikjc500/transsyn.htm ==>If there's some other need not met by that link feel free to ask. ==> ==>Mike Walter ==>Aon Corporation ==>The opinions expressed herein are mine alone, not my employer's. ==> ==> ==> ==> ==>"Hughes, Jim" <jim.hug...@doit.nh.gov> ==> ==>Sent by: "The IBM z/VM Operating System" <IBMVM@LISTSERV.UARK.EDU> ==>06/06/2011 11:40 AM ==>Please respond to ==>"The IBM z/VM Operating System" <IBMVM@LISTSERV.UARK.EDU> ==> ==> ==> ==>To ==>IBMVM@LISTSERV.UARK.EDU ==>cc ==> ==>Subject ==>Sending messages to z/OS from z/VM using RSCS ==> ==> ==> ==> ==> ==> ==>I am able to send messages to a z/OS TSO userid using the RSCS command ==>MSG from z/VM. ==> ==>How would the TSO userid send a message to me on the z/VM node? ==> ==>z/VM node is DIS3081. Z/OS node is MVSSYS. ==> ==>Would the z/OS TSO userid be able to issue commands to the z/VM system ==>or would PROP be involved? ==> ==>TIA ==> ==>____________________ ==>Jim Hughes ==>Consulting Systems Programmer ==>Mainframe Technical Support Group ==>Department of Information Technology ==>State of New Hampshire ==>27 Hazen Drive ==>Concord, NH 03301 ==>603-271-5586 Fax 603.271.1516 ==> ==>Statement of Confidentiality: The contents of this message are ==>confidential. Any unauthorized disclosure, reproduction, use or ==>dissemination (either whole or in part) is prohibited. If you are not ==>the intended recipient of this message, please notify the sender ==>immediately and delete the message from your system. ==> ==> ==> ==> ==> ==> ==>The information contained in this e-mail and any accompanying documents ==>may contain information that is confidential or otherwise protected from ==>disclosure. If you are not the intended recipient of this message, or if ==>this message has been addressed to you in error, please immediately alert ==>the sender by reply e-mail and then delete this message, including any ==>attachments. Any dissemination, distribution or other use of the contents ==>of this message by anyone other than the intended recipient is strictly ==>prohibited. All messages sent to and from this e-mail address may be ==>monitored as permitted by applicable law and regulations to ensure ==>compliance with our internal policies and to protect our business. E- ==>mails are not secure and cannot be guaranteed to be error free as they ==>can be intercepted, amended, lost or destroyed, or contain viruses. You ==>are deemed to have accepted these risks if you communicate with us by e- ==>mail. The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail.
