Each terminal emulator that is configured must have a number of backup sessions configured for it. For most emulators, you are required to have one session file for every session that you want to have running at the same time. These are usually stored as separate files.
When you configure an HLLAPI, DDE, or VBA emulator for use with Terminal Launcher, you must input a session file for it to use.
NOTE: Inputting a session file doesn't apply to Generic or Advanced Generic emulators.
To configure Terminal Launcher to use more than one session file:
Launch Terminal Launcher, then click Edit Available Emulators.
Select the required emulator from the Available Emulators window, then click Edit.
Add the backup session files to the Session Files dialog box.
Terminal Launcher can launch only as many emulator sessions as there are session files defined.
NOTE: After the emulator is launched, these session files are executed as a command line parameter. Some emulators (such as QWS3270 Plus) do not have session files. Instead, these emulators have individual sessions stored in the registry. Think of these session files as command line parameters that are passed to the executable.