; QVS Configuration and Device Information file ; ; This file contains configuration information for Terminal Concentrator ; and may contain configuration information for other programs including ; non-QVS information. ; ; CDI File Configuration Options: ; ; QCDIFILE.MST ; ; This file is a 'master' CDI file. If this file exists, no other ; CDI files will be processed for configuration information. This ; file exists in the installation directory on the machine where TC ; is installed. ; ; ; More detailed discussion of the startup sequence: ; ; Support files: ; ; LastIPL.dat ; This file contains the store number used during the last ipl. ; LastIPL.dat is generated from the first terminal to come ; online. ; ; ; ; The following are documentation-only versions of the cdi file: ; ; qcdifile.all (also formerly qcdifile.sam). ; This file documents all of the keywords supported by the ; current release of TS or TC. ; ; ; ; Format information: ; ; Comment lines are indicated with a ';' ; Option strings set to "" indicate default ; ; ; The CDI file can contain conditional expressions. Conditional expressions can ; be used to define a variable or to set any QCDIFILE option ; ; #if (conditional expression) then ; #define attribute ; or ; #if (conditional expression) then ; option="value" ; ; The expressions take the form: ; #if (conditional expression) then ; xxxxxx ; #elseif (conditional expression) then ; xxxxxx ; #else ; xxxxxx ; #endif ; ; A conditional expression in a CDI file is any logical expression that can be ; expressed in terms of: ; ; Store Number (STORE_NUM) ; Terminal Number (TERM_NUM) ; Controller ID (CTLR_ID) (used with TC when it runs on a 4690 or CSF controller) ; A previously defined attribute ; ; The logical operators &&, ||, and ! are supported as well as the relational ; operators >, >=, <, <=, ==, and !=. ; NOTE: Be sure to use ==, not = in this expression. Also note that none of the ; values are quoted. Example: #if (TERM_NUM == 16) then : ; Example: ; ; #if ( (TERM_NUM >= 50) && (TERM_NUM < 60) ) then ; #define PHARMACY ; #endif ; #if PHARMACY then ; physPrinter= "4610" ; #else ; physPrinter = "7156" ; #endif ; ; ; ------------------------------------------------------------------------- ; SECTION: CDI FILE OPTIONS - ALLOWS USE OF CDI FILES IN ADDITION TO OR ; INSTEAD OF QCDIFILE.000. ; ; ------------------------------------------------------------------------- [CDI] ; ------------------------------------------------------------------------- ; ------------------------------------------------------------------------- ; ; The next keyword is only valid in QCDIFILE.000. ; ; cdiBasedOnTermNum ; Y or N, default = Y, If Y, QCDIFILE.nnn will be used if found. ; If N is specified, QCDIFILE.000 will be used instead. ; ; The next keywords are valid in any CDI FILE except QCDIFILE.IPL ; ; cdiAppendNnn ; Y or N, default = N. QCDIFILE.nnn options are appended to the ; QCDIFILE.000 options. Note that the "Nnn" in this parm does NOT ; represent a number. If "N" is specified, QCDIFILE.nnn replaces ; QCDIFILE.000. If this keyword is set to "N" in an appended file, ; the appended file replaces any parameters read in to that point. ; ; The next keyword is valid in any CDI FILE except QCDIFILE.IPL ; ; cdiAppendCDIFileList ; Specifies list of additional CDI files to process. These files are ; processed in sequence and can be nested (an appended file can call ; a list of appended files, all of which are processed before returning ; to the next file in the initial list). The sequence of files can have ; the same parm listed more than once. If this happens, the most ; recently-read version of the parm is made active. Recall also that ; any parms in the QCDIFILE.IPL file cannot be overridden. In effect, ; parms in the QCDIFILE.IPL file are read last. It is a good policy to ; use a unique naming convention for files contained in this list: ; example: pharmacy.cdi, video.cdi, etc ; The cdiAppendCDIFileList may include qcdifile.ipl. ; ; Example: ; ; qcdifile.000 ; [CDI] ; #if TERM_NUM >= 1 AND TERM_NUM <= 50 then ; cdiAppendCDIFileList="qcditerm.dfl" ; #elseif TERM_NUM >= 51 AND TERM_NUM <= 60 then ; cdiAppendCDIFileList="qcditerm.sco" ; #elseif TERM_NUM >= 61 AND TERM_NUM <= 99 then ; cdiAppendCDIFileList="qcditerm.hh" ; #endif ; ; qcdifile.007 ; [CDI] ; cdiAppendCDIFileList="qcdifile.dfl, qcditerm.fe, qcdigrp.fe" ; ; qcdifile.dfl ; [CDI] ; cdiAppendCDIFileList="qcditerm.fe, qcdigrp.fe" ; ; qcditerm.fe ; qcditerm.ph ; ; qcdigrp.fe ; qcdigrp.ph ; ; ; Examples of special keyWords for new qcdifile.loc: ; [CDI] ; qcdiLocMadeFrom00="qcdifile.000:20031007153507" ; qcdiLocMadeFrom01="qcdifile.007:20031007153507" ; qcdiLocMadeFrom02="qcdifile.dfl:20031007153507" ; qcdiLocMadeFrom03="qcditerm.fe:20031107123507" ; qcdiLocMadeFrom04="qcdigrp.fe:20031107123507" ; qcdiLocMadeFrom05="qcditerm.fe:20031107123507" ; qcdiLocMadeFrom06="qcdigrp.fe:20031107123507" ; cdiBasedOnTermNum="" cdiAppendNnn="" cdiAppendCDIFileList="" ; END SECTION: CDI FILE OPTIONS ; -------------------------------------------------------------------------- ; SECTION: TERMINAL SERVICES/TERMINAL CONCENTRATOR [TS] ; -------------------------------------------------------------------------- ; -------------------------------------------------------------------------- ; -------------------------------------------------------- ; Terminal Load Definition and Java Environment Information ; ; These options allow configuration of items such as ; the default terminal application and keyboard definition name. ; ; The special keyword GET_FROM_CONTROLLER is used to tell TS/TC to ; read this information from the 4690 controller terminal load definition ; file(s). If GET_FROM_CONTROLLER is not specified, the terminal ; application and keyboard definition name can be specified here and it ; is not necessary to have a terminal load definition on the controller. ; (It is necessary, however, to have terminals defined on the 4690 ; conftroller "lan terminal definitions" under system configuration). ; Note also, that a "load configuration" or equivalent must be done to ; make TS/TC update this information. Simply changing the QCDIFILE and ; re-starting TS/TC is not enough. ; ; defaultApp1 is the name for the default starting application ; program. This replaces the default application name in defining ; the terminal load definition in the controller. Maximum of 24 characters. ; Make sure to include the "r::adx_ipgm:" if the file is to be loaded ; from the controller. ; keybDefName is the name of the keyboard definition file to be used for ; translating scan codes into function codes. Keyboard definition files ; are created under 4690 Terminal Configuration on the 4690 controller. ; termJava - indicates if 4960 java applications will be run. Set to '1' ; to enable java. ; defaultJapp1 is the Java class name for the default Java starting ; program. This replaces the default Java name in defining the terminal ; load definition in the controller. Maximum of 64 characters. defaultApp1="GET_FROM_CONTROLLER" keybDefName="GET_FROM_CONTROLLER" ; Java Redirection Information ; ; These options control the information that is returned to the terminal ; application at offset 59 of the terminal application status information ; structure when the ADXSERV function 4 (Get Application Status ; Inforamation) is executed. This byte shows which devices have been ; redirected to the Java application and what handlers and monitors have ; been installed by the Java application. ; ; NOTE: When a value for defaultJapp1 has been defined in the CDI file ; then ALL settings for Java Redirection Information must also ; be specified. ; ; iopRedirected ; "1" - I/O processor has been redirected to Java app ; "0" - I/O processor has not been redirected to Java app ; ; andisp1Redirected ; "1" - ANDISPLAY1 device has been redirected to Java app ; "0" - ANDI SPLAY1 device has not been redirected to Java app ; ; andisp2Redirected ; "1" - ANDISPLAY2 device has been redirected to Java app ; "0" - ANDISPLAY2 device has not been redirected to Java app ; ; crMonitorInstalled ; "1" - Java app has installed a cash receipt station monitor ; "0" - Java app has not installed a cash receipt station monitor ; iopRedirected="0" andisp1Redirected="0" andisp2Redirected="0" crMonitorInstalled="0" ;--------------------------------------------------------- ; SurePos Keyboard Type ; ; surePosKeyboardType - is required when termJava set to 1 and the 4690 ; configuration files indicate that the terminal is a SurePos terminal ; (configured using the Java terminal config screens), or in a OPOS/JPOS ; environment where the physical keybord type cannot be determined. This ; keyword indicates to TS which keymap to use and must be explicitly ; specified because TS cannot determine what type of physical keyboard ; is attached at runtime as 4690 can. Possible settings: ; ; "50Key" - 50 key keyboard attached ; "133Key" - 133 key keyboard attached ; "ANPOS" - ANPOS keyboard attached ; "SurePoint" - SurePoint keyboard attached ; surePosKeyboardType="" ; -------------------------------------------------------- ; Java Classpath and JVM for Terminal Application ; ; prependJavaClasspath specifies an arbitrary string value that will be ; prepended to the classpath that is sent to the JVM when the ; Java program is started ; javaJVM specifies the .EXE name of the java runtime environment that is ; is to be used to run java programs. There are at least three ; different runtime names popularly in use: JRE.EXE, JVIEW.EXE, ; JAVA.EXE. JRE.EXE is the default. A fully qualified path is ; optional. ; javaJVMArgs specifies an arbitrary string value that will be ; passed to the JVM when a java program is started. This string will be ; inserted in between the name of the JVM program and the '-cp' classpath ; specification. ; debugClassName & debugClassPath ; these settings are meant to be used by QVS developers to help debug ; 4690 java applications. They allow you to specify an application ; specific classpath that will be used to start the JVM. For example. if ; you were to run the java class 'MainPgm [args] ...' you could override ; the classpath being used to run the JVM (either from the 4690 ; configuration files or from the CDI javaClasspath setting) by setting ; the variable debugClassName="MainPgm" and then defining the varible ; debugClassPath="xxx". "xxx" would then be used as the class path when ; the JVM to run MainPgm is started. ; prependJavaClasspath="" javaJVM="" javaJVMArgs="" debugClassName="" debugClassPath="" ; ---------------------------------------------------------------------------- ; File Caching Support ; ; TS supports copying and keeping up-to-date certain controller-based files ; to the local hard drive. Keeping local copies makes terminal loading ; significantly faster. By default, the following files are copied: ; ; -Terminal sales application files ; -Terminal sales shared runtime libraries ; -Java class archive files specified in the java class path ; -X and Y ramdisk preload archives ; ; You can disable all file caching logic by specifying "NONE" as the ; value for the FileCacheFiles setting. The default value for this ; setting is 'AUTO' ; ; Also, you can specify additional files to be cached by using the ; FileCacheAdditionalFiles setting. List the additional files to be ; cached enclosed in quotes and seperated by commas. For example: ; ; FileCacheAdditionalFiles="R::JAVALIB:XYZ.GIF,R::JAVALIB:ABC.JAR" ; FileCacheFiles="AUTO" FileCacheAdditionalFiles="" ; --------------------------------------------------------------------------- ; TCC/IP Information (see ADX_SPGM:ADXTCCIF.DAT for additional info) ; ; tccipEnable - Set this to 1 to use TCC over IP instead of over DLC. The ; default is 0 to use DLC. ; ; tccipTTL - This is the "time to live" value. This parameter controls how ; many routers TCCIP packets will be sent across. The default value for ; this is 1. ; ; tccipAckPort - This defines the TCCIP Ack port value. The default is 4692. ; ; tccipMultiCastPort - This defines the TCCIP Multicast port value. The ; default is 4691. ; ; tccipMultiCast_Addr - This defines the TCCIP Multicast address value for ; the 4690 controller. The default is "224.46.90.1". ; ; tccipAckTimeout - This defines the amount of time TS/TC waits to receive a ; required acknowledgement from the controller. The value is specified ; in milliseconds and has a default value of 1000 (1 sec). This value must ; match a similar value contained in controller file: ADX_SPGM:ADXTCCIF.DAT : That value is the final parm in the file and has a range from 1000 to 9999. ; The two values must match. If either parm is missing or if the file on ; the controller is missing, a default value of 1000 milliseconds is used. ; If the values do not match, TS / TC will abort. ; ; tccipXidAddrList - A list of 1 to 8 specific ip addresses to which XIDs ; requests are simultaneously sent. This list provides an alternative ; to using ip multi-cast to find store controllers. Each ip address ; in the list should be separated by a comma. A typical list will contain ; 2 addresses: one for the primary tcc controller and one for the backup ; tcc controller. For stores with more than 2 controllers, up to 8 ; can be specified. ; ; A user may prefer to specify HOSTNAMES instead of the dot IP addresses. ; These can be substituted for the IP addresses, but IP addresses and ; HOSTNAMES CANNOT be mixed. ; ; Using this keyword forces TS / TC to enable unicast mode of TCC over IP. ; Corresponding software must be installed on the Store Controller to ; enable unicast support at the Store Controller. Please refer to the ; Insight User's Guide for information on configuring unicast TCC over IP ; on the Store Controller. ; tccipEnable="" tccipTTL="" tccipAckPort="" tccipMultiCastPort="" tccipMultiCast_Addr="" tccipAckTimeout="" tccipXidAddrList="" ; ; ; -------------------------------------------------------- ; Terminal Concentrator Information ; ; tcPrimaryServer - set this to 0 if this server is not to respond as primary. ; The default for this value is 1. This would normally be used conditionally ; by terminal number for load balancing or between two TC servers. ; Note: This parm is not used if the client uses TERMRPAM. It is used ; if the client uses QVSRPAM (sockets-based) ; For example: ; #if (TERM_NUM >= 51) && (TERM_NUM <= 100) then ; tcPrimaryServer=1 ; #else ; tcPrimaryServer=0 ; ; tcBackupServer - set this to 1 if this is a backup TC server for QVSRPAM ; clients. ; Note: This parm is not used if the client uses TERMRPAM. It is used ; if the client uses QVSRPAM (sockets-based) ; ; tcServerFindPort - tcp/ip port used by server to receive broadcast ; datagrams from clients trying to find a server. Default is port 7503. ; ; tcServerListenPort - tcp/ip port used by server to listen for tcp ; connections. Default is port 7502. ; ; ; tcStartingTermNum - used only in non-RPA concentrator environments with ; TLRDV001.DLL subdriver module. This is used very rarely. ; Due to its rarity, it is not included in the config util. ; (LTB - 8/7/03) ; ; licenseKey = license key entered during TC installation ; ; tcPipeName - activates support for PRS pipe clients and specifies the ; PRS pipe letter used for client-to-server communications. ; Only valid for TC/4690. ; tcShMemDll - specifies either "tshmem6" or "tshmem18" and indicates ; which .dll should be used for TC. The default is ; tshmem18. tshmem18 supports up to 60 heads running ACE. ; tshmem6 supports up to 20 heads running SA. ; termrpamCmdLine - used to set options (typically debug logging) for the ; termrpam.286 program which runs in POS terminals in some ; TC configurations. Possible values are: ; "-v" enable ascii logging to the controller. Log ; files go to the TC_DIR:\logt directory. Log ; filenames are in the form nnnRPA1.LOG where ; nnn is terminal number. ; termrpamLogFlushInterval - number of millis econds between TERMRPAM debug ; log flushes. TERMRPAM has a 32KB in memory ; log buffer. The log buffer is flushed when it ; gets full or at the interval specified (when ; the terminal is online). The default is 15000 ; (15 seconds). ; tcEnableTransactionRecoveryAfterSwitch - ; Set to '1' to enable TC terminals running SA to recover their ; transactions when switching between the primary and backup ; TC server. Default is '0'. ; ; tcMaxTerms - Number of terminals pre-initialized by TC. If this number is ; greater than 4, you must also enter a valid licenseKey parm. ; This licenseKey value will be provided to you when you purchase ; TC. This keyword specifies how many terminal instances are to ; be started. You should specify a number that is not greater ; than the maximum number of terminals you intend to use in this ; store. If you are running TC on a 4690 controller and memory ; is tight, you may want to optionally specify the tcMinTerms ; parm (see below). ; ; tcMinTerms - Number of terminals pre-initialized by TC. Pre-initialize ; means that a process is started which will become the ; terminal sales instance. By default, all terminals specified ; by tcMaxTerms are pre-initialized unless this parm is used. ; Use of this keyword allows TC to use less memory if less than ; tcMaxTerms clients are actually connected. Saving this memory ; is not really an issue for Windows but it can be under TC/4690. ; ; tcMinCtlrFreeMemKB - This keyword enables TC to limit additional terminal ; application memory requests if and when the controller ; reaches a critically low level of free memory. When ; the limit is reached, TC will fail all requests for ; terminal sales dynamic memory and it will fail requests ; to start new sales instances. If controller free memory ; later goes above the specified level, TC will again start ; granting requests for memory and/or new sales startup. ; An example value for this keyword might be 3072 (3 MB). ; The default value for this keyword is 1536 (1.5 MB). ; This has meaning only in TC/4690. ; tcPrimaryServer="1" tcBackupServer="0" tcServerFindPort="" tcServerListenPort="" licenseKey="" tcPipeName="" tcShMemDll="" termrpamCmdLine="" termrpamLogFlushInterval="" tcEnableTransactionRecoveryAfterSwitch="" tcStartingTermNum="" tcMaxTerms="" tcMinTerms="" tcMinCtlrFreeMemKB="" ; tcStartingTermNum parm not included in configuration utility - ltb 8/7/03 ; ---------------------------------------------------------------------------- ; Other Options ; ; storeNum - identifies the store number of the controller that TS/TC will ; connect to. This allows for multiple controllers to exist on ; the same lan such as in a lab environment. It only makes sense ; to use this option with a local QCDIFILE.MST. It should not be ; used when QCDIFILE is used from the 4690 controller. For this ; case, the store number is provided to the terminal through normal ; 4690 controller-to-terminal communications. ; termNum - again, this is probably just for the lab. It specifies the ; terminal number to be used, thus avoiding the "Z001" process. ; ctlrId4690 - used rarely for stand-alone TSF and TC to set the 2 character ; controller ID which would normally be obtained from the ; controller. TS/TC defaults to 'CC' if this value is not set. ; display - controls whether or not TS/TC display console is shown or hidden ; at startup. Default is to show. Set to 'Hide' to hide display. ; ; vdisplay - controls whether or not TS/TC VDISPLAY console is shown or hidden ; at startup. Default is to show. Set to 'Hide' to hide the ; VDISPLAY console. This keyword has meaning only when the ; physVdisplay keyword is used to define a VDISPLAY device as ; active. ; disableBeep - Former TERM_CMD_LINE1=-B option. The default is "" (beep is on) ; To turn off the system beep, set the value to "y". ; ; loadDelay - Former TERM_CMD_LINE1=Ldelay,nnn option ; ; monKeybWrites - Former TERM_CMD_LINE1=W option. The default is OFF (""). ; "Y" turns it on. ; dateTimeChanges - By default, TS/TC updates the system date/time on ; command from the 4690 controller. Set this option to 'N' to disable. ; javaConsoleAlwaysShow - Controls how and when the java console video session ; is made visible. Normally, the java console is visible for text mode ; java programs and completely hidden for graphics mode java programs. ; Setting this option to "Y" causes TS to not completely hide the java ; console session. Setting to "N" forces the normal behavior. This setting ; defaults to "N" when TS/TC tracing is off and defaults to "Y" when ; TS/TC tracing is on. This setting is only meaningful in terminals ; configured to use 4690 java applications. ; javaConsoleTitle - string used as title of the java text-mode console. ; SkipLoadShrink option - the default is "". If set to "Y", the terminal ; Load Shrink file processing is disabled. ; ProcessLoadShrink - if set to "Y", this forces TSF to process the terminal ; load shrink file on the controller. The default is "N"; so that the ; terminal load shrink file is processed if 1) the terminal load definition ; indicates that the terminal sales application is to be loaded from a ; Ramdisk (eg. x:eamts10l.285) or 2) terminal load definition indicates a ; java application is to be started. ; ;dumpOnApplFatal ; If the 4690 application ends abnormally dumpOnAppFatal set to "Y" causes TSF ; to dump and shut down. Without this setting TSF simply displays a W103 or ; W104 message on the system display when the 4690 application abends. ; ;sysShutdownOnApplTerm ; If you would like TSF to shut down when the 4690 application terminates ; normally set this setting to "Y". Without this setting TSF does nothing ; when the 4690 application terminates. storeNum="" termNum="" ctlrId4690="" display="" vdisplay="" disableBeep="" loadDelay="" monKeybWrites="" dateTimeChanges="" javaConsoleAlwaysShow="" javaConsoleTitle="" SkipLoadShrink="" ProcessLoadShrink="" dumpOnApplFatal="" sysShutdownOnApplTerm="" ;---------------------------------------------------------------------------- ; IbmAppTermType ; used to specify the terminal type returned to the application on an ; ADXSERVE, Function 4 call. The possible values supported are: ; ; IbmAppTermType="1" - 4693 terminal type returned ; IbmAppTermType="2" - 4694 terminal type returned ; IbmAppTermType="3" - 4683 terminal type returned ; IbmAppTermType="5" - SurePos terminal type returned ; ; The Default value is IbmAppTermType="3" IbmAppTermType="" ;---------------------------------------------------------------------------- ;IbmKybDef keyword ; ; - set to "Y" to force TS to use the remote IBM keyboard definition ; files, even though the keyboard is defines as a virtual device. ; This allows a client appl to originate keyboard switch key ; values which will be translated by TS using the controller ; keyboard definition files. ; This keyword is not included in the config utility due to its ; rare and very specific useage. ltb 8/7/03 IbmKybDef="" ; ; LanAdaptID keyword ; ; - this keyword is used when more than 1 LAN adapter definition ; is active on the machine where TS is installed. Without this ; keyword, TS always defaults the DLC binding to adapter 0 in ; machine. This keyword can be used to specify the LAN adapter ; number to be used for TCC communications. ; Example ; LanAdaptID = "01" ; LanAdaptID = "" ; ; Note: This parm replaces the former "loadDelay" parm which was ; a replacement for the TERM_CMD_LINE1 parm: Ldelay,nnn ; ReqDevTimeOut="" ; Preferred = 20 (no 48 5 devices) ; Preferred = 45 (w/485 devices) ; ;---------------------------------------------------------------------------- ;IPL Status Messages ; ; iplStatus - set to "Y" to have TS/TC display information about what it is ; doing during IPL. Setting specifically to "N" disables IPL ; status. The default is for IPL status to display whenever ; tracing is on at TS/TC startup. Typical IPL status messages ; are: ; ; "Store Num sss" ; "Term Num ttt" ; "Reading QCDIFILE.SAM" ; "Reading QCDIFILE.MST" ; "Reading QCDIFILE.000" ; "LANTCC" ; "Finding CTLR" ; "CTLR sss found mmmmmmmmmm" ; "CTLR sss found mmmmmmmmmm" - will display multiples if more ; than one controller is found. ; sss is store number. ; "Session with CC Established" ; "Reading KEYMAP.000" ; "Reading ADXCSCTF" - terminal config ; "Reading ADXCSCKF" - store config ; ; ; iplStatusDelay - TS/TC will wait this many milliseconds after displaying ; each IPL status message to give the user a chance to read ; them. The default is 2000 (2 seconds). ; iplPosDevice - TS If set to "Y", then status msgs relative to POS device ; searches will be displayed prior to the 2X20 display ; driver being installed. ; iplStatus="" ; Preferred = Y iplStatusDelay="" ; Preferred = 0 iplPosDevice="" ; Preferred = Y ;------------------------------------------------------------------------- ;Modifying the MONITOR pipe size. The MONITOR pipe has a default size ;of 1024*100 for outbound messages. This size can be increased by specifying ;the MONITOR pipe size in KBYTES using the following CDI keyword. Coding ;a value of "512" would define the size as 1024*512. Valid values are ;100 to 2048. The default size is still 100*1024: MonitorPipeSize="" ; -------------------------------------------------------- ; Tracing Options ; ; traceCmdLine - controls tracing if no tracing was specified on the ; TPROCESS command line. ; ; Possible values: ; "" - default ; "-t" - same as '-t' TPROCESS option ; "-tx" - same as '-t' but delayed until application has loaded ; "-m[nnnnn]" - big memory trace buffers option. nnnnn is size in ; kb of per-process trace buffer for most processes. ; The default for nnnnn is 640. Some processes can get ; extra large trace buffers. These processes get 10Mb ; trace buffers by default. ; ; Note that the options specified here can take any form that the ; trace options take on the TPROCESS command line. This includes ; specifying tracing for specific tasks such as "-t4". ; Note that use of -v or -vx is not recommended except for use in ; the QVS LAB because -t provides more information and/or smaller ; trace files. Some initialization tracing my be missed when compared ; to using the options from the command line. ; ; traceXtraBigTrcBuff - list of processes that get extra large trace ; buffers. Without -m, size is 500KB. Processes are listed by their ; EPTDA 'procname'. Multiple processes, separated by spaces or commas ; can be specified. An example: ; traceXtraBigTrcBuff="RIOAM_CTL IOP_TRIG0". ; traceCmdLine="" traceXtraBigTrcBuff="" ; -------------------------------------------------------- ; Display Case Options ; These options apply to ANDISPLAY/ANDISPLAY2/ANDISPLAY3 ; ; "0" all uppercase (default) ; "2" display mixed ; ; Note 1: To replace the environment setting TERM_CMD_LINE1=-dDISPLAY1,case ; use casefmt="2" casefmt="" ; Control physical line I/F for the ASYNC connection where ; a pinpad type device does not have physical HW lines to raise ; either DTR or CTS signals. ; ; use ; raiseSerDtr = "N" ; to force TS to simulate report the true DTR/DSR line values. Default ; is to always report these values as high to the GETLONG request. ; ; Default: report DTR/DSR lines as high. AllowPinpadRcvdMsgPassthru="" ; By default, TSF will pass an Ack (0x06) from a serial device separate ; from other pending data from the serial device. This is required by some ; older EFT applications. ; ; use ; AllowPinpadRcvdMsgPassthru="Y" ; to force TSF to return all pending data when the EFT application ; issues a serial READ request. ; ; Default: AllowPinpadRcvdMsgPassthru="N" ; ------------------------------------------------------------------ ; Mag Stripe Reader Options ; ; appMsrTracks - This option is used to specify the MSR track capabilities ; expected by the application. Its format is "nttt" where ; n is number of tracks that the MSR device can read and 'ttt' ; corresponds to tracks 1, 2, and 3 respectively. Each 't' ; position can be either 0 or non-zero indicating if that ; track can be read. Here are some examples: ; "3123" - three track MSR; read tracks 1, 2 and 3 ; "2120" - two track MSR; read tracks 1 and 2 ; "1020" - single track MSR; read only track 2 ; "2023" - two track MSR; read tracks 2 and 3 ; "3120" - three track MSR; read tracks 1 and 2 ; "0000" - no MSR ; ; the default for appMsrTracks is "2120" ; ; physMsr - The following options are possible: ; "virtual" - TS should install virtual support for this ; device. ; "POSS" - TS should install IBM POSS support for this ; device ; "rpamClient" ; ; appMsrTracks="" physMsr="" ; ---------------------------------------------------------------------- ; Printer Options ; ; These options are used to specify the IBM printer type and features ; expected by the 4690 application and to specify information related ; to the physical printer. ; ; appPrinter - mod2, mod4, mod4r, 4610, 4610_TI4, ; Note: 4610_TI4 is only recognized when physPrinter is set to ; "virtual". It tells the virtual 4610 driver to report model ; TI4 as the 4610 model type instead of model TI2. Other ; ; physPrinter - mod2, mod4, 4610, 7193, 7194, 7156, 7158, K580, 7167, ; 7197, E5000, E6000, virtual, A758, POSS, ; rpamClient ; Notes: ; "POSS" - TS should install IBM POSS support for this device. ; POSS will detect and report the actual printer model. ; "rpamClient" can be used by itself or it can precede another ; printer type (for example rpamClient7158) ; physPrinterPort - used to specify COM port number of attached printer. ; Set to 'USB' for usb attach. Note 'USB' is supported only for ; the following physPrinter types: 4610, E6000. ; Examples: "1" or "USB" ; physPrinterBaud - used to specify baud rate of attached printer ; valid values are 9600, 19200, 38400, 57600, 115200 ; physPrinterECLevel - used to override 4610 EC Level when emulating ; a 4610 on NCR printers. Valid values are like "24", "36". This is ; currently only supported in CE environment. ; physPrinterCodePage - indicates which code page to select when using ; a 7193, 7194, 7156, 7158, K580, 7167, 7197, E5000 or E6000 to ; emulate an IBM Model 4 printer. Only valid when appPrinter is ; set to "mod4". Valid values and code pages they correspond to are: ; 437 - US English ; 850 - Multilingual ; 852 - Slavic ; 860 - Portuguese ; 863 - French Canadian ; 865 - Nordic ; 858 - Multilingual with Euro Symbol ; 866 - Cyrillic ; (Ex: physPrinterCodePage="865" selects Nordic code page). ; ; rpamPrinterFilter - set to Y if RPAM client is used and wishes to ; monitor output to a printer controlled by directly by TS. ; This keyword is ignored if physPrinter setting starts with ; 'rpamClient'. The default for this keyword is "N". ; ; ; NOTE1: if physPrinter is specified as 4610, then physPrinterBaud is ; ignored and the 4610 MUST be set at 19,200 BAUD Rate. ; ; NOTE2: if appPrinter is specified as 4610, then physPrinter must be ; specified as either 7158, 7194, or 4610. All other choices ; for physPrinter are invalid and TS will panic at startup. ; ; These options are not necessarily required. For example, TS will ; auto-detect the attached printer type if the printer is attached via ; RS-485. These parameters are only used when auto-detection of the ; device is not possible such as when the device is being emulated in ; software or with a totally different device. ; ; appPrinter="" physPrinter="" physPrinterPort="" physPrinterBaud="" physPrinterECLevel="" rpamPrinterFilter="" ; --------------------------------------------------------------------------- ; Display device options ; ; The following options are possible: ; ; systemDisplay - defines a display device as the one used by the ; cashier. This is the display used by the I/O Processor ; and Application for prompts and messages. There is no ; default for this keyword (it should be specified). ; A non-null value in this keyword causes the deprecated ; 'andisp' and 'vdisp' keywords to be ignored and all ; display configuration to come from these keywords. ; ; Note that under TS and TC, system display data may also ; be mirrored to the workstation video display. These ; 'mirror' displays are activated if a) the workstation ; video display is not already configured as the 4690 ; pos system display and b) the TS/TC console screen is ; configured as "show" and not "hide" during installation. ; ; "andisplay" ; "andisplay2" ; "vdisplay" ; ; systemDisplay_i - same description as systemDisplay but this one is ; meant for use in .ipl files. systemDisplay_i will ; be used only when systemDisplay is not found. Use of ; an _i keyword allows the controller CDI keyword to ; override the .ipl version. ; ; physAndisplayX (physAndisplay, physAndisplay2, or physAndisplay3) ; "none" - not used (default) ; "POSS" ; "POSS highest" - The highest designation corresponds to the address ; of the device on the RS485 device channel. The ; address of a device is based on two things: the ; device itself and whether it is plugged into an 'A' ; port or a 'B' port. 'A' port addresses are even ; (and therefore lower) while 'B' port addresses are ; odd. ; "POSS lowest" - See "highest" description above. ; "virtual1" - map 2x20 display to first (or only) workstation ; (vga) display ; "virtual2" - map 2x20 display to second workstation display ; "virtual" - virtual display device (doesn't map to any physical) ; "rpamClient" ; ; ; physVdisplayX ; "none" - not used (default) ; "virtual1" - map VDISPLAY display to first (or only) workstation ; (vga) display ; "virtual" - virtual display device (doesn't map to any physical) ; "rpamClient" ; ; vdisplayXDefaultMode (required if physVdisplayX is used) ; "12x40" ; "16x60" ; "25x80" ; "16x80" ; ; vdisplayXWindowMode ; "FullScreen" (default) ; - TS VDISPLAY window has no border or caption and ; covers the entire screen including the taskbar ; unless the keyword 'coverWindowsTaskbar' is set ; to 'N' ; ; "Windowed" - TS VDISPLAY window has a caption and a thin border ; and a minimize box. It has a screen area that is ; 800x600 pixels regardless of the size of the display ; ; "WindowedFull" - TS VDISPLAY window has a caption and a thin border ; and a minimize box. It covers the entire screen ; except for the taskbar. ; ; vdisplayXWindowTitle ; "" (default) ; "Any Window Title Text" ; ; vdisplayXShowCursor ; "N" (default) ; "Y" Mouse cursor is visible on the VdisplayX console ; ; rpamAndisplayXFilter - set to "Y" if RPAM client is used and wishes to ; monitor output to a display device controlled by ; "rpamClient". ; "Y" ; "N" (default) ; ; coverWindowsTaskbar ; "Y" (default) - cover the Windows taskbar with the VDISPLAY full ; screen window (take up the entire visible screen ; area). ; "N" - do not cover the Windows taskbar with the VDISPLAY ; full screen window. ; systemDisplay="" systemDisplay_i="" physAndisplay="" physAndisplay2="" rpamAndisplayFilter="" rpamAndisplay2Filter="" physVdisplay="" vdisplayDefaultMode="" vdisplayWindowMode="" vdisplayWindowTitle="" vdisplay1ShowCursor="" ; ------------------------------------------------------------------------ ; Cash Drawer Option ; ; Specifies information on how the cash drawer is attached. ; ; The following options are possible: ; ; physCashDrawerX ; "virtual" - TS should install virtual support for this device. ; "printer" - Indicate that cash drawer is connected to the printer. ; Note that in some environments, this is the default ; and specifying "printer" is not required. ; "POSS" - TS should install IBM POSS support for this device. ; "rpamClient" ; ; Note: Currently, only valid values for physCashDrawer2 are "POSS" and ; "JPOS". ; ; physCashDrawer="" ; ------------------------------------------------------------------------ ; Scale Options ; ; Specifies information about the scale device. ; ; The following options are possible: ; ; physScale ; "virtual" - TS should install virtual support for this device. ; "POSS" - TS should install IBM POSS support for this device. ; "rpamClient" ; ; physScale="" ; ------------------------------------------------------------------------ ; Keyboard Options ; ; Specifies information about the keyboard device. ; ; The following options are possible: ; ; physKeyboard ; "virtual" - TS should install virtual support for this device. ; "POSS" - TS should install IBM POSS support for this device. ; "rpamClient" ; ; ; physKeyboard="" ; ------------------------------------------------------------------------ ; Scanner Options ; ; Specifies information about the scanner device. ; ; The following options are possible: ; "virtual" - TS should install virtual support for this device. ; "POSS" - TS should install IBM POSS support for this device. ; "rpamClient" ; ; physScanner="" ; ------------------------------------------------------------------------ ; NVRAM Options ; ; Specifies information about the NVRAM (hard totals) device. ; ; physNvRam - The following options are possible: ; "virtual" - TS should install virtual support for this device ; (TS uses BATPRMEM.DAT file as NVRAM). ; "POSS" - TS should install IBM POSS support for this device. ; "rpamClient" ; ; physNvRamSize - by default, TS/TC reports NvRam size as 1K and terminal ; type as 4683. By setting this option to "16", you are ; e nabling NvRam size of 16KB (4693/4694). By setting this ; option to "99", you are enabling CMOS size of 99KB, ; corresponding to a SurePos 700 series terminal ; ; physNvRam="" physNvRamSize="" ; ------------------------------------------------------------------------ ; Serial Port (incluing 485 tailgate) Options ; ; Specifies information about the serial port devicies (pinpads, mag stripe, ; etc). ; ; physSerialX - A non-null value in any of these keyword causes ; all deprecated "cXtohdwr" and "cXOverride" keywords to be ; ignored. ; ; The following options are possible: ; "virtual" - install virtual support for this device ; "POSS 0xNN" - install IBM POSS support for this device. The 0xNN ; value is as follows and must be present. ; PosDEVICE_RS232_25A 0x64 ; PosDEVICE_RS232_25B 0x65 ; PosDEVICE_RS232_23A 0x68 ; PosDEVICE_RS232_23B 0x69 ; ; "COMx" - TS will support by mapping PC COM port X where X can ; be 1 - 15. ; "rpamClient" - This value is currently on valid for physSerial1 and ; physSerial2. ; ; physSerialXOverride - Optionally override .286 application OPEN SERIAL ; RS-232 parameters ; ; Example: To force settings for application port 3 to 9600 baud ; even parity, 7 data bits, 1 stop bit specify: ; ; physSerialXOverride="9600,E,7,1" ; ; AppSerialXReportXmitPending - Optionally allow reporting of actual device ; transmit pending status. ; ; AppSerialXReportXmitPending="Y" ; ; Notes: 1) These overrides are likely never used for RS-485 attached ; devices ; 2) By default, TS will override any application baud rates less ; than 4800 to 4800. ; ; rpamSerialXFilter - set to Y if RPAM client is used and wishes to ; monitor i/o to a serial device controlled by directly by TS. ; This keyword is ignored if physSerial setting starts with ; 'rpamClient'. The default for this keyword is "N". ; physSerial1="" physSerial2="" physSerial3="" physSerial4="" physSerial1Override="" physSerial2Override="" physSerial3Override="" physSerial4Override="" AppSerial1ReportXmitPending="" AppSerial2ReportXmitPending="" AppSerial3ReportXmitPending="" AppSerial4ReportXmitPending="" rpamSerial1Filter="" rpamSerial2Filter="" rpamSerial3Filter="" rpamSerial4Filter="" ; -------------------------------------------------------- ; TS/TC Detailed Trace Control ; ; See TRCHEUR.BAT for additional definitions. These definitions are meant ; to be used under direction of a QVS person. Not all options are ; supported even if documented here. The options that are most likely to ; be used are csftsfTraceCtrl options/offsets 2 and 4 which control max ; trace buffer and file sizes. ; ; Offset meanings for csftsfTraceCtrl: ; ; 0 turn on Base Kernel Tracing (default is 1) ; 1 turn on Extended Kernel Tracing (default is 0) ; 2 Log file size ; 0 = .5MB 4 = 10 MB (default if #3=1) ; 1 = 1MB 5 = 20 MB ; 2 = 2MB F = 250 MB ; 3 = 5MB (default) ; 3 Log file instances ; 0 = Log per process (default) ; 1 = Single Combined Log File (CSF1.LOG) ; 4 Memory trace buffer size (most processes) ; 0 = 0 KB (no tracing) ; 1 = 8 KB 5 = 128 KB ; 2 = 16 KB ; 3 = 32 KB (default) ; 4 = 64 KB ; 5 Global trace buffer size ; 0 = 0 KB (no tracing) (default) ; 1 = 128 KB ; 6 File read/write max amount of data traced ; 0 = 0x20 bytes (default for in-memory tracing) ; 1 = 0x30 bytes ; 2 = 0x40 bytes ; 3 = 0x80 bytes (default for -t tracing) ; F = 0x7FFFFFFF bytes ; 7 Timestamp granularity ; 0 = Timestamps of log entries are seconds.millisconds (default) ; 1 = Timestamps of log entries are millisconds.microseconds ; 8-10 Future Use (default to ?) ; 11 turn on NOABORT/OKABORT Tracing (default is 0) ; 12 turn on NODISP/OKDISP Tracing (default is 0) ; 13 turn on KENTER Tracing (default is 0) ; 14 turn on MX Tracing (default is 0) ; 15 turn on ENABLE/DISABLE Tracing (default is 0) ; 16 turn on base DISK Tracing (default is 1) ; 17 turn on extended DISK Tracing (default is 0) ; 18 turn on base PIPE Tracing (default is 1) ; 19 turn on extended PIPE Tracing (default is 0) ; 20 turn on base RPAM Tracing (default is 1) ; 21 turn on extended RPAM Tracing (default is 0) ; ; 1 2 ;; 0123456789012345678901 ;csftsfTraceCtrl="??????????????????????" ; 1 ;; 01234567890123456789 ;tsfTraceCtrl="????????????????????" ; ------------------------------------------------------------------------ ; Local file access options ; ; Specifies location of local 4690 files when running TS or TC in local ; mode. ; ; By default, TS and TC scan local drives on the local machine for ; for a drive containing direcotory "\ADX_SPGM" starting with drive c:. ; The first drive found becomes c:, the second drive found becomes d:. ; Scanning stops if a network drive is encountered. ; ; An exception to this default is the case were TC and CSF run integrated ; on the same machine. For this case, the default is for TC to use the same ; file locations as CSF as specified by logical names in the fdsln.ln file. ; ; Note: If localModeCDrive is not defined, localModeDDrive is ignored. ; ; localModeCDrivePath - path on local machine where 4690 "C:" files are ; stored. Default="". ; localModeDDrivePath - path on local machine where 4690 "D:" files are ; stored. Default="" localModeCDrivePath="" localModeDDrivePath="" ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; ; SECTION: QVS ELECTRONIC SYSTEM JOURNAL SUPPORT ; [SJ] ;QVS Electronic journal support provides data capture for the IBM model ; 2/3/4 printer system journal station. If the function is enabled, then all ; application writes to the printer system journal station will be intercepted ; and written to a disk file on the Terminal Concentrator PC. EJ files are ; created using the following naming conventions: ; ; SJLOGNNN.DAT ; ; where: ; ; NNN = 3 digit terminal address ; ; ; The following options are provided to control the EJ support. ;EjDur="nnn" - Define the number of days Journal data will be archived ; "0" - Don't archive Journal data past current day ; ; If archiving is activated by the user, archive files will have a naming ; convention of: ; ; SJLOGNNN.MMM where MMM is the archive number ; For example. If archiving is activated for a duration of 3 days, the user ; will see the following archive progression: ; ; Day 1: SJLOGNNN.DAT ; Day 2: SJLOGNNN.001 and SJLOGNNN.DAT, where 001 is prior day log ; Day 3: SJLOGNNN.002, SJLOGNNN.001, and SJLOGNNN.DAT ; Day 4: SJLOGNNN.003, SJLOGNNN.002, SJLOGNNN.001, and SJLOGNNN.DAT ; ; DAY 5-? SJLOGNNN.003, SJLOGNNN.002, SJLOGNNN.001, and SJLOGNNN.DAT ; ; NOTE: Each day at midnight rollover, or when the terminal is next used, ; all ESJ log files will be renamed, such that (using the above example of 3 ; days): ; 1) delete SJLOGNNN.003 (will not initially exist) ; 2) rename SJLOGNNN.002 to SJLOGNNN.003 (will not initially exist) ; 3) rename SJLOGNNN.001 to SJLOGNNN.002 (will not initially exist) ; 4) rename SJLOGNNN.DAT to SJLOGNNN.001 (will not initially exist) ; 5) create a new SJLOGNNN.DAT ; ;EjParse="Y" - Parse all ecapse sequences from the printer data (1Bnn). This ; enables the journal data to be printed on a standard printer. ;EjPath="c:\SJ" - Alternate path where the journal file is to be maintained. ; The journal files are stored in a default directory named ; SJINFO, which is created as a sub-directory under the TCNT ; install directory. Thus the default directory name for the ; system journal files is: C:\TC_NT\SJINFO ; NOTE: If an alternate path is specified, it is the responsibility of ; the user to create this path prior to starting Terminal ; Concentrator. This alternate path, if specified, cannot be ; terminated with the backslash character. Thus "C:\ABC" is valid, ; but "C:\ABC\" is invalid. ;EjAddCR = "y" - add a CR character to the end of each print line being ; written the journal disk file.