OpenTP1 Version 7 TP1/Client User's Guide TP1/Client/J

Summary of amendments

The following table lists changes in this manual (3000-3-D59-20(E)) and the product changes related to uCosminexus TP1/Client/J 07-02.

Changes	Location
Parallel processing of receipt of service request messages is now supported in order to prevent scheduling delays (multi-scheduler facility). Due to this change, the following operands have been added to the TP1/Client/J environment definition: dcscdmulti dcscdmulticount	2.2.13, 5.2.1, 5.2.2
An operation similar to batch terminal startup provided by conventional mainframe OLTP is now supported (unidirectional server message reception function). Due to this change, the following methods have been added to the TP1Client class: acceptNotification cancelNotification openNotification acceptNotificationChained closeNotification In addition, the following classes have been added: ErrAcceptCanceledException ErrVersionException	2.5, 2.11.2, 3.1, 4. Class TP1Client, 4. Class ErrAcceptCanceledException, 4. Class ErrVersionException
UAP traces are now acquired from the following methods of the TP1Client class: setUapTraceMode setErrorTraceMode setMethodTraceMode setDataTraceMode	2.11.2
Performance analysis trace identification information is now output to UAP traces.	2.11.2, 2.11.7(5)
When an RPC is issued to TP1/Server version 07-02 or later using the remote API facility, identification information such as an IP address can now be added to the RPC message that is sent to the scheduler.	2.11.7(2)
When connection establishment is requested by an RPC or TCP/IP communication, the source host can now be specified (source host specification facility). Due to this change, the dccltcupsndhost operand has been added to the TP1/Client/J environment definition.	2.13, 5.2.1, 5.2.2
The receive port can now be fixed for RPCs that use the scheduler direct facility and the name service (receive port fixing facility). Due to this change, the dccltcuprcvport operand has been added to the TP1/Client/J environment definition.	2.14, 5.2.1, 5.2.2
A list of the TP1/Client/J environment definition operands has been added.	5.1.1
The maximum execution time from startup to termination of a transaction branch that is executed by the RAP-processing server can now be specified. Due to this change, the dcclttrcmplmttm operand has been added to the TP1/Client/J environment definition.	5.2.1, 5.2.2
Notes have been added about the dcrcvport operand of the TP1/Client/J environment definition.	5.2.2
Changes to the API, definitions, commands, and default values during upgrading have been described.	Appendix A

The following table lists changes in this manual (3000-3-D59-20(E)) and the product changes related to uCosminexus TP1/Client/J 07-01.

Changes	Location
Information has been added about the files provided by DTP1/Client/J and the directories for storing the files.	1.3.1(1)
A facility for setting terminal identification information has been added in order to fix a DCCM3 logical terminal that is allocated to a CUP when communication is established with a DCCM3 logical terminal by means of a permanent connection. Due to this change, the setConnectInformation method has been added to the TP1Client class. In addition, the dccltconnectinf operand has been added to the TP1/Client/J environment definition.	2.9.1(6), 2.9.3, Table 2-29, Table 3-2, 4. Class TP1Client, 5.2.1, 5.2.2
A data compression facility has been added in order to compress user data that is sent over the network by RPC. Due to this change, the dccltdatacomp operand has been added to the TP1/Client/J environment definition.	Table 2-42, 2.12, 5.2.1, 5.2.2
Notes have been added about the execution of methods of instances of the same TP1Client class.	3.2

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