At the end of a recording session, you click the Generate and Load button. The rrmsg.log is read in by the parseInputFile method, extracting code fragments based on the parsing tokens described in "Parsing Tokens", earlier in this chapter.
The code fragments are saved to a number of arrays and flat files. The arrays and files are then combined into a .cls file by the genClassFile method . The .cls file is then loaded into the database using jadloadb, the batch Schema Load utility. All of the files involved are in the logs folder for the database.
In general, it is best to avoid complexity in the parseInputFile method. Its processing is of necessity quite convoluted, with some code fragments needing to be attached at the beginning of the prior method, or called from the handleShowModal method instead of the runTest method, and so on. The complexity is much more easily handled at capture time, when all of the original objects are easily accessible. If something extra needs to be generated, take care to minimize changes to the parseInputFile method.
The fact that the .cls file contains jadeVersionNumber "6.2.15" indicates that it is not intended to be replayed on a database with a JADE version older than 6.2.15. It is not an indication of the level at which it was recorded.