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
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.

Anchor
lycia_version
lycia_version
Lycia Version

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

Anchor
os
os
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

Anchor
java
java
Java Version

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

Anchor
c++
c++
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

Anchor
config
config
Configuration Files

Copy these files and include them into the issue report:

inet.env is a Lycia configuration file that contains environment variables used at runtime when running applications via LyciaDesktop and LyciaWeb.

Note
If any of the configuration files contain 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:

Anchor
inet
inet
inet.env
Windows: C:\ProgramData\Querix\Lycia\etc\
Linux: /opt/Querix/Lycia/etc

environ.bat is a Lycia configuration file that contains environment variables used when working with Lycia Command Line (NT).

environ.bat exists only in Image Removed.

In Linux Image Removed, this function is performed by environ:

. environ

env.properties is a Lycia configuration file that contains environment variables used at program compilation in LyciaStudio.

Anchor
environ
environ
environ.bat
Windows: C:\Program Files\Querix\Lycia 3 Development Suite 7.1\Lycia\bin\
Linux: . environ
Anchor
envproperties
envproperties
env.properties
Windows: C:\Program Files\Querix\Lycia 3 Development Suite 7.1\Lycia\etc\
Linux: /opt/Querix/Lycia/lyciastudio/etc/
Anchor
lyciacfg
lyciacfg
lycia.cfg

is a general Lycia configuration file that contains default modules and paths, code generators and database drivers, message file settings, logging channels configurations, etc.:C

Windows: C:\Program Files\Querix\Lycia 3 Development Suite 7.1\Lycia\etc\
Linux: /opt/Querix/Lycia/etc
Anchor
lyciastudioini
lyciastudioini
lyciastudio.ini

is a Lycia configuration file that includes a number of basic LyciaStudio configurations:

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

Anchor
logs
logs
Log Files

Note
If any

configuration

of the log files contain

secret company information - like user names or passwords - you can hide it by masking the corresponding values of environment variables.

But do not delete the environment variables themselves - we need to know that they were set correctly.

Logs

Image Removed

Logs are needed to get the detailed information about the application behavior.

Set

sensitive information (e.g. usernames or passwords), make sure to mask it before sending the files to the Querix Service Desk

Open the inet.env Lycia configuration file and set QXDEBUG to its full value

in order

to get the most detailed logs:

Find and copy

QXDEBUG=UuBbSsEedPptLlCcmGOzAzKzQv

Image Removed

Locate the log files and

then include

send them

into the issue report:

application logs,

AppServer logs,

LyciaStudio logs, and

LFD logs.

to the Querix support team:
- 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

- stored in the folder specified in listener.xml

. By

- , which, by default,

it

- is
  Windows:

CAppServer log files are located

- C:\ProgramData\Querix\Lycia\logs
  Linux: /opt/Querix/Lycia/logs

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).

- Application server logs are stored in the Jetty configuration folder:

C

- Windows: C:\ProgramData\Querix\Lycia\jetty\logs
  Linux: /opt/Querix/jetty/logs
- LyciaStudio logs are

log files that log the operation of LyciaStudio.LyciaStudio logs are located

- stored in your workspace .metadata

. By

- which, by default,

it

- is
  Windows:

C

- C:\Users\<user>\workspace\.metadata\.log
  Linux: /home/<user>/workspace/.metadata/.

logLycia Form Designer logs are log files that

- log

the operation of Lycia Form Designer.

To get Lycia Form Designer logs, you must add these the following 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

Image Removed

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

Anchor
database
database
Database information

Database information that may be requested by the Querix support team includes the following:

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

Image Removed:1

Image Removed

retrieve information about your database driver, follow the instructions below.

Image Added

Run the following commands in the command prompt:C:\Program Files\IBM Informix Client SDK\bin>esql.exe -version > ifxVer.txt
dbaccess -V >> ifxVer.txt

2

Image Removed

Open the ODBC Data Source Administrator, and then double-click the data source name

to open the

. The About IBM Informix ODBC tab

:

Image Removed

3 Image Removed

Copy the information or make a screenshot.

To learn the db driver (ODBC driver and version) on Unix/Linux

Image Removed

will open containing the required information.

Image Added
Run the following commands in the command prompt:/etc/odbcinst.ini
. /$INFORMIXDIR/bin/check_version csdk >> ifxVer.txt

dbaccess

dbaccess -V >> ifxVer.txt

Database driver environment

To learn the db driver environment on Windows

Image Removed, you must get values of the registry branch

Image Added

Use the following records in the registry to get information about your Database driver environment:
HKEY_LOCAL_MACHINE\SOFTWARE\Informix\Environment
HKEY_LOCAL_MACHINE\SOFTWARE\Informix\ONLINE\<db_driver_name>\Environment

Image Removed

To learn the db driver environment on Unix/Linux

Image Removed, perform this command

Image Added

Run the following command in the command prompt:
env >> lnxdrvenv.txt

Database locales and code pages

on the server side

To

learn

retrieve the database locales and code pages on the server side

, you must

:

Step 1

Run

Run dbaccess

.

Step 2

Select

the necessary database.

Step 3

Go to Database → Info → Nls.

Step 4

Copy the information or make a screenshot.

a database
Go to Database → Info → NIs

Versions Compared

Old Version 3

New Version Current

Key

Anchor
lycia_version
lycia_version
Lycia Version

Anchor
os
os
Operating System Info

Anchor
java
java
Java Version

Anchor
c++
c++
C/C++ Runtime Version

Windows without MinGW

Windows, Linux with MinGW

Anchor
config
config
Configuration Files

Anchor
logs
logs
Log Files

Logs

Database information

Anchor
database
database
Database information

Database

driver

Database driver environment

Database locales and code pages

Page Comparison

Versions Compared

Old Version 3

New Version Current

Key

Anchorlycia_versionlycia_versionLycia Version

AnchorososOperating System Info

AnchorjavajavaJava Version

Anchorc++c++C/C++ Runtime Version

Windows without MinGW

Windows, Linux with MinGW

AnchorconfigconfigConfiguration Files

AnchorlogslogsLog Files

Logs

Database information

AnchordatabasedatabaseDatabase information

Database

driver

Database driver environment

Database locales and code pages

Anchor
lycia_version
lycia_version
Lycia Version

Anchor
os
os
Operating System Info

Anchor
java
java
Java Version

Anchor
c++
c++
C/C++ Runtime Version

Anchor
config
config
Configuration Files

Anchor
logs
logs
Log Files

Anchor
database
database
Database information