
VTCPD Features User Manual
Page 50 P0602483 Ver: 03.41
VTCPD Features User Manual
Message Identification (ID)
VTCPD uses a Message ID to associate received messages with application requests.
Requests sent to the host from an application and the response to the application are
identified as corresponding to each other because they use the same Message ID.
Message IDs are not used when there is only one connection per line, because in this
configuration, the line identifies the source and destination of the message.
Messages are identified by unique combination of N consecutive bytes, starting from
the M -byte position of the message. This is called the Message ID. Unless a host
connection is exclusively reserved for a phone line (see below), all messages must
include message ID.
VTCPD uses one of the following methods to assign the Message ID:
If the Message ID is assigned by applications, they are responsible for assuring that no
two outstanding requests have the same ID. The daemon doesn't check the context of
the ID field. It only matches it byte for byte with the ID in host responses. If two
requests with the same ID are pending at the same time, the results will be
unpredictable.
If host data contains a Message ID that cannot be associated with any phone line, the
data is discarded. However, it is possible to pre-assign an administrative phone line
that receives all unidentified messages. The messages are sent to the line as the data
portion of the condition unexdata.
Message ID
Bytes Message ID Example
one Binary phone line number of the application sending the request
-I 2
two Binary phone line number and MPS number of the requesting
application.
-I 2:1
three ASCII phone line number of the requesting application in the
format 999.
-I 201
six
ASCII phone line and MPS number of the requesting
application.
-I 6:24
Comentários a estes Manuais