OpenTP1 Version 7 Description

Summary of amendments

The following table lists changes in this manual (3000-3-D50-30(E)) and product changes related to this manual for uCosminexus TP1/Server Base 07-03, uCosminexus TP1/Server Base(64) 07-03, uCosminexus TP1/Message Control 07-03, uCosminexus TP1/Message Control(64) 07-03, uCosminexus TP1/NET/Library 07-04, and uCosminexus TP1/NET/Library(64) 07-04.

Changes	Location
A performance verification trace (JNL performance verification trace) can now be output by using the journal service.	1.4.3, 4.1.1(2), 5.3.6 and 5.3.6(6)
A performance verification trace (LCK performance verification trace) for locking events that use lock services can now be output.	1.4.3, 4.1.1(2), 5.3.6 and 5.3.6(7)
An explanation of global domain has been added.	3.2.1(5)(b)
A function for prioritizing using service information of a specific node (service information prioritizing function) has been added.	3.2.2, 3.2.2(2), and Appendix E
An explanation of the causes for the MCF event that reports UAP abnormal termination and the MCF event that reports discarding of an unprocessed message has been changed.	3.3.7(3)(a)
An explanation of fall-back operation has been changed.	3.3.8(2)
An explanation regarding cases in which messages cannot be recovered has been added.	3.3.9(4)(b)
An explanation of the send order of messages has been changed.	3.3.10
An explanation of the function for receiving data that is reported by the dc_rpc_cltsend function has been changed.	3.5.1(2)
An explanation of the differences between an OpenTP1 file system and an OS file system has been changed.	4.1.1(1) Table 4-2
An event trace (FIL event trace) can now be output by requesting access to OpenTP1 files.	4.1.1(2), 5.3.6, and 5.3.6(13)
An explanation of the shared memory size for the DAM service when using a DAM file that has been specified for cacheless access has been changed.	4.4.1(15)
The number of services for acquisition of performance verification has been changed. Related definitions have also been changed.	7.1
A description of the system services that can specify port numbers for receiving data has been added.	7.3.1
The statuses of application timer start requests can now be displayed.	Appendix B Table B-2
The prctee process, which redirects OpenTP1 standard output and standard error output, can now be stopped and restarted.	Appendix B Table B-2
The statuses of user timer monitoring can now be displayed.	Appendix B Table B-2
Changes in the following product versions are listed: TP1/Server Base 07-03 TP1/Message Control 07-03 and TP1/NET/Library 07-04 TP1/Message Control 07-02 and TP1/NET/Library 07-03 TP1/Message Control 07-01 and TP1/NET/Library 07-01	Appendix C.1, Appendix C.2, and Appendix C.3
An overview regarding the processing of remote procedure calls has been added.	Appendix D

The following table lists changes in this manual (3000-3-D50-30(E)) and product changes related to this manual for uCosminexus TP1/Message Control 07-02, and uCosminexus TP1/NET/Library 07-03.

Changes	Location
A function for dynamic loading of service functions can now be used by using MHP.	2.6.2(3)(b), 3.8, 3.8.1 and Appendix E
The following operations can now be performed by using library functions: Displaying the status of, establishing, and releasing connections Displaying the status of requests to establish server connections, and starting or terminating reception of those requests Deletion of application timer start requests Displaying the status of a logical terminal, shutting it down, and releasing it from shutdown, and deleting the output queue Displaying the status of the MCF communication service or the application start service	3.3.7(3)(a), 3.3.9(3) and Appendix B Table B-1
A message is now output when memory is automatically added from the unused area if MCF static shared memory is insufficient.	7.2.2(4)
The status of a network that is related to a message exchange with a remote system can now be displayed.	Appendix B Table B-2

The following table lists changes in this manual (3000-3-D50-30(E)) and product changes related to this manual for uCosminexus TP1/Message Control 07-01, and uCosminexus TP1/NET/Library 07-01.

Changes	Location
A performance verification trace (MCF performance verification trace) can now be output by main events during message exchanges.	1.4.3, 4.1.1(2), 5.3.6, and 5.3.6(8)
Reception of requests to establish server connections can now be manually started and terminated.	Appendix B Table B-2

In addition to the above changes, minor editorial corrections have been made.

The following table lists changes in the manual (3000-3-D50-20(E)) and product changes related to that manual for uCosminexus TP1/Server Base 07-02, uCosminexus TP1/Message Control 07-01, and uCosminexus TP1/NET/Library 07-01.

Changes
A performance verification trace (PRF trace) can now be output by the XA resource service.
A function that enables service functions to be loaded dynamically has been added.
Items that can be monitored by the timer monitoring facility have been added. OpenTP1 definitions related to the monitored items have been changed accordingly.
The schedule service can now be implemented on a service-by-service basis.
The description of usage of the User Authentication facility in TP1/Client/P for MS-DOS has been deleted.
The description of the remote API facility has been changed.
An audit log output function has been added.
A function that allows parallel access to system journal files has been added.
An event trace can now be output by the name service.
An event trace can now be output by a process service
A function that allows the system to operate without using system journal files (non-journal operation function) has been added. With this addition, the valid number of system service processes has been changed.
Changes in the following product versions are described: TP1/Server Base 07-02 TP1/Message Control 07-01 and TP1/NET/Library 07-01

The following table lists changes in the manual (3000-3-D50-20(E)) and product changes related to that manual for uCosminexus TP1/Server Base 07-01.

Changes
A function (MSDTC linkage) that enables transactional linkage by means of two-phase commit between OpenTP1 and an application that runs on .NET Framework has been added.
A function has been added for displaying the product name, version number, and other information about products operating in environments set up in the OpenTP1 directory. With this addition, the dcpplist command has been added.
Changes to functions, definitions, commands, and defaults when upgrading to a later version are described.