Versions Compared

Old Version 2

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

Saved on

compared with

New Version 3

changes.mady.by.user Elena Sviridenko (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.

  • 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)
  • Relevant 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)


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:Execute this command in a command line: java -version > javaVer.txt


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

On Image Removed

Windows without MinGW

Step 1

Open
  1. In Microsoft Visual Studio, open the About dialog
in Microsoft Visual Studio
  1. .

Step 2

Press the
  1. Click Copy Info
button
  1. .

Step 3

Paste this information into a text file, then include this file to the issue report.

Image Removed

On Image Removed and Image Removed with MinGW
  1. 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.

t
ClosedImage RemovedRelated articles:

Configuration files

Image Removed

Configuration files are needed so that Querix support team could configure the system in the proper way.

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.

C:\ProgramData\Querix\Lycia\etc\
/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 .

In Linux , this function is performed by environ:

. environ

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

C:\Program Files\Querix\Lycia 3 Development Suite 7.1\Lycia\etc\
/opt/Querix/Lycia/lyciastudio/etc/

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:\Program Files\Querix\Lycia 3 Development Suite 7.1\Lycia\etc\
/opt/Querix/Lycia/etc

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

C:\Program Files\Querix\Lycia 3 Development Suite 7.1\Lycia\LyciaStudio\
/opt/Querix/Lycia/lyciastudio/

If any configuration 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.


ClosedImage ModifiedRelated articles:

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:

C:\ProgramData\Querix\Lycia\logs
/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).

AppServer log files are located in the Jetty configuration folder:

C:\ProgramData\Querix\Lycia\jetty\logs
/opt/Querix/jetty/logs

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

LyciaStudio logs are located in your workspace .metadata. By default, it is:

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

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:

%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 ModifiedRelated articles:

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.