Forum Post: RE: 4GL Sockets and Hexadecimal values...

  • Thread starter Thread starter Matt Gilarde
  • Start date Start date
Status
Not open for further replies.
M

Matt Gilarde

Guest
SocketConnect expects an INT64 for the lvi64Header parameter. The code you showed in the first post is passing a character string. There's nothing special about hexadecimal numbers. They're just a different way of expressing numeric values. You could change the definitions as follows and nothing would be different: DEFINE VARIABLE CSI AS INT64 INIT 2147483648 NO-UNDO. DEFINE VARIABLE SIF_GENERAL AS INT64 INIT 134217728 NO-UNDO. DEFINE VARIABLE SIS_LOGIN AS INT64 INIT 256 NO-UNDO. DEFINE VARIABLE CSI_LOGIN AS INT64 NO-UNDO. /* Request header */ ASSIGN CSI_LOGIN = CSI + SIF_GENERAL + SIS_LOGIN. I think you just need to pass CSI_LOGIN to SocketConnect. And shouldn't the PUT-UNSIGNED-LONG in SocketConnect be PUT-UNSIGNED-INT64? Or does the API expect a 4-byte value? Can you show us the definition of the structure you're filling in SocketConnect?

Continue reading...
 
Status
Not open for further replies.
Back
Top