gtpi1m3t | System Installation Support Reference |
The Mapping of Airline Traffic over Internet Protocol (MATIP) router user
exit, UMATRO, allows messages to be routed to the appropriate application when
a terminal address table (WGTA) entry is not used to route the message.
This user exit is entered when data is received for either Type-A host-to-host
messages or Type-B messages.
UMATRO is called in CMADAT.
Input
- session_type
- An unsigned integer containing the type of message (Type-A host-to-host or
Type B).
- sock
- An integer containing the socket number.
- IPaddress
- A pointer to the 4-byte Internet Protocol (IP) address of the message
origin.
- message_text
- A pointer to a data message.
- subtype
- An integer containing the traffic subtype for Type-A host-to-host
sessions, or end-to-end messaging responsibility transfer protocol used for
Type B.
- message_ID
- A pointer to the message identifier.
- For Type-A host-to-host sessions, the message identifier contains the H1,
H2, and flow ID.
- For Type-B sessions, the message identifier contains the sender and
recipient high-level designator (HLD).
- pload_len
- The data length.
Programming Considerations
- The message passed to UMATRO is not translated or converted to AM0SG
format, and an routing control parameter list (RCPL) is not built before
UMATRO is entered.
- UMATRO is not used for Type-A conversational sessions.
- Equates for the type of message are defined in the
c$trmeq.h header file, which is included by
UMATRO.
- Equates for the traffic subtype for Type-A host-to-host sessions and for
end-to-end messaging responsibility transfer protocol used for Type-B sessions
are defined in UMATRO:
- IATA host-to-host traffic subtype for Type-A host-to-host sessions.
- SITA host-to-host traffic subtype for Type-A host-to-host sessions.
- BATAP end-to-end message responsibility transfer protocol for Type-B
sessions.
Return Values
UMATRO is expected to be entered without a return to the caller.