In the case you found a bug in Lycia or need technical assistance, it would be a great help for our support team if you gather as much information as possible about the issue. This would allow for its faster reproducing and resolving.
- Lycia version
- Operating system & Database
- Java version, C/C++ runtime version (on demand)
- Relevant log files (e.g. LyciaStudio logs, application logs, application server logs, LFD logs)
- Lycia configuration files (e.g. inet.env, environ.bat, lycia.cfg, env.properties, lyciastudio.ini), which would help the Querix support team recreate your configuration
- Issue description (steps to reproduce, expected result, observed result, test program)
Below, you will find the instructions on how to obtain all the mentioned information.
Anchor lycia_version lycia_version
Lycia Version
| lycia_version | |
| lycia_version |
Execute the following command in Lycia Command Line: gfgl -V
| Anchor | ||||
|---|---|---|---|---|
|
Run the following commands in the command prompt:
Windowssysteminfo > sysDesc.txt
Linuxuname -a > sysDesc.txtcat /etc/*elease >> sysDesc.txtlocale >> clientLoc.txtsudo lshw > sysDesc2.txt
| Anchor | ||||
|---|---|---|---|---|
|
On Windows, run the following command in the command prompt: java -version > javaVer.txt
| Anchor | ||||
|---|---|---|---|---|
|
Windows without MinGW
- In Microsoft Visual Studio, open the About dialog.
- Click Copy Info.
- Send the copied information to the Querix support team.
Windows, Linux with MinGW
Run the following commands in the command prompt:gcc --version > gccDesc.txtg++ --version > g++Desc.txtld --version > ldDesc.txtldd --version > lddDesc.txt
| Anchor | ||||
|---|---|---|---|---|
|
| Note |
|---|
If any of the configuration files contains sensitive information (e.g. usernames or passwords), make sure to mask it before sending the files to the service desk. |
Here is the list of Lycia configuration files that might come in handy:
- inet.env
Windows: C:\ProgramData\Querix\Lycia\etc\
Linux: /opt/Querix/Lycia/etc - environ.bat
Windows: C:\Program Files\Querix\Lycia 3 Development Suite 7.1\Lycia\bin\
Linux: . environ - env.properties
Windows: C:\Program Files\Querix\Lycia 3 Development Suite 7.1\Lycia\etc\
Linux: /opt/Querix/Lycia/lyciastudio/etc/ - lycia.cfg
Windows: C:\Program Files\Querix\Lycia 3 Development Suite 7.1\Lycia\etc\
Linux: /opt/Querix/Lycia/etc - lyciastudio.ini
Windows: C:\Program Files\Querix\Lycia 3 Development Suite 7.1\Lycia\LyciaStudio\
Linux: /opt/Querix/Lycia/lyciastudio/
| Info |
|---|
Find more information about Lycia configuration files in Lycia Online Tutorials |
Logs
Logs are needed to get the detailed information about the application behavior.
Set QXDEBUG to its full value in order to get the most detailed logs:
QXDEBUG=UuBbSsEedPptLlCcmGOzAzKzQv
Find and copy log files and then include them into the issue report:
- application logs,
- AppServer logs,
- LyciaStudio logs, and
- LFD logs.
Application logs are logs initialized at the moment of application launch and are created every time you run the application:
Application log files are located in the folder specified in listener.xml. By default, it is:
These logs can also include the information about additionally created dump files:
dump file *.dmp -attach dump file
AppServer logs are log files that log the operation of the application server (currently, Jetty).
AppServer log files are located in the Jetty configuration folder:
LyciaStudio logs are log files that log the operation of LyciaStudio.
LyciaStudio logs are located in your workspace .metadata. By default, it is:
Lycia Form Designer logs are log files that log the operation of Lycia Form Designer.
To get Lycia Form Designer logs, you must add these properties to lyciastudio.ini after -vmargs:
-Dcom.querix.fgl.forms.designer.renderer=cef
-Dcom.querix.fgl.forms.designer.render.arg.log-file=c:/temp/ceftmp.log
-Dcom.querix.fgl.forms.designer.render.arg.log-severity=verbose
-Dcom.querix.fgl.forms.designer.jslog=C:/temp/fd_scripts.js
Additional logs can be found here:
If any log files contain secret company information - like user names or passwords - you can hide it by masking the corresponding values.
But do not delete the log itself - we need to know what it said beside your secret information.
Database information
Database information is needed so that Querix support team could use the same database as the one that has encountered the issue.
Check out this information, copy the files and make the necessary screenshots, then include them into the issue report:
- database driver (ODBC driver and version),
- database driver environment, and
- database locales and code pages on the server side.
Database driver (ODBC driver and version)
To learn the db driver (ODBC driver and version) on Windows 
:
1 | C:\Program Files\IBM Informix Client SDK\bin>esql.exe -version > ifxVer.txt dbaccess -V >> ifxVer.txt |
2 | Open the ODBC Data Source Administrator, and then double-click the data source name to open the About IBM Informix ODBC tab:
|
3 | Copy the information or make a screenshot. |
To learn the db driver (ODBC driver and version) on Unix/Linux 
:
/etc/odbcinst.ini
. /$INFORMIXDIR/bin/check_version csdk >> ifxVer.txt
dbaccess -V >> ifxVer.txt
Database driver environment
To learn the db driver environment on Windows , you must get values of the registry branch:
HKEY_LOCAL_MACHINE\SOFTWARE\Informix\Environment
HKEY_LOCAL_MACHINE\SOFTWARE\Informix\ONLINE\<db_driver_name>\Environment
To learn the db driver environment on Unix/Linux , perform this command:
env >> lnxdrvenv.txt
Database locales and code pages on the server side
To learn the database locales and code pages on the server side, you must:
Step 1 | Run dbaccess. |
Step 2 | Select the necessary database. |
Step 3 | Go to Database → Info → Nls. |
Step 4 | Copy the information or make a screenshot. |