The following System Object Access APIs for iSeries™ Access for Windows® are listed alphabetically.
System Object Access also includes enablers (APIs), which applications can use to access data in iSeries objects or to request graphical lists and attribute views of the object data. The APIs for manipulating lists of objects must be called in the correct order. The basic flow is as follows:
CreateErrorHandle -- Creates a handle to an "error" object to be passed to other APIs CreateListHandle -- Instantiates a list object on the client OpenList -- Builds list on iSeries server associated with client list (Manipulate the list and its objects using various generic and subclass APIs) CloseList -- Closes list and release resource on iSeries server DeleteListHandle -- Destroys list object on the client
The CWBSO_CreateListHandle API must be called to create a list before any other list APIs are called. The CWBSO_CreateListHandle API returns a list handle to the caller. The list handle must be passed as input to all other list APIs.
After the list is allocated, the CWBSO_SetListFilter API can be called to change the filter criteria for the list. CWBSO_SetListFilter is optional; if it is not called, the list will be built with the default filter criteria. Similarly, the CWBSO_SetListSortFields API can be called to define the attributes on which the list will be sorted. If it is not called the list will not be sorted.
The CWBSO_OpenList API must be called to build the list of objects. This will result in a request to be sent to the iSeries server. The list will be built on the iSeries server, and some or all of the objects (records) in the list will be buffered down to the list on the client. Although all objects in the list are not necessarily cached on the client, the APIs will behave as if they are. Once the CWBSO_OpenList API is called successfully, the following APIs can be called: