You can use the jadclient non-GUI application with the following arguments to recompile all methods in your JADE database. (For details about automating a non-GUI application, see "
jadclient path=database-path
[ini=jade-initialization-file]
schema=RootSchema
app=JadeRecompileAllMethods
endJade
[command-line-arguments]
The command line argument that you can define after the endJade parameter in command=value; format is as follows.
includeAlreadyCompiled=true|false
The following example recompiles uncompiled methods and methods that are in error.
jadclient path=c:\jade\system ini=c:\jade\system\testjade.ini schema=RootSchema app=JadeRecompileAllMethods endJade
To force a recompilation of all previously successfully compiled methods, specify the includeAlreadyCompiled command line argument with a value of true. (The includeAlreadyCompiled argument defaults to false.)
The following example recompiles all methods that had previously successfully compiled.
jadclient path=c:\jade\system ini=c:\jade\system\testjade.ini schema=RootSchema app=JadeRecompileAllMethods endJade includeAlreadyCompiled=true
The JadeRecompileAllMethods application returns a non‑zero exit code 1183 (Uncompiled or in error methods remain) if methods could not be compiled or if any methods did not compile without error. The output is logged to the JadeRecompileAllMethods.log file in the default log directory. The log file contains details of the methods that were not successfully compiled.
The following information is output to stdout.
Number of methods compiled
Number of methods that are in error
Number of methods that could not be compiled because there was no source
If methods are in error, you must access the JADE development environment Methods Status List Browser to view these errors and make the appropriate changes.
The JadeRecompileAllMethods application does not compile methods that are checked out.