gtpm2m26 | Migration Guide: Program Update Tapes |
The following section discusses the migration considerations for Mapping of Airline Traffic over Internet Protocol (MATIP) enhancements.
See the APEDIT for APAR PJ26693 for information about prerequisite APARs.
Mapping of Airline Traffic over Internet Protocol (MATIP) enhancements expands MATIP support that was previously shipped by providing a way to define a host descriptor table for Type-A and Type-B hosts. It does so by adding new parameters to the ZMATP command, new error messages, and a new user exit. See Mapping of Airline Traffic over Internet Protocol (MATIP) (APAR PJ26161) for information on MATIP support that was previously shipped.
If you are migrating from the original MATIP support on PUT 10 (APAR PJ26161) to these MATIP enhancements, you must define one or more host names in the new MATIP host name table by entering the ZMATP command to start MATIP client sessions with a remote host or workstation. Without an appropriate host name, the TPF 4.1 system is unable to obtain an Internet Protocol (IP) address that is needed to start the client session. In addition, you must modify the new MATIP host name user exit to locate the host name in the host name table that is used to start a specific MATIP client session.
Agent set control unit (ASCU) information was previously defined and changed through the MATIP ASCU user exit and the MATIP security user exit. Now you can also change and define ASCUs through the ZMATP command as well as associating ASCUs with a specific host name. The ASCU information is preserved on file so that it does not have to be specified again after the TPF 4.1 system is re-IPLed. The DISPLAY parameter of the ZMATP command has been enhanced to display various characteristics associated with a specific MATIP session.
The architecture for MATIP enhancements is based on that for MATIP support, allowing for the management of Transmission Control Protocol/Internet Protocol (TCP/IP) wrappers around messages in legacy protocols. These wrappers allow the messages to be sent over TCP/IP networks. MATIP enhancements will continue to provide TPF server and TPF client capabilities in the three Societe Internationale de Telecommunications Aeronautiques (SITA) message types:
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 693 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.
Build Script | Type | New, Changed, or No Longer Supported? | Description of Change |
---|---|---|---|
CMATBS | DLL | Changed | Added the MATIP host name user exit, UMATCH, and the ZMATP TPF collection support (TPFCS) command handler. |
There are no changes.
There are no changes.
Table 694 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$iscfdt.h | Changed | No |
c$trmeq.h | Changed | No |
Table 695 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 | Changed | No |
i$mscb.h | Changed | No |
netdb.h | Changed | No |
There are no changes.
Table 696 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 |
---|---|---|---|---|
C511 | COMX | Changed | C Language | Updated to save the domain for child sockets. |
C518 | COMX | Changed | C Language | Updated to bypass offload processing if information is available in the TPF 4.1 system. |
C519 | COMX | Changed | C Language | Updated to bypass offload processing if information is available in the TPF 4.1 system. |
There are no changes.
Table 697 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 |
---|---|---|---|---|
CMACMD | DLL | Changed | C Language | Updated to access new control block structures that contain host names and ASCU information. |
CMADAT | DLL | Changed | C Language | Updated to access new control block information. |
CMAP | DLM | Changed | C Language | Updated to add support for new parameters on the ZMATP command. |
CMATAB | DLL | Changed | C Language | Allocated control block structures for host names and ASCUs. |
CMATO2 | DLL | New | C Language | Saves host names and ASCUs in TPF collection support. |
CMIC | DLL | Changed | C Language | Updated to add an additional parameter to the session manager function call. |
CMOA | DLM | Changed | C Language | Updated to use new control block structures. |
CMOB | DLM | Changed | C Language | Updated to use new control block structures. |
CRII | DLM | Changed | C Language | Enabled to use TCP/IP native stack support. |
UMATCH | DLL | New | C Language | MATIP host name user exit. |
UMATSE | DLL | Changed | C Language | Updated the sample code. |
UMATSS | DLL | Changed | C Language | Updated to add a comment to the prolog. |
There are no changes.
There are no changes.
There are no changes.
Table 698 summarizes the copy member changes. This information
is presented in alphabetic order by the name of the copy member.
Copy Member | Type | CSECT Where Copy Member Is Located | DLM Where CSECT Is Located | New, Changed, or No Longer Supported? | Description of Change |
---|---|---|---|---|---|
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.
There are no changes.
Table 699 summarizes the data macro changes. This information
is presented in alphabetic order by the name of the data macro.
Data Macro | New, Changed, or No Longer Supported? | Do You Need to Reassemble Programs Using This Data Macro? |
---|---|---|
ISCFDT | Changed | No |
There are no changes.
Table 700 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 701 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 702 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 703 summarizes segment changes. This information is
presented in alphabetic order by the name of the segment.
Segment | Type | Link-Edit Module (Where Offline Segment Is Linked) | New, Changed, or No Longer Supported? | Description of Change |
---|---|---|---|---|
CMID | Real-Time Assembler | Not Applicable | New | Issues the CINFC macro to obtain the number of line numbers, interchange addresses, and terminal addresses (LNIATAs) in the TPF 4.1 system. |
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.
Function | User Exit Activated In | User Exit Program | New, Changed, or No Longer Supported? | Description of Change |
---|---|---|---|---|
MATIP Host Name User Exit | CMACMD | UMATCH | New | Selects remote hosts or modifies host record data areas for inbound and outbound sessions. |
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 705 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.
Command | New, Changed, or No Longer Supported? | Description of Change |
---|---|---|
ZMATP | Changed | Updated to add new parameters. |
Table 706 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? |
---|---|---|
MATP0017I | Online | New |
MATP0018I | Online | New |
MATP0019W | Online | New |
MATP0020I | Online | New |
MATP0021I | Online | New |
MATP0022E | Online | New |
MATP0023E | Online | New |
MATP0024E | Online | New |
MATP0025E | Online | New |
MATP0026I | Online | New |
MATP0027I | Online | New |
MATP0028E | Online | New |
MATP0029E | Online | New |
MATP0030E | Online | New |
MATP0031E | Online | New |
MATP0032E | Online | New |
MATP0055E | Online | Changed |
There are no changes.
A specific area of the system heap has been allocated for MATIP enhancements such as the host name table and the LNIATA chain. The number of LNIATAs used in the host name table is the same as the number of LNIATAs configured in keypoint C.
File storage has been allocated for host name and ASCU information. The number of hosts is determined by using the number of hosts defined in the TPF collection support MATIP_DS database with half the number of host names added.
You can define the size of a core memory area (the MATIP Session Control Block (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 707 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.
Publication Title | Softcopy File Name | Description of Change |
---|---|---|
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 enhancements. |
TPF Migration Guide: Program Update Tapes | GTPMG201 | Updated with migration considerations for MATIP enhancements. |
TPF Operations | GTPOPR0B | Updated with information about the commands that were added and changed for MATIP enhancements. |
TPF System Installation Support Reference | GTPINR0B | Updated with information about the UMATCH user exit that was added for MATIP enhancements. |
There are no changes.
There are no changes.
There are no changes.
There are no changes.
There are no changes.
Before you can use MATIP enhancements you must complete the following two phases:
To determine if you will be able to install MATIP enhancements in your TPF 4.1 system, do the following:
If you have used MATIP addresses previously, see your network administrator to ensure that all host names are associated with the IP addresses in MATIP enhancements.
Applications 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 RCPLDES3 destination field 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.
The MATIP host name user exit, UMATCH, is used to associate LNIATAs with host names for MATIP sessions that do not have specified host names.
Applications that do not use LNIATAs to send Type-A host-to-host or Type-B message traffic have the ability to set the RCPLORG destination field to contain a pointer to a host name of up to 255 alphanumeric characters that ends in a null character. The application enters the CMOA MATIP program for Type-A host-to-host traffic or the CMOB program for Type-B traffic. The host name is passed to an IP address when starting a Type-A host-to-host session or a Type-B session and a message is sent across the MATIP session. If MATIP is able to connect to the desired remote session, it returns the host ordinal (an index to the host name in the host name table) to the application after the session is started and the data is sent. The application passes that host ordinal number to RCPLDES on subsequent enters to the CMOA or CMOB programs when additional data is sent across the session.
To install MATIP enhancements in your TPF 4.1 system, do the following:
If you want to define a host name and a list of agent set control units (ASCUs) you can enter either the ZMATP command with the DEFINE parameter specified or the MATIP host name user exit.
If you want to add additional ASCUs to a defined host, you can enter either the ZMATP command with the ALTER parameter specified or the MATIP host name user exit.
See TPF Operations for more information about the ZMATP command.
ZINET ADD S-MATIPA MODEL-AOR AORL-4 PGM-CMIA PROT-TCP PORT-350 STATE-CRAS
ZINET ADD S-MATIPB MODEL-AOR AORL-4 PGM-CMIB PROT-TCP PORT-351 STATE-CRAS
ZINET ADD S-IPBRIDGE MODEL-AOR PGM-CRII PROT-TCP PORT-userport
See TPF Operations for more information about the ZINET ADD command.
See TPF Operations for more information about the ZMATP command.