Skip to Content

Enqueue name conflicts

The FST2 transaction issues an enqueue on BMCFST2Q.applid, where applid is the CICS APPLID, when an FST2 transaction is initiated. Subsequent FST2 transactions attempt to enqueue on this name before running, and terminate if the enqueue is busy.

Related topic

General-considerations

The BCRT transaction issues an enqueue on BBK1CRTR.applid, where applid is the CICS APPLID, when the transaction is initiated. Subsequent BCRT transactions attempt to enqueue on this name before running, and terminate if the enqueue is busy.

The JNL2 transaction issues an enqueue on CMRJRNL.applid, where applid is the CICS APPLID, when the transaction starts. This enqueue exists for the life of the JNL2 task and is used to prevent additional JNL2 tasks from initializing.

Issue the CEMT INQUIRE ENQMODEL(*) command to see if there is an existing ENQ model that will include the BMC AMI Ops Monitor for CICS enqueue names. If a conflict exists, see CICS-temporary-storage-and-enqueue-name-conflicts for information about applying a zap that changes the enqueue name.


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC AMI Ops Monitor for CICS 7.4