To be able to record properly, the AtcgRecordApp application must be run as a standard (fat) client. A presentation (thin) client cannot be used because many of the required GUI event method calls are suppressed if there is no explicit user code in them.
Single-user mode cannot be used because the load of the generated class file is done with an external batch schema load (jadloadb) standard client.
The AtcgReplayApp and AtcgControlApp applications can be run as standard (fat) or presentation (thin) clients. As the AtcgControlApp application starts the AtcgRecordApp application in its own node when using clean‑start mode, the AtcgControlApp application can be used only be used in thin client mode only when you set the value of the CleanStartMode parameter in the [ATCG] section of the JADE initialization file to false. (This parameter is true, by default.)
Typically, the JADE development environment is run as a fat client, the AtcgControlApp application is started from the development environment, and the AtcgRecordApp and AtcgReplayApp applications are started from the AtcgControlApp application. All applications are therefore run in the same fat client node. All three applications run in the AtcgTestCodeSchema.
ATCG can be used with older releases of JADE, including JADE 2016 and JADE 7.1.