Design of the trigger server
The design of the trigger server is similar to that of the trigger monitor,
except that the trigger server:
- Allows MQAT_CICS as well as MQAT_OS400 applications
- Calls i5/OS applications in its own job (or uses STRCICSUSR to start CICS(R) applications) rather than submitting an i5/OS job
- For CICS applications, substitutes the EnvData, for example,
to specify the CICS region, from the trigger message in the STRCICSUSR
command
- Opens the initiation queue for shared input, so that many trigger servers
can run at the same time
Note:
Programs started by AMQSERV4 must not use the MQDISC call
because this stops the trigger server. If programs started by AMQSERV4 use
the MQCONN call, they get the MQRC_ALREADY_CONNECTED reason code.