P.S., in the networking world, it is called a port number. On Wed, Sep 25, 2013 at 9:24 PM, Anthony Thompson <[email protected]> wrote: > A socket descriptor (which seems to be a fancy name for a number) is 4 bytes. > > The output of BPX1SOC includes a 'socket vector', where the socket descriptor > is returned, which is a double word. It is eights bytes long because BPX1SOC > can request a socket pair. > > I don't know where you got 16 bytes from. > > Ant. > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Donald Likens > Sent: Thursday, 26 September 2013 11:24 AM > To: [email protected] > Subject: Confused by BPX1CON > > When invoking BPX1CON it states: > > Socket_descriptor > Supplied parameter > Type: Integer > Length: Fullword > The name of a fullword that contains the socket file descriptor for > which the > connect is to be done. > > It also states that this is the output of BPX1SOC and I also believe this to > be 16 bytes. > > My confusion is the Socket descriptor for what I am doing is 16 bytes long! I > believe this is defined in the next two parameters. > > What are they talking about for this fullword? > > A sample would explain a lot with field definitions (The examples in the book > do not show the DS statements for the calls. > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN
-- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
