APPC Subsystem on MPE/XL Node Manager's Guide (30294-90007)

100 Chapter4

APPC Subsystem Conﬁguration

Conﬁguring the APPC Subsystem

Automatic TP Startup?

This parameter tells the APPC subsystem whether or

not to stream a job to run the local TP when an allocate

request arrives from the remote TP.

Y The APPC subsystem will start the

local TP automatically by streaming a

job when it receives an allocate request

from the remote TP. If the local TP is

conﬁgured to accept queued allocate

requests, the APPC subsystem will

stream the job only once. If the local TP

is not conﬁgured to accept queued

allocate requests, the APPC subsystem

will stream the job to start a new TP

process every time it receives an

allocate request from the remote TP.

N The APPC subsystem will not start the

local TP automatically. The user must

start the local TP by issuing the MPE

RUN command or by streaming a job

that issues the RUN command.

NOTE

While you are developing and debugging a remotely initiated TP, you

might want to start it manually. However, after the TP has been

debugged, Hewlett-Packard recommends that you allow the APPC

subsystem to start it up.

Figure 4-16 shows how allocate requests from the remote TP can be

queued to wait until the local TP calls the MCGetAllocate intrinsic.

The TP in Figure 4-16 loops through the same conversation, beginning

with MCGetAllocate and ending with MCDeallocate, until it receives

the last allocate request.

The TP could be written to handle a predetermined number of allocate

requests, or it could loop through the conversation until the last

MCGetAllocate call timed out because the queue was empty. When

MCGetAllocate times out, it returns with a status value of +29. The

MCGetAllocate time-out value is conﬁgured in the “APPC: Transaction

Program Data” screen.