RE: Non-blocking I/O in sockets program

[Tim McCarthy <timm@xxxxxxxxxxxx>]

You can execute the FIONBIO anytime after you have the socket...whenever
you want to switch blocking off. If you unblock before the connect then
of course you must expect to get an "in progress" returned and you'll
have to retry eventually. Perform FIONBIO after the connect and you
won't have to worry about that. That said however, posing that question
you make me ask why you're using unblocked operations? Your code will be
a whole lot more complicated this way. 

TrailBlazer Systems, Inc.
http://www.as400ftp.com
AS/400 Communications & E-Commerce Solutions

Chaos, panic and disorder...my work here is done.

> -----Original Message-----
> From: York, Albert [SMTP:albert.york@nissan-usa.com]
> Sent: Friday, March 10, 2000 5:16 PM
> To:   'MIDRANGE-L@midrange.com'
> Subject:      RE: Non-blocking I/O in sockets program
> 
> Thanks. 
> 
> I can translate that to RPG.
> 
> Do you execute the call before or after you CONNECT to the socket?
> 
> Albert
> 
> > -----Original Message-----
> > From:       Tim McCarthy [SMTP:timm@as400ftp.com]
> > Sent:       Friday, March 10, 2000 12:44 PM
> > To: 'MIDRANGE-L@midrange.com'
> > Subject:    RE: Non-blocking I/O in sockets program
> > 
> > Well in C it would be 
> > int sd, rc, on=1;
> > rc = ioctl(s, FIONBIO, &on);
> > 
> > TrailBlazer Systems, Inc.
> > http://www.as400ftp.com
> > AS/400 Communications & E-Commerce Solutions
> > 
> > Chaos, panic and disorder...my work here is done.
> > 
> > > -----Original Message-----
> > > From:     York, Albert [SMTP:albert.york@nissan-usa.com]
> > > Sent:     Friday, March 10, 2000 12:31 AM
> > > To:       'MIDRANGE-L@midrange.com'
> > > Subject:  Non-blocking I/O in sockets program
> > > 
> > > I'm trying to write an RPG  sockets program and I can't find the
> > > correct way
> > > to use the ioctl or fcntl function to set the socket descriptor
> for
> > > non-blocking I/O.
> > > 
> > > Does anyone have an example that they can share? 
> > > 
> > > +---
> > > | This is the Midrange System Mailing List!
> > > | To submit a new message, send your mail to
> MIDRANGE-L@midrange.com.
> > > | To subscribe to this list send email to
> MIDRANGE-L-SUB@midrange.com.
> > > | To unsubscribe from this list send email to
> > > MIDRANGE-L-UNSUB@midrange.com.
> > > | Questions should be directed to the list owner/operator:
> > > david@midrange.com
> > > +---
> > +---
> > | This is the Midrange System Mailing List!
> > | To submit a new message, send your mail to
> MIDRANGE-L@midrange.com.
> > | To subscribe to this list send email to
> MIDRANGE-L-SUB@midrange.com.
> > | To unsubscribe from this list send email to
> > MIDRANGE-L-UNSUB@midrange.com.
> > | Questions should be directed to the list owner/operator:
> > david@midrange.com
> > +---
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to
> MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
> david@midrange.com
> +---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---