gtpi1m3v | System Installation Support Reference |
The Mapping of Airline Traffic over Internet Protocol (MATIP) session start
user exit, UMATSS, initializes a session with a device or remote
system. Characteristics for the session can be defined when a line
number, interchange address, and terminal address (LNIATA) and an IP address
pointer are passed to UMATSS. UMATSS also enables you to start a Type-A
host-to-host session or a Type-B session with a remote system when a terminal
address table (WGTA) entry is not associated with the session.
UMATSS is called in CMACMD.
Input
- session_type
- A pointer to an unsigned integer containing the session type (Type-A
conversational, Type-A host-to-host, or Type B).
- lniata
- A pointer to the LNIATA being addressed. If the LNIATA is equal to
-1, no WGTA entry is associated with the session.
- IPaddress
- A pointer to the in_addr structure that contains the 4-byte IP
address returned by the gethostbyname function.
- session_ID
- A pointer to the message identifier (ID). The contents of this
field will be set by the user and will be consistent with the session type
associated with the session.
- For Type-A conversational sessions and Type-A MATIP printers, an H1, H2,
A1, A2 value can be defined.
- For Type-A host-to-host sessions, an H1, H2, and flow ID can be
defined.
- For Type B sessions, a sender and recipient high-level designator (HLD)
can be defined.
- encoding
- A pointer to an integer containing the encoding of the format (such as
ASCII, EBCDIC, and so on).
- subtype
- A pointer to an integer containing the agent set control unit (ASCU)
length, traffic subtype, or messaging responsibility transfer protocol
used.
- The ASCU length for Type-A conversational sessions can be:
- 0 if no ASCUs are being specified
- 2 if a 2-byte ASCU is being specified
- 4 if a 4-byte ASCU is being specified.
- The traffic subtype for Type-A host-to-host sessions can be IATA
host-to-host or SITA host-to-host.
- The message responsibility transfer protocol for Type-B sessions can be
BATAP. The default is routing based on the application index in the
associated terminal address table (WGTA) entry.
- multiplex
- The type of ASCU or host-to-host session:
- The ASCU type for Type-A conversational sessions can be:
- A group of ASCUs with a 4-byte ID for each ASCU (H1H2A1A2)
- A group of ASCUs with a 2-byte ID for each ASCU (A1A2)
- A single ASCU for a single session (A1A2).
- The type of session for Type-A host-to-host can be:
- A multiple flow inside the TCP/IP connection (more than one host can be
connected)
- A single flow (a single host connected to a single host).
Programming Considerations
- All data levels must be returned to the caller in the same state that they
were on entry.
- You must modify UMATSS to initiate a MATIP session with a device or remote
system if you do not use the ZMATP command to associate an IP address with the
device or remote system.
Return Values
UMATSS returns one of the following values:
- 0
- The session setup data is returned.
- Negative Number
- The session setup data is not returned.