Transaction service (trn)

Starts and terminates transaction processing, and manages the processing for updating resources based on reaching a synchronization point in a transaction.

Name service (nam)

Manages the correspondences between LAN network addresses and user servers in order to provide inter-UAP communications (remote procedure calls).

Schedule service (scd)

Manages the scheduling for remote procedure calls and for message control facilities.

Process service (prc)

Manages processes within a node.

Status service (sts)

Mainly stores history information unrelated to transactions into dedicated files, and manages the information.

Interval service (itv)

Manages the monitoring of internal processing times for each system service listed here.

Journal service (jnl)

Stores history information (journal) related to transaction processing in system journal files and checkpoint dump files, and manages the information.

Checkpoint dump service (cpd)

Sets and manages checkpoints in the system journal file to reduce the time for reading journals.

Lock service (lck)

Manages various locks in accordance with the transaction processing.

Log service (log)

Manages the message log that an OpenTP1 system uses to inform an operator of internal information.

Time service (tim)

Provides various time-monitoring facilities such as monitoring whether a transaction is taking too much time.

DAM service (dam)

Manages OpenTP1-dedicated user files (DAM access) that are used in application processing.

TAM service (tam)

Manages OpenTP1-dedicated user files (TAM access) that are used in application processing.

IST service (ist)

Manages the internode shared tables in memory shared by multiple OpenTP1 systems.

MCF service (MCF manager service, MCF communication service, application startup service)

Provides various message-control facilities for communicating with non-OpenTP1 systems.

MCF message queue service (que)

Manages the wait queues (input and output queues) that store messages when using the message control facilities.

Mapping service (map)

Aid for using, in OpenTP1, the Extended Presentation facility for GUIs.

These services require TP1/Message Control, which is the resource manager for message control.

MQA service (mqa)

Manages MQA message queuing when transferring messages between UAPs asynchronously. This service requires TP1/Message Queue, which is the resource manager for controlling MQA message queuing.

Resource manager monitor service (rmm)

Controls the start and termination of resource managers via OpenTP1.

Client service (clt)

Manages the processes that are required for TP1/Server Base when starting a transaction from an application program (CUP) of TP1/Client.

Tester service (uto)

Manages the execution environment of the online tester.

Transaction journal service (tjl)

Stores history information (journal) of transaction processing as a dedicated journal (the transaction recovery journal), and manages the information and journal. A user might decide to obtain such history information for transactions that take a long time in order, for example, to reduce recovery time.

Real-time statistics service (rts)

Manages real-time statistics that are required to check the operating status of the OpenTP1 system in real time.

Global archive journal service (jnl)

Archives and manages the system journal files for each OpenTP1 node in a cluster system or parallel-processing system.

ISAM service (ism)

Manages indexed sequential user files (ISAM) that comply with X/Open ISAM standards and are used in application processing.