Appendix C: Definition and Use of the MIR Modifiers

This topic contains MIR modifiers for: 

Introduction

The Machinable Interface Record is programmatically generated when a ticket is issued and applicable linkage is in place. The data is delivered to the interfaced Third Party Agency Management System.

Travelport Apollo System/Travelport+ provides the ability to generate PNR/BOOKING FILE information to more than one interfaced computer system by using the Dual MIR. The use of the Dual MIR is to send PNR/BOOKING FILE information to two interfaced systems simultaneously.

Non-Ticketing MIR and/or the Non-Faring MIR (Travelport Apollo System only) also provide data to more than one interfaced computer system.  Initially, the Non-Ticketing and Non-Faring MIRs were conceived as methods to hand off data to an interfaced computer prior to the actual tickets having been issued.  This information is generally used for pre-trip information, passenger manifests, forecasting, and budgeting.

Helpful Hints

Many agents want to feed to a single, central point interface system. Each AAT must then contain the same GTID. It is recommended that the central site is loaded first, then the branches.

MIRs are designed for the real-time environment, so batch mode whilst available is not recommended.  It is not recommended to allow MIRs to build up on the buffer as a standard process and this must be considered when designing your interface and instructing your users.

Overview of the D Modifiers

Following are the "D" modifiers used by Travelport Apollo System/Travelport+ to generate various documents. Where linkage exists, the use of HB in Travelport Apollo System and TKP in Travelport+ will generate a ticket and one MIR for each ATFQ/filed fare in the PNR/Booking File.

D modifier

Result

DBD

Sends an accountable ticketing MIR to the interfaced computer system for agencies that do back office ticketing  This modifier adds ticketing information to the ARC Electronic Credit Card Billing System. (Travelport Apollo System).

DAD

Sends a non-accountable MIR only to the interfaced computer system that the CRT is physically linked.

DID

Issues an Itinerary only, from the itinerary printer.  No MIR or Ticket is sent.

DTD

Issues a ticket only, from the ticket printer.  No MIR or Itinerary is sent.

DXD

Issues a Ticket, Itinerary, a MIR - to the MIR device that the CRT is physically linked, and a copy of that MIR - to the MIR Device targeted in the DXD command.

DND

Sends a non-accountable MIR to the MIR Device targeted in the DND command, for a PNR/BOOKING FILE which may or may not have been ticketed.

DJD

Sends a non-accountable MIR without fare information to the MIR Device targeted in the command.  This modifier bypasses the undecodeable airline and city tables (Travelport Apollo System).  The DJD command will also transmit a non-faring MIR for non-participant carriers with or without a MIR device targeted in the command (Travelport Apollo System and Travelport+).

DGD

Global MIR

DLD

Generates a Electronic Ticket (electronic ticket) message to the Carrier, plus Itinerary and MIR based on linkage. (Travelport Apollo System).

Note: The DXD/DND/DJD entries must be routed to the correct GTID and to the receiving pseudo city code.  The AAT for both the sending and the receiving pseudos must contain the same MIR Types.

Dual MIR

Many travel agents want to feed to a single, central point and also interface to a local agency management system. The Dual MIR meets this need.

The Dual MIR generates two identical MIRs which are sent simultaneously to two different GTIDs (MIR Devices), representing two interfaced computer systems.  When using the Dual MIR command, "DXD", Travelport Apollo System/Travelport+ is able to issue a Ticket, Itinerary, and a MIR to the MIR device which the CRT is physically linked to and a copy of the same MIR to the device targeted in the Dual MIR command.

Glossary

Sending Pseudo city/MIR Device (GTID): This is the pseudo city code/GTID from which the agent is driving the Dual MIR command.  This pseudo city/GTID is receiving the original MIR, and is also known as the primary MIR device.

Target Pseudo city/MIR Device (GTID): This is the pseudo city code/GTID that is targeted in the Dual MIR command.  This pseudo receives a copy of the sending pseudo city's MIR, and is also known as the secondary MIR device.  The target pseudo city code can be the same as the sending pseudo city code, but a different MIR GTID is used.

Requirements

  • The Dual MIR command must be directed to a MIR Device (GTID) different than the MIR Device (GTID) the issuing CRT is physically linked to.

  • The receiving location's MIR GTID must be present in the OUTPUT section of the  AAT Table for the transmitting agency for Travelport Apollo System and receiving agency in Travelport+.  (If the transmitting agency and the receiving agency are the same, both MIR GTIDs must be present in the AAT Table).

  • The Dual MIR command may be directed to the same pseudo city code the agency is currently working in, or another pseudo city.

  • The sending and receiving locations must be on the same MIR type. If this is not the case, Travelport Apollo System/Travelport+ responds with:

    In Travelport Apollo System: INVLD MIR TYPE

    In Travelport+: INVALID MIR TYPE

  • The sending agency must be linked to a MIR device.

  • The sending agency must be set up for TINS (Ticket & Invoice Numbering System) Ticketing if Ticket and Invoice numbers are desired in the MIR.  It is not necessary for the receiving agency to set TINS on.

  • One CRT at the target agency pseudo must be linked to the MIR Device targeted in the Dual MIR command (Travelport Apollo System).

Notes:

  • The MIR device at the Sending Pseudo city needs to be brought to UP status (if not left in "UP" status all day long) before the target MIR can be received at the down line pseudo city/GTID.  If the primary MIR Device is usually left DOWN, then target MIRs are held by the primary device, until it is brought UP.  These target MIRs are not represented in the "Demand Pending" counts for either pseudo city code.

  • When Dual MIRs are generated to two different types of back office accounting systems, the T- Ticket Remarks in Travelport Apollo System and DI. entries in Travelport+ and other accounting formats must be taken into consideration.  Some back office systems require restrictive formats that are not compatible with other back office systems.

Linkage

The TINS settings in the Agency Account Table determine what is included in both MIRs:

1. If both Ticket and Invoice are set to "Y" the ticket number and the invoice number will appear.

2. If only ticket is set at "Y", then only a ticket number will appear.

3. The linkage formats are the same as when sending regular MIRs. To display linkage, type: HMLD.

Travelport Apollo System/Travelport+ RESPONSE:

CRTTKT DEV  ST FM / ITIN DEV  ST FM / MIR DEV  ST FM

2D831B2D8104D   U  T    2D8103D   U  I   2D8303D   U

If your set is not linked to a MIR Device you can do so by typing:

HMLM<GTID>DA

4. If the MIR Device at the receiving location is down, the target MIR will buffer.

To bring a MIR device up, you can do so by typing:

HMOM<GTID>-U

5. If the MIR Device at the sending location is down, then both the original MIR and the target MIR will buffer.  Both the sending MIR and the target MIR are sent when the MIR device of the sending location is brought UP. In Travelport+, using HQC only 1 MIR is shown in each of the DXD GTIDs, in HQC/GTID 2 are shown.

Format

The basic input for issuing a Dual MIR consists of demand input HBDXD or HB:DXD in Travelport Apollo System or TKPDXD in Travelport+, followed by the GTID of the receiving output device (target device) and the Pseudo city Code of the receiving location (target pseudo). In Travelport+, can be stored in the fare with TMU or the filed fare can be specified with TKP.

In Travelport Apollo System, the entries are:

HB: DXD +<GTID>       + <PSEUDO>

* *  * *

* *  * *

* *  * *

* *GTID and Pseudo city Code of the

* *Target MIR.  (Where you want the

* *second MIR to go).

* *

*DXD MODIFIER

*

TICKETING COMMAND

When using the DXD command, the Travelport Apollo System response is:

TICKET / ITIN ISSUED

DUAL MIR ISSUED

In Travelport+, the entries are:

TKPDXD  . <GTID> . <PSEUDO>

* *  * *

* *  * *

* *  * *

* *GTID and Pseudo city Code of the

* *Target MIR.  (Where you want the

* *second MIR to go).

* *

*DXD MODIFIER

*

TICKETING COMMAND

When using the DXD command, the Travelport+ response is described in the screen outputs of Enhanced Document Set.

Notes:

  • In Travelport Apollo System:

    • When sending a Dual MIR and one is sent to a pseudo city other than the one driving the command, both MIRs are given unique Travelport Apollo System sequence numbers. Therefore, you can retransmit either of the MIRs using the HQT command.

    • The MIR is retransmitted to the device identified as the OUTPUT GTID after typing:  HQB/ACC/00000 (Sequence number).  To transmit the second MIR you must emulate the target pseudo city (SEM/<PSEUDO>/AG) then HQB/ACC/00000 (Sequence Number).

  • In Travelport+: 

    • To resend a Dual-MIR HQNN will transmit both after the HQB entry. It is not possible to retransmit only one.

Combinable Modifiers

The following modifiers can be combined with the DXD modifier.  All other modifiers are restricted and will generate the error message "INVALID FORMAT/DATA".

Modifiers combined with DXD

 Result

F

Allows the Form of Payment to append to this command.

CXX

XX = (Carrier Code) Allows you to add a Carrier Override to the DXD command.

9B/9Pin Travelport Apollo System

DBP in Travelport+

Allows you to combine Boarding Pass requests with the DXD command. This is not yet available in Travelport+ today but is planned.

ZXX

(XX = Commission Percent/Dollar Amount) Allows you to include a commission amount in this command

Z$XXX.XX in Travelport Apollo System

 

(XX = Commission Percent/Dollar Amount) Allows you to include a commission amount in this command.

DID

Allows the "Itin Only" command to be combined with the DXD modifier.

In Travelport Apollo System, the format in this case must be: HB:DIDXD+<GTID>+<PSEUDO>

In Travelport+, the format in this case must be: TKPDIDXD . <GTID> . <PSEUDO>

Using this format will generate only an Itinerary and two MIRs.

Notes:

  • In Travelport+, all modifiers can be combined with DXD.

  • Because the DID command can now be combined with the DXD command, you can generate an Itinerary and two MIRs for Non-Air PNR/BOOKING FILEs.

  • In Travelport Apollo System you cannot combine "N" (Name Select) or "S" (Segment Select) modifiers with the DXD command.  However, if the Name and/or Segment Select modifiers are used in an  ATFQ field or Pricing Record both modifiers are recognized when the Dual MIR command is used.

  • In Travelport+ you can combine “N” (Name Select) and/or “S” (Segment Select) modifiers with the DXD command if the MIR is being generated from a non filed fare Booking File. You can combine “N” (Name Select) modifier with the DXD command if the MIR is being generated from a filed fare and the name is in the filed fare.

                 eg TKPP1/S1/FS/Z9/CTP/DIDXD.F101DA.XM3

                      TKP1P1/DIDXD.F101DA.XM3

In Travelport Apollo System: the screen response is:

NO MIR ISSUED - NEED DEVICE LINKAGE

This unsolicited message is sent if the CRT is not linked to a MIR Device.  Check this by typing:  HMLD. If there is nothing listed under the / MIR DEV / heading use the following format to link to the MIR Device:

HMLM2D8303DA

*  **

*  **

*  *DEVICE TYPE (Demand Accounting *MIR*)

*  * 

*MIR GTID

*

LINKAGE COMMAND

  • In Travelport+: If the ticket printer is linked, there is no error message. When combined with DID and no MIR is issued it causes a systems error and no MIRs are issued.

  • In Travelport Apollo System: The screen response is:

    INVLD LNIATA - SENDER = TARGET

    This message is sent if the GTID used in the DXD command is the same GTID displayed under the / MIR DEV / heading when HMLD is entered.  These GTIDs MUST be different.

  • In Travelport+: Two MIRs are sent and there is no error message.

  • In Travelport Apollo System: The screen response is:

    DXD ERROR - TARGET MIR NOT SENT

    This error appears if there is a problem in processing the Dual MIR.  The original MIR is sent to the MIR Device the CRT is linked to but the second MIR is not sent.  To send the second MIR to the second accounting system you can either retrieve the PNR/BOOKING FILE and use the DND format that sends a Non-Ticketing MIR (which requires that the accounting system ignore the Non-Ticketing MIR Flag) or reissue the MIR using the HB:DXD command.

  • In Travelport+: Two MIRs are sent and there is no error message.

Dual MIR for HBRF (Full RF/Partial RP) Refunds - Travelport Apollo System Only

Enables the DXD (Dual MIR) command for Travelport Apollo System to transmit a refund transaction to back office systems for both the ticketing location and the booking location for HBRF full (RF) and partial (RP) refunds. 

Requirements

The prerequisites and procedures to issue a DXD (Dual MIR) for Travelport Apollo System HBRF full (RF) and partial (RP) refunds are highlighted in this section.

  • The sending and receiving agencies of the Dual MIR must have their MIR Type Table and MIR Options Table enabled to receive a refund MIR.

    • MIR Type Table -  REFUND must be set to “Y” (Yes)

    • MIR Options Table -  REFUND DATA must be set to “Y” (Yes)

  • The agency sending the DXD (Dual MIR) for a refund must be linked to a MIR device (GTID).

  • One Travelport Apollo System terminal at the target Pseudo City Code (PCC) must be linked to a MIR device (GTID) that will be used in the sender’s DXD (Dual MIR) command.

  • Linkage formats are the same as when sending regular MIRs.

  • The DXD (Dual MIR) command for a refund must be directed to a MIR device (GTID) different than the MIR device (GTID) the issuing (sending) Travelport Apollo System terminal is linked.

  • The DXD (Dual MIR) command for a refund must be directed to a PCC different from the PCC issuing (sending) the MIR.  The target PCC must not be the same as the issuing (sending) PCC.

  • The DXD (Dual MIR) command for a refund cannot be directed to a PCC other than the “owning” booking or ticketing PCC.  The booking location and ticketing location may have different PCCs, but share an ARC/IATA number.

  • Both MIR devices must be in an up status in order for all data to appear in the MIR.

Notes:

  • A DXD (Dual MIR) command for an Travelport Apollo System HBRF (RF/RP) refund will continue to send an “R” (Refund MIR) in MIR Label T50IN12 (Ticketing Command Used).

  • The DXD (Dual MIR) command will not apply to ARNE refunds.

Formats

Travelport Apollo System Format to Request an HBRF Full (RF) or Partial (RP) Refund with Dual MIR

>HBRFaaaxxxxxxxxxx/DXD+gggggg+cccc/RF

>HBRFaaaxxxxxxxxxx/DXD+gggggg+cccc/RP/RC-xx

     

HBRF= primary action code

       aaa= 3 digit airline code

       xxxxxxxxxx= 10 digit ticket number

/= delimiter

DXD= dual MIR command

+= end item

gggggg= 6 target MIR GTID

+= end item

cccc= 3-4 target PCC

/= delimiter

       RP or RF= partial or full refund modifier

/= delimiter

       RC-= routing code modifier (mandatory for Canada)

       xx= 2 digit routing code as determined by agent

 

Non-Ticketing MIR

The Non-Ticketing MIR allows you to transmit PNR/BOOKING FILE data from Travelport Apollo System/Travelport+ to an interfaced computer system without initiating ticketing.

A one character field in MIRs 62 and 67 identifies either a Ticketing MIR or a Non-Ticketing MIR in Travelport Apollo System.  Travelport Apollo System sets the indicator to "Y" or "N" depending on how the MIR is issued. 

MIR contains an indicator in the Header identifying exactly which command is used to drive the MIR.  Many Interface vendors choose to ignore the MIR when a Non-Ticketing MIR is received (Non-Ticketing MIR indicator is set to "Y") while other systems have programmed specifically to receive this information.

The Non-Ticketing MIR hands off the last ticket and invoice numbers, from *HT (History TINS) if tickets and/or invoices were issued for this PNR/BOOKING FILE.  This type of information is most likely used in a report data base in addition to the uses listed for the Dual MIR.

Note: Special consideration must be given to the capacity of the interfaced computer system.  When sending both Non-Ticketing MIRs and MIRs generated with ticketing, that volume is greatly increased to the interfaced computer.

Requirements

  • Sending and receiving locations must be on the same MIR level.

  • In Travelport Apollo System, the interfaced computer system, using MIR 62 or 67, must be programmed to read label T50IN17, for the Non-Ticketing MIR indicator. In Travelport+, for GMIR the label is T50IN13.

    • N = TICKETING MIR

    • Y = NON-TICKETING MIR

  • If the Travelport Apollo System/Travelport+ user intends to include Ticket and Invoice Numbers or Ticket Numbers alone, in the Non-Ticketing MIR TINS must be turned on. In Travelport+, this is the sending agency.

  • The TINS setting in the Agency Account Table determines what is displayed in the Non-Ticketing MIR:

    • If both Ticket and Invoice are set to "Y", the ticket and the invoice number appears in the Non-Ticketing MIR.

    • If only Ticket is set at "Y", then only a Ticket Number appears in the Non-Ticketing MIR.

  • If the table is set to indicate no Ticket or Itinerary, then neither field appears in the Non-Ticketing MIR.

  • The receiving MIR GTID must be present as an Output Device in the Agency Account Table of Travelport Apollo System agencies and a link must be established with the other location. In Travelport+, this must be set up for the sending agency.

Linkage

  1. Link formats are the same as those used to send MIRs.  And similarly, if the link status at the receiving location is down, Non-Ticketing MIRs will buffer.

  2. There are differences in the initial set up for the Non-Ticketing MIR:

    • Sending and receiving locations do not need to be linked, and they do not require the same group code.

    • The receiving GTID must be present as an Output Device in the sending location's Agency Account Table in Travelport Apollo System. In Travelport+, this is the receiving agency.

  3. Output Device Counts (HQC and HQCGTID) do not differentiate between Ticketing MIRs and Non-Ticketing MIRs.  Both are shown together in the Queue Count for ACC.

Format

The basic input for issuing a Non-Ticketing MIR consists of HBDND in Travelport Apollo System and TKPDND or TMU etc. in Travelport+, then the GTID of the receiving output device (target device) and the Pseudo city Code of the receiving location (target pseudo).

In Travelport Apollo System:

The entries are:

HB:DND+<GTID>+<PSEUDO>

* *  * *

* *  * *

* *  * *

* *GTID and Pseudo city Code of the

* *Target MIR.  (Where you want the

* *Non-Ticketing MIR to go).

* *

*DND MODIFIER

*

TICKETING COMMAND

If using the DND command, when an ATFQ exists in the PNR, Travelport Apollo System's response is:

NON-TICKETING MIR ISSUED - TOT FARE $400.00 - ATFQ NOT UPDATED

 

When using the DND command, the Travelport Apollo System response will be:

NON-TICKETING MIR ISSUED - TOT FARE 0.00

In Travelport+:

The entries are:

TKPDND  . <GTID> . <PSEUDO>

* *  * *

* *  * *

* *  * *

* *GTID and Pseudo city Code of the

* *Target MIR.  (Where you want the

* *second MIR to go).

* *

*DND MODIFIER

*

TICKETING COMMAND

When using the DND command, the Travelport+ response, when a Filed Fare exists in the BOOKING FILE, Travelport+'s response is:

NON-TICKETING MIR ISSUED - TTL FARE followed by currency code and amount.

RECORD LOCATOR followed by up to 8 numerics including the decimal point.

Combinable Modifiers

The following modifiers can be combined with the DND modifier.  All other modifiers are restricted and will generate this error message "INVALID FORMAT/DATA".

Modifiers combined with DND

Results

F

Allows the Form of Payment to append to this command.

CXX

XX = (Carrier Code) Allows you to add a Carrier Override to the DXD command.

9B/9Por DBP

Allows you to combine Boarding Pass requests with the DXD command.

ZXX

(XX = Commission Percent/Dollar Amount) Allows you to include a commission amount in this command.

Z$XXX.XX

(XX = Commission Percent/Dollar Amount) Allows you to include a commission amount in this command. Travelport Apollo System only.

DID

Allows the "Itin Only" command to be combined with the DND modifier.

  • In Travelport Apollo System, the format in this case must be: HB:DIDND+<GTID>+<PSEUDO>

  • In Travelport+, the format in this case must be: TKPDIDND . <GTID> . <PSEUDO>

Using this format will generate only an Itinerary and Non-ticketing MIR where both contain the same information.

Notes:

  • Because the DID command can now be combined with the DND command, you can generate an Itinerary and a Non-Ticketing MIR for Non-Air PNR/BOOKING FILEs.

  • In Travelport Apollo System you cannot combine "N" (Name Select) or "S" (Segment Select) modifiers with the DND command.  However, if the Name and/or Segment Select modifiers are used in an ATFQ field or Pricing Record, both modifiers are recognized when the Non-Ticketing MIR command is used.

  • In Travelport+ you can combine “N” (Name Select) and/or “S”(Segment Select) modifiers with the DXD command if the MIR is being generated form a non filed fare Booking File. You can combine “N” (Name Select) modifier with the DXD command if the MIR is being generated from a filed fare and the name is in the filed fare.

Non-Faring MIR - Travelport Apollo System

The Non-Faring MIR completely bypasses Travelport Apollo Systems faring process and is generally used for transmitting group PNR information to an interfaced computer system.  Since the Non-Faring MIR does not go through Travelport Apollo System’s faring process, undecodable airlines and cities are not decoded and a fill-in-format is not offered.  No tickets are issued when using the Non-Faring MIR modifier.

Requirements

*Sending and receiving locations must be on the same MIR level..  If this is not the case, Travelport Apollo System’s response is:

INVLD MIR TYPE

*The interfaced computer system must be programmed to read label T50IN17, the Non-Ticketing MIR indicator.

N = TICKETING MIR

Y = NON-TICKETING MIR

*The receiving MIR GTID must be present as an Output Device in the Agency Account Table, and a link must be established with the receiving location.

*Ticket Numbers are never present in a Non-Faring MIR.

Linkage

  1. Link formats are the same as those used to send MIRs.  And similarly, if the link status at the receiving location is down, Non-Faring MIRs will buffer.

  2. There are differences in the initial set up for the Non-Faring MIR:

    • Sending and receiving locations do not need to be linked, and they do not require the same group code.

    • The receiving GTID must be present as an Output Device in the sending location's Agency Account Table.

  3. Output Device Counts (HQC and HQCGTID) do not differentiate between Ticketing MIRs and Non-Ticketing MIRs.  Both are shown together in the Queue Count for ACC.

Format

The basic input for issuing a Non-Faring MIR consists of HBDJD, the GTID of the receiving output device (target device) and the Pseudo city Code of the receiving location (target pseudo)

HBDJD+<GTID>+<PSEUDO>

* *  * *

* *GTID and Pseudo city Code of the

* *Target MIR.  (Where you want the

* *Non-Faring MIR to go).

* *

*DJD MODIFIER

*

TICKETING COMMAND

When using the DJD command, the Travelport Apollo System response is:

NON-FARED MIR ISSUED - TTL FARE 0.00

Since fare information is not included in the Non-Faring MIR, "HB:" is not allowed.

Segment select and name select modifiers can be used. For example:

HBS1+3/N1-1/DJD+<GTID>+<PSEUDO>

Combinable Modifiers

The following modifiers can be combined with the DJD modifier.  All other modifiers are restricted and will generate the error message "INVALID FORMAT/DATA".

Modifiers combined with DJD

Results

F

Allows the Form of Payment to append to this command.

CXX

(XX = Carrier Code) Allows you to add a Carrier Override to the DJD command.

ZXX

(XX = Commission Percent/Dollar Amount) Allows you to include a commission amount in this command.

Z$XXX.XX

As above.

DID

Allows you to combine the "Itin Only" command with the DJD modifier.  The format in this case must be:

HBDIDJD+<GTID>+<PSEUDO>.

Use of this format generates an Itinerary and a Non-Faring MIR where both contain the same information.

GIF

Allows you to transmit the DJD modifier to the back office accounting system without setting the Non-Ticketing/Faring MIR indicator, label T50IN17 to "Y".  (When you combine the GIF modifier with the DIDJD modifiers, you can produce an Itinerary and Non-Faring MIR that contain the same information.  i.e. Air Segments without fare, Auxiliary Segments with Due/Paid amounts).

Note: Because the DID command can now be combined with the DJD command, you generate an Itinerary and a Non-Faring MIR for Non-Air PNR.

Queue Ticketing Entries

Non-Ticketing / Non-Faring MIR

Queue Ticketing capability is available for ticketing modifiers (DND, DJD).  Previously, individual entries were required for each individual PNR in order to issue a Non-Ticketing, or Non-Faring MIR.  The Queue Ticketing capability allows you to enter one format for each queue.

Examples for Non-Ticketing MIR queue ticketing:

HB:Q/10/DND  +<GTID>+<PSEUDO>

*  * *   *    *

*  * *   *    *

*  * *GTID and Pseudo city of the

*  * *Target MIR.  (Where you want

*  * *Second MIR or Non-Ticketing
*  * *MIR to go).

*  * *

*  *DND MODIFIER

*  *

*QUEUE NUMBER

*

TICKETING COMMAND

Examples for Non-Faring MIR queue ticketing:

HBQ/10/DJD+<GTID>+<PSEUDO>

*  * *   *  *

*  * *   *  *

*  * *GTID and Pseudo city of the

*  * *Target MIR.  (Where you want

*  * *Non-Faring MIR to go).

*  * *

*  *DJD MODIFIER

*  *

*QUEUE NUMBER

*

TICKETING COMMAND

Note: While this capability provides functionality similar to queue ticketing, you cannot issue Non-Ticketing, Non-Faring or Dual MIRs for all PNRs when you are signed into queue.  If issuance is attempted while in queue, the following error response is given:

INVALID FORMAT

Non-Faring MIR - Travelport+

The Non-Faring MIR completely bypasses Travelport+ faring process and is generally used for transmitting PNR information to an interfaced computer system. Since the Non-Faring MIR does not go through Travelport+ faring process, undecodable airlines and cities are not decoded and a fill-in-format is not offered. No tickets are issued when using the Non-Faring MIR modifier.

Requirements

  • The receiving MIR GTID must be present as an Output Device in the Agency Account Table, and a link must be established with the receiving location.

  • Ticket Numbers are never present in a Non-Faring MIR.

Linkage

  1. Link formats are the same as those used to send MIRs. And similarly, if the link status at the receiving location is down, Non-Faring MIRs will buffer.

  2. There are differences in the initial set up for the Non-Faring MIR:

    • Sending and receiving locations do not need to be linked, and they do not require the same group code.

    • The receiving GTID must be present as an Output Device in the sending location's Agency Account Table.

  3. Output Device Counts (HQC and HQCGTID) do not differentiate between Ticketing MIRs and Non-Ticketing MIRs. Both are shown together in the Queue Count for ACC.

Format

The basic input for issuing a Non-Faring MIR consists of TKPDJD or TKPDJD with the GTID of the receiving remote output device (target device) and the Pseudo city Code of the receiving remote location (target pseudo)

 

TKPDJD

* * * *

* *

*DJD MODIFIER

*

TICKETING COMMAND for issuing Non-Faring MIR at current location

 

TKPDJD+<GTID>+<PSEUDO>

* * * *

* *GTID and Pseudo city Code of the

* *Target MIR. (Where you want the

* *Non-Faring MIR to go).

* *

*DJD MODIFIER

*

TICKETING COMMAND

 

When using the DJD command, the Travelport+ response is:

NON-FARED MIR GENERATED - TTL FARE 0.00

Segment select modifiers can be used. For example:

TKPDJD/S1

Combinable Modifiers

The following modifiers can be combined with the DJD modifier. All other modifiers are restricted and will generate the error message "INVALID FORMAT/DATA".

Modifier combined with DJD

Result

F

Allows the Form of Payment to append to this command

CXX

(XX = Carrier Code) Allows you to add a Carrier Override to the DJD command

ZXX

ZAXXX.XX

(XX = Commission Percent/Dollar Amount) Allows you to include a commission amount in this command

DID

Allows you to combine the "Itin Only" command with the DJD modifier. The format in this case must be:

TKPDIDJD

Use of this format generates an Itinerary and a Non-Faring MIR where both contain the same information.

Note: Because the DID command can now be combined with the DJD command, you can generate an Itinerary and a Non-Faring MIR for Non-Air PNR.