System i: Programming Secure Sockets APIs - IBM

More documents

Recommendations

Info

Name of Header File Name of File in QSYSINC Name of Member qp0lscan.h H QP0LSCAN Qp0lstdi.h H QP0LSTDI qp0wpid.h H QP0WPID qp0zdipc.h H QP0ZDIPC qp0zipc.h H QP0ZIPC qp0zolip.h H QP0ZOLIP qp0zolsm.h H QP0ZOLSM qp0zripc.h H QP0ZRIPC qp0ztrc.h H QP0ZTRC qp0ztrml.h H QP0ZTRML qp0z1170.h H QP0Z1170 qsoasync.h H QSOASYNC qtnxaapi.h H QTNXAAPI qtnxadtp.h H QTNXADTP qtomeapi.h H QTOMEAPI qtossapi.h H QTOSSAPI resolv.h H RESOLV semaphore.h H SEMAPHORE signal.h H SIGNAL spawn.h H SPAWN ssl.h H SSL sys/errno.h H ERRNO sys/ioctl.h SYS IOCTL sys/ipc.h SYS IPC sys/layout.h SYS LAYOUT sys/limits.h H LIMITS sys/mman.h SYS MMAN sys/msg.h SYS MSG sys/param.h SYS PARAM sys/resource.h SYS RESOURCE sys/sem.h SYS SEM sys/setjmp.h SYS SETJMP sys/shm.h SYS SHM sys/signal.h SYS SIGNAL sys/socket.h SYS SOCKET sys/stat.h SYS STAT sys/statvfs.h SYS STATVFS sys/time.h SYS TIME sys/types.h SYS TYPES sys/uio.h SYS UIO sys/un.h SYS UN 102 System i: Programming Secure Sockets APIs
Name of Header File Name of File in QSYSINC Name of Member sys/wait.h SYS WAIT ulimit.h H ULIMIT unistd.h H UNISTD utime.h H UTIME You can display a header file in QSYSINC by using one of the following methods: v Using your editor. For example, to display the unistd.h header file using the Source Entry Utility editor, enter the following command: STRSEU SRCFILE(QSYSINC/H) SRCMBR(UNISTD) OPTION(5) v Using the Display Physical File Member command. For example, to display the sys/stat.h header file, enter the following command: DSPPFM FILE(QSYSINC/SYS) MBR(STAT) You can print a header file in QSYSINC by using one of the following methods: v Using your editor. For example, to print the unistd.h header file using the Source Entry Utility editor, enter the following command: STRSEU SRCFILE(QSYSINC/H) SRCMBR(UNISTD) OPTION(6) v Using the Copy File command. For example, to print the sys/stat.h header file, enter the following command: CPYF FROMFILE(QSYSINC/SYS) TOFILE(*PRINT) FROMMBR(STAT) Symbolic links to these header files are also provided in directory /QIBM/include. Top | UNIX-Type APIs | APIs by category Errno Values for UNIX-Type Functions Programs using the UNIX ® -type functions may receive error information as errno values. The possible values returned are listed here in ascending errno value sequence. Name Value Text Details EDOM 3001 A domain error occurred in a math function. ERANGE 3002 A range error occurred. ETRUNC 3003 Data was truncated on an input, output, or update operation. ENOTOPEN 3004 File is not open. You attempted to do an operation that required the file to be open. ENOTREAD 3005 File is not opened for read operations. You tried to read a file that is not open for read operations. EIO 3006 Input/output error. A physical I/O error occurred or a referenced object was damaged. ENODEV 3007 No such device. ERECIO 3008 Cannot get single character for files opened for record I/O. The file that was specified is open for record I/O and you attempted to read it as a stream file. Secure Sockets APIs 103
Page 1:
System i Programming Secure Sockets
Page 4 and 5:
Note Before using this information
Page 6 and 7:
Related Information . . . . . . . .
Page 8 and 9:
vi System i: Programming Secure Soc
Page 10 and 11:
APIs These are the APIs for this ca
Page 12 and 13:
ufID (Input) The following values c
Page 14 and 15:
v GSK_CONNECT_CIPHER_SPEC v GSK_SID
Page 16 and 17:
[GSK_INSUFFICIENT_STORAGE] Not able
Page 18 and 19:
gsk_attribute_get_enum()—Get enum
Page 20 and 21:
secure session does not start, and
Page 22 and 23:
API introduced: V5R1 Top | UNIX-Typ
Page 24 and 25:
v GSK_FD v GSK_HANDSHAKE_TIMEOUT v
Page 26 and 27:
[GSK_INVALID_STATE] One of the foll
Page 28 and 29:
8. If GSK_OS400_APPLICATION_ID is s
Page 30 and 31:
if validation fails because the cer
Page 32 and 33:
gsk_attribute_set_enum()—Set enum
Page 34 and 35:
active secure sessions will continu
Page 36 and 37:
gsk_attribute_set_numeric_value()
Page 38 and 39:
v GSK_V3_SIDCACHE_SIZE v GSK_LDAP_S
Page 40 and 41:
v “gsk_secure_soc_init()—Negoti
Page 42 and 43:
[ETERM] Operation terminated. If an
Page 44 and 45:
2. v GSK_SESSION_TYPE set to GSK_CL
Page 46 and 47:
Error Messages Message ID Error Mes
Page 48 and 49:
[GSK_AS400_ERROR_INVALID_POINTER] T
Page 50 and 51:
attributes. In most cases, as resul
Page 52 and 53:
Error Messages Message ID Error Mes
Page 54 and 55:
v “gsk_secure_soc_misc()—Perfor
Page 56 and 57:
matched sets. If a client applicati
Page 58 and 59:
Authorities Authorization of *R (al
Page 60 and 61: gsk_secure_soc_startRecv()—Start
Page 62 and 63: The handle specified was not valid.
Page 64 and 65: v “gsk_secure_soc_misc()—Perfor
Page 66 and 67: Authorities No authorization is req
Page 68 and 69: 6. Socket option SO_SNDTIMEO is not
Page 70 and 71: [EPIPE] [EUNATCH] The specified des
Page 72 and 73: Example The following example shows
Page 74 and 75: Qlg_Path_Name_T *keyringFileName (i
Page 76 and 77: v The CCSID specified in the keyrin
Page 78 and 79: unsigned protocol; /* SSL protocol
Page 80 and 81: Service Program Name: QSOSSLSR Defa
Page 82 and 83: Related Information v “SSL_Create
Page 84 and 85: unsigned int cipherSuiteListLen The
Page 86 and 87: [EBADF] [EBUSY] Permission denied.
Page 88 and 89: ignore attempts by applications to
Page 90 and 91: C Constant System Value TLS_RSA_WIT
Page 92 and 93: ignore attempts by applications to
Page 94 and 95: v Use the system default cipher spe
Page 96 and 97: An error occurred in SSL processing
Page 98 and 99: Parameters int sslreturnvalue (Inpu
Page 100 and 101: Parameters SSLHandle* handle (input
Page 102 and 103: [EUNATCH] [EUNKNOWN] The protocol r
Page 104 and 105: Authorities No authorization is req
Page 106 and 107: struct SSLHandleStr { /* SSLHandleS
Page 108 and 109: Error Messages Message ID Error Mes
Page 112 and 113: Name Value Text Details ENOTWRITE 3
Page 114 and 115: Name Value Text Details EHOSTDOWN 3
Page 116 and 117: Name Value Text Details EISDIR 3471
Page 118 and 119: Name Value Text Details EBADFID 351
Page 120 and 121: CONDITIONS OF MERCHANTABILITY, FITN
Page 122 and 123: IBM Corporation Software Interopera
Page 124 and 125: SAA SecureWay SOM System i System i
Page 126: 118 System i: Programming Secure So
show all

System i: Programming Secure Sockets APIs - IBM

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?