OpenTP1 Version 7 TP1/Client User's Guide TP1/Client/W, TP1/Client/P

Summary of amendments

The following table lists changes in this manual (3000-3-D58-20(E)) and product changes related to this manual for uCosminexus TP1/Client/W 07-02 and uCosminexus TP1/Client/P 07-02.

Changes	Location
A facility that assembles messages and a facility for checking whether a message has been delivered have been added. With this addition, the following functions have been added: dc_clt_assem_send_s dc_clt_assem_receive_s CBLDCCLS('ASMSEND') CBLDCCLS('ASMRECV') The following operand has been added to the client environment definition: DCCLTDELIVERYCHECK The description of the following message has been changed: KFCA02447-E The following messages have been added: KFCA02485-E KFCA02486-E	2.5.1, 2.5.2, 2.5.3, 2.5.4, 2.5.5, 3.1.1, 4.6.4, 4.6.5, 5.1.1, 6.6.5, 6.6.6, 7.2.1, 7.2.2, 7.2.5, 8.2.1(4), 8.2.1(5), and 10.3
Identification information for performance verification set by TP1/Client can now be included in the TP1/Server performance verification trace. With this change, the DCCLTPRFINFOSEND operand has been added to the client environment definition.	2.11.5, 7.2.1, 7.2.2, and 7.2.5
A facility that specifies the sending host for a TP1/Client CUP has been added. With this addition, the DCCLTCUPSNDHOST operand has been added to the client environment definition.	2.12.3, 2.13, 7.2.1, 7.2.2, and 7.2.5
An explanation of the facility that fixes the receive port has been added.	2.14
Notes on using functions and request statements have been added.	4.1 and 6.1
The explanation of the file loading order used when a path name is specified in the defpath argument has been changed for the following functions: dc_clt_cltin_s function dc_clt_accept_notification_s function dc_clt_cancel_notification_s function dc_clt_open_notification_s function	4.2.1(3), 4.7.1(3), 4.7.2(3), and 4.7.3(3)
The explanation of the file loading order used when a path name is specified as a data name has been changed for the following request statements: CBLDCCLS('CLTIN ') CBLDCCLS('EXCLTIN ') CBLDCCLS('NOTIFY ') CBLDCCLS('EXNACPT ') CBLDCCLS('CANCEL ') CBLDCCLS('EXNCANCL') CBLDCCLS('O-NOTIFY')	6.2.1(3), 6.2.2(3), 6.7.1(3), 6.7.2(3), 6.7.3(3), 6.7.4(3), and 6.7.5(3)
The explanation of the library name to be specified as a linkage option has been changed.	5.2.2
data-name-C has been added to the explanation of data areas to which CBLDCRPS('GETWATCH') returns values.	6.3.5(4)
CBLDCCLS('STCONIF ') has been added as a request statement for setting terminal identification information.	6.4.5
The notes on the following functions have been changed: dc_clt_send_s function CBLDCCLS('SEND ') CBLDCCLS('EXSEND ')	4.6.1(5), 6.6.1(6), and 6.6.2(6)
An explanation that applies when a value from 1 to 65535 is set has been added for data-name-E of CBLDCCLS('RECEIVE2').	6.6.4(3)
An explanation that request statements provided by the character code converter can operate correctly in a multi-thread environment has been added.	6.8 and 6.9
A list of client environment definition items has been added.	7.1
The range of specifiable values for the DCSCDMULTICOUNT operand in the client environment definition has been changed to 1 to 4096, and the default value for the operand has been changed to 1.	7.2.5
Version changes for the following versions have been added: TP1/Client/W 07-02 TP1/Client/P 07-02	B.1

The following table lists changes in this manual (3000-3-D58-20(E)) and product changes related to this manual for uCosminexus TP1/Client/W 07-01 and uCosminexus TP1/Client/P 07-01.

Changes	Location
The dc_clt_receive2_s function has been added to the functions that can be executed from a CUP to receive messages from an MHP.	2.5.3
An explanation of executing functions that are not suitable for a multi-thread environment has been added.	2.9.2 and 2.9.3
XATMI interface functions are no longer able to operate in a multi-thread environment.	3.1.1, 4, and 4.8
For the dc_clt_cltin_s function, how the following arguments are specified has been changed: logname passwd	4.2.1(3)
An explanation that a client environment definition can be specified each time for each function call has been added for the following functions: dc_clt_cltin_s function dc_clt_accept_notification_s function dc_clt_cancel_notification_s function dc_clt_open_notification_s function	4.2.1, 4.7.1, 4.7.2, 4.7.3, 7.2.8, and 7.2.9
The directory of COBOL templates for TP1/Client/W has been changed.	5.3
The following operands have been added to the client environment definition to prevent data transmission delays between TP1/Client and TP1/Server Base: DCCLTRECVBUFSIZE DCCLTSENDBUFSIZE DCCLTTCPNODELAY	7.2.1, 7.2.2, and 7.2.5
If the name of the service group called by the dc_rpc_call_s function has not been defined in the file specified in the DCCLTSERVICEGROUPLIST operand, the DCCLTNOSERVER operand in the client environment definition determines how TP1/Client operates. An explanation to this effect has been added for the DCCLTSERVICEGROUPLIST operand.	7.2.5
An explanation stating the following has been added: If TP1/Client connects to a RAP-processing server, the operands in the RAP-processing listener service definition take precedence for the following operands: DCCLTTREXPTM DCCLTTREXPSP DCCLTTRCPUTM DCCLTINQUIRETIME DCCLTTRSTATISITEM DCCLTTROPTIITEM DCCLTTRWATCHTIME DCCLTTRRBINFO DCCLTTRLIMITTIME DCCLTTRRBRCV DCCLTTRRECOVERYTYPE	7.2.5
An explanation stating that the following functions read definitions from the file specified in the defpath argument has been added: dc_clt_cltin_s function dc_clt_accept_notification_s function dc_clt_cancel_notification_s function dc_clt_open_notification_s function	7.2.8 and 7.2.9
Messages have been added.	KFCA02445-E, KFCA02446-E, KFCA02447-E, KFCA02450-W, and KFCA02451-W
An explanation of changes made to functions, definitions, and messages when the TP1/Client version was updated has been added.	Appendix B

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