*** Reply to note of Tue, 21 Mar 2006 14:39:51 -0500 (EST/CDT) *** by [email protected]
You could use a Co-pipeline from assembler and let CMS Pipelines do all the dirty work. Sal Steve Gentry <[EMAIL PROTECTED]> writes: >This is a multipart message in MIME format. >--=_alternative 006C064505257138_= >Content-Type: text/plain; charset="us-ascii" > >RXSockets: I'd say about 95% of our apps are written in assembler and >DMS. The user would run a green-screen app. entering the >necessary data. This data would then be sent to the WAS Intel box. The >info processed and returned back to VM to be displayed >on the green-screen. I don't think DMS is Rexx friendly. <g>. > > > > > >Adam Thornton <[EMAIL PROTECTED]> >Sent by: The IBM z/VM Operating System <[email protected]> >03/21/2006 02:27 PM >Please respond to The IBM z/VM Operating System > > > To: [email protected] > cc: > Subject: Re: VM, assembler and SOCKETS > > >On Mar 21, 2006, at 1:23 PM, Steve Gentry wrote: > >> >> Communicate: Well, that's the issue. That's one of the things I >> need guidance on. >> The application would run on VM and request the information from a >> WAS server running on Intel. >> That information would then be returned to the VM app. >> I assumed they would communicate via TCPIP >> I've done this using Rexx sockets but in the other direction. i.e. >> I have an app. running on an http server running on Linux (running >> on an IFL running VM) >> using hipersockets, etc. >> It requests info from VM, sends it back and displays it on a web >> page. But remember, I'd really like to avoid using Rexx sockets. >> If it is >> absolutely the only way to do it, then so be it. >> > >Yeah, if they're running on different boxes (it was not clear that >WAS wasn't running on z/Linux on the same box or under the same VM >instance in your original problem formulation) TCP is the obvious >choice. > >I'm sure assembler interfaces to sockets exist and work just fine, >but why not RXSockets? It's way, way easier than any alternative >that I'm aware of. > >Adam > > > >--=_alternative 006C064505257138_= >Content-Type: text/html; charset="us-ascii" > > ><br><font size=2 face="sans-serif">RXSockets: I'd say about 95% of our >apps are written in assembler and DMS. The user would run a > green-screen app. entering the </font> ><br><font size=2 face="sans-serif">necessary data. This data would then >be sent to the WAS Intel box. The info processed and returned back to VM >to be displayed</font> ><br><font size=2 face="sans-serif">on the green-screen. I don't think >DMS is Rexx friendly. <g>.</font> ><br> ><br> ><br> ><br> ><table width=100%> ><tr valign=top> ><td> ><td><font size=1 face="sans-serif"><b>Adam Thornton ><[EMAIL PROTECTED]></b></font> ><br><font size=1 face="sans-serif">Sent by: The IBM z/VM Operating System ><[email protected]></font> ><p><font size=1 face="sans-serif">03/21/2006 02:27 PM</font> ><br><font size=1 face="sans-serif">Please respond to The IBM z/VM Operating >System</font> ><br> ><td><font size=1 face="Arial"> </font> ><br><font size=1 face="sans-serif"> To: > [email protected]</font> ><br><font size=1 face="sans-serif"> cc: > </font> ><br><font size=1 face="sans-serif"> Subject: > Re: VM, assembler and SOCKETS</font></table> ><br> ><br> ><br><font size=2 face="Courier New">On Mar 21, 2006, at 1:23 PM, Steve Gentry >wrote:<br> ><br> >><br> >> Communicate: Well, that's the issue. That's one of the things >I <br> >> need guidance on.<br> >> The application would run on VM and request the information from a > <br> >> WAS server running on Intel.<br> >> That information would then be returned to the VM app.<br> >> I assumed they would communicate via TCPIP<br> >> I've done this using Rexx sockets but in the other direction. i.e. ><br> >> I have an app. running on an http server running on Linux (running > <br> >> on an IFL running VM)<br> >> using hipersockets, etc.<br> >> It requests info from VM, sends it back and displays it on a web > <br> >> page. But remember, I'd really like to avoid using Rexx sockets. > <br> >> If it is<br> >> absolutely the only way to do it, then so be it.<br> >><br> ><br> >Yeah, if they're running on different boxes (it was not clear that <br> >WAS wasn't running on z/Linux on the same box or under the same VM <br> >instance in your original problem formulation) TCP is the obvious <br> >choice.<br> ><br> >I'm sure assembler interfaces to sockets exist and work just fine, <br> >but why not RXSockets? It's way, way easier than any alternative > <br> >that I'm aware of.<br> ><br> >Adam<br> ></font> ><br> ><br> >--=_alternative 006C064505257138_=--
