Versions Compared

Old Version 7

changes.mady.by.user Elena Sviridenko (Unlicensed)

Saved on

compared with

New Version Current

changes.mady.by.user Alexandr Kudentsov (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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.

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

  1. In Microsoft Visual Studio, open the About dialog.
  2. Click Copy Info.
  3. 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


Note

If any of the configuration files contains 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
  • 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
    Windows: C:\Program Files\Querix\Lycia 3 Development Suite 7.1\Lycia\etc\
    Linux: /opt/Querix/Lycia/etc
  • Anchor
    lyciastudioini
    lyciastudioini
    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



Anchor
logs
logs
Log Files


Note

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

  1. Open the inet.env Lycia configuration file and set QXDEBUG to its full value to get the most detailed logs: QXDEBUG=UuBbSsEedPptLlCcmGOzAzKzQv
  2. 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 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.
ClosedImage RemovedRelated articles:


Anchor
database
database
Database information

Database information

is needed so that

that may be requested by the 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

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

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

  2. Open the ODBC Data Source Administrator, and then double-click the data source name
to open the
  1. . 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
  1. 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

To retrieve the database locales and code pages on the server side:

  1. Run dbaccess
  2. Select a database
  3. Go to Database → Info → NIs