gtpm2m1v | Migration Guide: Program Update Tapes |
The following section discusses the migration considerations for Mapping of Airline Traffic over Internet Protocol (MATIP).
See the APEDIT for APAR PJ26161 for information about prerequisite APARs.
MATIP support allows the TPF 4.1 system to receive and transmit airline reservation, ticketing, and messaging traffic over a Transmission Control Protocol/Internet Protocol (TCP/IP) network. MATIP support provides the following benefits:
MATIP support can coexist with current network configurations. Minimum changes to applications are needed for MATIP support; the current system architecture is maintained for the internal routing of messages between the network and the application.
MATIP support is provided for the communication of two main types of airline traffic: transactional and messaging.
Transactional traffic (known as Type A) can be described as real-time query and response. Type A is high priority but limited protection; if a message is lost in the network, you resend the query. Transactional traffic can be broken down into either Type-A conversational (host-to-terminal) or Type-A host-to-host (one airline host system to another).
Messaging traffic (known as Type B) is more highly protected but less immediate. The different protection protocols used to secure Type-B messages are transparent to MATIP support and are provided by you.
When MATIP support is enabled, logical sessions are established over Transmission Control Protocol (TCP) connections that link the TPF 4.1 system to the remote end. One MATIP session will correspond to one TCP connection or one TCP/IP socket. These sessions can handle only one traffic type at a time; a Type-A host-to-host message cannot be sent on the same session that was originally established for sending a Type-B message. Once session characteristics are established, each data message that flows over that session is assumed to have the same characteristics.
Type-A transactional traffic can be concentrated on one MATIP session. For example, the TPF 4.1 system can have one Type-A conversational MATIP session with a remote MATIP concentrator. The concentrator can have several agent set control units (ASCUs) attached to it, and each ASCU can have several different terminals attached to it. All data received by the TPF 4.1 system from this network cluster will be processed on the same MATIP session; any data going to one of the terminals will be sent over the same MATIP session. This is known as multiplexing the sessions. In the same way, Type-A host-to-host sessions can be multiplexed when they are defined as Societe Internationale de Telecommunications Aeronautiques (SITA) host-to-host sessions, allowing for several airline flows to be sent on one MATIP session. Host-to-host sessions defined as traditional International Air Transport Association (IATA) host-to-host sessions cannot be multiplexed.
The TPF 4.1 system with MATIP support uses a line number, interchange address, and terminal address (LNIATA) for internal routing of messages. When a destination terminal or host is migrated to use MATIP support, you update the corresponding terminal address table (WGTA) entry to indicate that the destination is now a MATIP device. All future messages for this LNIATA will now be handled by the MATIP layer, and the previous communications protocols will be bypassed. You do not have to modify the original application for this to happen. If your TPF 4.1 system does not use LNIATAs for message routing, seven new user exits are provided so you can customize MATIP support to route messages to their destination.
The IP Bridge, unique to the TPF 4.1 system, is provided with MATIP support. The IP Bridge allows you to send non-airline-specific traffic over a TCP/IP network. TCP/IP messages received on a user-defined port number are converted into application message format (AM0SG), assigned an origin LNIATA, and passed to the system message router for routing to the application. Applications can use the ROUTC macro to send messages from the TPF 4.1 system. The TPF 4.1 system intercepts outbound messages and bypasses other communication protocols after the LNIATA has been defined as an IP Bridge device. The message is removed from its AM0SG format and is sent over the previously established TCP connection.
For more information about MATIP, see the Societe Internationale de Telecommunications Aeronautiques (SITA) Web site at: http://www.sita.int
There are no changes.
The following section summarizes interface changes.
The following section summarizes C/C++ language changes. This information is presented in alphabetic order by the type of C/C++ language information. See the TPF C/C++ Language Support User's Guide and TPF Application Programming for more information about the C/C++ language.
Table 543 summarizes changes to the build scripts used by the build
tool. This information is presented in alphabetic order by the name of
the build script.
Table 543. Changes to Build Scripts for Mapping of Airline Traffic over Internet Protocol (MATIP)
Build Script | Type | New, Changed, or No Longer Supported? | Description of Change |
---|---|---|---|
CMAPBS | DLM | New | Build script for the ZMATP functional message. |
CMATBS | DLL | New | Build script for the MATIP primary DLL. |
CMIABS | DLM | New | Build script for MATIP Type-A inbound. |
CMIBBS | DLM | New | Build script for MATIP Type-B inbound. |
CMICBS | DLM | New | Build script for MATIP outbound interface to the session manager. |
CMIRBS | DLM | New | Build script for MATIP cycle down. |
CMITBS | DLM | New | Build script for MATIP cycle up. |
CMOABS | DLM | New | Build script for MATIP Type-A outbound. |
CMOBBS | DLM | New | Build script for MATIP Type-B outbound. |
CRIIBS | DLM | New | Build script for IP Bridge inbound. |
CRIOBS | DLM | New | Build script for IP Bridge outbound. |
CTALBS | DLM | Changed | Build script for the CTAL ISO-C library. |
There are no changes.
Table 544 summarizes the general use C/C++ language header file changes. This information is presented in alphabetic order by the name of the general use C/C++ language header file.
General use means these header files are available for your
use.
C/C++ Language Header File | New, Changed, or No Longer Supported? | Do You Need to Recompile Segments? |
---|---|---|
c$ck2sn.h | Changed | No |
c$iscfdt.h | Changed | No |
c$itrtbl.h | Changed | No |
c$rc0pl.h | Changed | No |
c$trmeq.h | Changed | No |
tpfapi.h | Changed | No |
Table 545 summarizes the general use C/C++ language header file
changes that are for IBM use only. This information is presented in
alphabetic order by the name of the general use C/C++ language header
file.
C/C++ Language Header File (IBM Use Only) | New, Changed, or No Longer Supported? | Do You Need to Recompile Segments? |
---|---|---|
i$matp.h | New | Yes |
i$mscb.h | New | Yes |
i$tcpc.h | Changed | No |
Table 546 summarizes changes to the library interface scripts used by
the library interface tool and the build tool. This information is
presented in alphabetic order by the name of the library interface
script.
Library Interface Script | New, Changed, or No Longer Supported? | Description of Change |
---|---|---|
CTALXV | Changed | Added linkage for the lwgtc and rwgtc internal library functions. |
Table 547 summarizes the library member (object file) changes.
This information is presented in alphabetic order by the name of the library
member (object file).
Library Member (Object File) | Library Module Name | New, Changed, or No Longer Supported? | Type | Description of Change |
---|---|---|---|---|
CLWGTC | CTAL | New | Real-Time Assembler | Processes the lwgtc internal library function. |
CRWGTC | CTAL | New | Real-Time Assembler | Processes the rwgtc internal library function. |
C513 | COMX | Changed | C Language | Updated the serialization of close function calls. |
C515 | COMX | Changed | C Language | Updated the serialization of close function calls. |
C524 | COMX | Changed | C Language | Updated the serialization of close function calls. |
C525 | COMX | Changed | C Language | Updated the serialization of close function calls. |
C533 | COMX | Changed | C Language | Updated the serialization of close function calls. |
C534 | COMX | Changed | C Language | Updated the serialization of close function calls. |
C539 | COMX | Changed | C Language | Updated the serialization of close function calls. |
There are no changes.
Table 548 summarizes changes to members (object files). This information is presented in alphabetic order by the name of the member (object file).
Notes:
Member (Object File) | DLM/DLL | New, Changed, or No Longer Supported? | Type | Description of Change |
---|---|---|---|---|
CLTR | DLM | Changed | C Language | Updated to return to segment CLC0 during system restart. |
CMACMD | DLL | New | C Language | Processes MATIP control packets. |
CMADAT | DLL | New | C Language | Processes MATIP data packets. |
CMAP | DLM | New | C Language | ZMATP command processor. |
CMARTN | DLL | New | C Language | Processes common routines used by MATIP and IP Bridge. |
CMATAB | DLL | New | C Language | Manages the MATIP session control block area. |
CMIA | DLM | New | C Language | Receives inbound MATIP Type-A data packets. |
CMIB | DLM | New | C Language | Receives inbound MATIP Type-B data packets. |
CMIC | DLM | New | C Language | Outbound interface to the MATIP session manager. |
CMIR | DLM | New | C Language | MATIP cycle-down processor. |
CMIT | DLM | New | C Language | MATIP cycle-up processor. |
CMOA | DLM | New | C Language | Processes outbound MATIP Type-A data packets. |
CMOB | DLM | New | C Language | Processes outbound MATIP Type-B data packets. |
CRII | DLM | New | C Language | Processes inbound IP Bridge data packets. |
CRIO | DLM | New | C Language | Processes outbound IP Bridge data packets. |
UMATAL | DLL | New | C Language | MATIP assign line number, interchange address, and terminal address (LNIATA) user exit. |
UMATAS | DLL | New | C Language | MATIP agent set control unit (ASCU) list user exit. |
UMATFI | DLL | New | C Language | MATIP flow ID user exit. |
UMATRO | DLL | New | C Language | MATIP router user exit. |
UMATSE | DLL | New | C Language | MATIP security user exit. |
UMATSS | DLL | New | C Language | MATIP session start user exit. |
UMATTR | DLL | New | C Language | MATIP translation user exit. |
There are no changes.
There are no changes.
There are no changes.
Table 549 summarizes the copy member changes. This information
is presented in alphabetic order by the name of the copy member.
Table 549. Changes to Copy Members for Mapping of Airline Traffic over Internet Protocol (MATIP)
Copy Member | Type | CSECT Where Copy Member Is Located | DLM Where CSECT Is Located | New, Changed, or No Longer Supported? | Description of Change |
---|---|---|---|---|---|
CLBV | Assembler | CCLAW1 | Not Applicable | Changed | Leave the CLAW polling switch on. |
CLB3 | Assembler | CCLAW1 | Not Applicable | Changed | Turn the CLAW polling switch off. |
CLXA | Assembler | CCCCP1 | Not Applicable | Changed | Updated processing of the ROUTC macro. |
There are no changes.
The following section summarizes the macro changes. This information is presented in alphabetic order by the type of macro.
There are no changes.
Table 550 summarizes changes to the communication macros. This
information is presented in alphabetic order by the name of the communication
macro or statement.
Communication Macro or Statement | New, Changed, or No Longer Supported? | Do You Need to Reassemble Programs? |
---|---|---|
SNAKEY | Changed | Yes |
Table 551 summarizes the data macro changes. This information
is presented in alphabetic order by the name of the data macro.
Table 551. Changes to Data Macros for Mapping of Airline Traffic over Internet Protocol (MATIP)
Data Macro | New, Changed, or No Longer Supported? | Do You Need to Reassemble Programs Using This Data Macro? |
---|---|---|
CK2SN | Changed | No |
DLTEC | Changed | Yes |
ISCFDT | Changed | No |
RC0PL | Changed | No |
There are no changes.
Table 552 summarizes the selected equate macro changes. This
information is presented in alphabetic order by the name of the selected
equate macro.
Selected Equate Macro | New, Changed, or No Longer Supported? | Do You Need to Reassemble Programs? |
---|---|---|
TRMEQ | Changed | No |
There are no changes.
Table 553 summarizes the system initialization program (SIP) skeleton
and internal macro changes. This information is presented in alphabetic
order by the name of the SIP skeleton and internal macro. If the SIP
skeleton and internal macro (inner macro) is changed, you must reassemble the
SIP Stage I deck and run the appropriate job control language (JCL) jobs from
the SIP Stage II deck.
SIP Skeleton and Internal Macro | New, Changed, or No Longer Supported? |
---|---|
SPPGML | Changed |
There are no changes.
Table 554 summarizes system initialization program (SIP) Stage II
macro changes. This information is presented in alphabetic order by the
name of the SIP Stage II macro. If IBMPAL is changed, you must run the
system allocator (SALO) and load the new program allocation table
(PAT) to the TPF 4.1 system.
SIP Stage II Macro | New, Changed, or No Longer Supported? |
---|---|
IBMPAL | Changed |
There are no changes.
There are no changes.
There are no changes.
Table 555 summarizes segment changes. This information is
presented in alphabetic order by the name of the segment.
Table 555. Changes to Segments for Mapping of Airline Traffic over Internet Protocol (MATIP)
Segment | Type | Link-Edit Module (Where Offline Segment Is Linked) | New, Changed, or No Longer Supported? | Description of Change |
---|---|---|---|---|
CLC0 | Real-Time Assembler | Not Applicable | Changed | Updated to process the TCT dump label. |
CSK0 | Real-Time Assembler | Not Applicable | Changed | Updated to include the MAXASCU and MAXMATIP parameters for the ZNKEY command. |
CTKR | Real-Time Assembler | Not Applicable | Changed | Updated to call the MATIP cycle-down processor. |
CTKT | Real-Time Assembler | Not Applicable | Changed | Updated to call the MATIP cycle-up processor. |
CVAB | Real-Time Assembler | Not Applicable | Changed | Added an entry for the ZMATP command. |
The following section summarizes system equate changes.
There are no changes.
Control Program (CP) User Exits and ECB User Exits summarize the control program (CP) and ECB user exit changes. See TPF System Installation Support Reference for a complete description of all user exits.
There are no changes.
This information is presented in alphabetic order by the name of the
function.
Table 556. Changes to ECB User Exits for Mapping of Airline Traffic over Internet Protocol (MATIP)
Function | User Exit Activated In | User Exit Program | New, Changed, or No Longer Supported? | Description of Change |
---|---|---|---|---|
MATIP Agent Set Control Unit (ASCU) User Exit | CMACMD | UMATAS | New | Defines a list of ASCUs. |
MATIP Assign LNIATA User Exit | CMADAT, CMOA, CRII | UMATAL | New | Assigns an LNIATA to a data message. |
MATIP Flow ID User Exit | CMADAT | UMATFI | New | Allows SITA host-to-host communication to allocate message charges to the appropriate host airlines. |
MATIP Router User Exit | CMADAT | UMATRO | New | Allows messages to be routed to the appropriate application when a terminal address table (WGTA) entry is not used to route the messages. |
MATIP Security User Exit | CMACMD | UMATSE | New | Accepts or rejects the MATIP Session Open requests. |
MATIP Session Start User Exit | CMACMD | UMATSS | New | Defines the characteristics of a MATIP session that will be opened with a remote MATIP server. |
MATIP Translation User Exit | CMADAT, CMOA, CMOB | UMATTR | New | Translates message text according to user requirements. |
The following section summarizes functional and operational changes. This information is presented in alphabetic order by the functional or operational change.
See Appendix A, "PUT 2-15 Interface Changes by Authorized Program Analysis Report (APAR)" for a summary of functional and operational changes by APAR.
Table 557 summarizes command changes. This information is presented in alphabetic order by the name of the command. See TPF Operations for a complete description of all commands.
Attention: Changes to commands can impact any automation
programs you are using in your complex.
Table 557. Changes to Commands for Mapping of Airline Traffic over Internet Protocol (MATIP)
Command | New, Changed, or No Longer Supported? | Description of Change |
---|---|---|
ZMATP | New | Displays or modifies MATIP values. |
ZNKEY | Changed | Added the MAXASCU and MAXMATIP parameters. |
Table 558 summarizes message (offline and online messages) and system error changes.
The message IDs or system error numbers are listed in numeric order preceded by their alphabetic prefix. Some offline and online messages do not have a standard message ID. For these, the messages are presented in alphabetic order based on the initial message text; or for those messages that begin with variable information, the initial message text that follows that variable information. See Messages (System Error and Offline) and Messages (Online) for a complete description of all messages and system errors.
Attention: Changes to offline messages, online messages,
and system errors may impact any automation programs you are using in your
complex.
Message ID or System Error Number | Message Type | New, Changed, or No Longer Supported? |
---|---|---|
MATP0001I | Online | New |
MATP0002I | Online | New |
MATP0003E | Online | New |
MATP0004E | Online | New |
MATP0005E | Online | New |
MATP0006I | Online | New |
MATP0007I | Online | New |
MATP0008I | Online | New |
MATP0009E | Online | New |
MATP0010I | Online | New |
MATP0011E | Online | New |
MATP0012I | Online | New |
MATP0013E | Online | New |
MATP0014E | Online | New |
MATP0015E | Online | New |
MATP0016E | Online | New |
MATP0055E | Online | New |
MATP0064E | Online | New |
There are no changes.
MATIP support supplies a new core memory table, the MATIP Session Control Block (MSCB) area. You can define the size of the MSCB by using the ZNKEY command with the following parameters specified:
See TPF Operations for more information about the ZNKEY command.
There are no changes.
There are no changes.
There are no changes.
Table 559 summarizes changes to the publications in the TPF
library. This information is presented in alphabetic order by the
publication title. See the TPF Library Guide
for more information about the TPF library.
Table 559. Changes to TPF Publications for Mapping of Airline Traffic over Internet Protocol(MATIP)
Publication Title | Softcopy File Name | Description of Change |
---|---|---|
TPF ACF/SNA Network Generation | GTPACF09 | Updated the SNAKEY macro with the MAXASCU and MAXMATIP parameters. |
Messages (System Error and Offline) and Messages (Online) | Not Applicable | Updated with information about messages and system errors that were added, changed, and no longer supported for MATIP. |
TPF Migration Guide: Program Update Tapes | GTPMG200 | Updated with migration considerations for MATIP. |
TPF Operations | GTPOPR0A | Updated with information about the commands that were added and changed for MATIP. |
TPF Program Development Support Reference | GTPPDR0A | Updated with information about the TCT main storage dump label that was added for MATIP. |
TPF System Installation Support Reference | GTPINR0A | Updated with information about the user exits that were added for MATIP. |
There are no changes.
There are no changes.
There are no changes.
There are no changes.
There are no changes.
There are two phases you must go through before you use MATIP support:
To determine if you will be able to install MATIP support in your TPF 4.1 system, do the following:
Application programs that will be used to send data across an IP network issue a ROUTC macro with the LNIATA of the remote terminal or system in the destination field (RCPLDES3) of the routing control parameter list (RCPL). The LNIATA used in the RCPL is classified as a MATIP or IP Bridge device by the ZMATP command when the TPF 4.1 system is started.
Applications that do not use LNIATAs to send Type-A host-to-host or Type-B message traffic have the ability to set destination field RCPLDES of the RCPL to an IP address. This address initially is set when starting a Type-A host-to-host session or a Type-B session and a message is sent across the session. The application enters the CMOA MATIP program for Type-A host-to-host traffic or the CMOB program for Type-B traffic. If MATIP is able to connect to the desired remote session, it returns the socket number created to the application after the session is started and the data is sent. The application passes that socket number to RCPLDES on ensuing enters to the CMOA or CMOB programs when additional data is sent across the session.
To install MATIP support in your TPF 4.1 system, do the following:
See TPF Operations for more information about the ZINET ADD command.
See TPF Operations for more information about the ZNKEY command.