Nothing has changed for quite a while.

With GETSOCKNAME, the first output record is a 16-byte sockaddr_in structure
returned by bind().  This is documented with the description of the option,
but I should also document that format in the Output Record Format section.
Thanks for the reminder.

I cannot see any SPECS in the TCPLISTEN article I wrote.  You did say PIPE
AHELP TCPLISTEN, right?  And you did get the latest HELPLIB from Marist?
(Yes, Will wrote a bit of fiction in HELP PIPE TCPLISTEN, though it looks as
if he cut'n'pasted most of it from the AHELP.)

If you get EADDRINUSE issue NETSTAT ALLCONN to see what state the port is
in.

   j.

On 26 February 2010 01:46, Ian S. Worthington <[email protected]>wrote:

> This is what I've found:
>
> 1. The first record emited by tcplisten getsockname has a different format
> from the others.
>
> 2. The only documentation appears to be in the help pipe tcplisten, which
> is
> slighty wrong:
>
> specs 14 c2d 1
>
> should be
>
> specs 1.4 c2d 1
>
> 3. Although this sample server doesn't stop after processing a client
> request
> it has to be manually stopped/started: the second invocation of the clients
> returns EADDRINUSE -- not sure why yet.
>
> i
>
>
> ------ Original Message ------
> Received: 12:51 PM COT, 02/25/2010
> From: "Ian S. Worthington" <[email protected]>
> To: "CMS Pipelines" <[email protected]>
> Subject: Fwd: tcplisten output record not as defined in help?
>
> > The record output from tcplisten doesn't seem to be as defined in the
> help
> > text, nor wors with the ISONSRV example.
> >
> > Has it been changed?
> >
> >
> > pipe tcplisten 0     getsockname | console  | specs 1-* c2x 1 | console
> >    "
> > 0002107F000000000000000000000000
> >
> > ian
> > .
> > Ian S. Worthington, MBCS
> >
> >
> >
>

Reply via email to