IBM Version 4 manual Communications APIs, Provides Way to That, Is only provided Service Program

With the exception of the Get Client Handle API, which is available o Integrated Language Environment (ILE), the client software management and figuration APIs are available as both the original program model (OPM) a APIs.

Ÿ Add Client (QZCAADDC, QzcaAddClient) API

To manage a client one must keep track of								all	clients on	the	network.
provides a convenient way of keeping track								of clients. By calling thi
client	is added			to the database. If a				client is SNMP-enabled and
such	a	way	so	as to	send	traps to	the	managing AS/400,		the	client
ically	added		to	the	AS/400	database.	This	API	provides	a way to
that	may	not	be	SNMP-enabled.

ŸRemove Client (QZCARMVC, QzcaRemoveClient) API

This	API provides a way	to	remove a client from the database for
is	no longer required to	be	managed.

ŸRefresh Client (QZCAREFC, QzcaRefreshClientInfo) API

If a client is SNMP-enabled, this API makes an attempt to get hardwa software information from this client. Hardware information is retrieve host resource management information base (MIB), and software informat retrieved from both the Desktop Management Interface (DMI) and the resource MIB.

This information is		also	retrieved automatically when traps are recei
managing AS/400	from	its	clients. Therefore, this API provides a way t
a “refresh”	of	client	information to keep information current.

ŸUpdate Client Information (QZCAUPDC, QzcaUpdateClientInfo) API

This API provides a way to update a few fields that are not upd Refresh Client API.

ŸGet Client Handle (QzcaGetClientHandle) API

This API	returns a handle, which is	unique	for	every client known	to
As mentioned earlier, the interface		to this	API	is only provided	th
service	program.

Communications APIs

The user-defined communications APIs were created to provide users wit ability to develop their own high-level communications protocol with as li interference as possible. While the system manages the lower-level proto user develops the upper layers of a protocol in any high-level programm guage supported by the AS/400. Several lower-level protocols are supporte including X.25, Ethernet Version 2, IEEE Ethernet, token ring, and fiber data interface (FDDI) (the selection of which is chosen by the use

The APIs provide the ability to enable	a link (that is, line, controlle
disable a link, establish inbound routing	information	by setting	service
(that is, filters), transmit and receive	data, set	timers, and	query

The user-defined communications APIs are used primarily by users who h munications needs not normally associated with the other existing communic protocols, namely TCP/IP, SNA, or OSI. Applications that have been develope

8-2System API Programming V4R1