Setting the invocation environment

All binder API calls associated with a given binder dialog must be issued from the same TCB.

Your program's environment must have the following characteristics before invoking the API:

Enabled for I/O and external interrupts
Holds no locks
In task control block (TCB) mode
With PSW key equal to the job step TCB key
In primary address space mode
In 31-bit addressing mode
In either supervisor or problem program state
With no FRRs on the current FRR stack.

You can call the binder in both problem program and supervisor state and in any PSW storage key.

If your program is written in a high-level programming language, you must ensure that your program is in 31-bit addressing mode before calling the IEWBIND service. If your program is written in assembler language, the IEWBIND macro takes care of any addressing mode changes in a transparent manner.

All requests are synchronous. The binder returns control to your program after the completion of the requested service. Services cannot be requested in cross-memory mode.