Re: Socket issues with CCSID?

Sorry I misunderstood your question, Scott.  I am not using
Unix sockets.  This is a socket app that delivers email.

I believe the issue could be releated to the PDF issue I am
having, although the type of data it's transmitting isn't
an issue.  This is sending an email.

It won't even write data to my debug file (that errors out)
when doing this.  Only when job CCSID is 1381.  When it's
37, it works just fine.

As far as where the error is happening, it's actually in
the prototype definition for the socket API, line 72 from
the compile listing below which appears to be the socket
type parameter

 70 D Socket          Pr            10I 0 Extproc('socket')
         
 71 D                               10I 0 Value
                     
 72 D                               10I 0 Value
                     
 73 D                               10I 0 Value
                     

155 D AF_INET         C                   2  
156 D SOCK_STREAM     C                   1

646 C                   eval      SD = Socket( AF_INET :
SOCK_STREAM : 0) 

Let me know if this helps or if there's anything else I can
help with.

Brad

On Wed, 1 Nov 2006 17:03:19 -0600 (CST)
 Scott Klement <rpg400-l@xxxxxxxxxxxxxxxx> wrote:

No, this is using RPG on the iSeries.

Unix domain sockets are those that use a special IFS
object (of type 
socket) to enable communication between different
programs on the same 
computer.

You can use Unix-domain sockets from RPG.

    fd = socket(AF_UNIX: SOCK_STREAM: 0);
    fd = socket(AF_UNIX_CCSID: SOCK_STREAM: 0);

I did see some mention of that in the docs...  I didn't

think it applied in this case.

The only reason I suggested this is because that's the
only type of socket 
that I know of that uses CCSIDs.

Since you didn't say, and since it doesn't sound like
you're familiar 
with Unix domain sockets, I guess I'll assume you're
using internet 
sockets, probably TCP stream sockets.  But, since they
don't use CCSIDs 
(data is just transmitted as binary data -- just a stream
of bits) I don't 
know what that has to do with the CCSID.

It's on the iSeries side that the issue seems to exist

since I can 

chance the CCSID of the job from 935 back to 37 and it

works fine.

Hmmm. Which API accepts character data that the CCSID
would matter? 
Socket(), Listen(), Accept() Connect(), Recv(), Send(),
Close()... none of 
these uses character data, except for the data that's
send/received, and 
that's just binary data.

Other APIs, such as those that look up hostnames do use
character data -- 
but they don't use descriptors!  Though, under the covers
I guess they 
could.

Do you know which API, specifically, is failing?
-- 
This is the RPG programming on the AS400 / iSeries
(RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the
archives
at http://archive.midrange.com/rpg400-l.

Bradley V. Stone
BVS.Tools
www.bvstools.com