iSeries Access for Windows Communications and Security APIs

The iSeries™ Access for Windows^® Communications and Security topic shows you how to use iSeries Access for Windows application programming interfaces (APIs)

You can use these APIs to:

Get, use, and delete an iSeries system object. Various iSeries Access for Windows APIs require a system object. It holds information about connecting to, and validating security (user ID, password, and signon date and time) on, an iSeries system.
Obtain information about environments and connections that are configured in the system list when you use iSeries Access for Windows. The system list is a list of all currently configured environments, and of systems within those environments. The system list is stored and managed "per user," and is not available to other users.
Note: It is not necessary for you to explicitly configure new systems to add them to the system list. They are added automatically when you connect to a new system.

iSeries Access for Windows Communications and Security APIs required files:

Header file		Import library	Dynamic Link Library
System object APIs	System list APIs	cwbapi.lib	cwbco.dll
cwbcosys.h	cwbco.h	cwbapi.lib	cwbco.dll

Programmer's Toolkit:

The Programmer's Toolkit provides Communications and Security documentation, access to the cwbco.h and cwbcosys.h header files, and links to sample programs. To access this information, open the Programmer's Toolkit and select Communications and Security > C/C++ APIs.

iSeries Access for Windows Communications and Security topics:

Note: By using the code examples, you agree to the terms of the Code license and disclaimer information.

System object attributes
System object attributes affect the behavior of signing on and communicating with the iSeries system that the system object represents.
Communications and security: Create and delete APIs
These APIs are used for creating and deleting a system object
Communications and security: Connect and disconnect APIs
These APIs allow you to connect to and disconnect from the iSeries system, and for related behavior
Communication and security: Security validation and data APIs
These APIs provide security validation and data.
Communications and security: Get and set attribute APIs
Use the APIs to get and set other system object attributes, or determine if the attributes are restricted by policies.
Defines for cwbCO_Service
The following values define cwbCO_Service.
Differences between cwbCO_Signon and cwbCO_VerifyUserIDPassword
Following are listed some of the significant differences between cwbCO_Signon and cwbCO_VerifyUserIDPassword.
Similarities between cwbCO_Signon and cwbCO_VerifyUserIDPassword
The following information illustrates the similarities between cwbCO_Signon and cwbCO_VerifyUserIDPassword
Communications: Create and delete APIs
Use these APIs to create a list of configured systems, either in the currently active environment or in a different environment. Retrieve the number of entries in the list, and each entry in succession.
Communications: System information APIs
Use these APIs to obtain information about individual systems that are configured or connected in the current process. Unless the environment name is passed as a parameter, these APIs work only with the currently active environment.
Communications: Configured environments information
Use these APIs to obtain the names of environments that have been configured.
Communications: Environment and connection information
Use these APIs to determine if the calling application can modify environments and connection information.
Example: Using iSeries Access for Windows communications APIs
The example program below shows the use of communications APIs to retrieve and display the names of the default (managing) system, along with all the systems that are configured in the active environment.

Parent topic: iSeries Access for Windows C/C++ APIs

Related reference

Communications APIs return codes

Security APIs return codes

Global iSeries Access return codes

iSeries system name formats for connection APIs

OEM, ANSI, and Unicode considerations