I've found this very old file on PMS that had referred to a patch problem Patch 12535 at 24.25. Some of the details listed below will apply to you.
* Define LD 17 parameters ..
PMSI
MANU PMS1
PMCR 250
PORT 14
XTMR 4
XNUM 1
PMIN NO
PTMR 0
* Set up a tty with user PMS and BGD (speed 1200 BPS)
* Define LD95 parameters for the customer and then using a PMS simulator -
try and check in a room using the check in with name command ...
<STX> SE CP 2000 'Guest Name' CH IN <ETX> [BCC]
Expected Results:
Meridian accepts the input and returns an ACK if BCC correct.
Actual Results:
Depending on the length of the name - the Meridian will either return nothing or the 'NAME BIG' message. At this point - the Meridian PMS port will not repond to further input until the system is manually initialised.
The following is a capture of a failed check in with name ...
PMS Log - file started - 17/09/99 9:37:42
Key : -> Data sent from Simulator, <- Data received by Simulator
-> <STX> SE ST 2000 CH OU <ETX> 1
<- <ACK>
-> <STX> SE ST 2000 CH IN <ETX> 1C
<- <ACK>
-> <STX> SE ST 2000 CH OU <ETX> 1
<- <ACK>
-> <STX> SE CP 2000 'Greg Couzin from Ctas' CH IN <ETX> 8
<- <STX> NAME BIG <ETX> 48
-> <STX> SE CP 2000 'Greg Couzin from Ctas' CH IN <ETX> 8
-> <STX> SE CP 2000 'Greg Couzin from Ctas' CH IN <ETX> 8
Manual INI is now required to restore the PMS port to service.
Impact of problem
PMS interface to M1 effectively useless to the customer.
Workaround
There are two options available in working around the problem.
1) Using a 2 port SDI card - QPC139 - set the parity to ODD. This can be achieved by switches D22 or D31 (depending on which port you are using). Note that these switch settings are not documented in the NTPs - contact the originator for details.
OR
2) Leave the switch settings on the QPC139 as standard and in service the following work around patch in procedure CPND-START-NAME ...
PROCEDURE CPND_START_NAME;
BEGIN
% check for CPnd feature, make sure room is specified
IF ^BGW_CPND_MODE:BG_WPTR | (BGW_DN:BG_WPTR = 0) THEN
BEGIN
FLAG_ERROR;
RETURN;
END
IF BGW_REQUEST:BG_WPTR ^= .REQU_SET THEN
BEGIN
% name string input is not supported for print command
FLAG_ERROR;
RETURN;
END
% check if a name is entered
IF BG_XDUP[.MNEM_CPND_NA]:BG_UPTR = .FLAG_ON THEN
BEGIN
FLAG_MSG(.BMSG_NAMEDUP);
RETURN;
END
%|Patch Number : patch5
%|Patch Title : Remove test for MLIO pkg and setting of ALL_8_BITS
%|Global : BG_WORK_MOD
%|Local : CPND_START_NAME
%|Segment : bgcomxxx
% if Multi-Language-TTY-Input-Output package is equipped
% consider the eighth bit of the input character to be valid.
% Patch begin
%IF ^SERV_PACK_RESTR[.ML_TTY_IO_PKG] THEN
% ALL_8_BITS := .TRUE;
% Patch end
ALLOW_LCASE[SESS_IDX]:=.TRUE; % allow lower-case characters in name
BG_CPND_IP_CNT:BG_UPTR := 0; % init the char count
BG_CPND_NAME:BG_UPTR := .TRUE; % set the name string flag
END % procedure cpnd_start_name
Frequency: Always
Keywords
PMS MLIO
Other comments
This problem is evident on release 24 - the check for MLIO package
(.ML_TTY_IO_PKG) was introduced in procedure CPND_START_NAME in release
24.
Release 23.37 was tested in the lab and did not exhibit the problem.
A check in without name is OK
Firebird Scrambler
Nortel & Avaya Meridian 1 / Succession & BCM / Norstar Programmer
Website =
linkedin
