Queues

Queues are system files which can store PNRs or messages similarly to a folder. There are some pre-established queues and others that are free to be used according the customer´s need.The function of the pre established queues is to file and store PNRs or messages that contain a certain notification with different purposes, such as informing the passenger or facilitate the operator's job to check a reservation status.

List of pre-established queues

From queue 1 to 100 there will be PNRs that for some reason are automatically placed on queues, they are pre-established queues that must be worked manually.

PNRs that are inside queues are not repeated in the same queue if they are placed and are already inside.

This range of queues are only available for the headquarters city (HDQ), which is a fictitious city representing the General Control of all transactions within an airline/company. Queues within HDQ city usually contain messages and PNRs that require the control and analysis of an administrator.

From queue 201 onwards, they are free to store PNRs from passenger lists.

Below are the queue numbers and their respective description:

Queue	Category	Description	Detail
1		24H - TIME LIMIT	Stores all those PNRs that are within 24 hours of their ticket time limit. The PNRs that are removed will be placed again when the system repeats the check process. This process runs for all PNRs every hour
2		48H - TIME LIMIT	Stores all those PNRs that are within 48 hours of ticket time limit. .
3		ROBOT - TIME LIMIT	Store all PNRs that have their time limit modified by the ROBOT TL.(expiration)
4		AUTOMATIC TIME LIMIT AND ROBOT EXCEPTION	Store all PNRs that were created and modified with command 8T (Robot Time Limit exception)
5		CNL - TIME LIMIT	Stores PNRs that result in automatic cancellation by expiration.
6		CNL SSR/SEAT - TIME LIMIT	Stores pre-assigned seats time limit
7		CNL - BY CARRIER	Stores PNRS that are manually canceled by another airline (in case of existing agreements within KIU). For example, travel agencies will be able to display reservations that an airline manually cancels.
10		WAIT LIST CONFIRMED	Stores PNRs that are confirmed from a waiting list, automatically by the system. All PNRs with status KL.
20		PNR - REQUIRED	Stores individual PNRs with required status (HM), either because the flight is in a required state or for some other reason.
25		PNR - CONFIRMED	Stores individual PNRs with required status (HM) and confirmed (status KK).
30	1	SCHEDULE CHANGE * FLT 0 TO 2 DAYS FROM CHANGE	Stores PNRs with any flight schedule change with UN, TK or TL status that need be acknowledged. .PNRS with booked flights departing 0 to 2 days from the change date will be displayed
30	5	SCHEDULE CHANGE * FLT 3 TO 5 DAYS FROM CHANGE	Stores PNRs with any flight schedule change with UN, TK or TL status that needs be acknowledged. .PNRS with booked flights departing 3 to 5 days from the change date will be displayed
30	10	SCHEDULE CHANGE * FLT 6 TO 15 DAYS FROM CHANGE	Stores PNRs with any flight schedule change with UN, TK or TL status that needs be acknowledged. .PNRS with booked flights departing 5 to 15 days from the change date will be displayed
30	20	SCHEDULE CHANGE * FLT 16 TO 30 DAYS FROM CHANGE	Stores PNRs with any flight schedule change that needs be acknowledged. Therefore, they will be found with status UN and TK or TL. In this case, the own PNRs created in the pseudo city itself will be saved.PNRS with booked flights departing 16 to 30 days from the change date will be displayed.
30	50	SCHEDULE CHANGE * FLT 31 DAYS FROM CHANGE	Stores PNRs with any flight schedule change with UN, TK or TL status that needs be acknowledged. .PNRS with booked flights departing 31 days and beyond from the change date will be displayed
30	99	SCHEDULE CHANGE * UNDEFINED	Stores PNRs with any flight schedule change with UN, TK or TL status that needs be acknowledged.
31		SCHEDULE CHANGE - NEEDS MANUAL REAC	Stores PNRS with schedule change that need manual reaccommodation ( HDQ access only)
32		VMOVE - PNRS AFFECTED	Stores PNRS after VMOVE command is performed.(used to transfer a passenger list from one flight to another or several different flights.(HDQ access only)
40		GROUPS - REQUIRED	Stores group PNRs with required status segments(HM). These PNRs will be placed on the controlling carrier queue to notify that a group is on request and for the PNR creator to keep track of the groups requested.
45		GROUPS - CONFIRMED	Stores group PNRs with confirmed status segments(HK). These PNRs will be placed on the controlling carrier queue to notify that a group is on request and for the PNR creator to keep track of the groups requested.
46		SSR - REQUIRED	Stores PNRs containing SSRs with PN (Pending)status. Special Services required but no action has yet been taken.
47		SSR - CONFIRMED	Stores PNRs containing SSRs in HK or KK (confirmed) status. Special Services required but already confirmed.
48		SSR - REJECTED	Stores PNRs containing SSRs in UC status (unable to confirm) Special services required but unable to confirm.
49		SSR - ADPI REQUIRED	Stores PNRS requiring SSR ADPI
50		SSR - SCHEDULE CHANGE - NEEDS MANUAL REAC	Stores PNRs with required or confirmed SSRs for flights with schedule change or cancellation. SSRs will remain with UN status and will have to be requested again on the flights where reaccommodation takes place.
55	1	SEAT - SCHEDULE CHANGE - NEEDS MANUAL REAC * FLT 0 TO 2 DAYS FROM CHANGE	Stores PNRs with a schedule change when no new seats can be assigned automatically.This requires manual action. It will display reservations with flights starting from the date of change until 2 days later.
55	5	SEAT - SCHEDULE CHANGE - NEEDS MANUAL REAC * FLT 3 TO 5 DAYS FROM CHANGE	Stores PNRs with a schedule change when no new seats can be assigned automatically.This requires manual action. It will display reservations with flights starting from the date of change until 5 days later.
55	10	SEAT - SCHEDULE CHANGE - NEEDS MANUAL REAC * FLT 6 TO 15 DAYS FROM CHANGE	Stores PNRs with a schedule change when no new seats can be assigned automatically.This requires manual action. It will display reservations with flights starting from 6 days after the change up to 15 days.
55	20	SEAT - SCHEDULE CHANGE - NEEDS MANUAL REAC * FLT 16 TO 30 DAYS FROM CHANGE	Stores PNRs with a schedule change when no new seats can be assigned automatically.This requires manual action. It will display reservations with flights starting from 16 days after the change up to 30 days.
55	50	SEAT - SCHEDULE CHANGE - NEEDS MANUAL REAC * FLT 31 DAYS FROM CHANGE	Stores PNRs with a schedule change when no new seats can be assigned automatically.This requires manual action. It will display reservations with flights starting from 31 days after the change and ahead.
55	99	SEAT - SCHEDULE CHANGE - NEEDS MANUAL REAC * UNDEFINED	Stores PNRs with a schedule change when no new seats can be assigned automatically.This requires manual action. It will display reservations with flights starting from 31 days after the change and ahead.
60		PARTIAL ISSUES	Stores PNR with pending unticketed passengers.Controls unticketed passageners in PNR with both ticketed and unticketed passengers.
61		7T - AGENCY	Store PNRs manually ticketed by travel agents and added in field 7. (Exclusive for HDQ)
62		7T - HOST	Store PNRs manually ticketed in the host and added in field 7. (Exclusive for HDQ)
63	1	PNR INTEGRITY (ADT/CHD) * FLT 0 TO 2 DAYS	Stores PNRs with unticketed passengers or that require revalidation / exchange of adult passengers (ADT) and minors (CHD). Reservations with flights starting from the date of change up to 2 days after will be displayed
63	5	PNR INTEGRITY (ADT/CHD) * FLT 3 TO 5 DAYS	Stores PNRs with unticketed passengers or that require revalidation / exchange of adult passengers (ADT) and minors (CHD). Reservations with flights starting from 3 days after the change up to 5 days after will be displayed
63	10	PNR INTEGRITY (ADT/CHD) * FLT 6 TO 15 DAYS	Stores PNRs with unticketed passengers or that require revalidation / exchange of adult passengers (ADT) and minors (CHD). Reservations with flights starting from 6 days after the change up to 15 days after will be displayed
63	20	PNR INTEGRITY (ADT/CHD) * FLT 16 TO 30 DAYS	Stores PNRs with unticketed passengers or that require revalidation / exchange of adult passengers (ADT) and minors (CHD). Reservations with flights starting from 16 days after the change up to 30 days after will be displayed
63	99	PNR INTEGRITY (ADT/CHD) * MANUAL TRANSACTION	Stores PNRs with unticketed passengers or that require revalidation / exchange of adult passengers (ADT) and minors (CHD).Manual transaction
64	1	PNR INTEGRITY (ONLY INFANTS) * FLT 0 TO 2 DAYS	Stores PNRs with unticketed passengers or that require revalidation / exchange infant passengers(INF). Reservation with flight segments starting from the date of change up to 2 days later.
64	5	PNR INTEGRITY (ONLY INFANTS) * FLT 3 TO 5 DAYS	Stores PNRs with unticketed passengers or that require revalidation / exchange infant passengers(INF). Reservation with flight segments starting 3 days after the date of change up to 5 days later.
64	10	PNR INTEGRITY (ONLY INFANTS) * FLT 6 TO 15 DAYS	Stores PNRs with unticketed passengers or that require revalidation / exchange infant passengers(INF). Reservation with flight segments starting 6 days after the date of change up to 15 days later.
64	20	PNR INTEGRITY (ONLY INFANTS) * FLT 16 TO 30 DAYS	Stores PNRs with unticketed passengers or that require revalidation / exchange infant passengers(INF). Reservation with flight segments starting 16 days after the date of change up to 30 days later.
64	99	PNR INTEGRITY (ONLY INFANTS) * MANUAL TRANSACTION	Stores PNRs with unticketed passengers or that require revalidation / exchange infant passengers(INF) Manual
65		RP TO OTHER	Stores PNRs released to another airline,or travel agent.Allows controlling own PNRs release to others.
66		RP FROM OTHER	Stores PNRs releated from an agency to another agency or airline.
67		CLAIM	Stores PNRs transfered with CLAIM command by an agency
68		PNR FROM OTHER	Stores PNR that are transfered from the agent to the airline.
69		FAKE NAMES	Stores PNRS with FAKE NAMES
70		MANUAL TIME LIMIT INPUT	Stores PNRS that have a manual ticket time limit created in the HOST or Agencies(Only for HDQ)
71	1	FLT 0 TO 2 DAYS	Stores PNRs with no contacts. Reservation with flight segments starting from the date of change up to 2 days later.
	5	FLT 3 TO 5 DAYS	Stores PNRs with no contacts. Reservation with flight segments starting 3 days after the date of change up to 5 days later.
	10	FLT 6 TO 15 DAYS	Stores PNRs with no contacts. Reservation with flight segments starting 6 days after the date of change up to 15 days later.
	20	FLT 16 TO 30 DAYS	Stores PNRs with no contacts. Reservation with flight segments starting 16 days after the date of change up to 30 days later.
	99	MANUAL TRANSACTION	Stores PNRs with no contacts. Reservation with flight segments starting 31 days later.
75		PNR FROM INTERNET	Stores PNR generated on the web page
76		WEB ERROR	Stores PNRs generated on the WEB page (via Internet)with rejected sales when E-ticket is not issued but chage was made(Only for HDQ ).
80		AGENCY ISSUE MASK	PNRs which have been issued with forced masks outside the Host (Only for HDQ city).
81		HOST ISSUE MASK	PNRs which have been issued with forced masks in Host (Only for HDQ city).
82		AGENCY PRICE FORCED	Stores PNR with forced pricing outside the host.(only for HDQ city)
83		AGENCY ISSUE FORCED	Stores PNRs issued with forced pricing outside the host(only for HDQ city)
84		HOST PRICE FORCED	Stores PNR with forced pricing inside the host.(only for HDQ city)
85		HOST ISSUE FORCED	Stores PNRs issued with forced pricing outside the host(only for HDQ city)
86		AGENCY - ETKT REVALIDATED	Stores PNRS ticketed by travel agencies that have been revalidated.(Only for HDQ city)
87		HOST - ETKT REVALIDATED	Stores PNRs ticketed in the host that have been revalidated(Only for HDQ city)
88		EMOVE - PNR WITH ETKT REVALIDATED	Stores PNRS when EMOVE command is made(only for HDQ city)
89		ANCILLARY SERVICES - SERVICE COST OR TIME LIMIT REMOVED	Stores PNRs containing SSR or SEAT whose time limit or cost was manually removed.
90		UMNR - UNACCOMPANIED MINOR	Stores PNRS containing UMNR passenger type (UMNR unaccompanied minor)(Only for HDQ city)
95		CHECK IN - REJECTED PNRS	Stores PNRs which have NO SHOW in the check in process for not being able to cancel them.
101		OVER BOOKING (OB)	Stores overbooking messages generated manually by command (OB) by an agent on individual PNRs. This message also has a link on the reservation code to view it or retrieve it.
102		OVER BOOKING (OS)	Stores oversale messages generated manually by command (OS) by an agent on individual PNRs. This message also has a link on the reservation code to view it or retrieve it.
105		OVER BOOKING GROUPS	Stores oversale messages generated manually by command (KK) by an agent on group PNRs. This message also has a link on the reservation code to view it or retrieve it
115		WAIT LIST - VMWL	Stores messages that close, open or limit waiting lists by command (VMWL). Messages can be OPEN or CLOSE. An inventory link is generated to visualize or retrieve it.
120		ETKT INDICATOR MODIFIED (CHECK-IN)	Stores messages every time the ETKT indicator in the Control Panel (PC) is modified
125		LIMIT SALES - VMLS	Stores messages that close, open or set sales limits by command (VMLS) . Messages can be OPEN or the number of seats established by the limiter. An inventory link is generated to visualize or retrieve it.
130		REQUEST FLIGTH - VMRQ	Stores messages that set or remove flights on request by command (VMRQ). Messages can be ON or OFF and an inventory link is generated to visualize or retrieve
134		OVERSALE CLASS INHIBITED - VMIO	Store messages that set or remove class oversale inhibition by command. Messages can be ON or OFF and an inventory link is generated to visualize or retrieve
135		ACTIVATE CLASS - VMCL	Stores messages that close or open flight classes by command (VMCL) .Messages can be OPEN or CLOSE. An inventory link is generated to visualize or retrieve it.
136		CLASS OPENED BY TSO	Stores messages that automatically open flight classes, generated through the tables configuration of temporary opening of classes (TSO) in the flights. The messages generate an inventory link to visualize or retrieve it.
137		CLASS CLOSED BY TSC	Stores messages that automatically open flight classes, generated through the tables configuration of temporary closing of classes (TSO) in the flights. The messages generate an inventory link to visualize or retrieve it
140		FARE NOT FOUND	Stores messages of all fare quotes made by users unable to price the selected class.
142		CC/DC IGNORED CONTROL	Stores warning messages when a user ignores credit or debit card control while ticketing.
143		PU IC - FLT/DATE CONTROL IGNORED AT CHECK-IN	Stores warning messages when ignoring date and flight coupon during check-in process.
150		DUPE SUSPECT - AUT	Stores messages of automatic duplicities generated by overnight check process. The system checks all segments per day and places on queue all PNRs with the same last name in the same segment, on the same day. A link is generated with the reservation codes.
151		DUPE SUSPECT - MAN	Stores duplicity messages generated by DP command. This command works on a specific date and segment, generating a link with the reservation codes. Duplicity control is about the last name. Command: DP/DATE/ROUTE/FLIGHT NUMBER
152		DUPE - AUT	Stores messages of automatic duplicities generated by the overnight check process. The system checks all segments per day and places all pnrs on queues that have the same last name and name in the same segment, on the same day. A link is generated with the reservation codes. The control is more precise than queue 150. The PNRs that is placed on queued in 152 is not queued on 150.
153		DUPE - MAN	Stores duplicity messages generated by DP command. This command works on a specific date and segment, generating a link with the reservation codes. Duplicity control is about the last name. Command: DP/DATE/ROUTE/FLIGHT NUMBER This control is more precise than queue 150. The PNRs that is placed on queued in 152 is not queued on 150.
154		SUSPECT POSSIBLE CONNECTING FLIGHTS IN SEPARATE PNRS - AUT	Stores reservations messages that contain passengers with possible connections in other PNRs, and that were detected automatically by the system.
155		SUSPECT POSSIBLE CONNECTING FLIGHTS IN SEPARATE PNRS - MAN	Stores reservations messages that contain passengers with possible connections in other PNRs, and that were detected by a manual process performed by an airline user.
156		POSSIBLE CONNECTING FLIGHTS IN SEPARATE PNRS - AUT	Stores reservations messages that contain passengers with possible connections in other PNRs, and that were detected automatically by the user.
157		POSSIBLE CONNECTING FLIGHTS IN SEPARATE PNRS - MAN	Stores reservations messages that contain passengers with possible connections in other PNRs, and that were detected by a manual process performed by an airline user
160		ALERT AUTH. - 100%	Store flight occupancy messages when 100% is reached. This command works on the authorized flight including overbooking logic. It displays a message with the affected flight, date and time in which the sale that caused the message was generated and a link with the inventory of the flight.
162		ALERT AUTH. - 80%	Store flight occupancy messages when 80% is reached. This command works on the authorized flight including overbooking logic. It displays a message with the affected flight, date and time in which the sale that caused the message was generated and a link with the inventory of the flight.
164		ALERT AUTH. - 60%	Store flight occupancy messages when 60% is reached. This command works on the authorized flight including overbooking logic. It displays a message with the affected flight, date and time in which the sale that caused the message was generated and a link with the inventory of the flight.
170		CHECK IN FLT CLOSE AUT	Stores messages of those flights that have been closed automatically by the post check-in process.
171		MSG NOT PROCESSED	Stores messages from other GDSs by type B that for some reason were neither processed or placed on any of the following queues.
172		MSG REJECTS	Stores type B messages received from other GDSs that for some reason KIU could not process. It is an exclusive queue for the HDQ city. Only applies for those airlines that have contracts with other systems besides KIU, and that receive through messaging PNRs automatically.
173		MSG REJECTS ETKT	Reserved for messages
174		MSG PNR NAC	Type B messages that have been sent from KIU to other GDSs and that those GDSs have rejected for some reason.
175		MSG AVS SENT	Stores NAVS messages sent to other GDSs automatically. To place messages on this queue, the airline must have its flights published in another GDS.
176		MSG SSIM NAC	Stores Schedule messages that are sent from KIU to another GDS and that those are rejected for some reason
178		MSG ADL NO PROCESSED	All ADL messages that KIU does not process are placed on queue.
180		MP61 - ISSUED BY EXCHANGE	Stores messages from those credit E-MPDs generated as residual from an Exchange
181		MP61 - ISSUED	Stores messages of credit E-MPDs issued by a user, either through direct command or exchange of documents.
182		E-TICKET CHANGE STATUS	Stores E-ticket status change messages to OPEN FOR USE
183		PARTIAL REFUND/EXCHANGE	Stores partial refund documents.
184		E-TICKET UPGRADE / DOWNGRADE	Stores e-ticket class changes from one cabin to another. In this queue upgrade or downgrade transactions which have been applied with the ETUP command will be placed.
185		APPROVED FOPS - WITHOUT ISSUING	Stores messages generated when processing online validations (credit card, checking account, etc.) and for any error the e-ticket is not issued.
186		APPROVED FOPS - VOID OR REFUND	Type B messages that have been sent from KIU to other GDSs and rejected for some reason.
187		REFUND REQUEST	Stores messages generated by users who can not perform a refund when required.
188		ETKT - TAXES MODIFIED (TRAVEL AGENCY)	Stores messages informing PNRs data that contain Tickets issued with the indicator to modify the value of the taxes or fees (* TX). It is an exclusive queue for HDQ city. Only PNRs that contain Tickets issued by the travel agencies.
189		REFUND FOP CONTROL	Stores messages when the form of payment of a refund does not match the payment method of the original Ticket
190	1	OVERPE - DOCUMENT AFFECTED * EXCHANGE	Stores messages from PNRs with documents where the OVERPE command was included when an EXCHANGE was performed.
190	2	OVERPE - DOCUMENT AFFECTED * REVALIDATION	Stores messages from PNRs with documents where the OVERPE command was included when a REVALIDATION was performed.
190	3	OVERPE - DOCUMENT AFFECTED * REFUND	Stores messages from PNRs with documents where the OVERPE command was included when a REFUND was performed.

201+		FREE USAGE	AVAILABLE FOR ANY USE

Complete Queue Count

To access the full queue count, the command is as follows:

QCT/CTY

Description:

QCT/	Fixed command
CTY	City where the queue list is requested

Note:
The command can be made without adding the city, the result will be a queue count of the city where the agent is positioned.

Active Queues Count

If you want to access only the queues that have activity, and stop viewing the queues that are empty, the command is:

QC/

QUEUE	Queue number
ITEMS	Number of PNRS or stored messages
WORK	Number of PNR or messages in work
Description	Queue name

Options

Below are other options to display queues.

QC / 10	Display queue number 10 only
QC / 30 *	Displays only queue number 30 and the users signs working on it.

The display shows the signs of those who are working on that queue and the PNR code that has been retrieved at that moment.

Other options to display queue counts are:

QC/ALL	Shows all active queues
QC/ALL1	Shows all active queues 1

Contact view of a queue (PNR queues only)

To visualize contacts of a queue without accessing it, there is a command that displays a list of them. The command is:

Q/number*

Example

ITEM	Item number
CODE	Booking code with link to retrieve
##	Number of passengers in the PNR
TITULAR	First surname in the PNR
PHONE	First contact number in the pnr related to a specific location

Display queue elements with phone contacts from another city

You can get the same list but only retrieving the contacts of a specific city.

The command is the following:

Q/number*/CTY

Q/1*/SLA

Response:

The phone number of the requested city will be seen first and separated in brackets. Those PNRs that do not have telephones of the requested city will show the available ones with an arrow in front of them.

To retrieve the list of e-mail contacts. The command is the following:

Q/number *NET

Unlike the phone contact display, those who do not have mails in the contact field, will be marked with an asterisk.

Access a specific queue

To access a specific queue, you must enter the following command:

Q/1

Description

Q/	Fixed command
1	Queue number

Response

Redisplay within queues

To redisplay a PNR or a message while working on a queue, one of the following commands must be entered as appropriate:

*A Redisplays last  PNR

Place a PNR on a queue

To place a PNR on a queue the command must be performed with the PNR displayed as follows:

QP/210

Description

QP/	Fixed command
210	Queue number

Response:

OK

Send a PNR to another city

it is not necessary to specify the city code If the queue where the PNR will be sent is in the same city,otherwise it has to be specified.

Examlple

QP/COR21

To send a PNR to another city without displaying it the command is as follows:

QP/MQRYUU#COR2

Description

QP/	Fixed command
MQRYUU	Record locator
HDQ	3-letter city code
2	Queue number

Transfer a PNR to an agency

You can transfer a PNR from the airline to an agency. In order to do so, the owner of the PNR must be the agency (the PR). It will be placed on queue 68 of the agency. The command can de by done by displaying the PNR.

QP/-BUEA7760

BUEA7760 is the office of the agency where the PNR will be transferred.

If the PNR is not displayed on the screen, the command to be used is:

QP/OWWGTF#-BUEA7760

Description:

QP	Fixed command
OWWGTF	Record locator
BUEA7760	Agency office ID where PNR will be transferred.

Response:

OK (-BUEA7760)

Transfer a PNR from an agency to an airline queue.

You can transfer a PNR from an agency to an airline queue. To do this, the PNR must have at least one segment of the airline which will receive the PNR. It will be placed on queue 68 of the associated office where it was addressed. The command is (having the PNR displayed on the screen):

QP/-COR00XX4

COR00XX4 is the office of the agency where the PNR will be transferred.

If the PNR is not displayed on the screen, the command to be used is:

QP/OWWGTF#- COR00XX4

Description:

QP	Fixed command
OWWGTF	Record locator
COR00XX4	Agency office ID where PNR will be transferred.

System response

OK (-COR00XX4)

Place a PNR on queue and add a text

Place a PNR on a queue and add a text This field is optional. The maximum number of characters is 50.

The text must be entered after an asterisk as shown below:

QP / 210 * free text

The message entered will then be displayed on the top of the PNR sent to the queue.

Place a PNR on queue indicating time

A PNR can be placed on a queue indicating the number of hours ahead that the PNR is placed on queue.

This field is optional. The maximum number of hours to enter is 99.
The number of hours must be entered after the + symbol as shown below:

QP/210+2

In the previous example, the PNR displayed on the screen will be placed on queue 210 in the next 2 hours.

To this entry you can also add an optional message as shown below: QP / 210 + 2 * free text

Place a PNR on queue indicating day

A PNR can be placed on a queue indicating the date.

This field is optional.
The day must be entered after the + symbol as shown below

QP/210+24DEC

In the previous example the PNR displayed on screen will be placed on queue 210 on December 24th. An optional free text can also be added as shown next:

QP/210+24DEC*free text

Place a PNR on several queues at the same time

A PNR can be placed on several queues in the same transaction as displayed next:

QP/210/209

In this example above the PNR will be placed on both queue 210 and 209 with the same command.

Other combinations

Other possible combinations to place a PNR on queue are:

QP/209/210+8*free text

This entry will place the PNR on queues 209 and 210 8 hours after with the message added in the entry.

QP/209+27DEC*free text /HDQ210+2/-205

This entry will place the PNR on queue 209 on 27DEC and with the free text added,besides that PNR will also be placed on queue 210 in a two hours time and at last will also be placed on the own user queue 205. Hyphen before queue number means own queue.

Place PNRS from a flight list on a queue

In order to place PNRS from a flight list on queue you must perform the following command.

LD4900/26NOVAEP-Q201

This command places pnrs from passenger list of flight 4900/26NOV with boarding point AEP on Queue 201. You can also place pnrs from passengers lists with filters to a queue. The command is similar.

Example

LD4900/26NOVAEP/CY/T-Q201

PNR Lists can be place on a queue by applying the following filters: C (class), T (Ticketed passengers), V (Booked passengers), OF (by offices), K (confirmed Pnrs) and M (Pnrs subject to space) .

Example:

LD4176/20DECAEP/V-Q210

PNR lists can not be placed on a queue by applying the following extensions: FF (frequent passenger), ET (ticket numbers), F (Foid), R (return).

If you try to place a list with the previously mentioned extensions to queue, the system will respond: INVALID - OPTION NOT ALLOWED TO BE QUEUE PLACED

Place PNR from a flight list on another city queue

If the PNR from the list is in the same city or creation , it is not necessary add the city,otherwise it city should be clarified.

LD4900/26NOVAEP-QCOR201

Move or remove a PNR from a queue

To move or remove a PNR from a queue, one of the following commands can be used:

QR	Removes the PNR and displays the next one.
I	Move the PNR within the queue without removing it and displaying the next one.
E	Close the PNR and remove it. (Only PNRs)

Remove a PNR from multiple queues

To remove a PNR from multiple queues at once, the following command can be used:

QXP/ALL

To remove a PNR from multiple queues at once - without the pnr displayed

QXP/YHUTRT/ALL

QXP	Command
/	Slash
YHUTRT	PNR
/	Slash
ALL	All the queues

To remove a PNR from an specific queue - with the pnr displayed on the screen

QXP/AEP220

QXP	Command
/	Slash
AEP200	Queue number

To remove a PNR from an specific queue - without the pnr displayed

QX/YHUTRT/AEP220

QX	Command
/	Slash
YHUTRT	PNR
/	Slash
AEP220	Queue number

Other options

QR+20DEC	Removes the PNR and will place it again on queue on the indicated date.
QR+8	Removes PNR and will be placed again in the next 8 hours. 1 and 99 can be indicated in this command. An optional text can be added at the end of the entry.

Note:

Inside the messages queue you must ignore a PNR or message or close it if present if you want to retrieve a PNR.. Therefore, the I(ignore) command must be done twice, once for the PNR and once for the message.

Remove all PNRs from a queue

To remove all PNRs from a queue the following command must be used.

QZAP/201

Description:

QZAP	Fixed command
/	Slash
201	queue number

Note:

It is not necessary to add the city code when removing PNRs from the city where user is signed.

This command can only be done for PNR queues.

Move all PNRs from one queue to another

To move all PNRS from a queue to another the following command must be used.

QMOV/214/212

Description:

QMOVE	Fixed command
/	Slash
214	Queue number where PNRs are located
/	Slash
212	Queue number where PNRS will be moved.

Note

This command can only be done for PNR queues.

Move flight specific PNRS from one queue to another

QMOV/current queue/new queue+(flight)

Move PNRs with flight specific and date

QMOV/current queue/new queue+(flight)/date

Move PNRs with specified flights in a certain dates range.

QMOV/current queue/new queue+(flight)-(flight)/date-date

Move in ascending order

QMOV/current queue/new queue+(flight)-(flight)/date-date/A

Move in descending order

QMOV/current queue/new queue+(flight)-(flight)/date-date/D

Copy all PNRs from one queue to another.

To copy all PNRS from one queue to another the following command must be used.

QCOPY/BUE204/NQN210

Description:

QCOPY	Fixed command
/	Slash
BUE204	Queue number where PNRs are located
/	Slash
NQN210	Queue where PNRS will be copied.

Note:
When copying PNRs from the same city where the user is assigned it is not necessary to enter the city code.

Example:

QCOPY/204/210

This command can only be done for PNR queues.

Copy flight specific PNRS from one queue to another

QCOPY/current queue/new queue+(flight)

Copy PNRs with flight specific and date

QCOPY/current queue/new queue+(flight)/date

Copy PNRs with specified flights in a certain dates range.

QCOPY/current queue/new queue+(flight)-(flight)/date-date

Copy in ascending order

QCOPY/current queue/new queue+(flight)-(flight)/date-date/A

Copy in descending order

QCOPY/current queue/new queue+(flight)-(flight)/date-date/D

Exit queues

When working on queues you can exit with the following command.

QXI Exits the queue and ignores changes if any.
QXE Exits the queue and saves the changes if any (only for PNRs).
QXR Exits the queue and removes the last displayed PNR.

Work a PNR on queues

PNRs can be worked on queues normally, it is only necessary to take into account that, when ending transaction with the E command it will be removed from the queue and the next will be displayed.
You can end transaction with ER (close and retrieve) if you want to keep it on queues, and then ignore it (I) to move on to the next one.

Display queue count with special permission

To visualize the queue accounts to which you have special permission, the assigned user must execute the command:

QQC/CTY

QQC/	Fixed command
CTY	Assigned location to which you have access.

Example:

Other options:

QC/ALL

Display a specified queue.

Example:

QQC/HDQ183

QQ/HDQ183* Displays the items that are placed on a specific queue.

Example:

Access a specific queue with special permission

The command to access a specific queue with special permission is:

QQ/HDQ183

Description:

QQ/	Fixed command
HDQ183	City and queue number with permission

Display the queues history within a PNR

*QH

This command allows you to see all the PNR transactions that have occurred on the different queues. Basically, the possible transactions are the inputs and outputs, manually or automatically.
Keyword QHSHOW allows to view all the transactions that the PNR has had on all the queues of all the companies that have had access.

Example;

Note:
When the PNR is automatically placed on queues by system action the SYS sign will be recorded instead of the agent´s.

Queues that generate information in the * QH are the following:

10 WAIT LIST CONFIRMED
20 PNR – REQUIRED
25 PNR – CONFIRMED
30 SCHEDULE CHANGE
40 GROUPS – REQUIRED
45 GROUPS – CONFIRMED
46 SSR - REQUIRED
47 SSR - CONFIRMED
48 SSR - REJECTED
60 PARTIAL ISSUES
61 7T – AGENCY
62 7T – HOST
65 RP TO OTHER
70 MANUAL TIME LIMIT INPUT
80 AGENCY ISSUE MASK
82 AGENCY PRICE FORCED
83 AGENCY ISSUE FORCED
84 HOST PRICE FORCED
85 HOST ISSUE FORCED
86 AGENCY ETKT REVALIDATED
87 HOST ETKT REVALIDATED

PNRs and messages will remain on queues for a period of 7 days, counting from placement date - Once this period has elapsed, the PNRs and / or messages, if not removed they will be automatically removed from the queues without leaving a record in the history.

Queues

Queues

List of pre-established queues

Complete Queue Count

Active Queues Count

Contact view of a queue (PNR queues only)

Display queue elements with phone contacts from another city

Access a specific queue

Redisplay within queues

Place a PNR on a queue

Send a PNR to another city

Transfer a PNR to an agency

Transfer a PNR from an agency to an airline queue.

Place a PNR on queue and add a text

Place a PNR on queue indicating time

Place a PNR on queue indicating day

Place a PNR on several queues at the same time

Other combinations

Place PNRS from a flight list on a queue

Place PNR from a flight list on another city queue

Move or remove a PNR from a queue

Remove a PNR from multiple queues

Other options

Remove all PNRs from a queue

Move all PNRs from one queue to another

Move flight specific PNRS from one queue to another

Move PNRs with flight specific and date

Move PNRs with specified flights in a certain dates range.

Move in ascending order

Move in descending order

Copy all PNRs from one queue to another.

Copy flight specific PNRS from one queue to another

Copy PNRs with flight specific and date

Copy PNRs with specified flights in a certain dates range.

Copy in ascending order

Copy in descending order

Exit queues

Work a PNR on queues

Display queue count with special permission

Access a specific queue with special permission

Display the queues history within a PNR

Visualize the active PNR queues

Related pages