CICS applications (non-z/OS)

A non-z/OS CICS application program that issues an MQCONN or MQCONNX call must be defined to CEDA as RESIDENT. If you relink a CICS server application as a client, you risk losing sync point support.

A non-z/OS CICS application program that issues an MQCONN or MQCONNX call must be defined to CEDA as RESIDENT. To make the resident code as small as possible, we can link to a separate program to issue the MQCONN or MQCONNX call.

If the MQSERVER environment variable is used to define the client connection, it must be specified in the CICSENV.CMD file.

IBM MQ applications can be run in an IBM MQ server environment or on an IBM MQ client without changing code. However, in an IBM MQ server environment, CICS can act as sync point coordinator, and we use EXEC CICS SYNCPOINT and EXEC CICS SYNCPOINT ROLLBACK rather than MQCMIT and MQBACK. If a CICS application is simply relinked as a client, sync point support is lost. MQCMIT and MQBACK must be used for the application running on an IBM MQ MQI client.