OpenTP1 Version 7 Programming Reference C Language

[Contents][Index][Back][Next]

1.4.1 Starting and terminating each application program

Organization of this subsection
(1) Starting and terminating SUP
(2) Starting and terminating SPP and MHP
(3) Starting and terminating UAPs that handle offline work

(1) Starting and terminating SUP

(a) Starting

The SUP is started when:

Before the SUP can request an SPP for service, the SPP must begin the service and must have started before the SUP has.

(b) Terminating

Once the SUP has been started, it cannot be terminated normally by the OpenTP1. Even when a command to exit the OpenTP1 normally is executed, the OpenTP1 will not terminate until all the SUPs in the OpenTP1 terminate. When coding the SUP, design it so that it will terminate by itself. To bring an SUP into abnormal termination because of some problem, design the SUP so that it will terminate by itself by exit() or abort().

The SUP cannot be terminated normally by the dcsvstop command. However, the SUP can be brought into forced termination by the dcsvstop -f command.

Do not terminate any SUP process by the kill command.

(2) Starting and terminating SPP and MHP

(a) Starting

The SPPs and MHPs belonging to one user server (service group) start at once. They start when:

If the multiserver facility is in use, the same number of user server processes as the specified number of resident processes are acquired. If the number of service requests increases, nonresident processes will start as well.

(b) Terminating

The SPP or MHP terminates when:

Do not terminate any SPP or MHP process by the kill command.

(3) Starting and terminating UAPs that handle offline work

Users can start UAPs that handle offline work by any method. The UAPs are terminated by terminating the processes by the shell. Users are responsible for starting and terminating UAPs that handle offline works.