Configuring other z/OS applications to access IBM z/OS Connect for API calls
Before your z/OS applications that are not running on CICS® or IMS can make RESTful API calls through IBM z/OS Connect, you must configure the communication stub.
About this task
Restriction: Depending on the type of programs used, some restrictions apply to
accessing IBM z/OS Connect for API calls. Consider the
following restrictions before you configure your API requester communication stub:
- IBM z/OS Connect requires the z/OS Language Environment (LE) option POSIX(ON) for signal
handling. There can be only one LE enclave, the first enclave, with POSIX(ON) per
TCB. To avoid invalid configurations, specify POSIX(ON) at the application level by
using
CEEUOPT
. If there are any nested enclaves, the main program in the nested enclave must useCEEUOPT
to set POSIX(OFF). - If the first or main program for a child enclave is COBOL,
CEEUOPT
cannot be used to set POSIX(OFF). Child enclaves for these programs can inherit z/OS LE options only from their parent enclave, consequentially resulting in invalid configurations due to inheriting POSIX(ON) from the parent. Therefore, if you need to use nested enclaves for your program, the main program of the child enclave cannot be COBOL. To learn more about this restriction, see Child enclave has a COBOL main program.
The IBM z/OS Connect communication stub is a load module to configure in your z/OS system to handle the HTTP connection and communication with the IBM z/OS Connect server.
The load module for the communication stub must be added to the STEPLIB concatenation. In addition, the IBM z/OS Connect server name and port number must be specified for the communication stub. Use the CEEOPTS DD statement for the Language Environment® (LE).
Tip: z/OS provides functions to
optimize performance for HTTP connections. If IBM z/OS Connect and the z/OS subsystem are on the same LPAR, the fast local socket is automatically available. If IBM z/OS Connect and the z/OS subsystem are on different LPARs, you must enable the following functions:
- HiperSocket, a zSeries hardware feature that provides high-performance internal communications between LPARs within the same central processor complex (CPC). For more information, see HiperSockets concepts and connectivity in the z/OS documentation.
- Shared Memory Communication (SMC), which requires z/OS V2.2 or later on z13® in the same CPC. For more information, see Shared Memory Communications in the z/OS documentation.