You could use Rexx's IUCV support. Advantage (one reason why I started using it instead of SMSG/MSG): it can transfer large amounts of data. It is not too complicated. You can also use the CMS Multitasking queues. Brian Wade's web page has sample execs: http://www.vm.ibm.com/download/packages/descript.cgi?IPCSAMP Very easy and indeed synchronous if you want.
Why did I use RxIUCV then: well, our server had to be able to wait for various event. Both RxIUCV and the multitasking queues can somehow live alongside WAKEUP. 2008/12/11 Alan Altmark <[email protected]> > On Thursday, 12/11/2008 at 09:48 EST, Colin Allinson > <[email protected]> wrote: > > I am working with a Web CGI script and need to request information off > another > > Virtual machine and get a synchronous response back (eg: in a PIPE). > : > > I am convinced that I am missing something very obvious - but I cannot > think > > what. > > You aren't missing anything. Any time you choose to build a client-server > architecture that depends on remote command execution, you're asking for > problems. REXEC solves that problem, but introduces others. The SMSG > case assumes that the target server is enabled for SMSG communications. > Good news: If it is, and it's a server of your creation, then that logic > can be modified to deal with a more program-oriented connection as well. > Let the PIPE be issued in the *server* and the results streamed back to > the client. > > But comand output to a terminal is a naturally asynchronous event, so > everything that captures command output from outside the virtual machine > will be asynchronous. > > One exception: the CP FOR command. If you want to issue a CP command as > though you were another virtual machine sync, CP FOR will do it for you. > I.e. it can replace CP SEND CP. > > Alan Altmark > z/VM Development > IBM Endicott > -- Kris Buelens, IBM Belgium, VM customer support
