The Initialisation File "oscar.ini"

Depending on the operating system in which the MICROS Retail OSCAR POS application is installed, various program parameters and environment variables have to be set during the start of the MICROS Retail OSCAR POS application.

In the operating system UNIX, this is done by the files "oscar.def" and "oscar.cf", in WINDOWS by the file "oscar.ini". These files are located in the folder ../bin of the MICROS Retail OSCAR POS application.

Via the initialisation file "oscar.ini", the MICROS Retail OSCAR POS application is given various parameters and environment variables when starting.

Note:
If Window XP with service pack 2 and active Firewall is used the appropriate MICROS Retail OSCAR POS applications must be entered as exceptions in Firewall.

This can be done with the help of the Java Script "addToFirewallExceptList.js" in directory ..\bin:

Wscript addToFirewallExceptList.js –d C:\oscars\osc35

Some parameters, particularly the DEBUG parameters, are optional and can be activated or deactivated by ";" or by prefixing ". The output for the activated debug parameters is written into the file errlog in the folder work or in file \logs\YYYYMMDD.oml if variable OSCAR_CONSOLE=MESSLOG has been set. If the process unit is of the type "Login", the debug output will be written into the file errlog login.

In the following, you will find an example of an "oscar.ini file" with all currently possible parameters. Descriptions of the additional special parameters for the configuration of TCP/IP can be found in the file "Configuration Options for TCP/IP Connections".


The following warnings will be issued in later MICROS Retail OSCAR POS versions as per specific environment variables:

 

BfScheduler::schedule: Warning: Exceed memory usage by more than nn%, now mmm KB. [(date time, PID: pid)]

BfScheduler::assignSema: Warning: Exceed initial semaphore list by more than nn%, now sss semaphores.

BfScheduler::assignTimer: Warning: Exceed initial timer list by more than nn%, now ttt timers.

BfScheduler::assignFileDesc: Warning: Exceed initial file descriptor list by more than nn%, now fff file descriptors.

Tasks.C:makeFdForHandle:: Warning: Exceed initial handle list by more than nn%, nuw hhh handles.

Tasks.C:poll: Warning: Exceed initial wait handle limit by more than nn%, now www handles.

NetConnector::NetConnector: Exceed initial connector count by more than nn%, now ccc connectors.

 

The following rules apply:

 

 

The values shown have the following meanings:

mmm: Maximum used RAM store in KB.

sss: Maximum number of simultaneously used semaphores (Oscar-internal synchronisation objects)

ttt: Maximum number of simultaneously used timer (Oscar-internal objects for time monitoring).

fff: Maximum number of simultaneously used descriptors (Oscar-internal objects for maintaining activation of certain operating system objects, e.g. network sockets, file descriptors, Windows Handles).

hhh: Only Windows: Maximum number of all descriptors assigned simultaneously in Oscar for operating system handles.

www: Only Windows: Maximum number of operating system handles used simultaneously.

ccc: Maximum number of network connections used simultaneously.

 

The following applies to ccc and hhh: This refers to all objects available at present in the Oscar process. In all other cases only those objects for which a task is waiting is meant.


bmppath="..\bmp\"

By use of this environment variable, the MICROS Retail OSCAR POS application is informed about the path for the directory of the BMP files. Graphic images like keyboard descriptors, logos, symbols etc. are stored in this directory.


helppath="c:\osc_user\osc15h\"

By use of this environment variable, the absolute path for the directory of the MICROS Retail OSCAR POS application is identified.


helppath2="..\help\"

This environment variable is currently not in use.


OSCAR_SERVER=132.147.160.224

The environment variable OSCAR _SERVER informs the MICROS Retail OSCAR POS application about the network address of the server. The start of the MICROS Retail OSCAR POS application will be cancelled if the connection to the MICROS Retail OSCAR POS server cannot be established within a particular time period. A corresponding entry will be made in the file errlog in the folder work.


OSCAR_BACKUP=

The environment variable OSCAR_BACKUP informs the MICROS Retail OSCAR POS application about the network address of the backup server. The operation of the MICROS Retail OSCAR POS application with a backup server requires the configuration of an appropriate process unit.


OSCAR_INSTALLATION=1

By use of this environment variable, the MICROS Retail OSCAR POS application is informed about the installation number. An appropriate installation must have been configured.


OSCAR_OPTIONS=option:option…

As from version MICROS Retail OSCAR POS 41 several customer projects and program modules have been integrated which have to be activated with environment variables in file "oscar.ini".

 

To ensure that these features are not automatically available to all customers these environment variables should be entered as follows in "oscar.ini":

 

 

Note:

The following commands must be executed after every change of environment variables "OSCAR_OPTIONS=" to ensure that the changes are activated in MICROS Retail OSCAR POS.


oscar convert

oscar addAscFiles

oscar init UiText

oscar init DbText

oscar dofgl.fgl Sprache

 

 Click on the graphic for further help with setting up optional program modules..


OSCAR_PORTBASE=6100

By use of this environment variable, the MICROS Retail OSCAR POS application is informed about the free port address for the server and client services.


OSCAR_PROJECT=projMK

This environment variable informs the MICROS Retail OSCAR POS application that project-specific application programs can be called up which deviate from the default programs.

The appropriate programs (FSM, FGL. ASC etc.) can normally be found in directories and must be entered in file "oscar.ini" with the following environment variables:

Example "OSCAR_PROJECT=projMK

OSCAR_ASCPATH=:..\ascMK::..\asc

OSCAR_FGLPATH=..\fgluser:..\fglMK:..\fglDTM:..\fgl

OSCAR_FSMPATH=..\fsmMK:..\fsm

When these programs are called up the system firstly searches the current directory for the file (*.fsm, *.fgl, *.asc *.etc). If this file does not exist or is not readable the system goes to directory /fglProjektname. If this file is not available or not readable or if directory "fglProjektname" is not available or readable or empty the system searches directory /fgl.

Note:
Environment variables must be declared under operating program LINUX/UNIX via the command " export".


OSCAR_ASCPATH=..\asc

By use of this environment variable, the MICROS Retail OSCAR POS application is informed about the directory of the ASC files (ASCII). By use of the command oscar init ASC file name, a new table corresponding to the ASC file can be generated for the MICROS Retail OSCAR POS database.

Example:
Command OSCAR_ASCPATH=..\ascMK:..\asc informs the MICROS Retail OSCAR POS program that the search should start in directory ..\ascMK . If no matching *.asc file is found search continues in directory ..\asc .


OSCAR_FGLPATH=..\fgluser:..\fgl

By use of this environment variable, the MICROS Retail OSCAR POS application is informed about the directory for the 4GL files. In the folder ..\fgl, the standard files are located. Customer-specific 4GL files can be stored in the folder..\fgluser to prevent 4GL files of the same name from being overwritten.

When the commands oscar *.fgl are executed, the files will be searched for in the folder ..\fgluser first and then in the folder ..\fgl.

Attention!
For the intergrated projects of MICROS Retail OSCAR POS the correspondending environment variable for the OSCAR_FGLPATH and OSCAR_PROJECT must be set.

Example:

OSCAR_PROJECT

OSCAR_FGLPATH

Nordic

OSCAR_FGLPATH=..\fgluser:..\fglNordic:..\fglDTM:..\fgl

Nordic Avecra

OSCAR_PROJECT=projAvecra

;OSCAR_FGLPATH=..\fgluser:..\fglAvecra:..\fglNordic:..\fglDTM:..\fgl

 

Nordic Expert

OSCAR_PROJECT=projExpert

OSCAR_FGLPATH=..\fgluser:..\fglExpert:..\fglNordic:..\fglDTM:..\fgl

 

Nordic Golf

OSCAR_PROJECT=projGolf

OSCAR_FGLPATH=..\fgluser:..\fglGolf:..\fglNordic:..\fglDTM:..\fgl

 

Nordic Iittala

OSCAR_PROJECT=projIittala

OSCAR_FGLPATH=..\fgluser:..\fglIittala:..\fglNordic:..\fglDTM:..\fgl

 

Nordic Interflora

OSCAR_PROJECT=projInterflora

OSCAR_FGLPATH=..\fgluser:..\fglInterflora:..\fglNordic:..\fglDTM:..\fgl

 

Nordic Optic

OSCAR_PROJECT=projOptic

OSCAR_FGLPATH=..\fgluser:..\fglOptic:..\fglNordic:..\fglDTM:..\fgl

 

Nordic Skεnetrafik

OSCAR_PROJECT=projSkanetrafik

OSCAR_FGLPATH=..\fgluser:..\fglSkanetrafik:..\fglNordic:..\fglDTM:..\fgl

 

Nordic Tivoli

OSCAR_PROJECT=projTiv

OSCAR_FGLPATH=..\fgluser:..\fglTiv:..\fglNordic:..\fglDTM:..\fgl

 

Nordic Antell

OSCAR_PROJECT=projAntell

OSCAR_FGLPATH=..\fgluser:..\fglAntell:..\fglNordic:..\fglDTM:..\fgl

 

Nordic Bauhaus

OSCAR_FGLPATH=..\fgluser:..\fglBauhaus:..\fglNordic:..\fglDTM:..\fgl

Nordic Dinners

OSCAR_FGLPATH=..\fgluser:..\fglDinners:..\fglNordic:..\fglDTM:..\fgl

Nordic Espresso

OSCAR_FGLPATH=..\fgluser:..\fglEspresso:..\fglNordic:..\fglDTM:..\fgl

Nordic Hors

;OSCAR_FGLPATH=..\fgluser:..\fglHors:..\fglNordic:..\fglDTM:..\fgl

Nordic Prior

OSCAR_FGLPATH=..\fgluser:..\fglPrior:..\fglNordic:..\fglDTM:..\fgl

Nordic Sibylla

OSCAR_FGLPATH=..\fgluser:..\fglSibylla:..\fglNordic:..\fglDTM:..\fgl

Nordic Svenska Spel

OSCAR_FGLPATH=..\fgluser:..\fglSvSpel:..\fglNordic:..\fglDTM:..\fgl

Nordic Tropehagen Zoo

OSCAR_FGLPATH=..\fgluser:..\fglTropZoo:..\fglNordic:..\fglDTM:..\fgl

Note:
MICROS Retail OSCAR POS- 4GL is an application component embedded in MICROS Retail OSCAR POS and can be called up from there. MICROS Retail OSCAR POS - 4GL is an interpreter for a simple programming language, similar to Basic, that serves the creation of reports, particularly the selection and printing processing of the data from the MICROS Retail OSCAR POS database.


OSCAR_FSMPATH=..\fsm

By use of this environment variable, the MICROS Retail OSCAR POS application is informed about the directory for the FSM files.

FSM stands for Finite State Machine. In these files, the function processes for the terminal program are defined.

 Click on the graphic for further information on files of the MICROS Retail OSCAR POS Message Logger


OSCAR_OMLPATH=..\logs,30

The MICROS Retail OSCAR POS application is informed of the directory for the OML files (OML = MICROS Retail OSCAR POS Message Logger) with this environment variable. The directory for the OML files is defined with parameter "..\logs" and the maximum number of OML files in this directory is stated in parameter ",30".

Normally, status and error messages and information on set debug parameters are stored in file "errlog" and/or "errlog.login" in directory "..\work".

Alternatively, these messages can also be stored in so-called OML files in a specific directory if storage in these files has to be diverted as a result of parameter "OSCAR_CONSOLE=MESSLOG"..


OSCAR_VERSION="Oscar3_003_000"

This environment variable transfers the version no. to the MICROS Retail OSCAR POS application.


OSCARLANG=2

By use of this environment variable, the MICROS Retail OSCAR POS application is informed about the number of the default language. Independent from this setting, a different language can be selected for each process unit.

Go to System -> Configuration -> Process Unit. Call up the process unit for which you would like to define the language by entering the number of the Installation and Process Unit and enter the number of the required language in the field Language.

The following numbers are occupied or reserved for particular languages:

Note:
The use of a particular language requires that this language is included in the files "UiText" and "DbText" and has been read into the MICROS Retail OSCAR POS database by use of the commands "oscar init UiText", "oscar init DbText" and "oscar dofgl.fgl Language" previous to the operation.

Further information on setting up another language can be found under Language.

Attention!
As from MICROS Retail OSCAR POS Version 2.1 the standard is the multidocument user interface. Conversion is not necessary as this has already been completed with command oscar dofgl.fgl LandesLanguage . If the MICROS Retail OSCAR POS standard user interface is to be used for whatever reason, the command oscar dofgl2.fgl LandesLanguage must be completed.


OSCAR_HOSTNAME=

This environment variable informs the MICROS Retail OSCAR POS application about the host name. The host name is the name of the system unit as it has been defined during the network configuration.


OSCAR_SQL=oscar

This environment variable informs the MICROS Retail OSCAR POS application about the name of the ODBC data source. This environment variable may only be set if the MICROS Retail OSCAR POS application works with an SQL database instead of the standard ISAM database.

Normally,  this parameter is deactivated. You can activate this parameter by removing the leading underlines “_“ or “;“ using an editor. This change will only be effective after you restart the MICROS Retail OSCAR POS application.

Note:
Further notes on the operation of the MICROS Retail OSCAR POS application with an SQL database can be found in the documentation MICROS Retail OSCAR POS -SQL.


OSCAR_CLIENTLOADALL=Y

The default here is that when the client database is loaded only the data which matches the language configuration will be loaded, i.e. only the texts (UiText.asc, DbText.asc) and the frames for the configured language. If all data in the client databases is to be stored for any reason this environment variable has to be set with parameter "=Y".


OSCAR_STABLESTATETIME=(default 3600000 Millisekunden.)

As from version MICROS Retail OSCAR POS 4.2 the use of resources can be monitored by the following parameter settings:

·        Memory space (only in Windows)

·        Network connections

·        Timers

·        File descriptors

·        Tasks

·        Handles

When the time defined by the variable OSCAR_STABLESTATETIME (default 3600000 milliseconds) in file "oscar.ini" (Windows or "oscar.def" (Linux) has elapsed, the currently achieved results are stored for future comparisons.

The memory used is checked every 10000 milliseconds. The time can be changed with variable OSCARRAMCHECKINTERVAL. Checks for all other resources are carried out after the current new limits are exceeded.

Every time the limit is exceeded by more than 50% the currently stored limits are written into file ..\work\errlog. A warning is written after completion of the defined Retail OSCAR_STABLESTATETIME. The default value of 50% can be modified with variable OSCAR_RESINRCELEVEL.

In addition to the variables stated above other resource values can be enforced with variable OSCAR_RAMCHECKINTERVAL. This information contains the results of the currently active semaphores, timers, file descriptors and network connections.

Example values for information on resource values:

·        OSCAR_STABLESTATETIME=20000

·        OSCAR_RESINCRLEVEL=10

·        OSCAR_RAMCHECKINTERVAL=5000

·        OSCAR_DUMPWHENINCRLEVELREACHED=Y


Retail OSCAR_RESINCRLEVEL=(per cent value)

Default = 50 %

Description under OSCAR_STABLESTATETIME


OSCAR_RAMCHECKINTERVAL=(value in milliseconds)

Default = 5000 milliseconds.

Description under OSCAR_STABLESTATETIME


OSCAR_DUMPWHENINCRLEVELREACHED=Y

Description under OSCAR_STABLESTATETIME


OSCAR_USER=Username

If no environment variable "OSCAR_USER" was set under Vista and Windows 7, this variable will be set automatically for the windows login user. This allows terminals which work with auto log-in to be operated.

If, however, OSCAR_USER=Username was set oscard starts  the processing units with GUI which are to be started automatically only in sessions of the defined user (if this person is logged on at the processor). This setting is advisable if the users continuously change at a system unit or if the system unit is to be operated via  Remote-Desktop / Terminal-Server.


ADMINDEBUG=Y

The parameter ADMINDEBUG records the Fgl functions that are called up during a Back Office session (administration terminal) in the file errlog.

Note:
Normally,  this debug parameter is deactivated. You can activate this parameter by removing the leading underlines “_“ or “;“ using an editor. This change will only be effective after you restart the MICROS Retail OSCAR POS application.

There will be no output in the file errlog if the environment variable OSCAR_CONSOLE=Y has been activated.


DLLDEBUG=Y

The parameter DLLDEBUG records the used DYNAMIC-LINK LIBRARIES during the runtime of the MICROS Retail OSCAR POS application in the file errlog.

Note:
Normally,  this debug parameter is deactivated. You can activate this parameter by removing the leading underlines “_“ or “;“ using an editor. This change will only be effective after you restart the MICROS Retail OSCAR POS POS application.

There will be no output in the file errlog if the environment variable OSCAR_CONSOLE=Y has been activated.


DLLWAIT=libname

This parameter serves testing purposes only. If this function is activated, the MICROS Retail OSCAR POS application will be stopped as soon as the library (e.g. libdev) has been loaded.

Note:
Normally,  this debug parameter is deactivated. You can activate this parameter by removing the leading underlines “_“ or “;“ using an editor. This change will only be effective after you restart the MICROS Retail OSCAR POS application.

There will be no output in the file errlog if the environment variable OSCAR_CONSOLE=Y has been activated.


DUMMYEBUG=Y

The activation of this parameter informs about the objects lying in the RAM. The output of this information is recorded in the file errlog.

An output in the file errlog requires that the MICROS Retail OSCAR POS POS application is ended correctly, i.e. the MICROS Retail OSCAR POS program must be ended at the back office with the function END and terminal processes have to be ended with the function END. Only if these requirements are met, a complete output will be recorded in the file errlog.

Note:
Normally,  this debug parameter is deactivated. You can activate this parameter by removing the leading underlines “_“ or “;“ using an editor. This change will only be effective after you restart the MICROS Retail OSCAR POS application.

There will be no output in the file errlog if the environment variable OSCAR_CONSOLE=Y has been activated.


SALESDEBUG=Y

If this parameter is activated, status and error messages of the terminal program will be recorded in the file errlog. The output is useful for the error analysis for the MICROS GmbH system support and should only be activated if required.

Note:
Normally,  this debug parameter is deactivated. You can activate this parameter by removing the leading underlines “_“ or “;“ using an editor. This change will only be effective after you restart the MICROS Retail OSCAR POS application.

There will be no output in the file errlog if the environment variable OSCAR_CONSOLE=Y has been activated


SIMPLEUSERMODE=Y

The activation of this parameter prevents an update program from being started more than once simultaneously.


EVDEBUG=Y

If this parameter is activated, event messages of the MICROS Retail OSCAR POS POS program will be recorded in the file errlog. The output is useful for the error analysis by system support and should only be activated if required.

Note:
Normally,  this debug parameter is deactivated. You can activate this parameter by removing the leading underlines “_“ or “;“ using an editor. This change will only be effective after you restart the MICROS Retail OSCAR POS application.

There will be no output in the file errlog if the environment variable OSCAR_CONSOLE=Y has been activated.


KEYBDEBUG=7

This parameter can be activated if a computer keyboard or an ADS keyboard has been configured as a device and if the output is to be recorded in the file errlog.

Note:
Normally,  this debug parameter is deactivated. You can activate this parameter by removing the leading underlines “_“ or “;“ using an editor. This change will only be effective after you restart the MICROS Retail OSCAR POS application.

There will be no output in the file errlog if the environment variable OSCAR_CONSOLE=Y has been activated.


DEVDEBUG=Y

If this parameter is activated, the status messages of the devices configured in the MICROS Retail OSCAR POS application will be recorded in the file errlog. Additional status messages for a particular device can be received via the configuration of further debug parameters in the device configuration.

The output is useful for the error analysis by system support and should only be activated if required.

Note:
Normally,  this debug parameter is deactivated. You can activate this parameter by removing the leading underlines “_“ or “;“ using an editor. This change will only be effective after you restart the MICROS Retail OSCAR POS application.

There will be no output in the file errlog if the environment variable OSCAR_CONSOLE=Y has been activated.


OSCAR_QUICK_DOFGL=Y

When this parameter has been activated the creation date of the FGL files is compared with the details in the database table "doFGL.dat". Only files with later dates are executed with "oscar dofgl.fgl Sprache". This procedure speeds up completion of "oscar dofgl.fgl Sprache"

Note!
If changes are made to environment variables "
OSCAR_OPTIONS" this environment variable should not be set, i.e. after a change in OSCAR_OPTIONS a complete "dofgl.fgl" must always be executed..


RPCDEBUG=Y

If this parameter is activated, the status messages of the network communication of the MICROS Retail OSCAR POS program will be recorded in the file errlog.

The output is useful for the error analysis by system support and should only be activated if required.

Note:
Normally,  this debug parameter is deactivated. You can activate this parameter by removing the leading underlines “_“ or “;“ using an editor. This change will only be effective after you restart the MICROS Retail OSCAR POS application.

There will be no output in the file errlog if the environment variable OSCAR_CONSOLE=Y has been activated.


DBDEBUG=Y

If this parameter is activated, the status messages of the database of the MICROS Retail OSCAR POS program will be recorded in the file errlog.

The output is useful for the error analysis by system support and should only be activated if required.

Note:
Normally,  this debug parameter is deactivated. You can activate this parameter by removing the leading underlines “_“ or “;“ using an editor. This change will only be effective after you restart the MICROS Retail OSCAR POS application.

There will be no output in the file errlog if the environment variable OSCAR_CONSOLE=Y has been activated.


OPERATORDEBUG=Y

If this parameter is activated, the update information of the operator in the sales program will be recorded in the file errlog.

Note:
Normally,  this debug parameter is deactivated. You can activate this parameter by removing the leading underlines “_“ or “;“ using an editor. This change will only be effective after you restart the MICROS Retail OSCAR POS application.

There will be no output in the file errlog if the environment variable OSCAR_CONSOLE=Y has been activated.


NETDEBUG=111111

If this parameter is activated, the network status messages of the MICROS Retail OSCAR POS program will be recorded in the file errlog.

The output is useful for the error analysis for the MICROS GmbH system support and should only be activated if required. Further notes on the general network configuration and the selection of appropriate TCP/IP addresses can be found in the chapter Configuration options for TCP/IP connections.

Note:
Normally,  this debug parameter is deactivated. You can activate this parameter by removing the leading underlines “_“ or “;“ using an editor. This change will only be effective after you restart the MICROS Retail OSCAR POS application.

There will be no output in the file errlog if the environment variable OSCAR_CONSOLE=Y has been activated.


SRVQDEBUG=Y

If this parameter is activated, the number of transactions in the spooler of the MICROS Retail OSCAR POS server will be recorded in the file errlog. If a value is put out which is greater than 2, the execution speed of the individual components of the MICROS Retail OSCAR POS system has to be improved.

The output is useful for the error analysis for the MICROS GmbH system support and should only be activated if required.

Note:
Normally,  this debug parameter is deactivated. You can activate this parameter by removing the leading underlines “_“ or “;“ using an editor. This change will only be effective after you restart the MICROS Retail OSCAR POS application.

There will be no output in the file errlog if the environment variable MICROS Retail OSCAR POS _CONSOLE=Y has been activated.


ODBCDEBUG=Y

If this parameter is activated, the status messages of the ODBC interfaces will be recorded in the file errlog. Activating this parameter is only useful in connection with the ODBC data source used by the MICROS Retail OSCAR POS program.

ODBC is the standard interface for various databases. There are databases for Visual BASIC, Visual C++, ORACLE 8.0 and MS SQL-Server 7.0; in addition, there are drivers for Access, Paradox, dBase, Text, Excel and Btrieve databases.

The output is useful for the error analysis by system support and should only be activated if required.

Note:
Further notes on the operation of the MICROS Retail OSCAR POS application with an SQL database can be found in the documentation MICROS Retail OSCAR POS -SQL.

Attention:
Normally,  this debug parameter is deactivated. You can activate this parameter by removing the leading underlines “_“ or “;“ using an editor. This change will only be effective after you restart the MICROS Retail OSCAR POS application.

There will be no output in the file errlog if the environment variable OSCAR_CONSOLE=Y has been activated.


OMOUSEMODE=1

This option should be activated if the operation at the administration terminal is to be completed via the keyboard instead of with the mouse.

 

 

 

The colours of the foreground and background are defined with parameters OMOUSEMODE1FGCOLORNO= n and OMOUSEMODE1BGCOLORNO= n. The colours linked to the numbers are shown in the Color table.

Parameter = 2 means that a blinking cursor marks the active input field.

The keyboard commands for operation at the administration terminal can be found in the table Key short cuts.

 

Note!
As from version MICROS Retail OSCAR POS 4.3 these parameters are no longer to be found in file "oscar.ini". They are updated in program System -> Configuration -> User network.


OMOUSEMODE1FGCOLORNO=3

If option OMOUSEMODE=1 has been activated this parameter can be used to define the foreground colour for the active input field.

The numbers linked to the colours are shown in the Color table.

 

Note!
As from version MICROS Retail OSCAR POS 4.3 these parameters are no longer in file "oscar.ini". They are updated in program System -> Configuration -> User network.


OMOUSEMODE1BGCOLORNO=10

If option OMOUSEMODE=1 has been activated, the background colour for the active input field can be defined.

The colours linked to the colours are shown in the Color table.

Note!
As from version MICROS Retail OSCAR POS 4.3 these parameters are no longer in file "oscar.ini". They are updated in program System -> Configuration -> User network.


UIDEBUG=XXXX

If this parameter is activated, the status messages of the graphic user interface of the MICROS Retail OSCAR POS application will be recorded in the file errlog. With the activated parameter = 1, the name of the help file will be additionally displayed in the help window.

The output is useful for the error analysis by system support and should only be activated if required.

XXXX is the range from 1 to 4096 for the various modules of the graphic user interface. Some parameters apply for WINDOWS only.

Note:
Normally,  this debug parameter is deactivated. You can activate this parameter by removing the leading underlines “_“ or “;“ using an editor. This change will only be effective after you restart the MICROS Retail OSCAR POS application.

There will be no output in the file errlog if the environment variable OSCAR_CONSOLE=Y has been activated.


FGLTRACE=Y

If this parameter is activated, the status messages of the 4GL files within the runtime will be recorded in the file errlog.

The output is useful for the error analysis by system support and should only be activated if required.

Note:
Normally,  this debug parameter is deactivated. You can activate this parameter by removing the leading underlines “_“ or “;“ using an editor. This change will only be effective after you restart the MICROS Retail OSCAR POS application.

There will be no output in the file errlog if the environment variable OSCAR_CONSOLE=Y has been activated.


UIDLGUNIT=1.0

This parameter has to be activated if the US version of Win NT US version is used as the operating system.


CONFIRMINFUTURE=5

When booking POS transactions, no bookings will be permitted if the terminal date is 7 days in the future. In this case, the date will be adjusted to the current server date. If a value smaller than 7 days is to be permitted for particular reasons, this value has to be set with this environment variable, e.g. CONFIRMINFUTURE=5.

Normally,  this environment variable is deactivated. You can activate this parameter by removing the leading underlines “_“ or “;“ using an editor. This change will only be effective after you restart the MICROS Retail OSCAR POS application.


NOEARLYUPDATER=Y

If this environment variable is applied, POS terminals that are offline at the time the statistical data is picked up (getstatistic) will be ignored. This has the effect that this data will not be sent to the server with the next data pick-up. Therefore, this variable should be applied in exceptional cases only.

Normally,  this environment variable is deactivated. You can activate this parameter by removing the leading underlines “_“ or “;“ using an editor. This change will only be effective after you restart the MICROS Retail OSCAR POS application.


OSCAR_CONSOLE=Y

If this parameter is activated, the output of relevant system and error messages will be recorded in a DOS window instead of the file errlog.

Normally,  this environment variable is deactivated. You can activate this parameter by removing the leading underlines “_“ or “;“ using an editor. This change will only be effective after you restart the MICROS Retail OSCAR POS application.


OSCAR_CONSOLE=MESSLOG

If this parameter is activated the status and error messages will be stored in so-called OML files instead of in file "errlog" or "errlog.login". The environment variable "OSCAR_OMLPATH=..\logs,30" defines the directory and the maximum number of these OML files.

 Click on the graphic for further information on the files of the MICROS Retail OSCAR POS Message Logger.


MESSLOGMILLISECONDS=1

If this parameter is activated, the time stamp of milliseconds will be added in the OML file (e.g. MESSLOGMILLISECONDS=Y or MESSLOGMILLISECONDS=1). The value of this parameter does not matter, only the environment variable must be exist to record in milliseconds. This is only valid for the OML file. There are no changes when working with the errlog file.


OSCAR_MAXOLDLOGS=10

When this parameter is activated, the number of LOG files in directory work.srv will be restricted to 10 LOG files. A value under 10 means that no LOG files will be deleted. If no synchronisation of client database is possible with the server database because a client is offline, the complete client database is always loaded. The value set for "OSCAR_MAXOLDLOGS" should be sensible to reduce the loading of the complete client database to a minimum.

Note:
Please note that deletion of Log files can be defined for a specified number of days later. The value set is shown in program Installation in window Installation condition in field "Hold Log no. of days (0=infinite)”.


MAXSEARCHROWS=1000

If this parameter is activated, the number of the displayed data records in the search function is not allowed to exceed the value defined here. If there are more data records in the database than the value allows to display, the message "too many records" will appear. The search can be continued by de-selecting the data record in the search table and starting a new search via the <F4> key.

The default maximum number of data records the search function is allowed to display is 1000. If you would like to change this value, you have to activate the desired value in this environment variable in the file "oscar.ini".

Normally,  this environment variable is deactivated. You can activate this parameter by removing the leading underlines “_“ or “;“ using an editor. This change will only be effective after you restart the MICROS Retail OSCAR POS application.


InternalCodePage=0-7

Via this parameter, you can adjust the correct conversion of the code page for the input/ output of the connected peripheral devices for the MICROS Retail OSCAR POS application. The various value ranges require that the operating system supports the code pages.

The MICROS Retail OSCAR POS program supports the following internal code pages by linking the appropriae value to the environment variables "InternalCodePage=" (e.g. InternalCodePage=3 to activate the code page Windows 1250 East European Latin font)of file "oscar.ini" (for Windows or "oscar.def" for Unix/Linux).

Val.

Code page

Operating system

Font type

0

Windows 1252

(Windows) / ISO 8859-1 (Linux)

West European / Latin 1

1

ISO 8859-2

(Linux)

East European / Latin 2

2

ISO 8859-15

(Linux)

West European with '€'

3

Windows 1250

(Windows)

East European Latin font

4

Windows 1254

(Windows)

Turkish font

5

Windows 1257

(Windows)

Baltic font

6

Windows 1251

(Windows)

East European Cyrillic font

7

Windows 1253

(Windows)

Greek font

10

Lan code page (DB 0)

 

 

11

Lan code page (DB 1)

 

 

12

Lan code page (DB 2)

 

 

13

Lan code page (DB 3)

 

 

14

Lan code page (DB 4)

 

 

15

Lan code page (DB 5)

 

 

16

Lan code page (DB 6)

 

 

17

Lan code page (DB 7)

 

 

18

Lan code page (DB 8)

 

 

19

Lan code page (DB 9)

 

 

Note:
If additional code pages are used, a code page table with the appropriate values has to be maintained via the update program Systems -> Configuration -> Character Sets.

If additional internal code pages are used, a code page table with the appropriate values has to be maintained via the update program Systems -> Configuration -> Internal Character Set.

Click on graphic for further help on Code page tables.


TOOLBAR_MODE=BIG

The buttons of the toolbar can be zoomed with this parameter. This option must be switched on in file "oscar.ini" before the command "oscar dofgl.fgl language" or "oscar UiDispatch.fgl language" is executed.


PRINTFORMDEBUG=5

The environment variable "PRINTFORMDEBUG=5" in file "oscar.ini" should be activated if the print formats based on the examples provided are to be changed. aktivieren.

 

Activation of this environment variable releases information in file errlog when a receipt is printed. The user can then recognise which print format was active during receipt print.

 

Example:

info(-5- ::printLine first pos: 3 last pos: 16) Grp/Frm/Sect/Cond 100/80/10/1

info(-5- ::printLine use leftspace: 0) Grp/Frm/Sect/Cond 100/80/10/1

info(-5- ::printLine set column: 3) Grp/Frm/Sect/Cond 100/80/10/1

info(-5- ::printLine append text: 16,00) Grp/Frm/Sect/Cond 100/80/10/1

info(-5- ::printLine set column: 8) Grp/Frm/Sect/Cond 100/80/10/1

info(-5- ::printLine append text: %-MwSt) Grp/Frm/Sect/Cond 100/80/10/1

info(-5- ::printLine set column: 15) Grp/Frm/Sect/Cond 100/80/10/1

info(-5- ::printLine append text: v) Grp/Frm/Sect/Cond 100/80/10/1

info(-5- ::printLine set column: 25) Grp/Frm/Sect/Cond 100/80/10/1

info(-5- ::printLine append text:  0,83) Grp/Frm/Sect/Cond 100/80/10/1

info(-5- ::printLine start) Grp/Frm/Sect/Cond 100/80/10/1

 

The print format for the current receipt in print as per the example can be read at the end of each line  (e.g. 100/80/10/1 implies = print format group 100, print format 80 print section 10print rule 1).


UPDATERDEBUG= Y

The MICROS Retail OSCAR POS standard application allows the user to reverse the function Update Installation.

Starting with a DTM order type "UPDATEINSTREMOTE" in head office the branch can initiate an operation by which the log files can be read remotely from head office and the database operation necessary for update of basic data can be done locally on the branch installation.

When this parameter is active status messages for Update Installation remote are written into file errlog.

 

Parameter = Y – the following messages are written into file ..\work.errlog:


NOMDIMAXIMIZE=Y

This parameter defines that the MDI user interface is not shown in full-screen mode.


NoPosStaticFrame=Y

This environment variable defines that the default "Statistic Mask" can be deactivated for all sales program masks. The command "oscar dofgl.fgl Sprache" must be executed after the environment variable has been set in file "oscar.ini".


SALEST3_8TOUCHCOLS=Y

This environment variable defines that the number of columns for the preset key is reduced from 9 to 8 for program T3. The command "oscar dofgl.fgl Sprache" must be executed after the environment variable has been set in file "oscar.ini".


OSCAR_CHECKED_TIME_SYNC=Y

If this variable is set Y (on the POS system unit) and the booking date is more than one day in the future, the date/time of the POS system unit won't be set.


Sales2_To_Specials=Y

This environment variable must be used when the following touch layouts are required. The command "oscar UiSales6To.fgl" has to be performed to generate the touch layouts.

 

Linkage of the touch layouts to the terminal programs can be found in the documentation Terminal program / Touch layout.


GLORY_TIMEOUT=1000

Timeout for the query of the cash balance (InventoryRequest). If GLORY_LOWWATER=Y is set , this setting has no meaning.


GLORY_WAIT=2000

Additional timeout for the query of cash balance (InventoryRequest). If GLORY_LOWWATER=Y is set , this setting has no meaning.


GLORY_LOWWATER=Y

The cash balance is automatically sent by the glory cash machine. No query of the cash balance (InventoryRequest) will be sent anymore.

 


GLORY_DEBUG=Y

Output of status and error messages in the error / OML-file.

 


Index


 Click on the image to return to the Table of Contents.


MICROS Retail Deutschland GmbH
Salzufer 8
D-10587 Berlin

Germany