Loading FRX Applications and Application Monitoring
Loading FRX Applications in ARESCommander
FRX plugins can be loaded with the same mechanism as ARES Commander offers for TX or LISP plugins. The most common way is to run APPLOAD command and select your FRX module.
Please refer the below document to explore other ways to load the plugin:
Monitoring Application
The FRX module tracks any functionality that the customer plugin calls, finds any functionality that is not implemented functionality, and detects wrong behavior of the module.
To trace FRX functions, run the FRXLOGGING command. This command will enable a logger palette that can be used for track your last calls of FRX functions. If the palette is not visible you can find it in the list of available palettes (right mouse button click ) under the name “FRX Logging“
The palette will notify about FRX functionality that the plugin calls at runtime, which lets you analyse and investigate an incident that happened during plugin execution. There is the possibility to store the information in file. The The result is a log file named FRXAsserts.log that can be found under: C:\Users\username\AppData\Roaming\ARES Commander Edition x64\crashes\username\sessions\bad\session_XXX.
Setting the EXPERT system variable to 1 in ARES Commander, displays a message box with the not implemented and no equivalent functions that are executed at runtime.
Send the log file to the Graebert team.