/A
|
Open the Administration panel, limited to the Upgrade section, right after logon.
|
/B
|
Disable version check. Prevents PANTHEON from checking whether the build numbers of the executable and the database are the same.
|
/BCKP
|
Backup database
/BCKP:EXE .. backup of programs
/BCKP:ALL .. backup databases and programs
/BCKP:DB= DATABASENAME1;DATABASENAME2 .. backup of selected databases.
/DATABASES:FILE=FileName.txt .. create a FileName.txt file on a computer disk or on location where Pantheon.exe is located. If .txt file is located in the same directory as Pantheon.exe then it is enough to just enter a name of the .txt file: /BCKP:FILE=FileName.txt. If .txt file is located elsewhere then a path in a parameter must also be defined /BCKP:FILE=E:\Datalab\FileName.txt. Databases in .txt file must be in one column, one database in each row with no separators inbetween. Parameter can be used for local backup or Cloud backup.
Backup to Cloud
In order to be able to use the functionality of backing up to Cloud, This Company/Our company must have a VAT No. (tax number) entered.
/BCKP:FULL .. full backup is activated
/BCKP:DIFF ... differential backup is activated
/BCKP:CLOUD ... upload to cloud after creating backup (If CLOUD parameter not included, backup to disk is executed)
/BCKP:PWD=<Password> ... Password for 7z file
Example: /L=AD:password /BCKP:DB=DATABASENAME /BCKP:FULL /BCKP:CLOUD /BCKP:PWD=Password
|
 |
A differential backup is a type of backup that copies all the data that has changed since the last full backup. For example, if a full backup is done on Sunday, Monday's differential backup backs up all the files changed or added since Sunday's full backup. The differential backup performed on Tuesday then backs up all the changed files since Monday's full backup, including the files changed on Tuesday -- and so on for the rest of the week.
If a full restore is needed at some point in time, only the last full backup and latest differential backup are required.
|
/I
|
Open the Change registered user panel right after logon.
|
/INI="<IniFileName>"
|
Run PANTHEON using the .ini file specified between the quotes.
More information about the .ini file.
|
/L=uid:pass
|
Log on automatically with the user name uid and password pass.
Useful mostly for automatization.
|
/LD
|
Log on as domain user. More secure than /L=uid:pass which reveals both username and password. Learn more in Automatic domain user logon.
|
/NOCD
|
Disable selecting companies at logon.
|
/MFSTART
|
Enable use of normal work orders (found in PANTHEON SE and ME) and scheduled work orders (in PANTHEON MF) at the same time. This is aimed primarily at the transitional period when gradually switching from MRP to MRP II.
Normal work orders
(in PANTHEON SE, ME) |
Scheduled work orders
(in PANTHEON MF) |
MF z /MFSTART |
Work orders without scheduling
(PANTHEON) |
Work orders with scheduling
(HEFAIST) |
Work orders with and without scheduling
(PANTHEON + HEFAIST) |
|
In this case, available stock is calculated by taking into account the gross quantity required to complete a work order. |
|
/MFOFF
|
Disable MRP II (PANTHEON MF) and show only functions of simple manufacturing. |
/MT
|
Enable MT manufacturing, which is used only for keeping track of finished work and materials consumption. |
/S=yyy
|
Autorun DPA with the ID yyy. The DPA is executed after logon and when it is finished, PANTHEON is closed. In combination with the /L parameter, a DPA can be executed fully automated.
Example
"c:\datalab\pantheon.exe" /S=A01
"c:\datalab\pantheon.exe" /S=A01 /L=UU:abc
Warning!
- Such a DPA must not require user input like additional parameters.
- Such a DPA must not contain reports, overviews, or editors.
- If an error occurs in the DPA, it is logged to the system log and the DPA is terminated.
Use
For example, you want a list of outstanding debts e-mailed to the sales manager every morning.
- First, you have to design a DPA that queries the database for outstanding debts and sends them to the appropriate e-mail address. Let us assume this DPA has the ID A01.
- Define a new scheduled task, that runs "c:\datalab\PANTHEON.exe /S:A01 /L=user:pass" every morning at 5 AM.
- The DPA will be run every morning at 5 AM and, if no errors occur, will close after it has finished its task.
|
/U
|
Upgrade PANTHEON automatically after logon. PANTHEON is closed after the upgrade is finished.
In combination with the /L parameter, the upgrade can be fully automated.
If you want regular automatic upgrades, it is recommended to create a new user specifically for that and give him only authorizations for upgrades. This is for reasons of security, preventing unauthorized users from accessing the database.
An example would be:
"C:\Program Files\DataLab\Pantheon.exe" /U /L=UU:abc
Add this to Scheduled tasks to get a fully automated upgrade at a convenient time.
|
/WN=ComputerName
|
Set the name of the computer that PANTHEON is using (for some computer-dependent settings, like printers) if PANTHEON is running on a Terminal Server.
The Windows API function that returns the computer name, returns the name of the computer the Terminal Server runs on, not the name of the Terminal Client.
|
/ZE=param
|
Parameter for OLAP cube processing (used by ZEUS).
Available options:
/ZE=FULL
(Re)create and process all cubes.
/ZE=FULL(Prodaja;Zaloga)
(Re)create and process cubes of Sales and Stock.
There must be no spaces between the word FULL and the opening parenthesis.
/ZE=REF
Refresh data in all cubes.
/ZE=REF(Prodaja)
Refresh data in Sales cubes.
Add the following line to Scheduled tasks for regular automated cube processing (e.g. at night).
"c:\Program Files\DataLab\Pantheon.exe" /L=uid:pass /ZE=FULL
|
PANTHEON automatically exits after processing cubes with the /ZE parameter. Therefore it is not recommended using the /ZE parameter together with other command line parameters (except /DSH) that perform tasks at PANTHEON start. |
|
/DSH
|
Parameter for processing and filling tables that are used for data prefetching.
To prefetch data for Dashboard components in the default database:
/DSH
To prefetch data for Dashboard components in all databases on the database server:
/DSH=ALL
|
The parameter /DSH=ALL works for all components, except those that show synthetic data. Dasboards with such components are: Activity Ratios, Profitability Ratios, Operation Efficiency, Quick Overview of Business Ratios, Altman Z-Score, Chesser Ratios, DuPont Financial Ratios, Kralicek Quicktest, Zmijewski Ratios, and Debt Ratios, and to a lesser extent on some other dashboards. |
To prefetch data for dashboard components in the listed databases:
/DSH=ALL(DB_1;DB_2;DB_n)
|
The parameter /DSH=ALL(DB_1;DB_2;DB_n) works all components, except those that show synthetic data. Dasboards with such components are: Activity Ratios, Profitability Ratios, Operation Efficiency, Quick Overview of Business Ratios, Altman Z-Score, Chesser Ratios, DuPont Financial Ratios, Kralicek Quicktest, Zmijewski Ratios, and Debt Ratios, and to a lesser extent on some other dashboards. |
|
PANTHEON automatically exits after prefetching data with the /DSH parameter. Therefore it is not recommended using the /DSH parameter together with other command line parameters (except /ZE) that perform tasks at PANTHEON start. |
|
/DREP
|
Creates reports of existing dashboard reports.
/DREP(ReportID_1,;ReportID_2;...;ReportID_n)
Example
/DREP(I00000;I00001)
|
PANTHEON automatically exits after creating reports with the /DREP parameter. Therefore it is not recommended using the /DREP parameter together with other command line parameters that perform tasks at PANTHEON start. |
|
/model
|
Set which PANTHEON edition to use:
/MF - PANTHEON MF
/ME - PANTHEON ME
/GE - PANTHEON GE
/SE - PANTHEON SE
/RE - PANTHEON RE
/LT - PANTHEON LT
If this parameter is not specified, the highest available edition is used (e.g. MF). If the specified edition is not available (no license), the highest licensed edition is started.
You can find an example of a combination of SE and LT editions in Licencing and Serial Numbers under Accounting Firm with Terminal Access.
|
/SSL
|
This parameter forces PANTHEON to connect to SQL Server through SSL - an encrypted connection. This means that the data transactions are protected from unauthorized eavesdropping. For this to work both the server and the client must have a certificate installed. Read more in Encrypting SQL Server Connections. |
/UDatabasesFile
|
/UDatabasesFile=DatabaseList.txt. Parameter must also be given the name of a .txt file which lists the database that you want to upgrade. If the .txt file is located in the same location as Pantheon.exe then the parameter is not necessary to define the entire path to the file, otherwise it is necessary to determine the further path. The names of the databases in the file are separated by enter, we do not use any punctuation such as comma or semicolon. example:
DATABASE1
DATABASE2
DATABASE3
|
/UDatabaseName
|
Defines which database is used for Pantheon client to connect to. Parameter takes precedense over parameter DATABASENAME in Datalab.ini file. Example: /UDatabasName="DATABASE2" |
| /ServerName |
Defines which server is used for Pantheon client to connect to. Parameter takes precedense over parameter SERVERNAME in Datalab.ini file. Example: /ServerName="DATALABX" |
| /UMetadb |
Defines meta database for upgrade. Example: /UMetadb="DATABASE2" |
| /UType=A |
Upgrade will be executed with ALPHA structures |
| /UType=B |
Upgrade will be executed with RC (release candidate) structures |
| /UDIR |
Defines the path for upgrade which will be used for Pantheon upgrade. Parameter takes precedense over defined directory path already set in Clotho. Example: /UDIR="E:\datalab\upgrade\" |
| /UDownload |
Newest structures are transfered for upgrade |
| /UCHGCOLLATE |
During upgrade collation change is executed. Collation of the database in changed (if different) to the collation of the server (instance). |
| /CLTRGCOLLATION |
During upgrade collation change is executed to a specified collation in a parameter. Example /CLTRGCOLLATION=Slovenian_CI_AS. Parameter is used in combination of parameter /UCHGCOLLATE that activates collation change. Example /UCHGCOLLATE /CLTRGCOLLATION=Slovenian_CI_AS. |
| /LOG |
Path to log file is specified. Usefull for creating log for supporter. Path must be valid and Pantheon can write to the path location. |
| /LOGSEVERITY=[1...5] |
Multiple levels of error logging are available in Pantheon. If value 5 is set, all errors are logged. But this makes log file huge and unreadable. Usefull for creating log for supporter. |
| /SQLProvider=Auto |
Provider auto |
| /SQLProvider=Native |
Native client provider |