Task: Define Printer Linkage

This task defines the particular printer and the functions it performs. It assigns printer functions to a GTID and its associated pseudo city code.

Section 1: Short Answer

Transaction Name:

TicketPrinterLinkage_1_0

Can any other transaction(s) perform this same task?

No other transaction can perform this task.

Can this task be performed in a sessionless environment?

This task must be used in a sessioned environment.

Are the request and response identical on both the Apollo and Galileo systems?

The request and response are identical on both Apollo and Galileo.

List any industry-specific knowledge required to understand this task in terms of the specific business process.

Knowledge to add printers in the AAT of the Pseudo City, and Printer Linkage entries in Agent mode. Corresponding devices must exist in your AAT table or they cannot be linked to. 

Explain any special limits or distinct restrictions to the input data that may not be readily apparent.

There are no special limitations.

Section 2: Detailed Description

Request

Unless otherwise specified, use ALL CAPS in any request data.

The <LinkageDefinitionMods> tag  (4070) will be used in the request to Define Printer Linkage.  The <ModifyPrinterStatus> tag will include the LNIATA and print modifier details. On Galileo, the ATB response (issued ticket, coupon number etc.) may also be required. The automatic ATB response would be sent in the <SimulatedATBResponse> tag.

Prerequisite tasks:

No prerequisite tasks are required.

Expected response:

If the Define Printer Linkage transaction completes successfully, the <DPOK> tag will be returned to indicate a good response.

Error and warning responses:

If the Define Printer Linkage transaction encounters an error, it will be returned in the <ErrText> tag. The following error messages may be received:

Apollo:

8822 - RESTRICTED

8825 - INVALID FORMAT INCOMPLETE

8826 - SYSTEM ERROR OCCURRED

8827 - CHECK FORMAT

8833 - INVALID LNIATA

8912 - INVALID STATUS

8913 - INVALID STOCK TYPE

Galileo:

8824 - INVALID GTID

8910 - INVALID SINE

8911 - INVALID FORMAT

8912 - INVALID STATUS

8913 - INVALID STOCK TYPE

Follow-on requests:

No follow-on requests exist.

Additional Printer Linkage capabilities:

Printer stock type can be designated for:

• Ticketing (HMOMF72303-TKT).
• Itinerary/Invoices (HMOMF92304-ITN).
• A blank printer (HMOMF32303-BLK).
• Boarding pass printer (HMOMF3102E-BPP) - note: for Apollo Only

Change Printer Status

Printer status can be changed from "down" to "up" or vice versa. A device status could be down because it is a MIR device. MIR devices are often only brought up once a day when the accountant is present and wants to send MIR information to a back office system. Or, a device status could be down because there is no ticket stock (for a ticket printer). In that situation, you would want to bring the device up before a ticket could be issued. (HMOMF82303-U or HMOMF82303-D)

The following entries are only available on the Galileo host:

• Printer status for an ATB printer can be changed from "busy" to "up". (HMOMF1075D-T/1700001764/04—This entry requires a printer GTID, number of the last successful ticket issued, plus the number of coupons used by the printer for that ticket).
• Printer status can be changed to "down" when a ticket book is not completed properly and reports a VOID on the TINS report. (HMOMF1075E-T/1563219457/06/V—This entry requires the printer GTID, the number of the last successful ticket, and the number of coupons used by the printer for that ticket).
• Printer status can be changed to "down" and ticket reported as VOID in the TINS report when no coupons have been used by the printer. (HMOMF1075E-T/1563219457/06/00—This entry requires the printer GTID and the number of the last successful ticket issued).

Section 3: Tables

Request (Input) Tags

Response (Output) Tags – Normal Response

Response (Output) Tags – Error Response

Related Samples

TicketPrinterLinkage_1_0_13