© 2012 Attachmate Corporation. All rights reserved.

• Introduction
• New Features
• Registry
• Fonts
• Product Files
• INFOConnect Database
• Device Initialization
• Locking
• CUPPS Modes


• Environmental Variables


• Interface Levels


• CUPPS XML Messages


• Custom Configuration


• Legal Notices

Introduction

This file provides information specific to Attachmate INFOConnect Enterprise Edition Print and Transaction Router 9.1 (PTR) Plus Service Pack 1, which includes CUPPS support. PTR Plus meets the IATA Common Use Passenger Processing System (CUPPS) standard by providing a CUPPS compliant library. You can run PTR Plus alone or as an add-on to INFOConnect Enterprise Edition. In this document, CUPPS specific features in PTR Plus are referred to as PTR Plus CUPPS.

For additional information about INFOConnect Enterprise Edition Print and Transaction Router Version 9.1, visit the Attachmate support Web site at http://www.attachmate.com/Support/

Important: Check the ReadMe folder for any instructions specific to using CUPPS with your airline.

New Features

This Service Pack includes support for CUPPS versions through 2010/05 (1.03).

For a complete list of new features in INFOConnect and PTR, see the INFOConnect Enterprise Edition and PTR Read Mes.

Registry

Before launching, registry entries that are required for the program to run are added to the HKEY_CURRENT_USER and HKEY_LOCAL_MACHINE hives. These entries are listed in the AtmData.reg file in the Registry subdirectory. When you close the application, these registry entries are removed.

Fonts

Seven program-specific font files are automatically copied to the C:Windows\Fonts directory. If write access is not allowed to this directory, you must manually copy the files to this directory, or somewhere within the PATH.

If characters don't appear on the status line or when you type, restart Windows to make the fonts available to the system.

Product Files

All permanent files for the application are stored on the fileserver. When you run the program, temporary files (such as configuration and log files), are stored in the transient storage provided by the CUPPS platform. These files are deleted when you quit the program.

INFOConnect Database

The first time PTR Plus is launched in a new airport (that is, from a new fileserver), a series of pop-up boxes may appear briefly on the screen. These boxes indicate that an INFOConnect Database is being generated and automatically saved on the fileserver as the new master for the airport. This database consists of three binary files (IC32.CFG, InsMgr32.CFG, and ICSDATE.CFG files) which contains the correct path information. When the correct database is in place, we recommend that you back up these files.

Device Initialization

Initialization files for AEA devices are stored on the fileserver with the permanent PTR Plus CUPPS files. The initialization files are small ASCII text files that contain the string pairs (outputs and expected responses on alternate lines) to initialize, set the mode and parameters, load logos, etc). The following three initialization files are included:

- Setup.bt (for the baggage tag printer)

- Setup.bp and Setup_tkt.bp (for the boarding pass printer)

Locking

When you start PTRPlus, all configured CUPPS readers (i.e. MS, OC, and/or BC devices) on the system are locked, and are kept in a locked state until you quit PTR. The text document printer (PR device) is only locked when there is data to print. The PR device is left unlocked at other times.

CUPPS Modes

Boarding pass printers (BP) and baggage tag printers (BT) are opened in AEA mode. The ZL and ZI devices (if any) are opened in special mode. The ZL Log devices (if used) may be opened in either Platform or Application scope. All other devices, such as document printers and readers, are opened in Standard mode. Raw mode devices are not used.

Environmental Variables

The following CUPPS environment variables are referenced during startup:

• CUPPSPN (Platform Node)
• CUPPSPP (Platform Port)
• CUPPSPLT (Optional Platform Parameter)
• CUPPSAL2 (Airline User)
• CUPPSTSD (Transient Storage Location)
• CUPPSUN (User Name)
• CUPPSCN (Computer Name)
• CUPPSXSDD (XSD Location)

Supported Interface Levels

The following IATA CUPPS interface levels are supported:

• 1.00 (Pilot)
• 1.01
• 2010.05 (1.03)

The highest interface level is selected automatically at runtime by the application examining what levels are available in the particular CUPPS platform. The same interface level is used for the platform connection and all device connections.

CUPPS XML Messages

The program may generate any of following CUPPS XML message names:

• "interfaceLevelsAvailableRequest"
• "interfaceLevelRequest"
• "authenticateRequest"
• "deviceAcquireRequest"
• "interfaceModeRequest"
• "aeaRequest"
• "aeaResponse"
• "printRequest"
• "deviceLockRequest"
• "deviceUnlockRequest"
• "readerReadRequest"
• "deviceReleaseRequest"
• "byeRequest"
• "applicationStopCommandResponse"
• "logOpenRequest"
• "logWriteRequest"
• "logCloseRequest"
• "iataMessageRequest"
• "iataMessageResponse"
• "notify"
• "messageIDErrorRequest (pilot schema only)"
• "illogicalMessageErrorRequest (pilot schema only)"
• "xmlParseFailureRequest (pilot schema only)"
• "streamErrorBodyRequest (pilot schema only)"
• "streamErrorHeaderRequest (pilot schema only)"
• "readerOpenRequest (pilot schema only)"
• "readerCloseRequest (pilot schema only)"

The program may receive following CUPPS XML message names:

• "interfaceLevelsAvailableResponse"
• "interfaceLevelResponse"
• "authenticateResponse"
• "deviceAcquireResponse"
• "interfaceModeResponse"
• "aeaRequest"
• "aeaResponse"
• "printResponse"
• "notify"
• "deviceLockResponse"
• "deviceUnlockResponse"
• "readerReadResponse"
• "deviceReleaseResponse"
• "byeResponse"
• "applicationStopCommandRequest"
• "logOpenResponse"
• "logWriteResponse"
• "logCloseResponse"
• "iataMessageRequest"
• "iataMessageResponse"
• "messageIDErrorRequest (pilot schema only)"
• "illogicalMessageErrorRequest (pilot schema only)"
• "xmlParseFailureRequest (pilot schema only)"
• "streamErrorBodyRequest (pilot schema only)"
• "streamErrorHeaderRequest (pilot schema only)"
• "readerOpenResponse (pilot schema only)"
• "readerCloseResponse (pilot schema only)"

Custom Configuration

Certain features of PTR CUPPS are controllable via a PTRCUPPS.INI file. (The options in the PTRCUPPS.INI may vary according to the airline's needs.) Before you make permanent changes to this file, make sure to inform the airline. To enable an optional XML trace, disable pop-ups, or make other changes to the PTRPlus CUPPS interface, you can specify values in the PTRCUPPS.INI file and save the modified file to the same directory as the local copy of the INFOConnect database on local hard disk. The modified local PTRCUPPS.INI file will override the PTRCUPPS.INI file located on the server. However, PTRPlus must be restarted for the new settings to take effect.

Legal Notices

See the INFOConnect Enterprise Edition Read Me file for legal and third party notices.