Re: [AS400programmer] 'ntohl' /'htonl' and Big Endian/Little Endian fun.

For the ones that want to know......
The reason for this thread was the fact that I had to deliver a 4 byte header 
(containing the length of the data to send) in Network_Byte_Order upfront the 
actual data send to a socket.
  Some investigation learned that the Network_Byte_Order is in fact Big Endian 
and Big Endian is the established Byte Order for all numeric values for TCP.
   
  Big Endian is however also the mnemonics of the iSeries while Pc type 
processors all have Litthe Endian Bite order.
   
  To be short:
  When we do nothing at the iSeries side and we just send an integer containing 
the length to the socket, it is in the correct Byte Order.
   
  Just to evade a lot of confusion for other for nothing.
   
  Kind regards,
  Eduard Sluis.
    
  
Eduard Sluis <eduard@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
  
Eduard Sluis wrote: Ok, the former subject was a little to much in disquise.
I've tried to figure out what Binding directory or better what service program 
is exporting these procedure, but could not find.
This is probably due to not knowing waht methods apart from DSPSRVPGM is 
available.
Is there an easy general way to figure out what objects are exporting what 
procedures??

Kind regards,
Eduard Sluis. 

Eduard Sluis wrote:
Dear All,

In what Binding directory 'ntohl' and 'htonl' are to be found?

Kind regards,
Eduard Sluis.


"Alan G. Campin" wrote:
Boy, the fact that the e-mail compress things down is such a pain. 

d ConvertLongToHostAPI...
d pr ExtProc('ntohl')
d Like(StdIntUns)
d PR_IntegerInNetworkOrder...
d Like(StdIntIns)

Does anybody know a way to stop it from doing this?

Should be. ~ added to keep from compressing. 

d ConvertLongToHostAPI...
d~~~~~~~~~~~~~~pr~~~~~~~~~~~~~~~~~~ExtProc('ntohl')
d~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~Like(StdIntUns)
d~~PR_IntegerInNetworkOrder...
d~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~Like(StdIntIns)