You can apply the query command to a circuit or client entity. Typically, you use a client entity, unless you need to query a system that has no corresponding client entity. You can use the same attributes for either a client or a circuit. For example, you can use either of the following commands:
ncl>query mop client client-name SAP sap
ncl>query mop circuit circuit-id SAP sap
In both commands, sap is the service access point on the target node, specified as 2 hexadecimal digits, to which the XID message is sent. The default is 00.
The dtr program functions as a slave to dts and exists as defined object 63 at the remote node. The dts program initiates each test by issuing a connect request to dtr. The dts program passes parameter information pertinent to the type of test requested to dtr in the optional data of the connection request. You can use the dts user interface to customize the test to be performed by issuing commands with options.
Do the following to start dts/dtr tests:
Step | Action | ||||
---|---|---|---|---|---|
1 | Be sure that all of the DECnet protocol layers (Session Control, Transport, Routing, and Data Link) are in the on state. | ||||
2 |
Enter one of the following commands:
The system responds with a message and a prompt similar to the following: DTS initiated on Mon Feb 26 13:06:22 1994 |
||||
3 | Enter dts commands at the command prompt. | ||||
4 | To end testing, type exit in response to the dts prompt. The dts program displays a termination message on your screen when it exits, and the system prompt reappears. |
You can also enter dts commands with a dts command file (see Section 3.10.4). You can press the up arrow key to recall previously entered commands.
Use the following format to enter dts commands:
test [qualifiers][test-specific-qualifiers]
The following table describes the command components.
Component | Description | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
test | Specifies the type of test, which must be one of the following: | ||||||||||||
|
|||||||||||||
qualifiers | Specifies any number of the following optional qualifiers. These qualifiers remain in effect for all applicable tests until you change them or exit from dts. A slash (/) must precede each qualifier. | ||||||||||||
Qualifier |
Description
|
||||||||||||
test-specific-qualifiers | Specifies any number of test-specific qualifiers, as defined in the sections that describe each test. Test-specific qualifiers apply to the current test only. |
The dts command syntax uses the following conventions:
The following OpenVMS example shows how to instruct dts to process the commands contained in the file dts.com and to redirect the output to the file dts.log.
$ run sys$system:dtsend/output=dts.log
The following Digital UNIX example shows how to instruct dts to process the commands contained in the file dtsscript and to redirect the output to logging file dts.log.
You can perform the following connect tests:
Test | Description |
---|---|
Connect reject without user data | The dts node sends a connection request to the dtr node. The dtr node returns a rejection message that does not contain optional data. |
Connect accept without user data | The dts node sends a connection request to the dtr node. The dtr node returns an acceptance message that does not contain optional data. |
Connect reject with standard user data | The dts node sends a connection request to the dtr node. The dtr node returns a rejection message that contains a standard string of optional data. If the transport is NSP, it is 16 bytes and, if the transport is TP4, it is 32 bytes. |
Connect accept with standard user data | The dts node sends a connection request to the dtr node. The dtr node returns an acceptance message that contains a standard string of optional data. If the transport is NSP, it is 16 bytes and, if the transport is TP4, it is 32 bytes. |
Connect reject with received user data used as reject user data | The dts node sends a connection request that contains optional data to the dtr node. The dtr node returns a rejection message that contains the same optional data. |
Connect accept with received user data used as accept user data. | The dts node sends a connection request that contains optional data to the dtr node. The dtr node returns an acceptance message that contains the same optional data. |
Do the following to start a connect test:
The following table describes the test-specific-qualifiers.
Qualifier | Description | |
---|---|---|
/ type= subtest | Specifies the type of test, where subtest can be: | |
accept | Connect accept test (default) | |
reject | Connect reject test | |
/ return= type or noreturn | Specifies the type of data returned by dtr. The type can be: | |
standard | Standard user data | |
received | Received user data | |
/noreturn | No optional user data returned (default) | |
/transport=dna_nsp or
dna_tp4 |
For Digital UNIX systems only. Defaults to the first available protocol tower. |
This command invokes a connect accept test (by default) with remote node MONTRL.
dts>connect/nodename=montrl/return=received
The dtr program returns received user data as part of the test.
You can perform the following data tests:
Invoke dts and use this command to start a data test:
data[qualifiers] [test-specific-qualifiers]
On OpenVMS systems, the value of the node qualifier must be a minimum of 4 characters.
The following table describes the test-specific-qualifiers.
Qualifier | Description | |
---|---|---|
/ type= subtest | Specifies the type of test, where subtest can be: | |
sink | Sink test (default) | |
sequence | Sequence test | |
pattern | Pattern test | |
echo | Echo test | |
/ size= number |
Specifies data message length in bytes.
On OpenVMS systems, number is a value from 5 to 4,095. On Digital UNIX systems, number is a value from 1 to 2,048 (default=128). The minimum value for number on a sequence test is 4 and on a pattern test is 5. A size of 4,095 returns an error message on an echo test. |
|
/ test-duration | Specifies duration of the test in one of the following formats: | |
seconds= number |
Range: 1 to 60
1 to 59 on OpenVMS |
|
minutes= number |
Range: 1 to 60
1 to 59 on OpenVMS |
|
hours= number | Range: 1 to 24 | |
OnOpenVMS systems, the default is
seconds=30.
On Digital UNIX systems, the default is seconds=15. |
||
/
flow=
type or
/ noflow (default) |
Specifies type of flow control, if any, where type can be: | |
segment | Segment flow control | |
message | Message flow control (default, if / flow is specified) | |
If dtr is running on OpenVMS software, it must use the system default. | ||
/
rqueue=
number or
/ squeue= number |
For Digital UNIX systems only. Specifies the number of pending receives for dtr to maintain, where number is a value from 1 to 16 (default = 1). If the remote system is a DECnet-Plus node, this parameter is ignored. | |
/
nak=
number or
/ noack |
For Digital UNIX systems only. Specifies the number of segments between negative acknowledgments (NAKs). If the remote system is a DECnet-Plus node, this parameter is ignored. | |
/
back=
number or
/ noback |
For Digital UNIX systems only. Specifies the number of segments before back pressuring. If the remote system is a DECnet-Plus node, this parameter is ignored. | |
/
transport=dna_nsp or
dna_tp4 |
For Digital UNIX systems only. Defaults to the first available protocol tower. |
This command invokes the data test with the sink subtest (by default). The dts program sends messages to dtr on node JONES (by default from a previous command). The message size is 512 bytes, and the test lasts 30 seconds. The transport protocol is printed only when you specify a transport.
dts>data/size=512/seconds=30 DTS --I-- Test started at 11:23:30 DTS --I-- Test finished at 11:24:00
Test parameters: Target node "jones" Test duration (sec) 30 Message size (bytes) 512 Summary statistics: Total messages SENT 48 Total bytes SENT 24576 Messages per second 1.60 Bytes per second 819.20 Line throughput (baud) 6553
You can perform the following disconnect tests:
Test | Description |
---|---|
Disconnect without data | The dtr node sends a disconnect message that does not contain user data to the dts node. |
Abort without user data | The dtr node sends an abort message that does not contain user data to the dts node. |
Disconnect with standard user data | The dtr node sends a disconnect message that contains a standard string of optional data to the dts node. If the transport is NSP, this is 16 bytes, and if the transport is TP4, it is 32 bytes. |
Abort with standard user data | The dtr node sends an abort message that contains a standard string of optional data to the dts node. If the transport is NSP, this is 16 bytes, and if the transport is TP4, it is 32 bytes. |
Disconnect with received connect user data used as disconnect user data | The dts node sends a message containing optional user data to the dtr node. The dtr node returns a disconnect message containing the same optional data to the dts node. |
Abort with received connect user data used as abort user data | The dts node sends a message containing optional user data to the dtr node. The dtr node returns an abort message containing the same optional data to the dts node. |
Invoke dts and use the following command to start a disconnect test:
disconnect[qualifiers] [test-specific-qualifiers]
The following table describes the test-specific-qualifiers.
Qualifier | Description | |
---|---|---|
type= subtest | Specifies the type of test, where subtest can be: | |
synchronous | Synchronous disconnect test for Digital UNIX systems only | |
abort | Disconnect abort test (default) | |
/
return=
type or
/ noreturn |
Specifies the type of data returned by dtr. The type can be: | |
standard | Standard user data | |
received | Received user data | |
The /noreturn qualifier causes no optional user data to be returned (default). |
This command invokes a synchronous disconnect test with remote node PARIS.
dts>disconnect/nodename=paris/type=synchronous
The dtr program will not return any optional user data.
You can perform the following interrupt tests:
Invoke dts and use this command to start an interrupt test:
interrupt[qualifiers] [test-specific-qualifiers]
The following table describes the test-specific-qualifiers:
Qualifier | Description | |
---|---|---|
/ type= subtest | Specifies the type of test, where subtest can be: | |
sink | Sink test (default) | |
sequence | Sequence test | |
pattern | Pattern test | |
echo | Echo test | |
size= number | Specifies data message length in bytes, where number is a value from 0 to 16 (default = 16). The minimum value for number on a sequence test is 4 and on a pattern test is 5. The minimum value for number on an echo test is 5. | |
test-duration | Specifies duration of the test in one of the following formats: | |
seconds= number |
Range: 1 to 60
1 to 59 on OpenVMS |
|
minutes= number |
Range: 1 to 60
1 to 59 on OpenVMS |
|
hours= number | Range: 1 to 24 | |
The default is seconds=15. | ||
/
rqueue=
number or
/ squeue= number |
For Digital UNIX systems only. Specifies number of pending receives for dtr to maintain, where number is a value from 1 to 16 (default=1). If the remote system is a DECnet-Plus node, this parameter is ignored. |
This command invokes the interrupt test with the pattern subtest. The dts program sends interrupt messages to dtr on node DALLAS, where test information is to be printed. The default message size value is used and the test lasts for 30 seconds.
dts> interrupt/nodename=dallas/print/type=pat/seconds=30 DTS --I-- Test started at 17:44:10 DTS --I-- Test finished at 17:44:40 Test parameters: Target node "dallas" Test duration (sec) 30 Message size (bytes) 16 Summary statistics: Total messages SENT 2734 Total bytes SENT 43744 Messages per second 91.1 Bytes per second 1458 Line throughput (baud) 11665
This chapter describes solving problems using DECnet over TCP/IP.
PS_PROFILE_003.HTML OSSG Documentation 2-DEC-1996 12:34:16.07
Copyright © Digital Equipment Corporation 1996. All Rights Reserved.