mcfauaps -s { MCF-communication-process-ID | application-startup-process-ID } [-e "[backout] [trace] [swmsg] [errevt] [execap] [holdlimit]"] -a application-name [-k application-name-type]

Sets the specified application in test mode and starts testing.

Enter the mcfauaps command only after shutdown of connection and completion of all message send and receive.

• -s MCF-communication-process-ID |
  application-startup-process-ID ~<hexadecimal> ((01-ef))
  Specify the MCF communication process ID or application startup process ID.
  To test an application specified by the dc_mcf_execap function, specify the application startup process ID. To test ERREVT, specify IDs based on Table 9-4. For other testing, specify the MCF communication process ID.
  Only one process ID can be specified.
  

  Table 9-4 IDs to be specified when testing ERREVT (mcfauaps command)

  ERREVT to be tested	ID to be specified
  	MCF communication process ID	Application startup process ID
  Invalid application name notification event (ERREVT1)	Y	--
  Message discard event that is issued by abnormal termination before the dc_mcf_receive function is issued (ERREVT2)	--	Y
  Message discard event generated by shutdown (ERREVT2)	Y#	Y#
  UAP abnormal termination notification event that is issued by abnormal termination during MHP execution (ERREVT3)	--	Y

  Legend:

  Y: Specifiable.

  --: Not specifiable.

  #: Specify both the MCF communication process ID and the application startup process ID.

  
  
• -e
  Specify the test mode options.
  Enclose two or more flag arguments with quotation marks (") and delimit each flag argument by inserting a space.
  

  Flag arguments:

  backout

  Restores the resources used in a transaction to pre-test status at completion of the transaction.

  When this flag argument is omitted, updated resources are used in their current status and are not restored to pre-test status.

  trace

  Collects MHP trace information during processing of a transaction in test mode.

  When this flag argument is omitted, no MHP trace information is collected.

  swmsg

  Invalidates messages sent by the MHP during processing of a transaction in test mode.

  Messages sent by the following functions issued by the test MHP are invalidated:

  dc_mcf_send function (message send)

  dc_mcf_sendsync function (synchronous message send)

  dc_mcf_resend function (message resend)

  When this flag argument is omitted, messages sent by the above functions are effective.

  errevt

  Suppresses error event activation if an error event occurs during testing. The following error events are suppressed:

  ERREVT1 (MCF event that reports detection of an invalid application name)

  However, the above error event can be suppressed only when testing is performed in a logical terminal.

  ERREVT2 (MCF event that reports discarding of a message at abnormal termination before issue of the dc_mcf_receive function)

  ERREVT2 (MCF event that reports discarding of a message generated at automatic shutdown)

  ERREVT3 (MCF event that reports UAP abnormal termination at abnormal termination during MHP execution)

  When this flag argument is omitted, activation of the above error events is not suppressed.

  execap

  Invalidates branch application startup messages issued by a transaction in test mode.

  When this flag argument is omitted, branch application startup messages are effective.

  holdlimit

  Suppresses MHP automatic shutdown should a transaction in test mode terminate abnormally.

  When this flag argument is omitted, MHP automatic shutdown is not suppressed.

• -a application-name ~<identifier of 1-8 characters>
  Specify the name of the application to be tested.
  You cannot use an asterisk (*) or a prefix character string plus an asterisk (prefix-character-string*) to specify application names in a batch.
  Only one application name can be specified.
  
• -k application-name-typet
  Specify the type of the application specified in the -a option:
  

  user

  User application

  mcf

  MCF event

  When this option is omitted, the application name specified in the -a option is assumed to be a user application name.