Oscar Start Parameters
At the start of the MICROS Retail OSCAR POS application various parameters are transferred with -oscar-.
The call-up takes place via the command oscar parameter
The possible parameters are listed in the table below:
|
|
|||
|
|
|
|
|
|
|
|||
|
|
|
||
|
|
|
||
|
|
|||
|
|
|||
|
|
|
||
|
|
|
||
|
|
|
|
|
|
|
|
|
|
|
|
|||
|
|
|
||
|
|
For detailed notes on the various parameters click on the parameter of your choice.
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":
- OSCAR_OPTIONS= Option1:Option2: etc.
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..
start
Via the command oscar start the MICROS Retail OSCAR POS application will be started in multi-user mode and the parameters of file oscar.ini and the data from the server or client database in the directory work.n or work.srv are read and evaluated.
Click on
the image for further help on the file oscar.ini.
In the multi-user mode, a background program (Daemon) controls the execution of the entire MICROS Retail OSCAR POS program, i.e. the start and the control of the server and client processes takes place via the daemon process. If the client and server processes are cancelled due to an error, they will be automatically restarted by the daemon process.
The start of the processes necessary for the MICROS Retail OSCAR POS application will be recorded in the directory work in the file errlog. Possible error messages can also be found there, too.
stop
Via the command oscar stop, the MICROS Retail OSCAR POS application will be ended. All processes will be stopped.
The ending of the MICROS Retail OSCAR POS application and of all processes will be recorded in the directory work in the file errlog. Possible error messages can also be found there, too.
singleuser
Via the command oscar singleuser, the MICROS Retail OSCAR POS application will be started in the so-called single-user mode. In this kind of operation, you can maintain the parameters necessary for the start of the multi-user mode. The single-user mode should generally be used only once to configure the necessary basic data or in exceptional cases, e.g. for service purposes. Changes to data in this operation type can be applied to the server database.
Attention!
Data of already existing client databases cannot be
modified in this kind of operation. Existing client databases definitely have
to be re-loaded after the data modification in the single-user mode.
init
Via the command oscar init, all tables of the MICROS Retail OSCAR POS database will be newly-created.
When new tables are created, there will be a check if ASCII files in the folder asc are to be converted. In the file oscar.ini, there is a corresponding entry (MICROS Retail OSCAR POS_ASCPATH=..\asc) for the asc directory.
Add the file name to the command oscar init if you want to create a new table only for single files, e.g. oscar init article creates a new empty table Article. However, if a file called article.asc is found in the directory asc, a new table will be created for this ASCII file.
Attention!
The execution of the command oscar init,
without additional file names, will have the effect that all tables of the
MICROS Retail OSCAR POS database in the directory work.srv will be
completely overwritten.
Therefore, back up your data of the directory work.srv before executing the command oscar init to avoid a complete data loss by accident.
convert
Via the command oscar convert, the MICROS Retail OSCAR POS server database is converted after a release change.
Note:
When the MICROS Retail OSCAR POS application is started,
there will be an automatic check sum control of all database tables. If a
difference is found, the error message "Database needs convert"
will be generated in the file errlog, and the start of the MICROS Retail
OSCAR POS application will be interrupted. In this case, the MICROS Retail
OSCAR POS POS database must be definitely converted.
Attention!
Back up your data of the directory work.srv
before executing the command oscar convert to avoid a complete
data loss due to an error or the interruption of the conversion.
check
Via the command oscar check, the MICROS Retail OSCAR POS server database tables in the directory work.srv will be checked. Errors and inconsistent files will be recorded.
reindex
Via the command oscar reindex, new index files will be generated for all database tables.
installService
The execution of the command oscar installService USERNAME PASSWORT generates the necessary entries for the services of the MICROS Retail OSCAR POS application in the registration database of the operating system Windows. This command is automatically executed via the installation program for MICROS Retail OSCAR POS.POS
Note:
This command is to be executed for a manual
installation of the MICROS Retail OSCAR POS application only, e.g. if you have
installed two or more parallel MICROS Retail OSCAR POS versions on one system
unit for test purposes and you want to start them in alternative turns.
removeService
Via the execution of the command oscar removeService USERNAME PASSWORT, the necessary entries for the services of the MICROS Retail OSCAR POS PSO application in the registration database of the operating system Windows will be deleted. This command is automatically executed via the installation program for MICROS Retail OSCAR POS.
Note:
This command is to be executed for a manual
installation of the MICROS Retail OSCAR POS application only, e.g. if you have
installed two or more parallel MICROS Retail OSCAR POS application versions on
one system unit for test purposes and you want to start them in alternative
turns.
changeService
This command can be executed in a new MICROS Retail OSCAR POS directory. Via the command oscar changeService, the settings for the services of the MICROS Retail OSCAR POS application will be configured. With the command oscar changeService, the settings, as they have been configured via the command oscar installService, will be adopted.
Note:
This command is only useful if you want to switch
over between two or more locally installed MICROS Retail OSCAR POS applications
versions. The execution of the command oscar
removeService is then unnecessary.
addUserRight
The users stated are assigned their rights to "ServiceLogonRight" with command oscar addUserRight Benutzer . This command only needs to be executed if a Windows user is to use the MICROS Retail OSCAR POS service "oscard".
*.fgl
Via the command oscar *.fgl, a 4GL file will be called up and executed via the 4GL interpreter. When calling up a 4GL script, the file name extension fgl has to be added.
The following command creates the necessary entries for all screen masks in the defined language:
- oscar dofgl.fgl English = MultiDocumentuserInterface (MDI)
- oscar dofgl2.fgl English = Standard User Interface
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. It serves predominantly the creation of reports, particularly
the selection and print processing of the data from the MICROS Retail OSCAR POS
database.
installshop
??
removeShop
???
installGrid
Via the command oscar installGrid, the necessary entries for the external service of the MICROS Retail OSCAR POS application are generated in the registration database of the operating system Windows. This command is automatically executed via the installation program for MICROS Retail OSCAR POS.
Note:
If the MICROS Retail OSCAR POS application is
installed manually, this command must be executed.
removeGrid
Via the command oscar removeGrid, the entries for this service of the MICROS Retail OSCAR POS application are deleted from the registration database of the operating system WIN-NT. This command is automatically executed via the installation program for MICROS Retail OSCAR POS.
Note:
If the MICROS Retail OSCAR POS application is
installed manually, this command must be executed.
isamtosql
Via the command oscar isamtosql, the SQL database tables will be generated from the existing ISAM database tables in the directory work.srv and copied to the SQL database.
The following requirements have to be met to make MICROS Retail OSCAR POS work with an SQL database:
- The database server must have been installed and started in the MICROS Retail OSCAR POS network.
- An appropriate ODBC driver must have been
installed on every MICROS Retail OSCAR POS system unit.
The following ODBC drivers have currently been tested:
Microsoft ODBC driver for Oracle
Intersolv 32-Bit Informix
SQL-Server
Sybase SQL Anywhere - The ODBC data source must have been configured correctly.
- A database named MICROS Retail OSCAR POS must be generated with the SQL server tools.
- A database user with the necessary privileges must be configured.
- In the file oscar.ini, the environment variable "OSCAR_SQL=" must contain the name of the ODBC data source.
sqltoisam
Via the command oscar sqltoisam, the ISAM database tables in the directory work.srv will be generated from an extant SQL database.
installDrawer
????
removeDrawer
???
installWebRep
Via the command oscar installWebRep, the appropriate parameters for the configuration of the Internet server will be set in order to make the MICROS Retail OSCAR POS web reports accessible via browser at the address "http://<host name>/oscrep".
Note:
For the usage of the MICROS Retail OSCAR POS POS
web reports via browser, further settings are necessary. For further notes on
the configuration, go to WEB Reports (ASP).
removeWebRep
Via the command oscar installWebRep, the necessary entries of the MICROS Retail OSCAR POS application for the usage of MICROS Retail OSCAR POS web reports via browser will be deleted from the registration database of the operating system Windows.
Note:
For the usage of the MICROS Retail OSCAR POS POS
web reports via browser, further settings are necessary. For further notes on
the configuration, go to WEB Reports (ASP).
initWebRepParam
Via the command oscar initWebRepParam, the report parameters for the web reports will be generated. After the execution, the report parameters for all reports of the MICROS Retail OSCAR POS application will be generated and occupied with preset values. The modification of single parameters is to be carried out in the update program Parameters -> Misc. Params -> Reportparameter.
Note:
For the usage of the MICROS Retail OSCAR POS POS
web reports via browser, further settings are necessary. For further notes on
the configuration, go to WEB Reports (ASP).
installOCX
Hinweis:
If the MICROS Retail OSCAR POS application is
installed manually, this command must be executed.
client
Via the command oscar client, a particular process unit can be started.
The command is: oscar client -un (n = number of the process unit)
Note:
Starting a process unit via this command requires
that the MICROS Retail OSCAR POS server is running and a relevant process unit
has been configured.
installRepNET
Via the command oscar installRepNET, the appropriate parameters for the configuration of the Internet server will be set in order to make the MICROS Retail OSCAR POS web reports accessible via browser at the address "http://<host name>/oscrep".
Note:
For the usage of the MICROS Retail OSCAR POS POS
web reports via browser, further settings are necessary. For further notes on
the configuration, go to WEB Reports (ASP).
removeRepNET
The call-up of the command oscar removeRepNET deletes the necessary entries of the MICROS Retail OSCAR POS program for the usage of MICROS Retail OSCAR POS web reports via browser in the registry database of the WIN-NT operating system.
Note:
For the usage of the MICROS Retail OSCAR POS POS
web reports via browser, further settings are necessary. For further notes on
the configuration, go to WEB Reports (ASP).
wizard
Via the command oscar wizard, the installation program for the MICROS Retail OSCAR POS application will be started with the prepared installation files.
Note:
Further notes on the installation by use of the
wizard program can be found in the chapter MICROS
Retail OSCAR POS Wizard.
wizardhelp
Via the command oscar wizard, the possible parameters for the start of the installation program MICROS Retail OSCAR POS Wizard will be displayed as follows:
"Usage : oscar wizard [language[Ui|Installation|Company|Branch|DemoData]]"
The command oscar wizard will start the installation tool in MICROS Retail OSCAR POS. Two optional parameters are available.
Language = Specifies the language name. The language name must exist in the database.
Wizardtype = Specifies which wizard to start.
Examples of usage :
oscar wizard = starts the Wizard in English
oscar wizard Deutsch = starts the Wizard in German
oscar wizard English Ui = starts only the Ui Wizard in English
oscar wizard Deutsch Ui = starts only the Ui Wizard in German
createEvents
As from version Oscar 3.5 program System -> User interface -> Screen page -> Layout Prg. will be used to update the keyboard layouts of the screen-based POS. This program allows the user to select the keyboard events from a list during the definition of key functions. This list is created by executing the command "oscar createEvents" in directory work. The execution of this command is only necessary for a new installation or for an update.
addAscFiles
As from version Oscar 3.5 the texts for the
standard languages 1 = German, 2 = English and 3 = French are no longer
together in files UiText.asc and DbText.asc.
In the standard version the files UiText.asc and DbText.asc only contain
language 2 =English. Languages 1 = German and 3 = French will be provided in
separate files and must be added to the files DbText.asc and UiText.asc before
a new language is embedded or prior to update. Adding another language must be
done with command "oscar addAscFiles". After execution of this
command in directory "..\work" the user must then decide which
additional language is to be added to the English version. At present only the
additional languages German and French are on offer. After the choice has been
made, the commands "oscar init UiText" and "oscar init
DbText" as well as "oscar dofgl.fgl lang" must be completed.
Example language selection:
Selection of languages to Oscar database.
add further languages to English(UK).
Enter one or more number of the following list.
Enter the number, separate with comma or
type 'a' for all,
blank or nothing, only English (UK) is used.
0) – DE
1) – FR
init UiText
When oscar init UiText is called up the texts for the operation interface of the MICROS Retail OSCAR POS application is loaded into the database. File "UiText.asc" and the appropriate texts must be available in directory "..\asc\".
Note:
As from Version Oscar 3.5 the texts for the standard languages 1 = German, 2 =
English and 3 = Francais will no longer be together in files UiText.asc and
DbText.asc.
In the standard version files UiText.asc and DbText.asc only have language 2
=English. Languages 1 = Deutsch and 3 = Francais will be supplied in separate
files and must be added to files DbText.asc und UiText.asc before a new
language is embedded or before an update.
Adding languages is done with command "oscar
addAscFiles".
NOTE!
If oscar init is called up
without file names the existing tables of the MICROS Retail OSCAR POS database
in directory work.srv will be overwritten.
Always do a data backup from directory work.srv before command oscar init is called up to ensure that there is not a complete loss of data.
init DbText
When oscar init DbText is called up the texts for the database tables of MICROS Retail OSCAR POS application will be loaded into the database. The file "DbText.asc" and the appropriate texts must exist in directory "..\asc\".
NOTE:
As from Version Oscar 3.5 the texts for the standard languages 1 = German, 2 =
English and 3 = Francais will no longer be together in files UiText.asc and
DbText.asc.
In the standard version files UiText.asc and DbText.asc only have language 2
=English. Languages 1 = Deutsch and 3 = Francais will be supplied in separate
files and must be added to files DbText.asc und UiText.asc before a new
language is embedded or before an update.
Adding languages is done with command "oscar
addAscFiles".
NOTE!
If oscar init is called up
without file names the existing tables of the MICROS Retail OSCAR POS database
in directory work.srv will be overwritten.
Always do a data backup from directory work.srv before command oscar init is called up to ensure that there is not a complete loss of data.
init DB
The database tables will be re-created as defined with command oscar init DB. This command is reserved for developers only.
Achtung!
If oscar init is called up
without file names the existing tables of the MICROS Retail OSCAR POS database
in directory work.srv will be overwritten
Always do a data backup from directory work.srv before command oscar init is called up to ensure that there is not a complete loss of data.
loadxml
Database tables in XML format can be loaded with command oscar loadxml directory file name. In program MICROS Retail OSCAR POS test suite this command can be used to import a database exported in XML format.
virtualDevices
The controller for the virtual devices is started with command oscar virtualDevices . This command is used mainly for testing. Normally, the virtual devices are started automatically as soon as they are configured in the MICROS Retail OSCAR POS application.
NewGuiReg
The recording values for the "GUIHandles", "UserHandles-Quota" and "desktop-heap" for the MICROS Retail OSCAR POS application are adjusted with command oscar NewGuiReg.
When commands oscar InstallService and oscar changeService are executed these settings are checked and if they are below value an error message is sent.
- "GDI-Quota: different to Oscar-Limit, use oscar NewGuiReg."
- "User-Quota: different to Oscar-Limit, use oscar NewGuiReg."
NOTE!
The system must be restarted after completion of "oscar NewGuiReg".
The following values are changed:
|
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows |
||
|
GDIProcessHandleQuota: |
After oscar NewGuiReg |
0x00004000 (16384) |
|
|
standard |
0x00002710 (10000) |
|
USERProcessHandleQuota: |
After oscar NewGuiReg |
0x00004650 (18000) |
|
|
standard |
0x00002710 (10000) |
|
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\SubSystems |
||
|
Windows: |
After oscar NewGuiReg |
SharedSection:....,8192,.... |
|
|
standard |
SharedSection:....,3072,.... |
mijnid
Mit dem Kommando mijnid wird
mijnid unreg
With the command mijnid unreg
FDMClient reg
With the command FDMClient reg
FDMClient unreg
With the command FDMClient unreg
installPCWSApi
With the command installPCWSApi
createOscarTile
With the command pinToTaskbar the tiles for the start screen on Windows 8.1 and Windows Server 2012 will be created.
pinToTaskbar
With the command pinToTaskbar the icons "OscarCmd", "OscarStart" und "OscarStop" will be pinned on the task bar for Windows user of Windo0ws 8.1 and Windows Server 2012.
setOscarEnvs
With the command setOscarEnvs the relevant environment variables will be set for Windows 8.1 und Windows Server 2012. On a new installation this command must be called first.
Click on
the image to return to the Table of Contents.
Salzufer 8
D-10587 Berlin