agent guide

Passenger Solutions and Services Liaison Agent User Guide

(2001) SITA All Rights Reserved The information contained herein is the property of SITA. Legal action will be taken against any infringement.

01/01/14 of 59

Liaison Agent Guide

Table of Contents

Topic

1.0 Goal

1.1 Targeted Audience

2.0 What is Liaison?

2.1 Liaison Basics

2.2 Access to Liaison Sessions

3.0 Liaison Features

3.1 Basic Liaison Features

3.1.1 Connection/Disconnection from an emulator session

3.1.2 Switching between GUI and Emulator windows

3.1.3 Working with Split screens

3.1.4 Print Screens

3.1.5 Copy/Paste options

3.1.6 Tracking Commands (view recent commands)

3.1.7 Toolbar and Status Displays

3.1.8 SOE Options

3.2 Advanced Liaison Features

3.2.1 Screen Snapshots

3.2.2 Screen Captures

3.2.3 Recording and Playback

3.2.3.1 Scripts

3.2.3.2 Macros

3.2.4 Hot Keys

3.2.5 Logs

3.2.6 Liaison About

4.0 Emulator Window Options

4.1 Font

4.2 Screen Size

4.3 Key Mapper

4.4 Function Keys

4.5 Scripting Commands

4.6 Printing Options

4.7 Properties Screen

5.0 What is PC/PCM?

5.1 PC/PCM Basics

5.2 Access to PC/PCM

6.0 PC/PCM Features



01/01/14 of 59

6.1 Device Options

6.1.1 Selecting Devices

6.1.2 Resets

6.1.3 Queues

6.1.4 Test Prints

6.2 Diagnostics

6.2.1 Message Store

6.2.2 Task light Info

6.3 Configuration Mode

6.4 Messages to CRT

6.5 Pectabs (parametric tables)

6.6 General Troubleshooting Tips

Appendices:

A – Liaison Glossary & Acronym Guide

B – Checkin GUI

C – Boarding GUI

D – WorldTracer GUI

E – All Toolbar Icons

F – PC/PCM Printers



01/01/14 of 59

1.0 Goal

The goal of this document is to provide a simple, concise overview of Liaison software operation. This information

can be used as a training tool or user guide. The Liaison Glossary/Acronym guide is included with this document as an

appendix.

1.1 Targeted Audience

The Liaison Agent User Guide is targeted towards non-technical Liaison users. Examples are provided for each topic

covered from a non-technical perspective. Individual airline trainers and supervisors are encouraged to provide

additional functionality examples as needed.

2.0 What is Liaison?

LIAISON is a software application created by SITA‟s Specialized Design and Development team. The Liaison product

line is designed to provide terminal emulation access to Unisys and IBM mainframes. It also provides a graphical user

interface (GUI) to 3 existing mainframe legacy applications, Check-in, Boarding and Worldtracer.

For users with scripting requirements, Liaison provides a scripting tool called Liaison Script Assistant to help simplify

the script-writing process. This feature is intended for use by technical support personnel with programming language

backgrounds and will not be addressed in depth for this guide.

Liaison runs on Windows 95/98, Windows NT & Windows 2000 and is fully certified on the SITA CUTE and ARINC

MUSE platforms`. Using Windows NT Terminal Server, Liaison can also run on thin client terminals.

Users of Liaison have their choice of three communication types:

TCP/IP

X.25

X.28 dial-up.

2.1 Liaison Basics

After installation of Liaison software on a user workstation, the application can be accessed via desktop icon. The

Liaison icon is a graphical representation of a globe (planet).

Liaison Icon

Double-clicking on this icon launches the Commander toolbar. The Commander toolbar serves as a central access

point to all Liaison sessions. All configured Liaison sessions appear on the Commander toolbar as icons. Double

clicking an icon on the toolbar will open the corresponding session. Separate sessions must be used for different GUI

applications. For example, an agent using both Checkin and Boarding applications would need to have a session

configured for each.



01/01/14 of 59

Liaison Commander Toolbar

Session Icons

2.2 Access to Liaison Sessions

Most users of Liaison begin their use of the product after session configuration. In this case, required sessions are

already available as icons on the Commander toolbar once Liaison is launched.

Launching a Session – To launch a session, double-click the session icon on the Commander toolbar. Depending on

the configuration of the session, it will open either as an emulator window or a GUI for a specific application.

Once the Liaison session window has opened, the session name description can be located in the title bar on the upper

left side of the window.

3.0 Liaison Session Features

The Liaison emulator window offers various tools and options to the user. These options are accessible from the

Liaison pulldown menus (such as File, Edit, etc) and also via toolbar icon. The session status bar (bottom of session

window) displays connect status, capture status, emulator type, date/time and row/column information. Varying

statuses such as message wait indicators and system wait indicators are also displayed on the session status bar.

Liaison Emulator Window

Title bar

Pulldown menus Toolbar icons

Emulator Window

Status Bar

Connection Status

Message wait indicator Emulator messages

Emulation type

PC data PC time

Row/Column indicator



01/01/14 of 59

3.1 Liaison Basic Features

The following features are considered basic aspects of Liaison usage.

3.1.1 Session Connection/Disconnection and Sign-in.

To connect to the SITA network, a user must provide a login username and password for terminal security. Usernames

and passwords for agents are requested from SITA by Airline Headquarters. Login information can be provided during

session configuration or provided by the user at each session launch. When the user login is provided during session

configuration, the session will automatically log the user in at each session launch. If user login information is not

provided during configuration, the user will be prompted to enter it (system response: “ENTER USER

ID/PASSWORD”) at each session launch.

Note: Liaison‟s default transmit key is <scroll lock>. (Section 4.3)

Once a user has logged into the SITA network, an Agent Sign-in is required to advance further. Agent Sign-ins are

assigned by and must be requested from a user‟s Airline Headquarters. A general sign-in consists of the following

information:

Example: SIXS###/####a/##

SI <sign-in>

XS <airline> (optional depending on airline setup –

please verify with agent supervisor) ###/ <agent number>

####a/ <password>

## <usergroup> (can be up to 3 digits)

Session Time-Outs

Session connects are given a 30 second window of connect time, after which the session will be timed out. Liaison will

respond to a time-out event by prompting the user to disconnect or reconnect the session.

Session Time-out Prompt

Toolbar Icons:

„Connect Session‟

„Disconnect Session‟



01/01/14 of 59

3.1.2 Switching between GUI and Emulator windows

When a Liaison session is launched, the working window will open to a default setting either as an emulator window

or a GUI window. These settings are determined during configuration and before the first use of the session. From an

emulator window default launch, the GUI for the application being used can be accessed by clicking the File pulldown

window and selecting Back to “”GUI”” (GUI application name can be „Checkin‟, „Boarding‟, „WorldTracer‟, etc).

Emulator Window – Accessing GUI

Once a user has accessed a GUI window for an application, “Expert Mode‟ must be selected from the GUI pulldown menu

to return to the emulator window. Commands executed in the GUI window will appear as Gabriel commands in the

emulator window. For example, if a passenger list is accessed in the GUI window, the same listing will appear in the

emulator window if the user returns to expert mode. Please refer to Appendices B, C & D for examples of other application

GUIs.

Checkin GUI



01/01/14 of 59

Toolbar Icon:

„Back to “GUI”‟

3.1.3 Working with Split Screens

Liaison Split Screens are additional emulator screens used to display different functions and results within the same

session. Liaison provides split screen capability for emulator sessions to allow the user the ability to switch between

different functions without losing existing data on any individual screen. Liaison features the ability to work in as

many as five split screens for a single session. Liaison users can toggle between split screens by pressing <ctrl> +

<tab>.

Split Screen Setup

The Liaison split screen setup window can be accessed by clicking the „View‟ pulldown menu, then clicking „Split

Screen‟ / „Setup‟.

Split screen menu options

The resulting window gives the user the option to select up to five split screens, each identified by a letter (A, B, C,

D) and the original session name in the title bar. For users who will access split screens frequently, there is an option

to automatically split screens at session launch.



01/01/14 of 59

Split Screen setup window

Clicking „OK‟ in this window will launch the split screens.

Maneuvering between split screens

Liaison split screens can be arranged on a user‟s desktop in a tile (side by side) or cascade (overlapping) format. These

options are accessible from the split screen pulldown menu and can be used once split screens have been launched.

The „Split‟ option in the split screen menu allows the user to access split screens at any point during an open session.

The „Shrink‟ option will close split screens, leaving the original session window open.

Use of split screens allows the user greater flexibility between transactions without losing convenient screen data.

Different types of transactions can be delegated to a specific screen without affecting other split screen windows. For

example, an emulator main window may be used to display and refresh a complete passenger list, while:

Split Screen A is used to process passengers with special needs

Split Screen B is used to process passengers to be „unchecked‟

Split Screen C is used to process standby passengers

Split Screen D is used to process walkup passengers without reservations.

Toolbar Icons:

„Split Screen Setup‟ „Split Screens‟ „Shrink Screens‟

3.1.4 Print Screens

The print screen option for Liaison is used to print the current contents of a user‟s screen without saving the contents

to a file. Print screens can be launched by clicking the „File‟ pulldown menu and selecting „Print‟ or by toolbar icon.



01/01/14 of 59

Print screen menu option

Toolbar Icon:

„Print Screen‟

3.1.5 Copy/Paste Options

Liaison copy/paste options are provided to give users a simple way to move text between screens or into other

applications for further use. Copy paste functions can be accessed by selecting the „Edit‟ pulldown menu or by toolbar

icon.

Cut/paste menu options

Copy Feature

The „Copy‟ feature can be used to copy text from one location on the window or screen and place it at another

location. This can be accomplished in Liaison by using the mouse. Text can be copied from the screen by first

selecting it with the mouse, then clicking either the „Copy‟ icon or selecting the „Edit‟ pulldown menu and selecting

the „Copy‟ option.

Paste Feature

The paste feature allows for the actual placement of text that has been copied. Pasting of text can be accomplished by

placing the cursor at the desired paste location, then clicking the „Paste‟ icon or selecting the „Edit‟ pulldown menu

and selecting the „Paste‟ option.



01/01/14 of 59

Paste Options

„Paste Options‟ is a window designed to give Liaison users the ability to choose paste settings. Liaison default paste

settings are set to „overwrite‟. This means that pasted text will overwrite any existing text at the paste location. Paste

options can also be set to „insert‟, meaning that pasted text will be inserted in front of any existing text at the paste

location. The paste options window can be found by selecting the „Edit‟ pulldown menu, then selecting „Paste

Options‟.

Paste Options Window

Tool bar Icons:

„ Copy‟ „Paste‟

3.1.6 Tracking Commands

The Liaison „Recent Commands‟ feature was designed to allow user access to a listing of the most recent commands

entered into the emulator. The recent commands window can be accessed by selecting the „View‟ pulldown menu,

then selecting „Recent Commands‟

View recent commands menu option



01/01/14 of 59

The recent commands option is different from screen capture in that it does not copy the actual results of the

commands listed. Commands listed can be executed by double clicking them with the mouse. Commands can also be

executed from the keyboard using arrow keys to move to the desired command and then pressing the „enter‟ key.

Recent commands window

There are no toolbar icons for this feature.

3.1.7 Toolbar and Status Displays

The icon toolbar and status bar on the Liaison emulator window are defaulted to appear for the user‟s convenience.

However, these features can be removed from the emulator window at the user‟s discretion. When either feature is

enabled, it will appear checked on the pulldown menu. If either feature has been disabled, it will appear as unchecked.

Toolbar and status bar settings can be enabled or disabled by selecting or clicking on the item in the pulldown window.

Liaison toolbar and status bar settings can be accessed by selecting the „View‟ pulldown menu.

Toolbar and Status bar settings enabled



01/01/14 of 59

Toolbar and Status bar disabled

3.1.8 SOE Options

In the context of use with Liaison, SOE is an acronym for „Start of Entry‟. Start of Entry is the point at which an

emulator screen will accept commands from the user. Commands entered at a location where there is no SOE will not

be accepted by the Liaison emulator. Liaison offers different methods for users to place the SOE at the desired location

on the emulator screen:

Home Location

The „home location‟ on the Liaison emulator is the first row, first column of the screen. Commands entered at this

point will be accepted by the emulator without an SOE character being present.

SOE Home Location



01/01/14 of 59

Menu option SOE

An SOE can be placed at any point on the emulator screen by first placing the cursor in the desired location, then

selecting the „Hot Keys‟ pulldown menu and selecting „SOE char‟.

SOE menu option

Toolbar Icon option SOE

An SOE can be placed at any point on the emulator screen by first placing the cursor in the desired location, then

clicking the „SOE‟ icon on the Liaison toolbar. Note: the Key Map option for SOE is <Ctrl> + s. (See Section 4.3)

Toolbar Icons:

„SOE‟

3.2 Liaison Advanced Features

The following features are considered advanced aspects of Liaison usage.

3.2.1 Screen Snapshots

A screen snapshot is the process during which an emulator records or „snaps a picture‟ of current screen contents. The

recorded contents can then be saved to a new text file or appended to an existing text file.

Snapshots can be used if a user has specific on-screen data to be saved. Snapshots of screen contents can be taken by

clicking the „File‟ pulldown menu then selecting „Screen Snapshot‟. The toolbar icon can also be used for the same

result.

Screen snapshot menu option



01/01/14 of 59

Once the snapshot has been taken, Liaison prompts the user to name the snapshot file.

Screen snapshot save prompt window

From the save prompt, a user can provide a name for the snapshot as a new file, or select an existing file to append or

overwrite the snapshot to.

New Snapshots

Providing a name for a new snapshot file and clicking „Open‟ will save the file to C:\Program

Files\SITA\Liaison\Scripts. The save prompt window will remember the last directory accessed. If another directory is

chosen, the save prompt window will automatically return to that directory to save the next snapshot.

Overwriting or Appending Snapshots

To overwrite or append a snapshot to an existing snapshot file, the user must select the snapshot in the save prompt

window and click „Open‟. This will launch the „File Exists‟ prompt, allowing the user to select an action.

File exists window



01/01/14 of 59

If the user chooses to Overwrite the existing file, the contents of the file will be replaced with the current screen

snapshot contents. If the user chooses to Append to the existing file, the current screen snapshot contents will be

appended at the end of the existing file contents.

Liaison saves all screen snapshots as notepad.exe or „.txt‟ files.

Toolbar Icons:

„Snapshot‟

3.2.2 Screen Captures

A screen capture is the process during which the user records or „captures‟ emulator command inputs and results for a

specified period of time. The recorded commands and results can then be saved to a text file for future use or appended

onto an existing file.

Screen capturing is ideal for use in recording and documenting errors, processes or specific settings and parameters.

For example, if a user encounters an error in processing, screen capture could be used to document that error for

correction efforts. Screen capture can also be used to document processes for example use or as future reference

material for other agents. For rarely used processes that require complicated command sequences, screen capture can

be used to record the codes and parameters used and the format of process results.

Screen capture can be launched by clicking the „File‟ pulldown menu and selecting „Screen Capture‟ or it can be

accessed by toolbar icon.

Screen capture menu item

Note: the Liaison emulator status bar includes a „capture on / capture off‟ status indicator.

Once screen capture has been launched, Liaison prompts the user to name the capture file prior to recording.



01/01/14 of 59

Screen capture save prompt window

From the prompt window, a user can provide a name for the screen capture as a new file or append the recorded data

onto an existing screen capture file.

New Screen Captures

Providing a name for a new screen capture and clicking „Open‟ will save the capture file to C:\Program

Files\SITA\Liaison\Scripts and begin recording. The save prompt window will remember the last directory accessed.

If another directory is chosen, the save prompt window will automatically return to that directory to save the next

screen capture.

Overwriting or Appending Screen Capture Files

To over write or append a capture file to an existing capture file, the user must select the capture in the save prompt

window and click „Open‟. This will launch the „File Exists‟ prompt, allowing the user to select an action.

File exists window

If the user chooses to Overwrite the exiting file, the contents of the file will be replaced with current screen capture. If

the user chooses to append to the exiting file, the current screen capture will be appended at the end of the existing

screen capture. Clicking „Overwrite‟ or „Append‟ on this screen will begin recording.

Completing Screen Captures



01/01/14 of 59

Once a user has started recording a screen capture, the status bar on / off indicator will display as „Capture On‟. Once

all desired commands and results have been accomplished, the user may end recording by clicking the „File‟ pulldown

menu and selecting „Screen Capture‟ again, or clicking the „Screen Capture‟ icon. Once recording is complete, the

„Finished Capturing‟ prompt appears, giving the user an option to view or print the captured data immediately.

Clicking „Yes‟ will open the capture file, making it available for printing, while clicking „No‟ will stop recording the

capture and return the user to the emulator window. The capture file can then be accessed at another time.

Finished capturing prompt

Liaison saves all screen captures as notepad.exe or „.txt‟ files.

Toolbar Icon:

„Screen Capture‟

3.2.3 Recording and Playback

Liaison offers the options of recording and playing back scripts and macros. These options are provided for use in

automating simple commands entered by the user. Detailed scripts requiring computer programming experience

should be handled by technical personnel and will not be addressed in this section.

3.2.3.1 Recording and Playback of Scripts

A script is a collection of functions or commands listed and performed in a specific order to automate and

complete a specific process or multiple processes. Scripts are best used for processes that are frequently

performed or processes that contain many steps. For example, if an agent would like to access a passenger list

and perform a number of generic commands in a single step, recording the commands as a script allows that

flexibility.

A script recording is the process during which the user records emulator commands inputs. The recorded

commands are then saved to a text file. Script recording can be launched by clicking the „File‟ pulldown menu

and selecting „Record Script‟ or by toolbar icon.

Record script menu item



01/01/14 of 59

Please also note the „Playback Script‟ command and „Edit Existing Script‟ command.

Before recording of a script begins, Liaison prompts the user to provide a name for the script.

Script save prompt window

From the save prompt, a user can provide a name for the script as a new file, or select an existing file to append

or overwrite the script to.

New Scripts

Providing a name for a new script and clicking „Open‟ will save the file to C:\Program

Files\SITA\Liaison\Scripts. The save prompt window will remember the last directory accessed. If another

directory is chosen, the save prompt window will automatically return to that directory to save the next script.

Overwriting or Appending Snapshots

To overwrite an entire script or append specific commands to an existing script, the user must select the script to

be overwritten or amended in the prompt window and click „Open‟. This will launch the „File Exists‟ prompt,

allowing the user to select an action.

File exists window



01/01/14 of 59

If the user chooses to Overwrite the existing file, the contents of the file will be replaced with the script being

currently recorded. If the user chooses to Append to the existing file, the current script contents will be

appended at the end of the existing script. If the user then would like to move commands to a different place in

the text file script, the cut/copy and paste commands within notepad.exe can be used.

Completing a Script Recording

Once a user has started recording a script, the status bar on / off indicator will display as „Recording ON‟. When

the script is complete, the user may end recording by clicking the „File‟ pulldown menu and selecting „Stop

Recording‟, or clicking the „Record Script‟ icon again. Once recording is halted, the „Liaison Terminal‟ window

appears, listing the location of the script. Clicking „OK‟ will return the user to the emulator window.

Finish script recording prompt (Liaison Terminal)

Liaison saves all script files as „.txt‟ text files in notepad.exe.

Script Playback

Script playback runs the emulator commands saved in a script file as if they were real-time commands. Liaison

users can launch script Playback by clicking the „File‟ pulldown menu and selecting „Playback Script‟ or by

toolbar icon.

Upon launching script playback, Liaison prompts the user to choose the script name.

Script selection prompt window

From this window, the user can select a script and select „Open‟ to play it back.



01/01/14 of 59

Editing an Existing Script

Liaison gives the user the ability to access a script for editing in notepad.exe. Once a script has been opened and

edited, it can be played back to verify changes made. Scripts can be accessed for editing by clicking the „File‟

pulldown window and selecting „Edit Existing Script‟.

When „Edit Existing Script‟ is selected, Liaison will prompt the user to select the desired script for editing.

Edit script selection window

Once a script has been selected, clicking „Open‟ will launch the script for editing. As Liaison saves script,

capture and snapshot files as „.txt‟ files, the open script will appear in notepad.exe.

Script recording only records commands entered into the emulator for playback. It does not record results of

commands entered into the emulator. The following is an example of part of a completed script. Please note that

„transmit‟ appears in the written script as „/X‟.

Script Example

1) da <transmit>

2) help: <transmit>

3) <tab> <tab> <transmit>

4) <tab> <tab> <transmit>

Translation:

For step #1, the user enters „da‟, and transmits. The script records: „send da/X‟.

For step #2, the user enters the command „help:‟ and transmits. The script records: „send help:/X‟.

For step #3, the user hits the tab key twice and transmits. The script records: „send /T/T/X‟.



01/01/14 of 59

For step #4, the user hits the tab key twice and transmits. The script records: „send /T/T/X‟.

Toolbar Icon:

‘Record / Stop Record’ „Script Playback’

3.2.3.2 Recording and Playback of Macros

A macro is a free-standing window or icon that can be created and edited to allow quick access to a specific

function, collection of functions (script) or application. Liaison macros can be used to automate repetitive

functions and tasks in a single action. Liaison features a Macro „bar‟, which is a toolbar for macros. Multiple

macro icons can be stored on the Macro bar and displayed on the screen for the user‟s quick access.

Liaison Macro Bar

Creating a Macro Bar

A macro bar can be created in a few simple steps. New macro creation can be launched by clicking the „View‟

pulldown window and selecting „Macro bar‟ / „Create New Bar‟.

Create new macro bar menu item



01/01/14 of 59

Selecting „Create new bar‟ will create an initial macro bar called „New1‟. Right clicking on „New1‟ will launch

a sub-menu offering the user an option to rename the macro bar. Clicking on this menu item will launch a

prompt window, allowing the user to assign a specific name.

Rename macro bar menu option

Rename macro bar prompt

Entering a name in this window will return the user to the new macro bar (The name „Example Macro Bar For

User Guide‟ was chosen for use in this document). Right clicking on the bar will again display the sub-menu.

Selecting the „Lock Macro Bar‟ option will disable the „New Macro‟ and „Rename New Macro‟ options on the

sub-menu. Selecting again will re-enable these options.

Creating a New Macro

To create a new macro, select the „New Macro‟ option from the submenu shown above. This will launch the

new macro icon.

New macro icon

Right clicking the new macro icon will launch the „Format Macro Item‟ window.

Format Macro Item window



01/01/14 of 59

The Format Macro Item window gives the user the ability to:

Rename the macro

Display the macro icon and name as preferred

Determine what command the macro will perform.

In the following example, the parameters are set as follows:

Picture: Accept Default

Display Text: Example Macro

Text Location: Text below the picture.

Action: Run a script file (script file name „Sample Script‟ from section 3.7.1)

Please note the default path - c:\Program Files\SITA\Liaison\Scripts\Sample Script.txt

Macro format example – Run a script file.

Macro format example – Run a single command

Clicking OK on the „Format Macro Item‟ window will complete the macro creation process.



01/01/14 of 59

Final macro

To modify this macro, re-launch the „Format Macro Item‟ window and make desired changes. The macro

created above will run the sample script outlined in section 3.7.1 of this document.

Adding an Existing Macro Bar

Liaison users can access existing macro bars for easy viewing during a session by selecting the „View‟

pulldown menu and selecting „Macro Bar‟ / „Add Existing Bar‟. This will launch the „Add Existing Macro Bar‟

window. In this window, the user can select the desired macro bar. Clicking „OK‟ will close this window and

open the desired macro bar on the user desktop.

Add existing macro bar window

Macro Playback

Once a macro bar is visible on a user‟s desktop, any macro displayed on the bar can be run by simply selecting

it. For example, selecting the macro on the macro bar below would run the action indicated in the „Example

Macro‟ earlier in this section.

Macro Bar and Example Macro

Selecting the example macro above will execute Sample Script.txt as indicated during the macro creation. The

results of running this macro will mirror the results of Sample Script.txt from section 3.7.1.

Macro Help

A help document has been provided with Liaison specifically for Macros. The Liaison Macro Help page can be launched by selecting the ‘View’ pulldown menu and selecting ‘Macro Bars’ / ‘Help’. There are no toolbar icons for this feature.



01/01/14 of 59

3.2.4 Hot Keys

Liaison „Hot Keys‟ is a pulldown menu designed to provide the user with quick access to commonly used commands

and actions.

Hot Keys menu option

Hot Keys consists of the following items:

Calculator - This hot key function opens calculator.exe (a Microsoft Windows program) in a separate window.

Calculator window

Clear Screen – This hot key function clears all text from the emulator screen.

SOE Char – This hot key function places an SOE character at a point designated by the user (see 3.12).

Ignore – This hot key function causes the emulator to ignore commands for the current PNR on display.

Page Back – This hot key function moves the user to the previously accessed page of data.

Page Next – This hot key function moves the user to the next page of data, if available.

3.2.5 Logs

Liaison/PC/PCM records logs for different processes that occur during its operation. These logs can be accessed

through the Liaison directory on the user workstation hard drive. Log-files are very useful in the event of problems, as

they can be sent to the Liaison support team to assist them in defining solutions.

There are two primary logs used:

SYSMSG.LOG



01/01/14 of 59

This log file is located under c:\Program Files\SITA\Liaison\PC/PCM\sysmsg.log. Sysmsg records all system

messages and transactions that transpire over a certain length of time, including errors.

PC/PCM.LOG

This log file is specifically recorded by PC/PCM. It is located under c:\Program

Files\SITA\Liaison\PC/PCM\PC/PCM.log. PC/PCM log records all system messages and transactions within PC/PCM

that transpire over a certain length of time, including errors and problems with printer configurations.

Note: A technician is required to ensure proper creation of log files.

3.2.6 Liaison About

Liaison „About‟ is a screen designed to give the user a simple listing of Liaison software version numbers and

copyright information. Information about additional software required for the operation of Liaison is also included.

Liaison „About‟ can be accessed by right clicking the „Settings‟ icon on the Liaison Commander toolbar, then

selecting „About‟ from the sub-menu.

Accessing Liaison About

Liaison Version

Version Information for

supporting software

Copyright Data

Liaison About window

View Registration Key View System

Information



01/01/14 of 59

4.0 Emulator Window Options

Liaison provides a number of options for emulator personalization and user information. Liaison options can be

accessed by selecting the „Options‟ pulldown menu, then selecting the desired feature. Each listing opens a separate

window where users can designate specific settings.

Options menu option

4.1 Options – Font window

The Liaison „Font‟ option gives the user the ability to choose from a number of fonts in regular and bold style.

Changes made in this window are automatically applied to the text in the emulator.

Font window

Note: New fonts are not applied to split screen windows until the session has been restarted.



01/01/14 of 59

4.2 Options – Screen Size window

The Liaison „Screen Size‟ option gives the user the ability to change the emulator window‟s size by adjusting the rows

and columns. Using the mouse, Liaison emulator windows can be automatically sized by clicking and dragging the

bottom right corner of the screen. However, using the screen size window sets a default window size that remains

constant for each session launched in Liaison.

Screen size window

Note: The screen size in this window must match the screen size specified for the session‟s PID on the host. A

technician or supervisor is required to check the „CRTD‟ field of the CONLNK if a problem related to this feature

occurs.

4.3 Options – Key Mapper

The Liaison „Key Mapper‟ option gives the user the ability to change the mapping assignments for specific keyboard

keys. The window is split into three sections:

Key Action

Key Map

Specific settings

Key mapper window

To map a specific key or key combination to a specific action:

Select the desired action from the Key Action listing

Select the desired key or key combination from the Key map listing

Click „OK‟.

Pressing the key or key combination designated in this window will launch the action mapped to that key. For

example, the Liaison default for „Clear Screen‟ is the key combination <Ctrl> + <X>. The example Key Mapper

window (above) shows the clear screen action, changed to map to the <Esc> key. As a result of this change, pressing



01/01/14 of 59

the <Esc> key will clear the emulator screen until the mapping is changed by the user. Key combination options

provided by Liaison are <Ctrl>, <Alt> and <Shift>.

Specific Settings

The key mapper window also offers a number of specific emulator options that commonly vary between users and

airlines. These settings are as follows:

Transmit character under cursor - this option allows the user to choose whether or not the character under the cursor

will be transmitted as the end of a command or if the character behind the cursor signifies the end of a command.

Uppercase text – this option allows the user to choose whether or not text entered into the emulator screen will appear

as all upper case or all mixed text.

CR also does EOL – this option allows the user to choose whether or not pressing the carriage return key signifies end

of line (text after the point of carriage return on a specific line will be deleted) or not signify end of line (text after the

point of carriage return on a specific line will be skipped over).

Invert colon key – this option allows the user to choose whether or not the colon key symbols will be inverted during a

Liaison session. For example, the colon key appears on the keyboard as:

:

; (Top line requires shift key)

Inverting this key will change it to:

;

: (Top line requires shift key)

With the inverted setting, the shift key does not have to be pressed to type a colon, thus saving keystrokes and entry

time.

Default – pressing the „Default‟ key will return all setting to the Liaison default.

Toolbar Icons:

„Configure Keyboard Mapping”

4.4 Options - Function Keys

The Liaison „Function Keys‟ option gives the user the ability to change the mapping assignments for specific keyboard

keys. Commands for Shift, Ctrl and Alt are listed on separate tabs in the Function key window. The window is split

into two columns:

Enable – lists the function keys

Text to Transmit - text that the chosen function key will transmit.

Function keys window



01/01/14 of 59

Different function key commands can be assigned to a single function key using key combinations. For example, F1

can be used to enter the command <help:/X>, while Ctrl + F1, Shift + F1 and Alt + F1 can be used for different

commands.

In the example above, the F1 key has been enabled and set to run the command <help:/X>. (/X is the symbol for

„transmit‟)

4.5 Options - Scripting Commands

Note: The '/' has special meaning in this script language. It denotes special features and options as noted below. In

particular, notice the 'send' command; if you want to send a '/', you need to specify '//'.

Command Purpose Syntax

beep Produce a beep sound on the PC speaker. beep

call Execute another script, a great way to create

subroutines. The script must be in the 'scripts'

subdirectory where you installed Liaison

call script2.txt

exit Stop executing the script at this point. exit

extract Get characters from emulator screen. extract (StartRow,StartCol,Length)

find Look for a pattern in the next host response. find PSA (find * finds anything)

for Iterate the loop for each item on the command line for x in 1 2 3 loops 3 times

goto Branch to a specified label that begins with a colon(:). goto mylabel

if Conditional control for any expression between if then. if %err%>0 then beep

input Gets the next record from a file and stores it in a

variable. The "/R" option resets the file to beginning.

input filename varname

input filename /R

loop Go back to the most recent while command. loop

next Go back to the most recent for command. next x (the for variable is required)

output Appends data from a variable to a file. The "/R" option

resets the file to the beginning.

output filename varname

output filename /R

position Moves the cursor to the desired screen position. position row,col

print Prints data to the printer. print string

send Send characters to the host. The characters will be sent exactly as typed. Use the following

codes to generate additional functions.



01/01/14 of 59

/C clears the screen

/X transmits the rest of the command line

// treats the slash as a literal character

/H cursor home

/D end of screen

/R cursor return

/P cursor up

/O cursor down

/B backtab

/S SOE character

/I cursor left

/T cursor right

/A erase to end of line

/F erase to end of screen

/Q delete character

/L delete line

/Y insert line

/W insert character

/G beginning of line

/N end of line

/V duplicate line

/Z lock keyboard

/U unlock keyboard

/K backspace

set Specify the value of script variable. set x=1

substr Returns a portion of a string. substr

(SourceString,StartPos,Length)

wait Sits idle for a specified number of seconds. wait 1

while Iterate the loop as long as the condition is true. while %x%<3

: Designates a line as a label, thus allowing goto

branching.

: mylabel

# Designates a line as a comment. # Script created 3-NOV-1997

4.6 Options – Printing

The Liaison Printing options window gives the user the ability to set printer defaults and behavior. All print jobs can

be defaulted to a window standard printer connected to the user workstation, or can be routed through PC/PCM and

printed on a MSG printer.

Printing options window

The printing options window also gives the user a choice of whether or not to print blank lines at the end of each page.



01/01/14 of 59

4.7 Options – Properties Screen

The Liaison „Properties‟ option accesses an information window. This properties window lists properties specific to a

particular session. No changes can be made in this window. Note: Automatic Sign-In information, when used, is

displayed in this window.

Session properties window

Toolbar Icon:

„Display Session Properties‟

5.0 What is PC/PCM?

PC/PCM is a software application created by SITA‟s Specialized Design and Development team to work in

cooperation with Liaison software. PC/PCM is designed to provide printer communications for Liaison using a single

PID instead of multiple PIDs for different print devices.

PC/PCM provides the user with a graphical user interface, displaying device polling, printer status, printer

configuration, messages to CRT and various other features. The PC/PCM software comes with the Liaison package

and is not used outside of Liaison.



01/01/14 of 59

5.1 PC/PCM Basics

PC/PCM is automatically installed as part of the Liaison software package. If a specific Liaison session is

configured to access PC/PCM, the session will automatically launch PC/PCM upon user signin. Upon session

launch, the PC/PCM window is not automatically displayed. Instead, the PC/PCM icon appears at the bottom of

the desktop window, indicating to the user that PC/PCM is available for use.

Emulator window with PC/PCM icon visible

PC/PCM

Icon

5.2 Access to PC/PCM

Users of PC/PCM access the program only during session use. Access to PC/PCM can only be achieved after the

user has provided a user login/password and has signed in to the SITA network.

Launching PC/PCM window – To access the PC/PCM window, the user can:

Single or double click the PC/PCM icon at the bottom of the screen.

Press <Ctrl> + p. (available only while PC/PCM window is minimized).

Press <Alt> + <Tab>. (available only while PC/PCM window is maximized).

Once the PC/PCM window has opened, the name of the session it is associated with appears in the upper left side

of the window. Print devices configured for the session are displayed as status bars on the left side of the screen

and system messages are displayed directly beneath the device status bars.



01/01/14 of 59

6.0 PC/PCM Features

The PC/PCM window offers complete print control for all devices used with Liaison sessions as well as CRT message

management. As with Liaison, PC/PCM offers various options and tools to the user via pulldown menus. The

PC/PCM main window displays all devices being used by specific sessions. These devices are constantly polled to

provide the user with a real time status.

PC/PCM main window

Pulldown

menu

Device Type

Device

Listing

Polling Lights

System

messages

Status Bar

PC/PCM Configuration/diagnostics

window

6.1 Device Options

PC/PCM provides a number of tools to manage print devices used in cooperation with Liaison. These tools

allow the user to track printer queues, messages, test specific settings and monitor print status.

6.1.1 Selecting Devices

Once the PC/PCM window has been opened during a session, different devices can be

accessed and viewed. Devices can be selected either by clicking on the device bar or by selecting the

„Device‟ pulldown menu and then selecting „Select‟. A separate window will appear, prompting the

user to enter the device number. Device bars are numbered 1 to 6 in the PC/PCM window and 0 to 5 in

the System Messages window.



01/01/14 of 59

Device pulldown menu in PC/PCM

„Select‟ menu option

Once the user has entered the desired device number in the prompt and pressed „OK‟, PC/PCM will

display diagnostic information for that device as shown below.

PC/PCM with device diagnostic displayed



01/01/14 of 59

6.1.2 Device Resets

Under certain circumstances, a device may need to be reset in order to continue error-free operation.

To do this, the device must be selected and reset within PC/PCM. Before resetting a device, the device

must first be selected. Once the device has been selected, it can be reset by selecting the „Device‟

pulldown menu, then selecting „Reset‟. The diagnostic window will show the results of the reset.

Device reset menu option

Diagnostic window before

device reset

Device reset result display

Diagnostic window after device reset



01/01/14 of 59

6.1.3 Device Queues

PC/PCM features three different device queues. PC/PCM queue windows are:

Device Queue – tracks general print jobs and messages. This queue can be accessed by

selecting the „Device‟ pulldown menu and selecting „Queue‟.

UE Queue – tracks unrecoverable errors. This queue can be accessed by selecting the „View‟

pulldown menu and selecting „Unrecoverable Error Queue‟.

SCN Error Queue – tracks errors reading stock control numbers. This queue can be accessed

by selecting the „View‟ pulldown menu and selecting „SCN Error Queue‟.

In order to view a queue for a specific device, the device must be selected and PC/PCM must be in

configuration mode. If a user attempts to view a device queue without first going into configuration

mode, PC/PCM will display an error message.

PC/PCM Error Message

Configuration mode may be accessed by selecting the „View‟ pulldown menu, then selecting

„Configuration‟. (please see section 6.3) Once in configuration mode, device queue information can be

viewed.

PC/PCM device queue information is displayed in the „Device Queue Viewer‟ window. This window

allows navigation through multiple messages, reprints of messages and the ability to delete messages. Device queue viewer window



01/01/14 of 59

6.1.4 Test Prints

Test printing in PC/PCM is used to verify that printer connections are working properly. PC/PCM will

send test prints to a specific device selected by the user. Test prints include test ATB coupons for ATB

printer, test messages for message printers, boarding passes for boarding pass printers, etc. The queue

for that device will also show the test print message (pls see device queue window in section 6.1.3).

Test print menu option

6.2 Diagnostics

PC/PCM diagnostics menu gives the user basic information about PC/PCM. The diagnostic window also

gives basic information about each device being used with a specific Liaison session, such as device readiness

and print confirmation. When PC/PCM is used for multiple sessions, the session names are listed under the

Diagnostics pulldown menu. The user can access this menu to switch between session PC/PCM windows, or

the mouse can be used to click on the desired window. Message Store and Task Light Information options are

accessible from this menu.

Message store menu option



01/01/14 of 59

6.2.1 Message Store

The „Message Store‟ menu option opens a separate window to display the location of the PC/PCM

message store. The message store is named SYSMSG.LOG.

Message store window

6.2.2 Task Light Info

The „Task Light Info‟ menu option opens a separate window to display descriptions of each task light

in the PC/PCM window.

Task Light info window



01/01/14 of 59

6.3 Configuration Mode

Configuration mode is the state during which all device polling and functionality is suspended in PC/PCM

until reactivated by the user. Configuration mode must be accessed before device queues can be viewed. (see

section 6.1.3) Upon accessing configuration mode, the user is warned that all polling will cease. Printing

requested during configuration mode will not commence until after configuration mode has been deactivated

by the user. Configuration mode can be activated and deactivated by selecting the „View‟ pulldown menu,

then selecting „Configuration‟.

Configuration menu option

Configuration mode warning message

6.4 Messages to CRT

Messages to CRT can be tracked in PC/PCM by accessing the device queue viewer. PC/PCM offers a unique

benefit here in that the user can resend, print or delete CRT messages or save them for later reference. To

view the messages to CRT queue, the user must do the following:

Access configuration mode

Select the CRT device bar

Select the „device‟ pulldown menu

Select „Queue‟

CRT message displayed in Device queue viewer window



01/01/14 of 59

Print commands sent from this window will not commence until the user deactivates configuration mode.

PC/PCM displays a reminder message to the user when a print job is initiated from the device queue viewer.

In the case of Messages to CRT, a print request will re-send the message to the CRT instead of printing a

physical hardcopy to a different device.

6.5 Pectabs (Parametric Table)

PC/PCM uses Parametric tables to set print configurations for specific print devices, such as ATB and bag tag

printers. The parametric table consists of a number of parameters for the printer to use as a guideline when

printing tickets, boarding passes and bag tags.

Load Test Pectab

The ability to load a test pectab for a specific session must be set during that session‟s configuration. Settings

enabled during session configuration are generally set by technical personnel prior to session use. For

information regarding the load test pectab feature, please refer to the Liaison User Guide (location –

C:\Program Files\SITA\Liaison\ UserGuide6.doc).

6.6 General Troubleshooting

{PSA/PDQ/RS/IR…}

or similar message

received on terminal

screen

This is a PC/PCM header message being displayed on the screen instead

of being intercepted by PC/PCM. This happens when the PID is

configured for PC/PCM on the mainframe, but PC/PCM is not

configured on the PC. Insure that the PC/PCM box is checked in the

Liaison Configuration Wizard Step 5 of 6, Protocol configuration

window.



01/01/14 of 59

Form feed

(unwanted) on

message printer

Check the PC/PCM Configuration Wizard. Select the Message Printer

device type, and in step 4 of 5 select the Character Translation tab.

Ensure the “Form Feed after Message” field is not selected.

That should work, but if not, try the following:

The printer may have a form length control, usually in the form of dip

switch settings. This can be reduced to the lowest possible value. Refer

to the printer manual for further details.

Use the Generic / Text Only driver instead of the printer manufactures

driver. Depending on the Windows version, it may have a form feed

option. If it does, turn form feed off.

General Printer troubleshooting procedures.

If the printer won’t

print

LOOK AT THE PC/PCM DIAGNOSTICS WINDOW FOR THE

DEVICE. See if this offers any helpful information as to what the

problem may be. Are the diagnostic lights all green or a combination of

green and red?

RESET THE DEVICE (PHYSICAL): Turn the power off and back on.

RESET THE DEVICE (PC/PCM): From the PC/PCM control window,

click View/Configuration to turn polling off. Click the Device, click

Device / Reset. Then click View/Configuration to turn polling back on.

DELETE THE DEVICE QUEUE: From the PC/PCM control window,

click View/Configuration to turn polling off. Click the device, and click

Device / Queue. Click the Delete All Items button. Click View /

Configuration Mode to turn polling back on. Note: before turning polling

back on, it may be helpful to reset the device again.

EXIT AND RE-ENTER THE SESSION.

REBOOT THE PC.

Check the physical

Is the printer plugged in?

Is the printer cable connected?

Is the printer cable connection secure on the PC end and the printer end?

Is the printer powered on?

Is the printer on-line?

For all other technical support issues, please contact [email protected].

mailto:[email protected]



01/01/14 of 59

THIS PAGE INTENTIONALLY BLANK



01/01/14 of 59

Liaison Agent User Guide

APPENDIX A

Liaison Glossary & Acronym Guide



01/01/14 of 59

Liaison Glossary & Acronym Guide

Term - SRT Definition

AAS Airline Application Services, a division of SITA.

API Call Applications Program Interface. LAPI.OCX is the Liaison application interface. Documentation is in LAPI.HTML.

Asynchronous Dialup connection.

ATB Device Automated Ticket and Boarding Pass printer or gate reader.

ATHENA Terminal controller application.

ATLDPXS Messaging Code – SITATEX code for requesting PID configurations.

ATLIS ATLanta Information Services

ATS Anomaly Tracking System – System accessible via SITA SAT web. Site lists Liaison (including PC/PCM) trouble reports and trouble resolution originating in the production and test environments.

BAG Unisys mainframe computer hosting the World Tracer lost baggage system.

BDM SITA Account Manager/Business Development Manager.

Boarding SITA DCS – Application used to manage passenger boarding process. Accessible from Liaison application in GUI or Expert Mode.

BTP Bag Tag Printer. Used to print baggage tags for checked luggage via PC/PCM.

Checkin SITA DCS – Application used to manage passenger checkin and flight reconciliation process. Accessible from Liaison application in GUI or Expert Mode.

CLF A code that is required by PC/PCM to read data from magnetic stripes.

CLF Code Translations The process of translating Pectab element numbers into CLF codes.

Commander Liaison Application Toolbar where application GUI, emulator and settings icons are displayed.

Comms Option Communications Option. See Comms Protocol.

Comms Protocol Communication Protocol. TCP/IP, x.25, and x.28 are the options available for Liaison. Liaison will not work with P1x24.

Communication Gateway A Server that acts as a central networking connection point for multiple terminals and/or additional servers.

COMS:ASCU Host Transaction that shows P1024C configuration. (P1024C – SITA proprietary transport, not compatible with Liaison).

COMS:TELECON Host Transaction that shows X.25 or TCP/IP PID configurations.

CONLINK Communications Device Control File – A file on the host containing specific system data for an individual PID number.

CRT Cathode Ray Tube - Computer Monitor

CRT Message Message sent to display on an agent CRT. Can be stored in PC/PCM and printed on command. Example: Gabriel ZZ messages.

CUTE Common Use Terminal Equipment. Developed by SITA. CUTE NT/Plus version compatible with Liaison.

CUTE Peripheral Mgr. Software program that manages peripheral machines (such as printers) attached to a CUTE workstation.

DCP Distributed Communications Processor. Multiple DCP’s are in Atlanta. Any connection to an Atlanta host will go through a DCP.

DCS Departure Control Systems. SDCS is the SITA Departure Control System.

DGJ transaction A Ticketing transaction that sends stock control numbers to the Ticketing Application.

Dynamic PID A PID number that is randomly assigned from a pool of numbers during an emulator session launch. PSA and PSB each have a pool of 10,000 dynamic PIDs available for use on a system wide basis.

ECF File Liaison 3270 configuration file.

EICON An independent corporation providing communications cards and software for x.25 connectivity.

Emulator A program that allows the user to use the PC as a dumb terminal. See also: Terminal Emulation.

Expert (native) Mode UTS Emulator screen. See also: Emulator.

Firmware Software residing on the printer that communicates with the user’s printing software (such as PC/PCM).

Flow Control None, DTR/DSR, RTS/CTS or both are the available selections in the PC/PCM configuration wizard.



01/01/14 of 59

Form Feed Printer function of feeding the paper to the top of form.

Form Mode Graphical user interface (GUI) mode.

Function (PC) keys A row of keys across the top of a standard keyboard used for specific functions defined by the user.

FQT Unisys mainframe computer hosting the Fares application.

Gabriel SITA Reservations system. Accessible via Liaison in Expert Mode

GUI Graphical User Interface. Checkin, Boarding, and World Tracer are the 3 currently released GUIs. See also: Form Mode

Homologate Process of validating a printer for Liaison compatibility and use.

IATA City code City code designated by the International Air Transport Association.

Icon Graphic or symbol used to depict an executable object. Example: Liaison uses a picture of a globe as it’s executable icon.

Inline CLR An option in PC/PCM configuration; used to enable SDCS configuration fields for Dynamic PID devices.

ISNET Information Service Network. A SITA product for connecting to the network via TCP/IP. A shared router in Atlanta serves the customer.

ISO Country Code Country code designated by the International Organisation for Standardisation.

Keyboard Mapping Assigning specific functions to specific keyboard keys or combinations of keyboard keys. Example: <Ctrl> + <X> to clear screen, <Ctrl> + <P> to print.

LAN Local Area Network

LANAS LAN (Local Area Network) Access Services – A SITA product for connecting to the network via TCP/IP. A dedicated in Atlanta router serves the customer.

Liaison Configuration Wizard

Step by step dialogue boxes used to guide users through Liaison session configuration. Each dialogue box prompts the user to provide specific information regarding security, session appearance, application used, etc.

Liaison Script Assistant A script writing tool included with Liaison software.

Local Print Prints current contents of screen, launched by menu or icon command. See also: Screen Print

LU-LU Session A session that is run connected to a 3270 host application.

Macro A free-standing window that can be created and edited to allow quick access to a specific function, collection of functions (scripts) or application. Used to automate repetitive functions and tasks.

Macro bar Floating windows of macro icons that are user defined. Each icon is programmed to perform a task of the user’s choosing. See Also: Macro

Master Dynamic PID Record Per Airline, the Master Dynamic PID Record defines default parameters for use with dynamic PID Access.

Message Printer Printer used for basic, text only printing. For Liaison users, this type of device is usually attached to the computer parallel port.

Message Store An option in PC/PCM that saves system messages and messages between PC/PCM and a printer device to the file SYSMSG.LOG. Sometimes useful for ATL in debugging Liaison problems.

Module Sections of the Liaison Application that allow the user to perform specific functions such as boarding, checking in passengers, or communicating with the host.

MUSE Multi User System Environment. Developed by ARINC. Liaison can be used on the MUSE platform.

NIC Network Interface Card

NUI Network User Identifier – Required for X.28 access. Obtained from geographic SDU.

OCR Optical Character Reader – The Cornet 6701 Passport Reader is currently (Feb01) the only OCR programmed for use with Liaison.

ODVN Office Device Number Identifier – A field in CONLNK that defines a Message Printer PID.

OIA Indicator Operator Information Area Indicator – Appears in Liaison 3270 emulation sessions.

OSI NSAP Open System Interface – Network Service Access Point. Entered in Liaison configuration for x.25 connections. Enter 9001031 to reach PSA or 9001181 to reach PSB.

PAD ID (DNA) 9001031 for PSA, 9001181 for PSB (DNA – Destination Network Address)

Parallel Printer Hard copy text only printer. For Liaison, generally used as a message printer. See Also: Message Printer

Parametric Table PECTAB. Required for ATB2 printing. Also can be used in bag tag printing.

PC/PCM A printer software program included with Liaison. PC/PCM controls access to various devices, such as CRT, printers, boarding gate readers, and OCRs. Allows multiple devices to share a single PID.



01/01/14 of 59

PC/PCM Config Wizard Step by step dialogue boxes used to guide users through the PC/PCM portion of Liaison session configuration. Each dialogue box prompts the user to provide specific information regarding types of print devices, printer settings, etc.

PC/PCM.LOG A file created by PC/PCM when the trace logging function is turned on. This file is very useful in debugging printer problems. Located in \program files\sita\liaison\PC/PCM directory.

PECTAB Parametric Table. Required for ATB2 printing. Also can be used in bag tag printing.

PID Position Identifier. Used as a session identifier by a Unisys host (i.e. PSA/PSB/BAG/FQT).

PNI Passenger Name Index

PNL Passenger Name List

PNR Passenger Name Record

PSA Unisys 2200 mainframe hosting several Atlanta applications, including Gabriel and SDCS. Used by carriers based in Europe, Middle East, and portions of the Asia region.

PSB Unisys 2200 mainframe hosting several Atlanta applications, including Gabriel and SDCS. Used by carriers based in North and South America, Africa, and portions of the Asia region.

Registration Key A coded algorithm used to determine which applications have been requested and contracted for a specific customer’s Liaison installation.

Rendezvous SITA Middleware Architecture. Rendezvous is the TCP/IP communications server system that Liaison clients talk to.

RES Reservations

SAT Former department of SITA - Specialized Applications and Technologies – Now referred to as Specialized Design and Development (SDD).

SCN Stock Control Number – Pre-printed/pre-encoded numbering sometimes used on ticket stock for security purposes.

SCN Error Queue Stock Control Number Error Queue – DGJ updates intended for the host will end up on this queue when an error in the host update process occurs. View from PC/PCM by clicking View / Unrecoverable Error Queue. Must click View / Configuration first.

Screen Capture A process during which an emulator records or ‘captures’ all command inputs for a period of time determined by the user.

Screen Print Prints current contents of screen, launched by menu File / Print command or the printer icon. See also: Local Print

Screen Snapshot A process during which an emulator records or ‘snaps a picture’ of current screen contents that can then be saved to a file.

Script A collection of functions or commands listed and performed in a specific order to automate and complete a specific process.

SDCS SITA Departure Control System

SDD Specialized Design and Development. A department of SITA specializing in design and development of new products, formerly called SAT (Specialized Applications and Technologies).

Serial Parameters Communication parameter settings such as Parity, stop bits, etc. Can be found in PC/PCM configuration. Parameters specified in PC/PCM must match settings on the printer.

Serial Port Physical connection to which a printer cable is attached. Located on the back of PC.

Serial Printer Printer with a serial interface as opposed to a parallel interface. Example: IER or Dassault Bag Tag or Boarding Pass Printers.

Session An object that is defined in the Liaison configuration wizard, it is configured to access a specific host application via a specific communications protocol. Sessions are accessible by icons from the Liaison Commander toolbar.

SITA XPAD Access point into the SITA network.

SITATEX Product of SITA used for messaging.

SNA Protocol Systems Network Architecture Protocol - Used when accessing IBM hosts, such as those based at XS LON.

Split Screen Additional emulator screen used to display additional functions within the same session. Created to allow ability to switch between different functions without losing existing data on a particular screen.

Static (specific) PID A specific or ‘fixed’ PID number that is pre-assigned to a specific user.

STX/ETX value Start of Text/End of Text. STX values – 02 or 91and ETX values 03 or 93 are common.

System Print Sys print - prints the contents of system buffer, using ‘PT’ command. To print the current PC/PCM CRT message, use PTPCM.

Task Light Info In PC/PCM, a list of descriptions for processes being monitored by task lights.

TCP/IP Transmission Control Protocol / Internet Protocol – The communications protocol used for the Internet and for parts of SITA’s private network.

Terminal Emulator A program that allows the user to use the pc as a dumb terminal. See also: Terminal Emulation.



01/01/14 of 59

Terminal Login Username and password information required to pass the ATHENA security check point.

Terminal Security Security measures put in place to control user access by ATHENA. Example: username and password constraints.

TKT Ticket or Ticketing

Trace File A log file used to track communications connections. See also PC/PCM.LOG, SYSMSG.LOG.

Trace Logging The process of recording network connection messages. See Liaison User Guide section 5.6 for instructions on enabling the Liaison trace logging function.

Tran Code (length) Transaction Code Length – length of transaction identifier field (i.e. hardcode) used by printers. Can be from 0 to 5. Required for Liaison PC/PCM configuration for ATB and BTP printers.

Unisys Vendor of the SITA Atlanta based mainframe computers.

UTS-20 Emulation Protocol used to access Unisys host computers.

WT WorldTracer – SITA application used to track lost baggage. Accessible from Liaison application in GUI or Expert Mode.

X.25 Direct Access Service – Uses a PC with an Eicon card and software to establish a connection with the SITA network.

X.28 Dial Access Service – Uses a PC with modem to establish a connection with the SITA network.

ZZ Address/ZZ Messaging Gabriel System instant messaging feature. Configured per airline by the Gabriel representatives with the ZZM: transaction.



01/01/14 of 59


APPENDIX B

Checkin Graphical User Interface



01/01/14 of 59

Departure Control Systems - Checkin GUI



01/01/14 of 59


APPENDIX C

Boarding Graphical User Interface



01/01/14 of 59

Departure Control Systems - Boarding GUI



01/01/14 of 59


APPENDIX D

WorldTracer Graphical User Interface



01/01/14 of 59

Departure Control Systems – WorldTracer GUI



01/01/14 of 59


APPENDIX E

Liaison Toolbar Icons



01/01/14 of 59

Liaison Toolbar Icons

Icon Description Icon Appearance Connect Session

Copy Text

Disconnect Session

Function Key Mapper

New Macro

Paste Text

Print

Record Script

Screen Capture

Script Playback

View Session Properties

Shrink Screen

Screen Snapshot

Start of Entry (SOE)

Split Screen Setup

Begin Split Screen



01/01/14 of 59


APPENDIX F

Liaison - PC/PCM

Printers

&

Firmware



01/01/14 of 59

Liaison - PC/PCM Printer Listing * The following printers have been homologated for use with Liaison-PC/PCM. Please direct any printer questions to

Liaison [email protected].

ATB Devices Bag Tag

Printers

Gate Readers Document Printers

Dassault BPR 600/TPR 800 Genicom 201 Dassault 320 OKI 180

Documax A3300 IER 423 IER 607 OKI 320

Genicom ATB 1550xp IER 508 IER 627 TI 810

IER 411 IER 512 TI 885

IER 457 TI 895

IER 517

IER 557

Sigma 7200

Dassault A640

Liaison - Certified IER Peripheral Firmware The following tables contain Firmware Versions certified for Liaison Desktop, Muse, and Cute operations.

Device Last Firmware Version Certified Firmware Version

Dassault 640 DLD1.GAE1.01 DLD1.GAE1.01

IER 411 98.044/10 98.944/10

IER 508 98614 1.01 98614 1.01

IER 508BP 98614 1.00 98614 1.00

IER 517 92708 1.03 92708 1.03

IER 512C ASIC 92934 1.01 92934 1.01

IER 512C AEA BP 930771 1.00 930771 1.00

IER 512C AEA BT 929342 2.00 929342 2.00

IER 557 STANDARD 90385 1.02 90385 1.02

IER 557 TURBO 90479 1.02 90479 1.02

IER 627A 91709 1.01 91709 1.01

MUSE

IER Peripheral Device Last Firmware Version Certified Firmware Version

IER 512C ASIC 92901 3.10 92901 3.05

IER 512B NS 92675 1.00 98602 1.00

IER 508 98602 1.00 98614 1.00

IER 557 STANDARD 90387 3.06 90387 3.03

IER 557 TURBO 90437 3.06 90437 3.04

IER 627A 91703 1.05 91703 1.04



01/01/14 of 59

Liaison - Certified IER Peripheral Firmware - Continued

CUTE

IER Peripheral Device Last Firmware Version Certified Firmware Version

IER 512C NS 92708 1.03 92708 1.03

IER 512B NS 92643 1.06 92643 1.05

IER 512C ASIC 92915 1.01 92915 1.01

IER 512B ASIC 92903 1.01 92903 1.01

IER 508 98615 1.00 98615 1,00

IER 557 STANDARD 90322 1.02 90322 1.02

IER 557 TURBO 90479 1.02 90479 1.02

agent guide

Documents