OpenTP1 Version 7 Tester and UAP Trace User's Guide
By creating a test data definition file, the user can easily create tester files using the tester file creation facility.
A test data definition file can have any name. The following tester files can be created from a test data definition file:
#comment ]1. start tester-file-ID tester-file-kind output-destination-file-name ]2. keyword = input-data ]5. keyword = input-data sep ]3. keyword = input-data : : : : keyword = input-data end ]4. |
Note that the italicized numbers in the box above correspond to the numbers under (3) Description below.
Allows the tester file creation command to create a tester file after the definition of test data needed for the tester file.
One line in the definition file can contain up to 512 bytes including a carriage return code.
The following describes an input data format for specifying user data.
Specify the length of the entire user data as fixed information data in the following format.
data_len=bytes
If the data specified as user data is larger than the data length, the system truncates the data and issues a message. If the data is smaller than the data length, nothing is appended to it.
Example:
Using the tester file creation command, initialize the user data for the specified user data length.
Set character data in the following format:
data='data'
Do not add a null character to the end of character data.
Example:
Set binary data in the following format:
data=data
Data can be written in decimal and hexadecimal notation, as follows:
Data is set with the int type.
Set hexadecimal code data in the following format:
data=(code)0xdata
In data, write n bytes of 2n-digit data using hexadecimal code. The user can write as many number of bytes as required within the maximum length of a line.
Write a value of 0x00-0xff for one byte of data.
The data is assumed as binary data written in hexadecimal notation if (code) is not specified.
Example:
The system processes a carriage return code, tab code, null character, single quotation mark ('), and backslash (\) to be special characters in character data. Enter these characters as follows.
Character | Notation |
---|---|
Carriage return | \n |
Tab code | \t |
Null character | \0 |
' | \' |
\ | \\ |
Use the following format when using data as user data read from the file.
data=(file) file-pathname
Specify the beginning of data as follows.
data=[offset-from-start-of-user-data] data
Example:
data=data =data : :
When multiple data types are described, adjacent data types may differ from each other. This time the tester file creation command sets data by automatically adjusting the boundary for the preceding data. However, no boundary adjustment takes place when:
The following tables list the keywords and the formats of the corresponding input data for each tester file. For the type of information to be specified, see the description of each tester file in Section 11.2 User-Created files.
Table 11-3 RPC request data file keywords and input data formats
Keyword | Specified information | Description |
---|---|---|
out_len | Response area length | Before data, specify the response area length in decimal or hexadecimal placed in the dc_rpc_call function. |
data_len | Data length | Before data, specify the user data length in decimal or hexadecimal passed to the server UAP with the dc_rpc_call function. |
data | Data | Specify the user data passed to the server UAP with the dc_rpc_call function. |
Table 11-4 XATMI request data file keywords and corresponding input data formats
Keyword | Specified information | Description |
---|---|---|
call_kind | Call kind | Before data, specify one of the following character strings as a function type for service request.
|
buff_type | Type | Before data, specify one of the following character strings as a buffer type.
|
sub_type | Subtype | Before data, specify a subtype within 16 characters.
|
flag | Flag | Before data, specify the following character string as a flag to be passed to the service function. Separate multiple flags with a vertical line (|).
|
data_len | Data length | Before data, specify the user data length in decimal or hexadecimal to be passed to the server UAP with the tpcall, tpacall, or tpconnect function. |
data | Data | Specify user data to be passed to the server UAP with the tpcall, tpacall, or tpconnect function. |
Table 11-5 TxRPC request data file keywords and corresponding input data format
Keyword | Specified information | Description |
---|---|---|
version | Version number | Before data, specify the version number in decimal or hexadecimal specified in the interface definition of the txidl command. This information is optional. If omitted, zero is assumed. The range of specification is 0-65535.
|
data_len | Data length | Before data, specify the user data length in decimal or hexadecimal to be passed to the server UAP. |
data | Data | Specify user data to be passed to the server UAP. |
Table 11-6 RPC response data file keywords and corresponding input data formats
Keyword | Specified information | Description |
---|---|---|
data_len | Data length | Before data, specify the user data length in decimal or hexadecimal to be passed to the client UAP on service termination. |
data | Data | Specify user data returned to the client UAP on service termination. |
Table 11-7 XATMI response data file keywords and corresponding input data formats
Keyword | Specified information | Description |
---|---|---|
buff_type | Type | Before data, specify one of the following character strings as a buffer type.
|
sub_type | Subtype | Before data, specify a subtype within 16 characters.
|
rval | Service termination code | Before data, specify one of the following character strings as a service termination code.
|
rcode | Return code | Before data, specify the return code in decimal or hexadecimal. |
data_len | Data length | Before data, specify the user data length in decimal or hexadecimal passed to the client UAP on service termination. |
data | Data | Specify user data returned to the client UAP on service termination. |
Table 11-8 TxRPC response data file keywords and corresponding input data format
Keyword | Specified information | Description |
---|---|---|
data_len | Data length | Before data, specify the user data length in decimal or hexadecimal to be passed to the client UAP. |
svc_rtn | Return value | Before data, specify the return value in decimal or hexadecimal to be passed to the client UAP. |
data | Data | Specify user data to be passed to the client UAP. |
Table 11-9 XATMI receive data file keywords and input data formats
Keyword | Specified information | Description |
---|---|---|
buff_type | Type | Before data, specify one of the following character strings as a buffer type.
|
sub_type | Subtype | Before data, specify a subtype within 16 characters.
|
event | Event flag | Before data, specify one of the following character strings as an event flag passed to the tprecv function.
|
data_len | Data length | Before data, specify the user data length in decimal or hexadecimal passed to the tprecv function. |
data | Data | Specify user data passed to the tprecv function. |
sep | sep statement | When specifying data for multiple services, place a sep statement at the end of data for one service. Do not place this statement after the last data. |
Table 11-10 MCF receive message file keywords and corresponding input data formats
Keyword | Specified information | Description |
---|---|---|
termname | I/O logical terminal name | Before data, specify an I/O logical terminal name within 8 characters passed to the dc_mcf_receive function. |
mapname | Map name | Before data, specify a map name within 8 characters passed to the dc_mcf_receive function. |
seg_kind | Segment type | Before data, specify one of the following characters as a segment type passed to the dc_mcf_receive function.
|
data_len | Message length | Before data, specify the user data length of the segment in decimal or hexadecimal passed to the dc_mcf_receive function. |
data | Message | Specify user data of the segment passed to the dc_mcf_receive function. |
Table 11-11 Operation command result data file keywords and corresponding input data formats
Keyword | Specified information | Description |
---|---|---|
status_code | Operation command result code | Before data, specify a result code in decimal returned by the operation command. |
outsize | Standard output character string length | Before data, specify the message length in decimal or hexadecimal the operation command outputs to standard output. |
errsize | Standard error output character string length | Before data, specify the message length in decimal or hexadecimal the operation command outputs to standard output error. |
data | Standard output character string | Specify a message with character data the operation command outputs to standard output. |
data | Standard error output character string | Specify a message with character data the operation command outputs to standard output error. |
sep | sep statement | When specifying data for multiple commands, place a sep statement at the end of data for one command. Do not place this statement after the last data. |
All Rights Reserved. Copyright (C) 2006, 2010, Hitachi, Ltd.