Tips for efficient troubleshooting

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)
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
Relevant log files (e.g. LyciaStudio logs, application logs, application server logs, LFD logs)
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.

Lycia Version

Execute the following command in Lycia Command Line: gfgl -V

Operating System Info

Run the following commands in the command prompt:

Windows
systeminfo > sysDesc.txt

Linux
uname -a > sysDesc.txt
cat /etc/*elease >> sysDesc.txt
locale >> clientLoc.txt
sudo lshw > sysDesc2.txt

Java Version

On Windows, run the following command in the command prompt: java -version > javaVer.txt

C/C++ Runtime Version

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.txt
g++ --version > g++Desc.txt
ld --version > ldDesc.txt
ldd --version > lddDesc.txt

Configuration Files

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 Querix 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/

Find more information about Lycia configuration files in Lycia Online Tutorials

Log Files

Open the inet.env Lycia configuration file and set QXDEBUG to its full value to get the most detailed logs: QXDEBUG=UuBbSsEedPptLlCcmGOzAzKzQv
Locate the log files and send them to the Querix support team:
- Application logs are stored in the folder specified in listener.xml, which, by default, is
  Windows: C:\ProgramData\Querix\Lycia\logs
  Linux: /opt/Querix/Lycia/logs
- Application server logs are stored in the Jetty configuration folder:
  Windows: C:\ProgramData\Querix\Lycia\jetty\logs
  Linux: /opt/Querix/jetty/logs
- LyciaStudio logs are stored in your workspace .metadata which, by default, is
  Windows: C:\Users\<user>\workspace\.metadata\.log
  Linux: /home/<user>/workspace/.metadata/.log

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:

%HOMEPATH%\Lycia<num>.log

$HOME/Lycia<num>.log

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.