Most sockets programming is done in C -- and it should perform well. I've never even seen sockets code in assembler. Of course, if you don't have a C compiler...
It might be better to start in REXX, and if the performance isn't accepta ble, then rewrite in C or Assembler. REXX is really good for prototyping. With a REXX compiler, it can even perform acceptably. (Just stay away from REXX level 2 I/O.) On Tue, 21 Mar 2006 15:03:27 -0500, Steve Gentry <[EMAIL PROTECTED] tteLife.com> wrote: >Nobody has written a little 4K assembler program to do this, huh? Geeez . >8-) >Seriously, thanks for the replies. I will pass the info on to the >programmer and see >what he wants to do. I like to code in Rexx to, but there is a >performance issue >with this one. Not that Rexx is bad ( and not wishing to start a flame >war). > >Steve G. > > > > > >Dave Jones <[EMAIL PROTECTED]> >Sent by: The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU> >03/21/2006 02:53 PM >Please respond to The IBM z/VM Operating System > > > To: IBMVM@LISTSERV.UARK.EDU > cc: > Subject: Re: VM, assembler and SOCKETS > > >Hi, Steve. > >First, thanks for clarifying your requirements...... > >Since you've already done some sockets programming (in Rexx), this will >be very similar. > >There are a couple of socket APIs available on CMS, if you don't want to >use the Rexx sockets function package (Adam and I like it, 'cause we >just like to code in Rexx; but your performance requirements may >precludes that...). You can: > >1) use the OpenExtensions (I think that's today's name) callable >services from Assembler to work with sockets. >2) use the Reusable Server Kernel tool, which supports the development >of very hight performance TCP/IP based servers, again in assembler. >3) use the LE callable socket functions from a HLL like COBOL. > >Good luck. > >DJ > >
