The symlinks would seem to be the root cause but I’m betting it’s the environment variables created by the setup script. if you are not running a different setup script then you are still pointing to ITX and not itx02.
two options. We run many concurrent launcher engines on one server using one of two methods. Typical method is to use two different accounts. Second account points to and sets up itx02. We set up file and dir permissions to use the group value to let the two accounts interact and navigate the common or shared areas. I have eight concurrent engines running on one server under separate accounts this way.
the other method is to set up a single install config to run multiple launcher instances. Need to rework the launcher admin.bin file to do that plus explicitly name the msl files you want each to run. This also requires extending the port range to handle all established engines I have one install that runs four separate engines this way.
I have never tried to do this using symlinks for the static ITX files though but it should work with the ones you have linked. Bottom line is it is very doable to run multiple launchers on one Linux server once you get the configuration built
Jim