OpenTP1 operations can be classified into:

• necessary routine operations
• operations that modify the OpenTP1 system
• other operations

This section describes these operations. For further details, see the manual OpenTP1 Operation.

Table 5-1 describes routine operations, Table 5-2 describes operations that modify the OpenTP1 system, and Table 5-3 describes other operations.

Table 5-1 Routine operations in an OpenTP1 system

Operation	Purpose	Procedure
Starting OpenTP1	To start operation. OpenTP1 can be started from the initial state, or restarted from its state at the previous termination.	In the system environment definition, specify whether the OpenTP1 system is to be started manually with the command dcstart, or started automatically whenever the OS starts.
Normal termination	To terminate operation normally.	You use the command dcstop to terminate OpenTP1.
Forced normal termination	Terminating OpenTP1 in a forced normal termination terminates an online system normally even if a UAP has terminated abnormally during online processing.	Use the dcstop -n command.
Planned termination (mode A)	Terminating OpenTP1 in a planned termination (mode A) halts the online system temporarily. For example, when an error occurs on a terminal managed by MCF, OpenTP1 terminates and leaves messages in the output queue.	Use the dcstop -a command.
Planned termination (mode B)	Terminating OpenTP1 in a planned termination (mode B) quickly terminates the online system. OpenTP1 terminates immediately after completion of the currently executing service.	Use the dcstop -b command.
Forced termination	Terminating OpenTP1 in a forced termination immediately terminates the online system. OpenTP1 terminates immediately without waiting for the completion of the currently executing service.	Use the dcstop -f command.
Starting a UAP	To start running a UAP.	Define UAPs that are to start automatically with OpenTP1 in the user service structure definition.
Terminating a UAP	To stop running a UAP. The UAP can be terminated normally or forcibly.	The UAP terminates automatically when OpenTP1 terminates. You can also use the command dcsvstop to terminate a UAP online.
Unloading a journal	Journals are unloaded when using the journal maintenance facility and to prepare against an error on a DAM or TAM file.	To unload a journal, use the command jnlunlfg to copy the system journal file to a file.
Backing up DAM and TAM files	DAM and TAM files should be backed up in case of an error in the files.	To back up DAM and TAM files, use commands to copy the DAM and TAM files.
Outputting the message log to a file	To use the messages output from OpenTP1 or UAPs.	You can output the messages stored in the message log file to the standard output.

Table 5-2 Operations that modify an OpenTP1 system

Operation	Purpose	Procedure	OpenTP1
			Stopped	Running
Modifying a definition	To modify the configuration or execution environment of an OpenTP1 system.	Change the contents of a definition file. If the superuser changes the definition Delete OpenTP1 from the operating system using the dcsetup -d command after changing the definition and terminating OpenTP1 normally. Then, execute the dcsetup command to re-register OpenTP1 in the operating system. If the OpenTP1 administrator changes the definition Execute the dcreset command after changing the definition and terminating OpenTP1 normally. Note that the dcreset command cannot be executed while operating OpenTP1.	Y	N
Replacing a UAP while OpenTP1 is running	To replace a UAP while OpenTP1 is running. (The new UAP will start when OpenTP1 restarts.)	Terminate the active UAP and then replace it. If necessary, the user service definition can also be replaced after the active UAP terminates normally. Then start the new UAP. If you replace the definitions without first terminating the active UAP, operation of the UAP is not guaranteed.	--	Y
Replacing a UAP while OpenTP1 is running (changing to a UAP in another directory)	To temporarily replace a UAP while OpenTP1 is running. (The UAP in the specified directory takes effect when OpenTP1 is restarted after termination.)	Terminate the active UAP and then change the search path using an operation command. After changing the search path, start the new UAP.	--	Y
Changing file capacity	To change the size of a file. (OpenTP1 must be stopped except when changing the size of a status file.)	Allocate a physical file with an increased capacity. Redefine the file. or Create a new file with a sufficient capacity. Define the file. The size of a status file can be changed using an operation command.	Y	Y*
Changing the network configuration while online	You can add or delete nodes in the network of the OpenTP1 system while online.	Online reconfiguration can be achieved in either of the following ways. Method 1 (Reconfiguration using the system common definition): Change the specification of the all_node operand in the system common definition. Execute the namndchg command. When the namndchg command is executed with the -l option, the specification of the current all_node operand can be output to the standard output. Method 2 (Reconfiguration using domain definition files): Create the all_node and all_node_ex domain definition files. Execute the namndchg command.	N	Y
Changing the main() function, UOCs, and libraries of the MCF communication service while OpenTP1 is running	You can reconfigure the MCF communication service without stopping OpenTP1.	To reconfigure the MCF communication service, use an operation command to partially stop the MCF communication service, and then change the main() function, UOCs, and libraries as you want.	N	Y

Legend:

Y: The task can be performed.

N: The task cannot be performed.

Y*: The task can be performed in part.

--: Not applicable.

Table 5-3 Other operations in an OpenTP1 system

Operation	Purpose	Procedure
Monitoring status	To monitor the status of OpenTP1.	Use the relevant command to output the OpenTP1 status information to the standard output.
Using the MultiOpenTP1	MultiOpenTP1 is useful when testing OpenTP1 with a UAP. Two OpenTP1 instances are activated on the same processor: one OpenTP1 instance is for the test and the other is for practical use.	To distinguish between the two OpenTP1 instances, assign each instance a name (an OpenTP1 identifier).