Renaming the BMCA transaction

BMC AMI Ops Automation for CICS dynamically creates and uses transaction BMCA to perform some of its initialization. It sets up the key 9 (user key) environment for BMC AMI Ops Automation to process transient data messages issued from tasks running in key 9. If this transaction ID conflicts with a transaction ID currently running at your site, you can define a differently named transaction instead.


Related topic

Implementing-BBI-SS-PAS-to-IBM-CICS-communication

At initialization of BMC AMI OpsA in the CICS region, the transactions are searched to determine if one is defined to use program OLTSCAO9 and that transaction will be used instead of BMCA.

To specify a different transaction ID than BMCA, complete the following steps:

  1. Use CICS transaction CEDA or the CICS utility program, DFHCSDUP, to define a new transaction with the following attributes:

    DEFINE GROUP(group) TRANSACTION(tran) PROGRAM(OLTSCAO9) ISOLATE(NO) TASKDATAKEY(USER) TASKDATALOC(ANY) PRIORITY(1)

  2. If you are using CEDA, be sure to INSTALL the TRANSID before CICS connects to the PAS.

For information about security requirements for your pre-defined transaction, see Site-specific-security and substitute your pre-defined transaction ID for BMCA.

 

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