Programming requirements for the SIOCGPARTNERINFO and SIOCSPARTNERINFO ioctl calls

You can use the following APIs to retrieve connection routing information, partner security credentials, or both by using the SIOCGPARTNERINFO ioctl (and optionally by using the SIOCSPARTNERINFO ioctl prior to the SIOCGPARTNERINFO ioctl):

Language Environment® C/C++ socket:
- SIOCGPARTNERINFO call [w_ioctl()]
- SIOCSPARTNERINFO call [ioctl()]
UNIX System Services Assembler Callable Service (BPX1IOC or BPX4IOC)
Trusted TCP connections API for Java™
Install the 31-bit or 64-bit software development kit (SDK) for Java, Java 2 Technology Edition, V5 or later.
Macro API (EZASMI)
CALL instruction API (EZASOKET) supporting COBOL, PL/I, and System/370 assembler languages
REXX socket API
Restriction: For the SIOCGPARTNERINFO ioctl, this API supports only the request types PI_REQTYPE_CONNTYPE and PI_REQTYPE_PARTNER_USERID. For more information about the SIOCGPARTNERINFO ioctl, see SIOCGPARTNERINFO (X'C000F612').
CICS® C socket calls
CICS CALL instruction API (EZASOKET - by including EZACICAL or EZACICSO)
IMS™ CALL instruction API (EZASOKET)

Restriction: The following APIs are not supported for the SIOCGPARTNERINFO and SIOCSPARTNERINFO calls:

TCPIP C socket API
X/Open Transport Interface (XTI)
Pascal API

Table 1 describes the programming requirements for trusted TCP connection APIs.

Table 1. Programming requirements for trusted TCP connection APIs
Function	Requirement
Authorization	Supervisor state or problem state, any PSW key. For special authorization requirements when retrieving partner security credentials, see Steps for retrieving partner security credentials.
Dispatchable unit mode	Task.
SRB mode	Some APIs can be invoked in SRB mode. All APIs can be invoked in TCB mode.
Cross-memory mode	The API can be invoked in only a non-cross-memory environment (PASN=SASN=HASN).
ASC mode	Primary address space control (ASC) mode.
Interrupt status	Enabled for interrupts.
Locks	No locks should be held when you issue these calls.
Functional recovery routine (FRR)	Do not invoke the API with an FRR set, which can cause system recovery routines to be bypassed and severely damage the system.
Storage	Storage acquired for the purpose of containing data that is returned from an API call must be obtained in the same key as that of the application program status word (PSW) at the time of the call.
Nested API calls	You cannot issue nested SIOCGPARTNERINFO ioctl calls when you are requesting partner security credentials.
Addressability mode (AMODE)	ALL APIs can be invoked in 31-bit addressability mode. Unix System Services assembler callable service, Language Environment C/C++ socket, and JAVA can be invoked in 64-bit addressability mode.