If no user exits are active then this feature has no effect on performance.
如果没有任何用户出口是活动的，则此功能对性能没有影响。
In Message Broker, user exits are supported only in C or C + + programming language.
在MessageBroker中，用户出口仅支持使用c或c++编程语言。
Every user exits should implement two mandatory functions defined in BipCpi.h header file.
每个用户出口应该实现BipCpi.h头文件中定义的两个必备函数。
After the user exits are written, they are compiled and made available to Message Broker.
编写用户出口以后，对其进行编译并使其对Message Broker可用。
Any changes made to the message assembly by a user exit will be visible to subsequent user exits.
用户出口对消息组装做出的任何更改都将对后续的用户出口可见。
User exits are not limited to built-in nodes, they are applicable to all user defined plug-in nodes.
用户出口并不仅限于内置节点，它们适用于所有用户定义的插件节点。
For each of these events, Message Broker lets you use the user exits to access specific information.
对于这其中每个事件，MessageBroker允许您使用用户出口访问特定的信息。
If user exits are registered and activated then performance is affected depending on the performance of the user's code within those exits.
如果注册并激活了用户出口，则性能会受到影响，具体取决于那些出口中的用户代码的性能。
Note: At point (1), the way user exits are invoked on the built-in input nodes is slightly different from the user-defined input nodes.
注意：在点(1)处，在内置输入节点上调用用户出口的方式与在用户定义的输入节点上稍有不同。
The API consists of utility functions that can be invoked from user exits and functions that are mandatory to be implemented inside user exits.
API包括可以在用户出口中调用的实用工具函数，以及必须在用户出口中实现的函数。
User exits are user or vendor-provided functions that can be invoked by Message Broker. These invocations can be triggered by the following events
用户出口是用户或供应商提供的可由MessageBroker调用的函数。
The user must use the host systems file access controls on the directory configured for user Exits Path to ensure that the library is not vulnerable.
用户必须在为用户出口路径配置的目录上使用主机系统文件访问控制，以确保库不容易受到攻击。
It lets you track message at certain points in their life cycle by invoking custom code from user exits while the message is passing through the message flow.
它允许您在消息通过消息流传递时调用用户出口中的自定义代码，从而在消息生命周期中的某个点跟踪消息。
Many user exits can be registered, in which case they are invoked in a defined order (see the reference on the mqsichangeflowuserexits command for details on this order).
可以注册多个用户出口，在这样的情况下，将按照已定义的顺序调用它们(有关该顺序的详细信息，请参阅有关mqsichangeflowuserexits命令的参考资料)。
If multiple channel exits are defined, you can define multiple sets of user data, separated by a comma.
如果定义了多个通道出口，则可以定义多个以逗号分隔的用户数据集。
If you define more channel exits than user data, the user data for the remaining channel exits will be a blank string.
如果定义的通道出口多于用户数据，则剩余通道出口的用户数据将为空字符串。
If the user's home directory is not present, it exits and does not allow the user to log in.
如果用户的主目录不存在，它就退出，不允许用户登录。
Channel exits are user code that is run at defined points in the life cycle of a WebSphere MQ channel.
通道出口是在WebSphereMQ通道生命周期中的定义点运行的用户代码。
Note here that the script exits after the user presses Ctrl-C, then emits the captured data.
注意，当用户按Ctrl - c时退出脚本，然后发送捕获的数据。
If any user invokes a delete operation, the script exits without comparing the user IDs, thus restricting the delete operation.
如果用户调用删除操作的话，脚本就会在不和用户IDs相比较的情况下存在，因此这就限制了删除操作。
If any user invokes a delete operation, the script exits without comparing the user IDs, thus restricting the delete operation.
如果用户调用删除操作的话，脚本就会在不和用户IDs相比较的情况下存在，因此这就限制了删除操作。
应用推荐