|
Scott, Thanks. I'll check out the articles. What bothers me is this logic has worked for the past couple of years. Just recently did the problem start. Mark message: 3 date: Tue, 12 Dec 2006 12:41:57 -0600 (CST) from: Scott Klement <rpg400-l@xxxxxxxxxxxxxxxx> subject: Re: Socket Server Error - Give Descriptor Error
GiveDescriptor(): The value specified for the argument is not correct.
The following is quoted from the Information Center page for the givedescriptor() API: This error code indicates one of the following: * The target_job parameter points to data that is not valid. * The target_job parameter refers to a job that is not active.
I have this same process running on two systems. It works fine on one system but the listener job will end once or twice a day on the other system.
Consider using the spawn() API instead of the icky givedescriptor() API. Or use inetd and eliminate the bind/listen/accept logic entirely. The following articles describe these techniques. Both articles do require a membership in the System iNetwork to read, but a free ("Associate") membership is sufficient: TCP/IP Server Programming (the example of the spawn() API is in the code download): http://www.systeminetwork.com/article.cfm?id=51809 An Easier Way to Write a TCP/IP Server Program http://www.systeminetwork.com/article.cfm?id=53182
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.