The cond_setup callable service makes the calling thread eligible to receive event notifications from other threads.
Operation | Environment |
---|---|
Authorization: | Supervisor state or problem state, any PSW key |
Dispatchable unit mode: | Task |
Cross memory mode: | PASN = HASN |
AMODE (BPX1CSE): | 31-bit |
AMODE (BPX4CSE): | 64-bit |
ASC mode: | Primary address space control (ASC) mode |
Interrupt status: | Enabled for interrupts |
Locks: | Unlocked |
Control parameters: | All parameters must be addressable by the caller and in the primary address space. |
|
AMODE 64 callers use BPX4CSE with the same parameters.
You must specify at least one event; you may specify both.
The name of a fullword in which the service returns a 0 upon normal completion, or -1 otherwise.
Error | Explanation |
---|---|
EINVAL | The system determined that the event list that was passed to the service is in error. The following reason codes unique to the cond_setup call can accompany the return code: JRAlreadySetup, JRNoEvents, JRUndefEvents. |
The name of a fullword in which the service routine stores the reason code. The cond_setup service stores a reason code only when the return value is -1. The reason code further qualifies the return code value. See z/OS UNIX System Services Messages and Codes for the reason codes.
The only exception to this is the queue_interrupt service. You can use the queue_interrupt service to "put back" the last signal delivered to the signal interface routine.
The program running on the thread should eventually call one of the cond_wait, cond_timed_wait, or cond_cancel services.
For an example using this callable service, see BPX1CSE (cond_setup) example.