Activates the SPP or MHP process corresponding to the specified service group name and executes the service function for the specified service name.

• service-group-name ~<identifier of 1-31 characters>
  Specify the name of the service group that contains the service to be activated.
  
• service-name ~<identifier of 1-31 characters>
  Specify the name of the service to be activated.
  
• RPC-request-data-file-name ~<pathname>
  Specify the name of the RPC request data file that contains the input data received by the first service function when requesting the service from an RPC interface SPP.
  
• XATMI-request-data-file-name ~<pathname>
  Specify the name of the XATMI request data file that contains the input data received by the first service function when requesting the service from an XATMI interface SPP.
  
• TxRPC-request-data-file-name ~<pathname>
  Specify the name of the TxRPC request data file that contains the input data received by the first service function when requesting the service from a TxRPC interface SPP.
  
• MCF-receive-message-file-name ~<pathname>
  Specify the name of the MCF receive message file that contains the data for input to the UAP by the MCF function when requesting the service from an MHP.
  To create concatenated messages, specify a second MCF receive message file, prefixed with a plus sign (+).
  

• The service group name must be defined in the offline tester environment definition and the service name must be defined in the user service definition.
• If a tester file cannot be accessed, or if the file contents are incorrect, the next prompt is displayed for file name input. When concatenation of MCF receive message files is specified, if an error occurs at one of the files, specify both of the file names in the specification.
  Format
  

  file(group1:service1)?> 1. 2.

  1. Service group name
  2. Service name