Could be lots of reasons really and without knowing your system will be hard to diagnose without more information. Some of my questions would be:
- Are you windows, linux, unix environment? I *think* from previous posts you are running Linux? I will answer further from that perspective...
- How are you trying to shut down the launcher?
- Are you trying to execute the command under the same account the launcher is running under by doing an su to the launcher account?
- Are you at the command line and not in a shell such as Midnight Commander (I learned this one the hard way)
- have you issued a pause command prior to asking it to stop? (best practice)
- have you checked for run away jobs after issuing stop and checked why they aren't stopping? You may have to use the kill command to terminate that running process and try again. If it is always the same job then you need to trouble shoot the process that isn't allowing it to shutdown.
Additionally - google AI had these suggestions from the following search prompt (so you can repeat and see documentation links) "itx launcher hung and won't respond to pause command":
"When your ITX Launcher hangs and ignores pause commands, it's often due to connectivity loss with monitored systems, permission issues in the temp directory, or an internal hung process needing a hard kill, requiring you to
manually kill the process (Task Manager on Windows, kill -9 <pid> on Linux) and potentially debug with IBM support by collecting core dumps for analysis. Check for related error logs, ensure correct permissions, and use command-line tools for proper shutdown if possible.
Immediate Actions (To regain control)
-
- Windows: Open Task Manager (Ctrl+Shift+Esc), find the ITX Launcher process, right-click, and select "End task".
- Linux/UNIX: Use
kill -9 <ProcessID> (e.g., kill -9 12345) to force termination, but first try kill -6 <ProcessID> to generate a core dump for IBM support if possible.
Common Causes & Solutions
-
- Lost Connection: The Launcher might appear hung if it loses connection to a remote system it's "watching" (like an NFS share or database).
- Permissions: A crash or hang can occur if the ITX temporary directory lacks write permissions, showing errors like "System <SystemName.msl> has stopped with result 190".
- Internal Hung Process: Sometimes an internal error or a blocked communication task (like a multi-line WTO on z/OS) freezes the console/launcher.
Next Steps (For diagnosing the root cause)
-
- Check Logs: Look at the Launcher logs and system logs for specific error messages or signs of connectivity failure.
- IBM Support: For persistent issues, use the
dtx_ui.sh script (or similar provided tools) to gather diagnostic information and contact IBM support.
- Verify Environments: Confirm that the server, platform, and deployment settings match what's configured in Design Studio."
Hope this helps!
------------------------------
Lisa Edwards
Software Engineer / Subject Matter Expert
Rainbow Data Systems, Inc
------------------------------