BPEATTCH

Attach a TCB (thread control block).

Return Code

Explanation

X'00000004'

The TCB index passed to the BPEATTCH program was not a valid index.

X'00000008'

There is no TCB type of the requested type defined to BPE.

X'0000000C'

A new TCB of the indicated type could not be attached because there were no available entries for it in the BPE TCB table. The maximum number of TCBs of this type is already attached.

X'00000010'

The MVS ATTACH for the new TCB failed.

X'00000014'

The caller is a non-thread running under the parent TCB of the TCB that was requested to be attached. This is not a valid environment for the BPEATTCH call.

X'00000020'

Internal processing error: The enqueue of an AWE (asynchronous work element) to the TCB attach processor for the requested TCB type failed.

X'00000024'

Internal processing error: The BPEWAIT for a response from the TCB attach processor for the requested TCB failed.

X'00000028'

Internal processing error: The routine called by BPEATTCH enqueued an AWE to the TCB attach processor for the requested TCB; however, the DDB address it saved in the AWE was invalid, and the attach processor rejected the attach request.

X'0000002C'

Internal processing error: The routine called by BPEATTCH enqueued an AWE to the TCB attach processor for the requested TCB; however, the TCB attach processor rejected the AWE because it contained an invalid function code.

X'00000030'

Internal processing error: BPEATTCH was unable to obtain a DQCB (dispatcher queue control block) for the new TCB -- the BPECBGET call for the DQCB failed.

X'000000F8'

The requested function is not present in the BPE system at run time. This is likely due to a macro or module mismatch.

X'000000FC'

The parameter list version generated by the macro is not supported by the called service routine. This is probably due to a macro or module mismatch.