Chapter Contents |
Previous |
Next |
Porting UNIX Socket Applications to the SAS/C Environment |
UNIX header filenames are really pathnames that relate
to the
/usr/include
directory.
In most cases, the headers reside directly in the
/usr/include
directory with no further subdirectories in the pathname.
For example, the
<netdb.h>
header file resides in the
/usr/include
directory. OS/390 and CMS file structures do not include
subdirectories. All angle-bracketed include files are in the SYSLIB concatenation
under OS/390 or in the GLOBAL MACLIB concatenation under CMS. The SAS/C Compiler
ignores subdirectories included in the filename. Specifying
<sys/socket.h>
appears the same to OS/390
and CMS systems as specifying
<socket.h>
.
Header files such as
<arpa/nameser.h>
and
<sys/socket.h>
are placed in an OS/390 partitioned data set or CMS
macro library based on the last part of the filename, for example,
socket.h
. Because of this, a UNIX program that
specifies a subdirectory in the header file pathname can work without modification.
It is best to code the pathname even for programs intended for use with SAS/C
software because they can be ported back to a UNIX operating system more easily
and because future releases of the SAS/C Compiler may attach significance
to these pathnames. The header files listed with the socket function descriptions
in Socket Function Reference include
subdirectories.
Chapter Contents |
Previous |
Next |
Top of Page |
Copyright © 2001 by SAS Institute Inc., Cary, NC, USA. All rights reserved.