#+VER0.0.0+
# Please NOTE: Do not modify the first line in this file.
# The customer may choose to make a copy of this file
# and strip out all comments or parameters which use
# default values or that do not apply to his
# configuration. The file should be named CDIFILE.xxx
# where xxx = 000 (default) or any terminal number. It
# should reside in the ADX_UDT1 directory of the Store
# Controller which serves as the Master File Server.
# This file should be a local file. It should not be
# a 4690 distributed file.
# NOTE: Do not change the format tag names (the names
# within the first 8 characters of each line)
# Changes:
# 1/29/02 Initial documentation of the latest CDIFILE
# formats. LTB
# 4/19/02 Clarified description of Dynakey and CID
# definition parms, added definition of
# "wtdispno" parm and differences in defining
# 7452-35xx vs 4xxx models. LTB
# 4/24/02 Clarified the use of blank vs "" values for
# parm values. Modified sample accordingly. LTB
# 7/11/06 Removed pa_com parm which was incorrectly
# documented. This parm is not implemented LTB
#
# --------------------------------------------------------
# Country Code
#
# Use the same country code setting specified for DOS
#
country="01"
#
# --------------------------------------------------------
#
# Date Format
#
# Choose one of the following:
# "1" m/d/y "2" d/m/y
# "3" m.d.y "4" d.m.y
#
date fmt="1"
# --------------------------------------------------------
# Print and Display Case Options
#
# These options apply to the printer and/or to the 2x20
# display (or the DYNAKEY 2x20 display area)
#
# "0" all uppercase
# "1" print mixed, display uppercase
# "2" display mixed, print uppercase
# "3" print & display mixed
#
case fmt="3"
# --------------------------------------------------------
# --------------------------------------------------------
#
# How to Set Up Parms for either VGA or Dynakey Displays
#
# QCONNECT provides two alternative formats to display
# VGA screen outputs. One format uses a DYNAKEY-style
# layout while the other requires the IBM Full Screen
# application and emulates its operation.
#
# To attach a single VGA screen when using a Full Screen
# IBM application:
# 1. Define the "vdisp" option (VDISPLAY or VDISPLAY2)
# w/System Display (options 10,20,30 or 01,02,03)
# 2. Define the dx_2x20 display options where x = 1,2
# Make sure the 2x20 placement specification is
# compatible with the Full Screen application
# 3. Set all other Dynakey-style definitions to null ("")
# 4. Set the "dynakey" option to "0"
#
#
# To attach either a DYNAKEY or VGA screen when using a
# non-Full Screen IBM application:
# 1. Disable the "vdisp" option ("00")
# 2. Define the appropriate Dynakey-style options. Begin
# by using the sample CDIFILE and make changes as
# needed. Set screen 0 Dynakey-style options as
# appropriate.
# 3. Set screen 1 Dynakey-style options to null ("")
# 4. If attaching a Dynakey screen, set the "dynakey"
# option to "1"; otherwise, set to "0"
#
# To attach both a DYNAKEY and a VGA display when using a
# Full Screen IBM application:
#
# Note: In this case, the DYNAKEY screen is "\w0" and the
# VGA screen is "\w1". The DYNAKEY screen will use
# a Dynakey-style format. The VGA screen will use
# the Full Screen format.
# 1. Define the "vdisp" option (VDISPLAY or VDISPLAY2)
# w/o System Display (options 40,50,60 or 04,05,06)
# 2. Define the dx_2x20 display options where x = 1,2
# Make sure the 2x20 placement specification is
# compatible with the Full Screen Application
# 3. Set all other Screen 0 definitions as appropriate
# 4. Set all Screen 1 definitions to null ("")
# 5. Set the "dynakey" option to "1"
#
# To attach both a DYNAKEY and a VGA display when using a
# non-Full Screen IBM application:
#
# Note: In this case, the DYNAKEY screen is "\w0" and the
# VGA screen is "\w1". Both screens will use a
# Dynakey-style format. The Dynakey screen will be
# the system display.
#
# 1. Disable the "vdisp" option ("00")
# 2. Define the dx_2x20 display options where x = 1,2
# 3. Set to null ("") the dx2x20 options where x = 3,4
# 4. Define all other Screen 0 definitions as appropriate
# 5. Define all other Screen 1 definitions as appropriate
# 6. Set the "dynakey" option to "1"
#
#
# For all of the above cases, you should also define a
# screen file (option "scrfile"). Examine the sample file
# you were sent. It uses options that mirror the Dynakey-
# style definitions. This file paints the screen only on
# bootup. You may be puzzled to see the "\w0" or "\w1" at
# the end of blank or mostly-blank lines in the file. This
# command is used as a NO OP (do nothing) command. It is
# used at the end of the line to assure that all the
# preceding blanks are not eliminated by your text editor.
#
# NOTE: The NCR 7452-3500 requires a DYNAKEY card (and the
# DYNAKEY to be connected to the DYNAKEY card interface)
# if you want to use a Customer Information Display. The
# 3500 motherboard DYNAKEY interface will not function
# properly in this environment (will not switch the
# display operation from DYNAKEY to the CRT VGA port and
# back). If you do not use a CID, you can attach the
# DYNAKEY to the motherboard interface. In this setup,
# any data written to the CID will go instead to the
# DYNAKEY where it will be displayed. In order to
# prevent writing CID data to the dynakey screen, you
# must define a CDIFILE similar to this sample (no
# "W1\xxxxxxx" definitions should be made) for that
# terminal. In addition, to prevent the WEIGHT field
# from being improperly displayed on the DYNAKEY screen,
# you should also define "wtdispno=1".
#
# If you are not using a CID with any NCR terminals that
# use a DYNAKEY card interface or for NCR 7452-4xxx models
# (or higher), data written to the VGA port is not written
# to the DYNAKEY screen. In this event, you can define a
# CDIFILE as if a CID screen were attached and would see
# no improper displays of data. This would allow a consistent
# CDIFILE to be used throughout the store whether all terminals
# were equipped with CID screens or not.
#
#
# Set the following parm to "1" if you have a Dynakey
# installed and/or you want to display dynakey prompts
# on the screen; "0", if not. If this parm is set on, you
# must also define additional Dynakey-style options. Make
# sure the DYNAKEY option in KEYMAP.xxx is removed, if
# present.
#
dynakey="1"
# --------------------------------------------------------
# Full Screen Video Options
#
# If you are using an application which requires support
# for FULL SCREEN VIDEO (drivers VDISPLAY: or VDISPLAY2:),
# you must activate the "xy" parameters as follows:
#
# x = 0 (VDISPLAY not used)
# = 1 (VDISPLAY as System Display in 12x40 mode)
# = 2 (VDISPLAY as System Display in 16x60 mode)
# = 3 (VDISPLAY as System Display in 25x80 mode)
# = 4 (VDISPLAY not used)
# = 5 (VDISPLAY as Customer Display in 12x40 mode)
# = 6 (VDISPLAY as Customer Display in 16x60 mode)
# = 7 (VDISPLAY as Customer Display in 25x80 mode)
# y = 0 (VDISPLAY2 not used)
# = 1 (VDISPLAY2 as System Display in 12x40 mode)
# = 2 (VDISPLAY2 as System Display in 16x60 mode)
# = 3 (VDISPLAY2 as System Display in 25x80 mode)
# = 4 (VDISPLAY not used)
# = 5 (VDISPLAY2 as Customer Display in 12x40 mode)
# = 6 (VDISPLAY2 as Customer Display in 16x60 mode)
# = 7 (VDISPLAY2 as Customer Display in 25x80 mode)
#
# Note: "System Display" means you are displaying system
# messages. "Customer display" means you are not.
#
# Important: If you choose a "system display" option, you
# must also define the attributes for "d1_2x20" and
# "d2x20". The position you choose for the 2x20 (system)
# display should be compatible with the format of the
# screen used by the Full Screen IBM application.
#
# If you have both a Dynakey and a VGA screen installed,
# you can specify the VGA to use either VDISPLAY: or
# VDISPLAY2: In this case, specify the Customer Display
# option. The DYNAKEY screen should use the Dynakey-
# style, not the Full Screen (VDISPLAY) definitions.
#
# The following example turns off both VDISPLAY and
# VDISPLAY2 definitions (x=0 and y=0):
#
vdisp="00"
#
# --------------------------------------------------------
# DYNAKEY-style Format Display Options
#
# The following command strings are used to select the
# display and specify the format of either a DYNAKEY or a
# VGA screen when the application does not support Full
# Screen operation or the user prefers the Dynakey-style
# display. If "vdisp" is enabled, unneeded Dynakey-style
# options should be set to null ("")
# Various types of information are displayed by the
# QCONNECT display support as follows:
# - 2x20 operator display lines 1 and 2 as written
# by the 4690 application program
# - Indicators representing the 4 LED lights on the
# 4690 keyboard.
# - receipt print lines printed to the display(s)
# - receipt print lines scrolled on the display(s)
# - the balance due amount as written to the TOTAL1:
# driver.
# Data to be displayed in each of the above situations
# is defined by the following controls. These parms
# specify the screen selected, the write location, the
# font, and colors. See definitions below:
#
# \Wx\Lrrcc\Chwbf
#
# where:
#
# \Wx display to screen x where x = 0 for screen 0
# or x = 1 for screen 1
# Note: If you have two screens attached,
# screen 0 always refers to the DYNAKEY
# screen.
# \Lrrcc screen location row rr, col cc
# \Chwbf display attributes
# h = 1, 2, or 3; single, double, triple high
# w = 1 or 2; single or double wide
# Note: Some font combinations may be
# invalid
# bf (background/foreground) colors:
# 0-black 1-blue 2-grn 3-cyan
# 4-red 5-magenta 6-brown 7-white
# 8-gray 9-lt blue A-lime B-lt cyan
# C-pink D-purple E-yellow F-br white
# \Srrccssdd - Scroll command
# rr=row of upper left corner of scroll area
# cc=col of upper left corner of scroll area
# ss=row of lower right corner of scroll area
# dd=col of lower right corner of scroll area
#
# Note: No data following the "=" indicates NOT USED.
# This forces a disabling of this parameter. If
# the parm is simply omitted, a default value
# is sometimes used, giving unpredictable results.
#
# Note: Location attributes always refer to the upper
# left corner. For example, an area with 3 high
# font attribute would be defined using the top
# row of the line to be displayed. The exception
# to this is the lower right attribute for the
# scroll area. In this case the absolute lower
# right line and column are required.
#
# Note: The attribute definitions assume a 25x80
# character screen.
#
# Note: If a Dynakey interface card is installed in
# the terminal, whether a Dynakey screen is
# attached or not, the Dynakey card will always
# be addressed as "W0".
#
# The following example assumes a single attached
# Dynakey screen.
#
# --------------------------------------------------------
# The following attributes apply to screen 0 (DYNAKEY)
# --------------------------------------------------------
# Attributes for 2x20 line 1 on screen 0
# Default is "\W0\L0301\C220F"
d1_2x20="\W0\L0301\C220F"
#
# Attributes for 2x20 line 2 on screen 0
# Default is "\W0\L0501\C220F"
d2_2x20="\W0\L0501\C220F"
#
# Attributes for bottom line of screen 0 scroll area
# The previous "current line" will be written to here
# Default is "\W0\L2302\C110F"
d5_scrl="\W0\L2302\C110F"
#
# Attributes to define upper left and lower right
# corners of the Scroll area for screen 0
# Note: Lower right and bottom line attributes must be
# compatible.
# Default is "\W0\S09022339"
d6_scrl="\W0\S09022339"
#
# Attributes for last line printed to screen 0.
# Default is "\W0\L2302\C110F"
d9_curr="\W0\L2402\C110F"
#
# -------------------------------------------------------
# The following attributes apply to screen 1 - Customer
# Information Display (CID). Use attributes for
# screen 0 as a model.
# -------------------------------------------------------
# Attributes for 2x20 line 1 on screen 1
# Default is ""
d3_2x20=""
#
# Attributes for 2x20 line 2 on screen 1
# Default is ""
d4_2x20=""
#
# Attributes for bottom line of screen 1's scroll area
# The previous "current line" will be written to here
# Default is "\W1\L1801\C221F"
d7_scrl=""
#
# Attributes to define upper left and lower right
# corners of the Scroll area for screen 1
# Note: Lower right and bottom line attributes must be
# compatible.
# Default is "\W1\S04011980"
d8_scrl=""
#
#
# Attributes for last line printed to screen 1.
# Default is "\W1\L2001\C32F0"
d0_curr=""
#
# Attributes for balance due from TOTAL1: driver
# Since the CID screen is not defined for this
# example, the "baldue" parm is commented out to
# allow you to see an example of how to specify
# this parameter
# Default is "\W1\L2351\C322F"
baldue=""
#
#
# -----------------------------------------------------------
# Turn off Display of Weight on Customer Information Display
# -----------------------------------------------------------
# Set wtdispno=1 under the following conditions:
# 1. You do not want to display the weight field
# on the Customer Information Display
# 2. You are using an NCR 7452-4xxx terminal with
# ONLY a dynakey attached to the Motherboard
# DYNAKEY connector (no Dynakey card installed)
# Default is "0"
wtdispno=
#
# --------------------------------------------------------
# System Status Lights for the Dynakey Screen (screen 0)
# --------------------------------------------------------
# Attributes/text for system status indicator 1 on
s1on="\W0\L0601\C120EWait"
# Attributes/text for system status indicator 1 off
# (text is normally blanks)
s5off="\W0\L0601\C120E "
# Attributes/text for system status indicator 2 on
s2on="\W0\L0612\C120EOffline"
# Attributes/text for system status indicator 2 off
# (text is normally blanks)
s6off= "\W0\L0612\C120E "
# Attributes/text for system status indicator 3 on
s3on="\W0\L0628\C120EMsg"
# Attributes/text for system status indicator 3 off
# (text is normally blanks)
s7off="\W0\L0628\C120E "
# Attributes/text for system status indicator 4 on
s4on="\W0\L0634\C120EMgr"
# Attributes/text for system status indicator 4 off
# (text is normally blanks)
s8off="\W0\L0634\C120E "
#
# --------------------------------------------------------
# Define phrases to be suppressed from the scroll area of
# the display that uses the Dynakey-style display options.
# Up to 50 phrases may be suppressed. If the quoted
# phrase is contained within a print line on the customer
# receipt, the line will not be displayed in the scroll
# area of the display.
# Example:
# x01cdtxt="FS CHG"
# This command will suppress display of any print line
# which contains the phrase: FS CHG
#
# Note: These commands are ignored on any screen that is
# controlled by the "vdisp" option and uses an IBM Full
# Screen application.
#
# Note also that the phrase used to suppress a print line is case
# sensitive. The phrases can be listed in any order.
x00cdtxt=""
x01cdtxt=""
x02cdtxt=""
# all the way through:
x49cdtxt=""
# --------------------------------------------------------
#
# Name of screen init file in the store controller.
# This file must be kept in the ADX_UDT1 directory.
# The file is just an ASCII text file with embedded
# screen control info similar to that above. This
# name must match the file name used on the controller.
# This file can initialize up to 2 display screens.
# It can be used to initialize either a DYNAKEY or
# VGA screen (or both).
#
scrfile="qdyna.scr"
#
# --------------------------------------------------------
#
# Number of seconds after the most recent keystroke
# that the screen saver is invoked on both the
# Customer Information (CID) and DYNAKEY displays.
#
# "-1", "0", or "" turns off the screen saver function.
# Any positive value specifies the number of seconds
# until the screen saver is activated (up to a maximum
# value of 600).
#
# Default is "0"
sv_scrn="300"
#
# --------------------------------------------------------
# --------------------------------------------------------
# Define Keyboard
#
# Specify "4690" if an IBM 4690 50-key keyboard is in use.
# Otherwise, specify ""
#
# Default is ""
keyboard=""
#
# --------------------------------------------------------
# --------------------------------------------------------
# Set Printer Type
#
# Possible printer types are:
# "4610", "NAT4610", "7193", "7152", "7156", and
# "7162"
#
# Note: "4610" ==> 4610 using Mod 3/4 Emulation Mode
# (See also ej4610 below if using this mode)
# "NAT4610" ==> 4610 using Native Mode
# "7156" ==> if using 7158 in 7156 Emulation
# Mode
# Note: Specify "" if using a real IBM Model 3 or 4
#
printer="7156"
#
# --------------------------------------------------------
# Set Document Insert Compressed Printing Option
#
# Setting this option on enables compressed printing
# in the Document Insert station for 7152, 7156, and
# 7158 printers. This parameter is ignored for all
# other printer types.
#
# "0" = off
# "1" = on
#
cpressed="0"
#
# --------------------------------------------------------
# Document Insert Automatic Open Flag
#
# Flag should be "1" only if the following two
# conditions exist:
# 1. Either a 7152 or 7162 printer is connected
# 2. The General Sales Application is running
#
# This causes the DI station throat to release the
# document some 3 seconds after printing is complete.
# This provides a way to release the document when a
# hardware button is not available.
#
# "0" = Disable DI Automatic Open
# "1" = Enable DI Automatic Open
#
slipopen="0"
#
# --------------------------------------------------------
# Electronic Journal Status for 4610 Printer
#
# Note: Applies only to Mod 3/4 Emulation Mode.
# This option is ignored for 4610 Native Mode
# or for any other printer type.
#
# When this option is enabled, any data written to the
# Summary Journal will be saved in the 4610 printer
# memory for later retrieval.
#
# "0" = Disable Electronic Journal
# "1" = Full Electronic Journal Operation
# "2" = Activate Electronic Journal only when offline.
#
ej4610="0"
#
# --------------------------------------------------------
# Set the left margin position for the 4610 DI
#
# Note: Applies only to Native 4610 printer mode.
# This option is ignored for 4610 mod 3/4 mode
# or for any other printer type.
#
# This value is the number of dots to move over before
# beginning the Document Insert print line.
#
# 1 inch = 75 dots.
# Maximum value is 474 dots.
lmargin="75"
#
# --------------------------------------------------------
# Additional Customer Receipt Cut commands
#
# QCONNECT normally implements Mod 3/4 emulation. This means
# that the printer will execute valid CR cut commands
# issued by the IBM application. If the user wishes to
# to do additional CR cuts not implemented by the
# application, the following commands can be used.
#
# If the customer application supports only a Mod 2
# printer, these commands can be used to cut the receipt
# tape.
#
# Up to 10 tags can be created. "aycut" can be used to
# identify text which will trigger a cut. "lyfeed" is
# used to specify how many line feeds prior to (-) a cut
# or following (+) a cut (where ?y? has a value between 0
# and 9 inclusive.
# Example #1:
# (To set the printer to cut 5 line feeds after
# it prints the text "Thanks for shopping here")
#
# a0cut="Thanks for shopping here"
# l0feed="-5"
#
# Example #2:
# (To set the printer to sequentially print the
# text "Thanks for shopping here", issue the CR
# cut, then issue 5 line feeds)
#
# a0cut="Thanks for shopping here"
# l0feed="+5"
#
a0cut=""
l0feed=""
#
a1cut=""
l1feed=""
# Up through:
a9cut=""
l9feed=""
#
# --------------------------------------------------------
# --------------------------------------------------------
# Discussion of COM port useage: This file provides much
# flexibility in COM port definition. Generally, if the
# application opens COM1 (port 1) or COM2 (port 2), there
# is no cdi file definition required. QCONNECT simply
# passes on the request. However, see the "plourde" parm
# for information on the one case that the serial OPEN
# parms can be overridden or COM port behavior modified.
#
# Other devices: scanner (sscnport), coin dispenser
# (dispense), serial 2x20 (2x20ser), and printer
# (ptprintr). Each of the devices to be used must have a
# port defined (1-5).
#
# --------------------------------------------------------
# Match Application COM port to Physical COM port
#
# IBM applications specify COM ports 1-4. These
# ports can be mapped to any of 5 possible physical
# COM ports.
# #
# To map the IBM application's use of COM4 to a
# physical COM3, add the following statement:
# c4tohdwr="3"
#
# Default value is ""
c1tohdwr=""
c2tohdwr=""
c3tohdwr=""
c4tohdwr=""
#
# --------------------------------------------------------
# Change COM Port IRQs
#
# Default IRQs for COM1 - COM5 are "4", "3", "5", "11"
# and "12", respectively.
#
# To change any COM port to use a different IRQ, modify
# one of the following parameters. (Note: This is a
# software-only change. The COM port hardware must
# match this setting)
#
# Example:
# To change COM4 to use interrupt 9, change the
# following statement from "11" to "9":
#
# i4comirq="9"
#
i1comirq="4"
i2comirq="3"
i3comirq="5"
i4comirq="11"
i5comirq="12"
#
# Set IO Addresses for COM ports
#
# If no values are entered below, the following default
# values will be used for COM1 - COM5:
# 3F8, 2F8, 3E8, 2E8, and 278
#
# To change a COM port to use a different IO Address,
# modify one of the following parameters. (Note: This
# is a software-only change. The COM port must match
# this setting)
#
# Example:
# (To set COM4 to the normal COM5 setting)
# p4pccom="278"
#
p1pccom=""
p2pccom=""
p3pccom=""
p4pccom=""
p5pccom=""
#
#---------------------------------------------------------
# Set PLOURDE pinpad flag
#
# Note: This bit changes the behavior of the COM1 port
# serial driver. When set to a non-zero value, it causes
# the COM1 port driver to indicate data available only
# when a complete input message has been received.
#
# This eliminates problems with an application that
# cannot properly handle partial messages from the COM1
# port. Normally, this is used for certain pin pad
# devices. Valid parameter values are:
#
# plourde="0" -- COM1 behaves as a normal serial port
# (default)
#
# plourde="1" -- Only an appl read of complete pin pad
# messages is allowed. Serial port parms
# are set to (overrides value set by the
#????????????????????? application):
#
# 4800,8,2,NONE
#
# Normally, this option is used to
# simulate the IBM "pigtail" serial-to-
# RS485 device connection
#
# plourde="2" -- Only an appl read of complete pin pad
# messages is allowed. The application
#????????????????????? sets the serial port baud rate and
# ??????????????? ?????other serial communications parms on
#????????????????????? OPEN.
#
plourde="0"
#
# --------------------------------------------------------
# Specify Printer COM Port
#
# Possible values are: "1"-"5"
#
ptprintr="4"
# --------------------------------------------------------
# Specify Coin Dispenser COM port
#
# Possible values are: "1"-"5"; "" ==> not used.
#
dispense=""
#
# --------------------------------------------------------
# Specify Scanner/Scale COM port
#
# Possible values are: "1"-"5"; "" ==> not used.
sscnport=""
#
# --------------------------------------------------------
# Specify Serial 2x20 Display COM port
#
# Possible values are: "1"-"5"; "" ==> not used.
2x20ser=""
#
# --------------------------------------------------------
# CMOS Driver - always set on!
cmosdrvr="1"
#
# --------------------------------------------------------
# Ramdisk configuration settings
#
# ?dsksize = (RAM disk size in KB)/32
# ?secdir = (number of files)/16
# where '?' can be 'X' or 'Y' for the two ram disks
# or 'L' for the ramdisk used to hold List Files
# for use in offline mode
#
# Note: Results should always be rounded up
#
# Example:
# To create a 100K X: drive with 21 files loaded into
# it, parms should be:
# 100/32 = 4 ==> xdsksize="4"
# 21/16 = 2 ==> xsecdir="2"
#
xdsksize="0"
xsecdir="0"
#
ydsksize="0"
ysecdir="0"
#
ldsksize="0"
lsecdir="0"
#
# --------------------------------------------------------
#
# List File names to be loaded into RAM for offline use.
#
# Note: The following files will be loaded into
# RAM only if the "ldsksize" or "lsecdir" parms
# are non-zero. The file names listed below
# will be loaded from the ADX_UDT1 directory
# of the Store Controller. Total List File
# sizes and counts are used to set the
# "ldsksize" and "lsecdir" parms above.
#
listfile="bakery.lst"
listfile="salads.lst"
listfile="desserts.lst"
listfile="cigarett.lst"
listfile="dairy.lst"
listfile="meat.lst"
#
# --------------------------------------------------------
# Change System Message Text
#
# This function is designed to allow for language
# translation. It can also be used to modify any of
# the listed messages for clarity.
#
# The first 4 characters of most messages below must be
# left intact. Note that each line is set up to display
# on a 2 x 20 display. Each line should be seen as 2
# 20-character segments. Assure that a word does not
# span the 20th and 21st character positions.
#
#Line 1 Line 2
#
w00="W003 CONTROLLER OFF LOOP "
w01="W004 CONTROLLER DOESNOT RESPOND "
w02="W006 TERMINAL ~~~ IS ALREADY IN USE "
w03="W012 TERMINAL NUMBER = ~~~ "
w04="Z001 ENTER TERMINAL,KEY S2 "
w05="W008 PROGRAM IS BEING LOADED... "
w06="W009 DATE FORMAT IS "
w07="W010 DATE/TIME NOT CORRECT. RE-ENTER "
w08="W203 SET DATE/TIME ONLY WHEN OFFLINE "
w09="N300 DOSFREE=~~~~~~~EMU STACK=^^^^^^^ "
w10="W200 FUNCTION NUMBERNOT VALID. RETRY "
w11="W205 STORAGE RETENTION ENABLED "
w12="W206 STORAGE RETENTION DISABLED "
w13="W321 PROCESSING WAIT FOR PROMPT "
w14="W000 NO MESSAGE PENDING "
w15="W013 TERM NUMBER NOTCORRECT. RE-ENTER "
w16="N320 DEFAULT APPL >>>>>>>>>>>>>>>>>>>>"
w17="N322 CURRENT APPL >>>>>>>>>>>>>>>>>>>>"
w18="N323 CURRENT KEY MAP>>>>>>>>>>>>>>>>>>>>"
w19="N330 ENTER TERM # S1 71xxxx S2 "
w20="N331 ENTER APPL S1 81xxxxxxxxxxxx S2"
w21="N332 ENTER KEY MAP S1 91xxxxxxxxxxxx S2"
w22="N333 APPL NAME NOT CORRECT. RE-ENTER "
w23="N350 PERMANENT DATA READ ERROR. "
w24="N351 PERMANENT DATA WRITE ERROR. "
w25="ENTER APPL NAME, S2 "
w26="ENTER TERM 1###, S2 "
w27="ENTER KEYMAP NAME,S2"
w28="SWIPE MANAGER CARD TO LOCK, S2 TO END "
w29="SWIPE MANAGER CARD TO UNLOCK, S2 TO END"
w30="ENTER MANAGER PASSWDTO LOCK, S2 TO END "
w31="ENTER MANAGER PASSWDTO UNLOCK, S2 TO END"
w32="MSR MANAGER CARD DIDNOT MATCH "
w33="W400 TERMINAL NUMBERCONFLICT "
#
#
# --------------------------------------------------------
# Character translation list
#
# This function is normally used to make language-
# sensitive translations of special characters which may
# not be displayed by the point of sale equipment.
#
# If translations are specified, they must be in "x y"
# format where 'x' is the original character and 'y' is
# the replacement character.
#
# Example:
# (To display or print an "x" instead of a "@")
#
# t0="@ x"
#
t0=""
t1=""
t2=""
t3=""
t4=""
t5=""
t6=""
t7=""
t8=""
t9=""
#
# --------------------------------------------------------
# IO Device Initialization Strings
#
# These parms allow strings to be sent to selected
# individual devices when the device is intialized or
# is reset. An example of its use would be to send a
# CODE PAGE setup string to the individual device. The
# required string for setting a proper CODE PAGE is
# normally contained in a technical manual associated
# with the particular device.
#
# popr -- string for the operator display
# pcst -- string for the customer display
# pprn -- string for the printer
# pkyb -- string for the POS keyboard
#
popr=""
pcst=""
pprn=""
pkyb=""
#
# --------------------------------------------------------
# QCONNECT trace activation
# Note: Turn on any options ONLY in response to a
# request from support personnel. In general,
# tracing will cause delays in the checkout
# operation. Any changes should be temporary.
#
# Tracing parms:
# L = TRACE_LOG
# P = TRACE_PAUSE
# R = TRACE_QTR Remote file services trace
# S = TRACE_SCREEN = Screen trace no pause
# D = DCINT_V
# T = TRACE_TOT
# C = TRACE_COM
# Z = TRACE_IOP
# 7 = TRACE_PRN
# V = TRACE_SCREEN + TRACE_PAUSE + TRACE_VERBOSE
#
# Example:
# (To activate TRACE_LOG, DCINT_V, TRACE_IOP and
# TRACE_PRN)
# tracing="LDZ7"
#
tracing=""
# Conditional Definitions
# These definitions are available for use in processing the DYNAKEY.xxx
# file. The intention is to allow a user to simply have one all-
# inclusive file (DYNAKEY.000) which contains definitions for DYNAKEYs
# for every store and terminal in the chain. It implies that the
# customer is able to define specific ranges of terminals store-wide
# for specific uses. For example, standard cashier frontends would be
# terminals, 1-30; pharmacy: 31-35, etc. Use of a common dynakey
# definition file makes management of dynakey files inherently easier.
# Variables can be defined based on either Store Number or Terminal
# Number or combinations of both.
# For example, see below (# is not a comment for these conditional
# statements). The statements below are active ones:
#if ((STORE_NUM==6863) || (STORE_NUM==6849)) then
#define MANHATTAN
#elseif ((STORE_NUM==5890)||(STORE_NUM==5788)) then
#define LONG_ISLAND
#else
#define OTHER_STORES
#endif
#if ((TERM_NUM>=20) && (TERM_NUM<40)) then
#define PHARMACY
#endif
# The negate (!) operator is implemented also. Just be careful to
# properly enclose the conditional statements to assure they are
# interpreted correctly
# When the DYNAKEY.000 file is loaded, statements within that file can
# be activated using these if, then, else conditionals using the above
# defines in the conditional logic. In addition, the global variables
# TERM_NUM and STORE_NUM are available for use in processing the
# DYNAKEY file.
