(a) set format

[set test_mode=target|usable|dmyspp|simmhp|no]
[set test_transaction_commit=Y|N]
[set test_adm_call_command=do|skip|file]
[set test_xatmi_send_file=Y|N]
[set test_debugger="{dbx|cbltd|cblcv}[command-argument]"]
[set test_data_trace=Y|N]

(b) Command format

None.

Enables execution of the online tester at the user server. Add the definitions to each service group in the OpenTP1 user service definition.

(a) set format

Operands

• test_mode=target|usable|dmyspp|simmhp|no ~<<no>>
  Specify whether the UAP is to be tested when the online tester is activated.
  

  target

  Test-only UAP

  Specify this option to set the UAP as a test-only UAP. All the facilities of the online tester (disabling resources updating, collecting UAP trace information, and so on) are used in testing the UAP.

  Service requests cannot be made from a test-only UAP to a non-test UAP, or from a non-test UAP to a test-only UAP.

  usable

  Usable UAP

  Specify this option to set the UAP as an SPP to which service requests are sent from the UAP being tested.

  A usable UAP runs in test mode when the UAP being tested makes a service request. The facilities of the online tester, such as disabling resources updating, can be used.

  When a service request is made from a non-test UAP, the usable UAP runs in non-test mode and the online tester facilities are not available.

  dmyspp

  Dummy SPP

  Specify this option to use the online tester's server UAP simulator to simulate the SPP without actually activating it.

  simmhp

  Simulate MHP

  Specify this option to use the online tester's MCF simulator and link simulation functions to the MHP.

  no

  Non-test UAP

  Specify this option to exclude the UAP from testing. Service requests cannot be made from a test UAP to a UAP with the no specification.

  The following tables show the relationships between the test_mode operands and the online tester facilities that can be used for UAPs, as well as the relationships between a calling UAP and a called UAP when a service is requested.
  

  Table 3-1 test_mode specifications and available test facilities

  Available test facility	target	usable	dmyspp	simmhp	no
  Client UAP simulator	Y	Y	--	--	N
  Server UAP simulator	Y	Y/N	--	Y	N
  MCF simulator	Y#	Y/N	--	Y#	N
  Disabling the resources update process	Y	Y/N	--	Y	N
  Operating command simulator	Y	Y/N	--	Y	N
  Collecting UAP trace information	Y	Y/N	--	Y	N
  Debugger interlocking	Y	N	--	Y	N

  Legend:

  Y: Available.

  Y/N: May be available, depending on the type of function.

  Main function

  Not available.

  Service function

  Available when using the client UAP simulator for service requests. In other cases, the test facility is available if it can be used with the calling UAP (or with the UAP that makes the first request when a service extends over multiple UAPs).

  N: Not available.

  --: Not applicable.

  #: The UAP must be linked to the MCF simulation functions provided by the online tester.

  
  

  Table 3-2 Relationships between calling UAP and called UAP when requesting services

  Calling UAP		Called UAP
  		target	usable	dmyspp	simmhp	no
  target		Y	Y	Y	--	N
  usable	Test mode	Y	Y	Y	--	N
  	Non-test mode	N	Y	N	--	Y
  dmyspp		--	--	--	--	--
  simmhp		Y	Y	Y	--	N
  no		N	Y	N	--	Y

  Legend:

  Y: Service requests can be made.

  N: Service requests cannot be made.

  --: Not applicable.

  
  
• test_transaction_commit=Y|N ~<<N>>
  Specify whether a commit or rollback is performed at a synchronous point when a transaction running in test mode occurs in this UAP.
  

  Y

  Commit

  N

  Rollback

• test_adm_call_command=do|skip|file ~<<do>>
  Specify whether to simulate operating command execution when a dc_adm_call_command function is issued in this UAP.
  

  do

  Execute operating commands.

  skip

  Instead of executing the command, use the default result.

  This option is valid only when target or simmhp is set in the test_mode operand, or when usable is specified and the UAP is running in test mode.

  file

  Instead of executing the command, use the data in the operating command result data file as the execution result.

  This option is valid only when target or simmhp is set in the test_mode operand, or when usable is specified and the UAP is running in test mode.

• test_xatmi_send_file=Y|N ~<<N>>
  Specify whether the data sent to the simulated UAP by the server UAP simulator is to be output to the XATMI send data file when a conversational service is requested in an XATMI interface.
  

  Y

  Outputs the send data to the file.

  N

  Does not output the send data to the file.

  This option is ignored if specified for a UAP other than a simulated UAP (dmyspp specified in the test_mode operand).
  
• test_debugger="{dbx|cbltd|cblcv}[command-argument]"
  When activating the UAP by interlocking the debugger, specify the necessary debugger command name and a command argument for that debugger command.
  When a UAP is given this definition, executing the utodebug command activates this UAP together with the specified debugger.
  Inadvertently executing the dcsvstart or dcstart command for a UAP with this definition causes the command to fail, outputting an error message.
  To terminate the UAP that was activated with the utodebug command, execute the utodbgstop command from a window other than that was used to execute the utodebug command.
  If the UAP is terminated with a command other than the utodbgstop command, the OpenTP1 system and the online tester may provide different UAP states. The executed command must wait until the debugger terminates.
  It is impossible to re-activate a UAP process that was activated with the debugger. After termination of the UAP process that is interlocked to the debugger, reexecuting this UAP needs to stop the debugger, then reexecute the utodebug command.
  The UAP with this definition can be active in a single process regardless of the parallel_count operand value specified in the user service definition of the corresponding UAP.
  It is impossible to enable or disable shutdown for the UAP that was activated with the debugger.
  
• test_data_trace=Y|N ~<<N>>
  Specify whether the complete I/O data issued in this UAP for the function is to be collected as trace information. For the function that can use a facility that collects the complete I/O data trace information, see Subsection 2.8.1 Collecting UAP trace information.
  

  Y

  Collects the complete I/O data as UAP trace information.

  This option is valid only when a value of 1 or greater is specified in the max_trace_file_size operand of the tester service definition to use the UAP as the test target.

  N

  Collects a part of the I/O data as UAP trace information.

  This option is valid only when a value of 1 or greater is specified in the max_trace_file_size operand of the tester service definition to use a UAP as the test target.

(b) Command format

None.

• When specifying simmhp in the test_mode operand, match all the other specifications in the user service definition with the SPP specifications.
  

  Example:

  type=other

  Also, specify queue in the receive_from operand.
  
• User service default definitions cannot be specified as online tester definitions in the user service definition. This prevents a real job UAP from being run in error in a test environment.
• When using the MCF simulator, specify Y in the atomic_update operand of the user service definition if a transaction MHP is to be executed.
• The schedule priority of a test UAP depends on value specified in the schedule_priority operand of the user service definition. When executing a test UAP concurrently with a real job UAP, consider the effect on the performance of the job UAP when specifying the priority of the test UAP.
• If zero is specified in the uap_trace_max operand of the user service definition (even if a value of 1 or higher is specified in the max_trace_file_size operand of the tester service definition), a warning message output, indicating that UAP trace information cannot be collected.
• When the online tester is not being used, the dc_rpc_open function returns an error code at activation of a UAP that has a value other than no specified in the test_mode operand. This prevents a test UAP from being run in error as a real job UAP.
• To interlock a UAP to the debugger, specify file or skip for the test_adm_call_command operand. When the UAP is interlocked to the debugger by specifying do for the test_adm_call_command operand, issuing the dc_adm_call_command function lets the UAP wait for a response, disabling debugger control. To solve this, issue the utodbgstop command to terminate the UAP, then terminate the debugger.
• Do not issue a fork system call or system(3C) function to a UAP interlocked with the debugger. Issuing these functions lets the UAP wait for a response, disabling debugger control. To solve this, issue the utodbgstop command to terminate the UAP, then terminate the debugger.
• Debugger interlocking is unavailable when running under the multi-node environment.
• If possible, avoid testing a UAP interlocked with the debugger under the OpenTP1 system where a real job UAP is active. This is to prevent a system failure caused by normal or abnormal termination of the UAP interlocked with the debugger under the OpenTP1 system where the UAP is operating.
• Consider debugger interlocking operations and operation times when specifying monitoring time values in the user service definition for the UAP interlocked with the debugger. A thoughtlessly specified value may frequently cause a time-out error.
• When do is specified for the test_adm_call_command operand for a UAP to start another UAP in the test mode using the dcsvstart command set in the argument of the dc_adm_call_command function, specify the environment variable DCUTOKEY in the user service definition of the UAP that issues the function.