× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



IBM's IFS Introduction manual says,

"If your application is using the "root" (/) file system, you can take
advantage of the IFS local socket support.  A local socket object (object
type *SOCKET) allows two jobs running on the same system to establish a
communications connection with each other.  One of the jobs establishes a
connection point by using the bind() C language function to create a local
socket object.  The other job specifies the name of the local socket object
on the connect(), sendto(), or sendmsg() function.  The local socket object
remains in the system until it is removed using the unlink() function or
the Remove Link command."

I don't see where bind(), connect() etc. receive object names instead of
port numbers.  When I execute a bind(), there are no journal entry type
'CO' (create object) that go into QAUDJRN.   Where and when are the sockets
created I wonder?  Using the MATAUOBJ instruction, I found some *SOCKET
objects owned by QSYS profile but with creation time of our last IPL.  Can
someone explain the IFS Introduction quote?


+---
| This is the MI Programmers Mailing List!
| To submit a new message, send your mail to MI400@midrange.com.
| To subscribe to this list send email to MI400-SUB@midrange.com.
| To unsubscribe from this list send email to MI400-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: dr2@cssas400.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.