How can we identify the individual map names (i.e., the source or executable maps) contained within each .msl file without referencing the corresponding .msd (Map Source Definition) files in a Linux environment?

and Is there a way to check the status of all launchers present on the server in a single command or script, instead of querying each launcher individually?

I'm not familiar with it on a Linux server but in Windows there's a log file that gets created every time the service starts.  It's located in the logs folder where ITX is installed.

Naming convention is "CompoundSystem-2025-05-23-07-06-46_<server name>.txt"  and it has all of the info you're looking for in each .msl.

For the log files to be created you have to uncomment the line in dtx.ini "; Launcher log types:" so the last line is "LauncherLog=ewsc".

Hope this helps.

Hello 
If you activate the log options in the dtx.ini launcher config file, there is a .txt log file generated by launcher when it starts the system
Here's the option in dtx.ini
; launcher log types - e = error, w = warning, s = startup c = cfg summary
LauncherLog=ewsc

And the txt file produced is named something like   [systemName].msl-[startupDateTime]_[hostName].txt

And to check the status of all Launcher started from a host, there is another option from dtx.ini which produces a .log file with each start/stop/status of a system 
However it doesn't give you all details you could retrieve from querying each launcher individually (such as how many map succeeded or failed ...) 

Hope it helps
rgds

Steve's reference to the CompoundSystem log is the best way.  The Linux log is similar to the Windows log and will list all maps in the msl along with all of the configurations for each watch.  You may need to set the dtx.ini or config.yaml to enable the logging and set the contents you want.

You can also just open the msl file on Linux with a text editor.  The maps and directory paths are in plain text.  You could also build a grep to pull out the map names too if you wanted.  Assuming your maps are in some directory called /maps, something like this:

grep -aho '/maps.\{20\}' yourfile.msl

that will read the binary msl and pull out all instances of "/maps" plus the next 20 chars.  You will get binary data past the ".lnx" or maybe need more than 20 depending on your map names, but it will dump all it finds to the screen.

Jim

Your original post asked about checking the status of all launchers on a server.  The Management Console is specifically designed for this.  You get it by installing the ITX Run-time and Monitoring bundle on a workstation.  The user would need to know the server name (i.e., IP address) of the server where the launcher is running, the launcher listening ports and an ITX username/password that from the Launcher Monitor that has been granted Monitor permission.  You can also start/stop and pause individual systems as well as enable a trace that has information about things like adapter errors on running systems.

The management console can also be run on the server (e.g., in a putty session) using the managementconsole.sh script.  This approach requires that the X windows protocol is enabled on the server and that you have an XWindows server on your workstation.

The management console gives you the current status of each system running in your launcher as well as counts of maps that have executed or failed, and information about which adapters are active and/or have errors associated with them.

If you have multiple launcher processes using different listening ports, you would need to create a server definition for each of them in the Management Console and connect to each of them individually.  I think this still qualifies as being able to see the status of all of your launchers in one place.

Here's a link to the docs in 11.0.1.  (It hasn't changed recently).

https://www.ibm.com/docs/en/ste/11.0.1?topic=mt-management-console

I hope this is useful

Rich