PC SOFT

ONLINE HELP
FOR WINDEV, WEBDEV AND WINDEV MOBILE

Home | Sign in | English US
  • Overview
  • JNL_FILES.FIC file
  • JNL_OPERATION.FIC file
  • JNL_USERS.FIC file
WINDEV
WindowsLinuxUniversal Windows 10 AppJavaReports and QueriesUser code (UMC)
WEBDEV
WindowsLinuxPHPWEBDEV - Browser code
WINDEV Mobile
AndroidAndroid Widget iPhone/iPadApple WatchUniversal Windows 10 AppWindows Mobile
Others
Stored procedures
Structure of log files (HFSQL Client/Server)
HFSQL Client/ServerAvailable only with this kind of connection
Overview
When logging a HFSQL Client/Server data file, the following files are automatically created:
JNL_FILES.FICDescription of logged files.
JNL_OPERATION.FICDescription of actions performed on a logged file.
JNL_USERS.FICDescription of users who perform an action on a logged file.
xxxJNL.FICFile created for each logged file. Contains the value of records used before and after each operation.
These files are created according to the following structure:
1. __JNL directory
This directory contains:
  • The file log
  • The user log
  • The operation log
  • For each logged file of each database, the corresponding log file. The tree structure used corresponds to the tree structure of the data files associated with the database.
For example, if the Orders file of DataApplicationA is logged, the __JNL\DataApplicationA sub-directory will contain the OrdersJNL.FIC file.
Another example: if the Customer file of DataApplicationB is logged, the __JNL\DataApplicationB\Customer sub-directory will contain the CustomerJNL.FIC file.
2. Directory of database DataApplicationA
3. Directory of database DataApplicationB
This page presents the structure of these files.
Note: From version 19, HFSQL is the new name of HyperFileSQL.
JNL_FILES.FIC file
The different items found in JNL_FILES.FIC are as follows:
JNLFile_IDFile identifier.
Source_DB_File_LocationName of database + '\' + relative path of log file.
Source_File_GUIDGUID of the logged file.
JNL_File_GUIDGUID of write-to-file log.
JNL_OPERATION.FIC file
The different items found in JNL_OPERATION.FIC are as follows:
Operation_IDIdentifier of the operation.
USER_IDIdentifier of user who performs the operation. This identifier corresponds to the identifier of JNL_USER.Fic
JNLFile_IDIdentifier of logged file where the operation is performed. This identifier corresponds to the identifier of JNL_FILES.Fic.
WLFunction_IDIdentifier of WLanguage function used in the program. To find out the name of the WLanguage function used, see the ListeDéfinitionHF.WL file (found in the "Personal\Extern\" sub-directory of product)
Server_TimeDate of operation on the server (in UTC format, universal time)
Record_NumberNumber of the modified record
Source_Record_Backup_IDIdentifier in the file of values. Corresponds to the record value before the operation.
Modified_Record_Backup_IDIdentifier in the file of values. Corresponds to the record value after the operation.
HLogInfoMsgValue defined by HLogInfo.
HPost_IDText defined by HPost.
JNL_USERS.FIC file
The different items found in JNL_USERS.FIC are as follows:
USER_IDIdentifier of the user.
LoginLogin of user.
Workstation_NameName of user computer.
Workstation_IPAddressIP address of user computer.
ApplicationApplication name
The *JNL.Fic file contains:
  • the items found in the table below,
  • all the logged items of the corresponding logged HFSQL file.
USER_IDIdentifier of the user who performed the operation. This number is used to identify the record in JNL_Users.Fic
Record_NumberNumber of the record in the initial logged file.
Record_StatusStatus of the record (modified, deleted, added, ...)
WLFunction_IDIdentifier of WLanguage function used in the program. To find out the name of the WLanguage function used, see the ListeDéfinitionHF.WL file (found in the "Personal\Extern\" sub-directory of the product used)
Server_TimeDate of operation on the server (in UTC format, universal time)
HLogInfoMsgValue defined by HLogInfo.
HPost_IDText defined by HPost.
IDJNLIdentifier of the log
Minimum required version
  • Version 10
This page is also available for…
Comments
Click [Add] to post a comment