If you can reproduce the problem, consider the conditions under which you can do so:
On z/OS, you can issue commands from the console, the syslog, or by submitting a batch job. You enter customization commands from an OMVS session. Console commands that you enter from the console or syslog might be converted to uppercase, depending on the system configuration. This can cause some commands, such as mqsichangetrace, to fail, especially if these commands contain parameters that must be lowercase. An error message indicating that the execution group is not available might be caused by the execution group name being in the wrong case. The same can happen on message flows.
On Windows, the environment for the broker comes from the system settings, not from a particular user's variables. However, the user's variables affect non-broker commands.
On UNIX platforms, only the service ID specified when the broker was created can start a broker.
On Windows, any authorized user can start a broker.
Related concepts
Flow debugger overview
Trace
Related tasks
Diagnosing errors
Making initial checks
Are the UNIX environment variables set correctly?
Using trace
Problems when developing message flows
Related reference
Commands
z/OS utility jobs
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
au13560_ |