<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html lang="en-us" xml:lang="en-us">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="security" content="public" />
<meta name="Robots" content="index,follow" />
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
<meta name="DC.Type" content="reference" />
<meta name="DC.Title" content="AF_UNIX_CCSID address family" />
<meta name="abstract" content="The AF_UNIX_CCSID family is compatible with the AF_UNIX address family and has the same limitations." />
<meta name="description" content="The AF_UNIX_CCSID family is compatible with the AF_UNIX address family and has the same limitations." />
<meta name="DC.Relation" scheme="URI" content="address.htm" />
<meta name="DC.Relation" scheme="URI" content="uafunixccsid.htm" />
<meta name="DC.Relation" scheme="URI" content="cafunix.htm" />
<meta name="DC.Relation" scheme="URI" content="../apiref/pns.htm" />
<meta name="copyright" content="(C) Copyright IBM Corporation 2001, 2006" />
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2001, 2006" />
<meta name="DC.Format" content="XHTML" />
<meta name="DC.Identifier" content="cafunixccsid" />
<meta name="DC.Language" content="en-us" />
<!-- All rights reserved. Licensed Materials Property of IBM -->
<!-- US Government Users Restricted Rights -->
<!-- Use, duplication or disclosure restricted by -->
<!-- GSA ADP Schedule Contract with IBM Corp. -->
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
<link rel="stylesheet" type="text/css" href="./ic.css" />
<title>AF_UNIX_CCSID address family</title>
</head>
<body id="cafunixccsid"><a name="cafunixccsid"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">AF_UNIX_CCSID address family</h1>
<div><p>The AF_UNIX_CCSID family is compatible with the AF_UNIX address
family and has the same limitations.</p>
<div class="section"><p>They both can be either connectionless or connection-oriented,
and no external communication functions connect the two processes. The difference
is that sockets with the address family AF_UNIX_CCSID use the sockaddr_unc
address structure. This address structure is similar to sockaddr_un, but it
allows path names in UNICODE or any CCSID by using the Qlg_Path_Name_T format. </p>
</div>
<div class="section"><p>However, because an AF_UNIX socket may return the path name from
an AF_UNIX_CCSID socket in an AF_UNIX address structure, path size is limited.
AF_UNIX only supports 126 characters so AF_UNIX_CCSID is also limited to
126 characters.</p>
</div>
<div class="section"><div class="p">A user cannot exchange AF_UNIX and AF_UNIX_CCSID
addresses on a single socket. When AF_UNIX_CCSID is specified on the <span class="apiname">socket()</span> call,
all addresses must be sockaddr_unc on later API calls. <pre>struct sockaddr_unc {
short sunc_family;
short sunc_format;
char sunc_zero[12];
Qlg_Path_Name_T sunc_qlg;
union {
char unix[126];
wchar_t wide[126];
char* p_unix;
wchar_t* p_wide;
} sunc_path;
} ;</pre>
</div>
</div>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><caption>Table 1. AF_UNIX_CCSID address structure </caption><thead align="left"><tr><th valign="top" id="d0e37">Address structure field</th>
<th valign="top" id="d0e39">Definition</th>
</tr>
</thead>
<tbody><tr><td valign="top" headers="d0e37 ">sunc_family</td>
<td valign="top" headers="d0e39 ">This field contains the address family, which is always
AF_UNIX_CCSID.</td>
</tr>
<tr><td valign="top" headers="d0e37 ">sunc_format</td>
<td valign="top" headers="d0e39 ">This field contains two defined values for the format
of the path name: <ul><li>SO_UNC_DEFAULT indicates a wide path name using the current default CCSID
for integrated file system path names. The sunc_qlg field is ignored.</li>
<li>SO_UNC_USE_QLG indicates that the sunc_qlg field defines the format and
CCSID of the path name.</li>
</ul>
</td>
</tr>
<tr><td valign="top" headers="d0e37 ">sunc_zero</td>
<td valign="top" headers="d0e39 ">This field is reserved. Set this field to hexadecimal
zeros.</td>
</tr>
<tr><td valign="top" headers="d0e37 ">sunc_qlg</td>
<td valign="top" headers="d0e39 ">This field specifies the path name format.</td>
</tr>
<tr><td valign="top" headers="d0e37 ">sunc_path</td>
<td valign="top" headers="d0e39 ">This field contains the path name. It is a maximum of
126 characters and may be single byte or double byte. It may be contained
within the sunc_path field or allocated separately and pointed to by sunc_path.
The format is determined by sunc_format and sunc_qlg.</td>
</tr>
</tbody>
</table>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="address.htm" title="The address family parameter on a socket() determines the format of the address structure to use on socket functions.">Socket address family</a></div>
</div>
<div class="relref"><strong>Related reference</strong><br />
<div><a href="uafunixccsid.htm" title="AF_UNIX_CCSID address family sockets have the same specifications as AF_UNIX address family sockets. They can be used for connection-oriented or connectionless and provide communications on the same system.">Use AF_UNIX_CCSID address family</a></div>
<div><a href="cafunix.htm" title="This address family provides interprocess communications on the same system that uses the socket APIs. The address is really a path name to an entry in the file system.">AF_UNIX address family</a></div>
</div>
<div class="relinfo"><strong>Related information</strong><br />
<div><a href="../apiref/pns.htm">Path name format</a></div>
</div>
</div>
</body>
</html>