hcitrxidtest

This command simulates getting the TRXID on an incoming message from the source thread.

This runs any inbound TPS for the source thread before the engine retrieves the TRXID. This is necessary because the TPS could change the message content.

hcitrxidtest [-a] -C [tclscript] [-V] [-x encoding] [-d] [-f format] 
[-c drivercontrol] -P [dbgport] [-r thread] thread data_file
  • -a processes all records in the file.
  • -C [tclscript]

    Specify a script to evaluate before running the UPoC. This is only supported for Tcl UPoC.

    You can use the script to do configurations. For example, to load external Tcl files using the source command:

    -C 'source myproc.tcl'
  • -V shows verbose mode.
  • -x encoding is the encoding name for the data file. This encodes from encoding to UTF-8.
  • -d processes as DATA messages. This is the default.
  • -f format specifies the file format:
    • -f len10 specifies 10-byte length-encoded.
    • -f nl specifies newline terminated. This is the default.
    • -f eof specifies end-of-file terminated.
  • -c drivercontrol is used to set the content to message metadata DRIVERCONTROL. You can input any content to set to drivercontrol using this option.

    For a test on DICOM messages, -c drivercontrol is required, where drivercontrol is {AbstractSyntax***} {TransferSyntax***}. This is required to get the TRXID.

    See DICOM abstract syntax values and DICOM transfer syntax values.

  • -P [dbgport]

    This is the TCP listening port number of the debugger server. If this is not given, then a free port is allocated by the operating system.

  • -r thread processes as REPLY to thread.
  • thread specifies the source thread to simulate.
  • data_file specifies the data file with which to test.